search

britkat1980 / giv_tcp

TCP connection (from inverter) and MQTT implementation
78 stars 37 forks source link

v2.3.3 SoC target set failure and multiple inverter sync/read errors #105

Closed Yorkie71 closed 1 day ago

Yorkie71 commented 1 year ago

The Palm SoC function has been working great until recently but the last three days or so, it's failed to set the SoC logging the following error.

2023-08-09 23:20:14,712 - Inv1 - palm_soc    -  [INFO    ] - Overmorrow correction not needed/applied
2023-08-09 23:20:14,713 - Inv1 - palm_soc    -  [INFO    ] - SoC Calc Summary;         Max Charge Min Charge      Max %      Min % Target SoC
2023-08-09 23:20:14,713 - Inv1 - palm_soc    -  [INFO    ] - SoC Calc Summary;               5.04      -5.36         26        -55         80
2023-08-09 23:20:14,714 - Inv1 - palm_soc    -  [INFO    ] - SoC (Adjusted);                 5.04      -5.36        106         25          
2023-08-09 23:20:14,715 - Inv1 - palm_soc    -  [CRITICAL] - Sending calculated SoC to inverter: 80
Min & max -74 4
Min & max -53 26.0
Min & max -49 114
Min & max -55 26
2023-08-09 23:20:15,569 - Inv1 - write       -  [INFO    ] - Setting Charge Target to: 80
2023-08-09 23:20:16,427 - Inv1 - write       -  [INFO    ] - Setting Charge Target 80 failed: (<class 'AssertionError'>, AssertionError('Unexpected response from remote end: Modbus Error: [Input/Output] No Response received from the remote unit/Unable to decode response'), <traceback object at 0x7fa8cabdc0>)

I can't be certain, but it was working fine before the recent HAOS and Supervisor updates. Interestingly, if I set the SoC manually via the slider in GivTCP the log reports a success.

2023-08-09 23:38:08,581 - Inv1 - write       -  [INFO    ] - Setting Charge Target to: 79
2023-08-09 23:38:10,971 - Inv1 - write       -  [INFO    ] - Setting Charge Target 79 was a success
2023-08-09 23:38:36,380 - Inv1 - write       -  [INFO    ] - Setting Charge Target to: 73
2023-08-09 23:38:38,672 - Inv1 - write       -  [INFO    ] - Setting Charge Target 73 was a success
2023-08-09 23:38:44,029 - Inv1 - write       -  [INFO    ] - Setting Charge Target to: 75
2023-08-09 23:38:46,344 - Inv1 - write       -  [INFO    ] - Setting Charge Target 75 was a success

Also, and perhaps unrelated, there are a number of inverter timeout and sync errors which are not unusual, (I have the poll set to 15s) but I can't recall seeing the battery object error in the past.

2023-08-10 00:42:28,050 - Inv1 - sync        -  [ERROR   ] - Connection to (192.168.1.117, 8899) failed: timed out
2023-08-10 01:18:39,766 - Inv1 - sync        -  [ERROR   ] - Connection to (192.168.1.117, 8899) failed: timed out
2023-08-10 02:06:18,167 - Inv1 - read        -  [ERROR   ] - Battery Object empty so skipping
2023-08-10 02:33:46,505 - Inv1 - sync        -  [ERROR   ] - Connection to (192.168.1.117, 8899) failed: timed out
2023-08-10 05:03:27,373 - Inv1 - sync        -  [ERROR   ] - Connection to (192.168.1.117, 8899) failed: timed out
2023-08-10 05:12:26,603 - Inv1 - read        -  [ERROR   ] - Battery Object empty so skipping
2023-08-10 05:31:43,003 - Inv1 - sync        -  [ERROR   ] - Connection to (192.168.1.117, 8899) failed: timed out
2023-08-10 05:33:07,572 - Inv1 - write       -  [INFO    ] - Setting dayRate via external trigger
2023-08-10 05:53:35,403 - Inv1 - sync        -  [ERROR   ] - Connection to (192.168.1.117, 8899) failed: timed out
2023-08-10 06:03:59,317 - Inv1 - sync        -  [ERROR   ] - Connection to (192.168.1.117, 8899) failed: timed out
2023-08-10 06:05:05,381 - Inv1 - sync        -  [ERROR   ] - Connection to (192.168.1.117, 8899) failed: timed out
2023-08-10 06:27:23,205 - Inv1 - sync        -  [ERROR   ] - Connection to (192.168.1.117, 8899) failed: timed out
2023-08-10 07:18:13,654 - Inv1 - read        -  [ERROR   ] - Battery Object empty so skipping

Hopefully this makes sense. This is a great addon BTW. Thanks for the hard work in maintaining this.