You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-1Lines changed: 2 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,8 @@ This custom integration for Home Assistant sends commands to the ECU to retreive
20
20
- Added individual Inverter Online sensors for automations
21
21
- Ability to enable Zero Export (ECU-C and ECU-3)
22
22
- Limit maximum Power of each panel (ECU-R-Pro, ECU-C, ECU-3)
23
-
- dBm expression for Zigbee Signal Strength, ideally between -10dBm (best signal) and -70dBm (worst signal)
23
+
- dBm expression for Zigbee Signal Strength, ideally between -10dBm (best signal) and -29dBm (worst signal).
24
+
24
25
> [!CAUTION]
25
26
> - ECU entities are not migrated from the predecessor of this integration (https://github.com/ksheumaker) because the ECU-ID is now part of the ECU specific entities to enable the use of multiple ECU's.
26
27
> - Inverter entities have remained the same, except for the Zigbee signal (this unit is converted from % to dBm). To avoid duplication of inverter entities ("inverter_408000123456_power_ch_1" becomes two entities: "inverter_408000123456_power_ch_1" and "inverter_408000123456_power_ch_1-1") you have to completely remove the old integration and reboot before activating the new one. The old entities are then first removed and later added again without losing historical data. Always use the UI to remove an integration.
0 commit comments