Thanks again for all the feedback!!
New/updated in pre19
- Fixed a typo in the code which prevented the Integration from starting 😢
- Take into account the gridOffPower of the SF800Pro and SF2400
- Fix power distribution issue with socLimit
- Fix error calculating Available Energy at startup
- Lost the 0.5 kWh switch in the last update
New/updated in pre18
- Each device, and the ZendureManager now have an entity Available Energy in kWh, which is adjusted for the minSoc. This value might be helpful in automations.
- The power distribution has proven to be quite difficult. I spend a lot of time testing it, with different Fuse Group configurations, and with charding and discharging, and it seems to work, at least for me 😉
- When a device is 'auto calibrated' (see socStatus) it is not responding to commands. This now taken into account
Rename Cluster to FuseGroup
One drastic change is the rename of "device cluster" to "Fuse Group". The name 'cluster' was already been used by Zendure for a Hyper2000 zenCluster. Also a lot of new users did not know what to do with it, and it is, out of safety reasons, quite important. In each country there are rules on how you are allowed to 'use' the device. If you want to feed more into the grid, tahn the standard 800w you have to sign-off in the ZendureApp. The name 'FuseGroup' means that you have to add alll the devices which are on the 'same fuse', to a group. Because depending on the 'fuse' you are allowed a specific maximum load. Which probably is also different per country!
So if you have a fuse, which is not dedicated for your device, you should use "FuseGroup max. 800w". If you have more than one device on the same fuse, you should add them to the same group, and the Zendure Manager will make sure that all the devices in the same group, do never feed more than 800w into the grid. Depending on your country, you can choose Fuse Groups of 800, 1200, 2400 or 3600w. An example looks like this:
If you have a device with a dedicated fuse, you can select: "Device has its own circuit or phase" in which case no other devices can be added. It is important that out of safety regulations, you must select the correct configuration. Since this is your responsibility, the initial value for the fuse group is: "Unused, device has No FuseGroup". In this case the device is not used for the smart matching!!
Also if a device is in HEMS mode, the smart mode cannot use it. Therefore I have replaced the 'online'entity with "connection status" which can have the following values:
- unknown
- connected
- HEMS
- No FuseGroup
Power distribution
Some issues were reported on the power distribution which are hopefully fixed in this release
- Clip output/input to the FuseGroup
- Wrong calculation if the P1 power value was bigger than the maximum available device power
- Fixed an error when socLimit was not available
Other issues
- An initial version of a new sensor is added, which counts the number of switches of the inverter between idle, charging and discharging
- Fixed an issue with MQTT json load