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
+8-1Lines changed: 8 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,14 @@ List of confirmed working go-eCharger Firmware versions with this integration:
24
24
- 57.0 & 57.1
25
25
- 56.2 - 56.11
26
26
- 055.0, 055.5, 055.7, 055.8
27
-
27
+
28
+
#### Firmware update note (April 2026)
29
+
Since you must use the go-eApp to update the go-eCharger firmware, it can happen that the mobile App and the Integration start some sort of race condition concerning the use of the websocket connection.
30
+
31
+
**To avoid any issues, when you want to update the go-eCharger firmware, it's recommended to pause the HA integration while you’re going to upgrade the firmware via the go-eApp.**
32
+
33
+
At least that was the case for me when updating from 60.3 to 60.4. I did not notice any similar issues with any firmware updates before.
34
+
28
35
### go-eController Firmware Versions
29
36
30
37
List of confirmed working go-eController Firmware versions with this integration:
0 commit comments