britkat1980 / giv_tcp

TCP connection (from inverter) and MQTT implementation
71 stars 32 forks source link

EVC time out #184

Open abbottcam opened 2 months ago

abbottcam commented 2 months ago

Hello, Ive been having problems with GivTCP not connecting to my EVC. this is the message I get in the logs:

2024-04-29 18:33:46,472 - Inv1 - mqtt_client_evc - [ERROR ] - No serial_number_evc found in MQTT queue. MQTT Control not available. Traceback (most recent call last): File "/app/GivTCP_1/mqtt_client_evc.py", line 106, in client.loop_forever() File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1756, in loop_forever rc = self._loop(timeout) File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1164, in _loop rc = self.loop_read() File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 1556, in loop_read rc = self._packet_read() File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 2439, in _packet_read rc = self._packet_handle() File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 3039, in _packet_handle return self._handle_connack() File "/usr/local/lib/python3.10/site-packages/paho/mqtt/client.py", line 3138, in _handle_connack on_connect( File "/app/GivTCP_1/mqtt_client_evc.py", line 90, in on_connect client.subscribe(MQTT_Topic+"/control/"+GiV_Settings.serial_number_evc+"/#") AttributeError: type object 'GiV_Settings' has no attribute 'serial_number_evc'. Did you mean: 'serial_number'? 2024-04-29 18:35:08,905 - Inv1 - read - [CRITICAL] - Publishing Home Assistant Discovery messages 2024-04-29 18:35:13,698 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.251, 502) failed: [Errno 104] Connection reset by peer 2024-04-29 18:40:03,988 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.251, 502) failed: [Errno 104] Connection reset by peer 2024-04-29 18:40:08,628 - Inv1 - read - [CRITICAL] - Publishing Home Assistant Discovery messages 2024-04-29 18:45:07,293 - Inv1 - read - [CRITICAL] - Publishing Home Assistant Discovery messages 2024-04-29 18:45:14,309 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.251, 502) failed: [Errno 104] Connection reset by peer 2024-04-29 18:50:04,567 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.251, 502) failed: [Errno 104] Connection reset by peer 2024-04-29 18:56:00,920 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.251, 502) failed: [Errno 104] Connection reset by peer 2024-04-29 18:56:16,681 - Inv1 - write - [INFO ] - Setting battery charge rate to: 6000 (50) 2024-04-29 18:56:21,090 - Inv1 - write - [INFO ] - Setting battery charge rate 50 was a success 2024-04-29 18:56:27,512 - Inv1 - write - [INFO ] - Setting Battery Pause Mode to: Disabled 2024-04-29 18:56:29,674 - Inv1 - write - [INFO ] - Setting Battery Pause Mode to Disabled was a success 2024-04-29 18:58:59,102 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.251, 502) failed: [Errno 104] Connection reset by peer 2024-04-29 19:03:23,371 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.251, 502) failed: [Errno 104] Connection reset by peer 2024-04-29 19:16:22,137 - Inv1 - sync - [ERROR ] - Connection to (192.168.0.251, 502) failed: [Errno 104] Connection reset by peer

britkat1980 commented 1 month ago

You need to request latest beta firmware from GE, there are modbus server instability issues with current versions