I'm struggling to get GivTCP 3 working on my fairly standard setup:
Home Assistant OS (latest 2024.10.x)
Raspberry Pi 4 - 1GB RAM, 32GB microSD
Using WiFi (although makes no difference if ethernet is used)
GivEnergy AIO, Gateway, AC3 and EVC
I've tried the latest beta (3.0.4) and dev (3.0.23) and both have the same issue. The problem has been there for all versions since the /23 fix was applied.
The problem:
Beta: Start the GivTCP add-on, it takes a couple of minutes to boot up, the logs suggest it is detecting my inverters and then all of a sudden I lose connectivity to Home Assistant because it appears to have restarted itself and the add-on is now stopped.
Dev: Start the GivTCP add-on, it seems to get further but eventually everything freezes and Home Assistant is inaccessible until I power cycle the Pi.
This is on a clean installation of Home Assistant. I've tried flashing it from scratch a couple of times just to be certain.
Here's the startup log for the beta:
2024-10-08 14:40:35,432 - startup - [INFO] - ==================== STARTING GivTCP==========================
2024-10-08 14:40:35,493 - startup - [INFO] - Network Found: 192.168.0.1/23
2024-10-08 14:40:37,507 - startup - [INFO] - Searching for Inverters
2024-10-08 14:40:37,508 - startup - [INFO] - Scanning network for GivEnergy Devices...
2024-10-08 14:40:42,659 - startup - [INFO] - INV- Scanning network (1):192.168.0.1/23
2024-10-08 14:41:06,401 - client - [INFO] - Connection established to 192.168.1.62:8899
2024-10-08 14:41:06,404 - client - [INFO] - Detecting plant
2024-10-08 14:41:07,653 - client - [INFO] - Plant Detected
2024-10-08 14:41:10,414 - startup - [INFO] - Inverter CE2122G257 which is a Gen1 - Ac with 1 batteries has been found at: 192.168.1.62
2024-10-08 14:41:10,423 - client - [INFO] - Connection established to 192.168.1.81:8899
2024-10-08 14:41:10,424 - client - [INFO] - Detecting plant
Here's the startup log for the latest dev version:
But... and this is where it's getting really confusing - sometimes the beta/dev versions will actually get further and then just crash out stopping the container, but leaving HA all alone. Here's a boot-up log from that scenario:
I can't find a consistent reproducable single thing to debug. I think there may be multiple issues here but separating them out is tricky. I have Glances installed to keep an eye on the Pi hardware in case there's anything obvious there but nothing is jumping out.
So far my testing seems to suggest that if I clear out all of the GivTCP files in the GivTCP folder, then the first run of etiher container after that causes HA to restart or crash. If I then start up the add-on again but leave the previously created GivTCP files in place then I get the KeyError.
Please let me know what diagnostics you'd like me to produce in order to try and get to the bottom of the issue, maybe we stick with one specific release (dev or beta). I would have asked on the Facebook chat but I'm finding that tricky to keep track of who is saying what to who on there so thought it would be more sensible to raise the issue on here instead.
I'm struggling to get GivTCP 3 working on my fairly standard setup:
I've tried the latest beta (3.0.4) and dev (3.0.23) and both have the same issue. The problem has been there for all versions since the /23 fix was applied.
The problem:
This is on a clean installation of Home Assistant. I've tried flashing it from scratch a couple of times just to be certain.
Here's the startup log for the beta:
Here's the startup log for the latest dev version:
But... and this is where it's getting really confusing - sometimes the beta/dev versions will actually get further and then just crash out stopping the container, but leaving HA all alone. Here's a boot-up log from that scenario:
I can't find a consistent reproducable single thing to debug. I think there may be multiple issues here but separating them out is tricky. I have Glances installed to keep an eye on the Pi hardware in case there's anything obvious there but nothing is jumping out. So far my testing seems to suggest that if I clear out all of the GivTCP files in the GivTCP folder, then the first run of etiher container after that causes HA to restart or crash. If I then start up the add-on again but leave the previously created GivTCP files in place then I get the KeyError.
Please let me know what diagnostics you'd like me to produce in order to try and get to the bottom of the issue, maybe we stick with one specific release (dev or beta). I would have asked on the Facebook chat but I'm finding that tricky to keep track of who is saying what to who on there so thought it would be more sensible to raise the issue on here instead.