1
0
Fork 0
mirror of https://github.com/Zendure/Zendure-HA.git synced 2025-12-15 17:08:19 +01:00
3 Function description
harrymayr edited this page 2025-11-24 22:43:20 +01:00

Zendure Manager

The target of the manager is to keep the P1 sensor at 0W by controlling the in- and output power of the devices (Smart Matching, Smart charge/discharge). There are several modes available

  • OFF: In this mode, the manager does not controll the devices. This is usefull if you want to use HEMS or another energy-program in the App, or implementing your own strategy to control the device by using the AC-mode and the entities inputLimit and outputLimit. These are the same controls as in the page On-grid setting in the App.

If the Zendure manager is set to any other mode, he will control the device by sending http or MQTT commands to the devices. If there is HEMS or another energy-program enabled in the App, unpredictable behavior will happen, because the Zendure Manager and the App will compete against each other!

The next release will take at least HEMS into account and will disregard a device, where HEMS is enabled. But the effect on the P1 sensor of the HEMS enabled device will be taken into account. i.e. if HEMS load a device via AC with 200W, P1 will see that, and the manager will try to compensate (depending on the mode) and may unload another device to load the HEMS controlled device.

The manager controls some devices (SF 800 pro, SF 2400AC) via AC mode and the inputLimit and outputLimit entities. Manual changes to these entities are therefore immediately overridden by the manager. For other devices, such as the Hyper 2000 or the Hub family, these entities do not affect the behavior of the inputs and outputs. However, if you disable the manager, the settings of the AC mode and the inputLimit and outputLimit entities will be applied.

The power for the single devices will be distributed according to their fusegroup setting. And it's necessary to select at least Device has its own circuit or phase otherwise not smart function is possible.

  • Manual Power In this mode a constant value will be put or taken into the grid. The amount can be set with the Manual Power entity. A negative value will charge the battery (if the device support AC loading), a positive value will unload the battery. The value control the AC in- output, not the power in- or out of the battery. In case you have connected PV panels to your device, any solarpower higher than the demanded power, will load the battery (with positive Manual Power). If the battery is full, than the power feed into grid may exceed the Manual Power depending on you bypass (gridReverse) setting

  • Smart Matching In this mode, the manager tries to keep the P1 sensor at 0W as long there is battery-capacity to fulfill the needs. As stated earlier, the power of multiple devices will be distributed according the fuse-group settings and depending on the SoC level within the fuse group. When a device switches to bypass mode, the excess power is used to charge other AC-capable devices.

  • Smart discharge only This mode is smilar to Smart Matching, but allows only discharge of the devices. This will not affect the solarInputPower of attached PV panels, any excess power will load the battery, but devices wich are used with AC load/unload only are not charged.

  • Smart charge only Also similar to Smart Matching, but allows only chargeing of the devices. Also more useful for AC load/unload only devices to charge them over the day, to have energy for the night. This helps also on strongly switching scenarios i.e. a stove which need more power than solarpower is available, that there is no frequent charge/discharge of the battery.