Released 31/05/2023 - Previous version 3.051
V5.162 released 01/06/2023
V5.166 released 14/06/2023
V5.168 released 24/06/2023
Please note this firmware release only applies to the original eddi.
These eddis have a serial number starting with a "1"
It does not apply to the version of eddi with the built in WiFi/Ethernet.
This firmware now supports the myenergi libbi battery and includes some improvements to load control and other general bug fixes and improvements.
Full details of the v5 firmware are available at: V5 Firmware - What's new?
Important - when updating to V5 firmware it is important that all zappis and eddis are also updated to V5 so that they can continue to work together. Please see this article for full instructions on how to update your hub, eddi and zappi
---> V5 firmware update - full instructions <--
5.162 - Hotfix 01/06/2023
- Further improvements to third party battery support
- Resolves bug with "Grid CT Lost" appearing incorrectly
- Removes oscillations in the eddi output particularly when device limit is set
5.166 - Bug Fix 14/06/2023
- Load Control Phase Rotation fixes for internal load CTs - handles bugs identified if the three phase zappi is not wired L1 - L2 - L3
- If no Grid CT's are setup in the network then the Grid CT Lost feature is disabled.
5.168 - Bug Fix 24/06/2023
-
Response delay improvement for export threshold when diverting.
-
Improvements to export control when generation power is low. Eddi now performs more reliably when surplus is less than 300W.
-
Export threshold. Re-introduction of the export threshold feature into (new load control) and response delay on eddi.
-
Eddi (non-master) in stop mode would still be allocated power from the master device. Eddi now correctly reports its max load as 0W when in stop mode.
Comments
2 comments
Since updating to this my eddi keepings overheating. How can I rollboack to the previous version. This worked perfect for me
Since these updates my Eddi seems to have stopped adding up the total savings.
That is…..under the Savings menus, the value of ‘ALL:’ has remained stationary. While all values given for ‘This Week, Month, Year’ etc. look to be reporting fine.
Is this a known bug??
Please sign in to leave a comment.