deye-sun-5k-sg03lp1 causes timeout when use port 48899 and AT commands #141
Comments
|
hi @pfostenberg I implemented a change that splits register ranges longer than 0x40 into smaller chunks. Let's see if this will let the logger to respond on time. Here is a beta image containing this change. Try it out |
|
Hi, looks a litte bit better.... first call works...next timeout... Any idear? 2024-01-24 21:36:23,669 - DeyeDaemon - INFO - Reading start |
|
Hi, some more info...but not a solution... pi@bpi-js:~/git/deye-logger-at-cmd$ ./build/main -t 192.168.178.150:48899 -xmb 00430030 then pi@bpi-js:~/git/deye-logger-at-cmd$ ./build/main -t 192.168.178.150:48899 -xmb 00430040 then no read at all.... tried a second one -:) I have two in paralell -:) pi@bpi-js: some kind of protection? maybe someone has an idea. After a couple of min I can repleat... it look like there is a problem with address 70... there is a longer response... pi@bpi-js: is the logger firmware up to date? BR |
|
more testing.... pi@bpi-js:git/deye-logger-at-cmd$ ./build/main -t 192.168.178.151:48899 -xmb 00030020 can you make a try version or add a length in the config... thinks we need that for the newer one... BR Andreas |
|
There you have it. |
|
Hi, with: DEYE_LOGGER_IP_ADDRESS=192.168.178.150 Now checking the data readed... But I think the fix can be applied. Thanx... Can I support you work? log: |
|
the most values are fine..only the AC volt seems to be wrong.. Is there a easy way to change the config and run? |
Support is always welcome. There is a paypal link at the top of the README
New inverter model might require new registers mapping.
Sad to hear that. I develop it on my laptop (intel cpu) |
Describe the bug
A new deye-sun-5k-sg03lp1 ( port 8899) is closed an need to use 48899.
DEYE_LOGGER_IP_ADDRESS=192.168.x.x
DEYE_LOGGER_PORT=48899
DEYE_LOGGER_SERIAL_NUMBER=271xxxxxx
DEYE_LOGGER_PROTOCOL=at
The config and deye-inverter-mqtt work with a deye-sun-8k-sg01lp1 like a charm.
DEYE_LOGGER_IP_ADDRESS=192.168.x.x
DEYE_LOGGER_PORT=8899
DEYE_LOGGER_SERIAL_NUMBER=271051xxxx
DEYE_LOGGER_PROTOCOL=tcp
DEYE_METRIC_GROUPS=deye_hybrid,deye_hybrid_battery
but when used with the sg03lp1 it stops when reading more than 0x40 bytes.
To Reproduce
Steps to reproduce the behavior:
use the actual ( 1/2024) deye inverter.
start the docker image with config below.
sudo docker run --name deye-mqtt --env-file config.env ghcr.io/kbialek/deye-inverter-mqtt
2024-01-22 23:02:58,884 - DeyeDaemon - INFO - Please help me build the list of compatible inverters. #41
2024-01-22 23:02:58,884 - DeyeConnectorFactory - INFO - Creating Modbus/AT Logger connector
2024-01-22 23:02:58,921 - paho.mqtt.client - DEBUG - Sending CONNECT (u1, p1, wr1, wq1, wf1, c1, k60) client_id=b'deye-inverter-2799381840'
2024-01-22 23:02:58,923 - paho.mqtt.client - DEBUG - Received CONNACK (0, 0)
2024-01-22 23:02:59,924 - paho.mqtt.client - DEBUG - Sending PUBLISH (d0, q1, r1, m1), 'b'deye1/status'', ... (6 bytes)
2024-01-22 23:02:59,925 - DeyeMqttClient - INFO - Successfully connected to MQTT Broker located at 192.168.178.128:1883
2024-01-22 23:02:59,926 - DeyeDaemon - INFO - Feature "Report metrics over MQTT": enabled
2024-01-22 23:02:59,927 - DeyeDaemon - INFO - Feature "Set inverter time once online": disabled
2024-01-22 23:02:59,927 - DeyeDaemon - INFO - Feature "Time-of-use configuration over MQTT": disabled
2024-01-22 23:02:59,928 - DeyeDaemon - DEBUG - Start to execute the daemon at intervals of 60 seconds
2024-01-22 23:02:59,930 - paho.mqtt.client - DEBUG - Received PUBACK (Mid: 1)
2024-01-22 23:02:59,932 - DeyeDaemon - INFO - Reading start
2024-01-22 23:02:59,933 - DeyeDaemon - INFO - Reading registers [metrics group: deye_hybrid_battery, range: 0003-0070]
2024-01-22 23:02:59,934 - DeyeAtConnector - DEBUG - Sending AT command: b'WIFIKIT-214028-READ'
2024-01-22 23:03:00,035 - DeyeAtConnector - DEBUG - Received AT response in 1. attempt: b'192.168.178.150,402A8F39E514,2799381839'
2024-01-22 23:03:00,036 - DeyeAtConnector - DEBUG - Sending AT command: b'+ok'
2024-01-22 23:03:00,137 - DeyeAtConnector - DEBUG - Sending AT command: b'AT+INVDATA=8,01030003006e3
-> Timeout starts.
check with deye-logger-at-cmd -> same.
main -t 192.168.178.128:48899 -xmb 00030070
pi@raspberrypi:
/git/deye-logger-at-cmd $ ./build/main -t 192.168.178.150:48899 -xmb 00030040/git/deye-logger-at-cmd $ ./build/main -t 192.168.178.150:48899 -xmb 000300702024/01/23 00:13:41 * Connecting :0 -> 192.168.178.150:48899...
2024/01/23 00:13:46 +ok=01038032333130323532313839000081020000151500003385C3650000C35000000201000000FF000A180117000B3100011388051400000000000000000000000000FF07D016760000000003E8FFFF000000000001000000010000000000000000C350000000001964000000000000000100010002000000FA000003E00000010E03B6F011
2024/01/23 00:13:47
pi@raspberrypi:
2024/01/23 00:13:52 * Connecting :0 -> 192.168.178.150:48899...
2024/01/23 00:13:58 read udp 192.168.178.128:34164->192.168.178.150:48899: i/o timeout
Expected behavior
if this a bug in this tool? the logger? or my mistake?
or does a workarround help ( reduce the big call with 1..2 shorter one)
Hardware (please complete the following information):
Software (please complete the following information):
DEYE_LOGGER_IP_ADDRESS=192.168.178.150
DEYE_LOGGER_PORT=48899
DEYE_LOGGER_SERIAL_NUMBER=2799381840
DEYE_LOGGER_PROTOCOL=at
MQTT_HOST=192.168.178.128
MQTT_PORT=1883
MQTT_USERNAME=xxx
MQTT_PASSWORD=xxx
MQTT_TOPIC_PREFIX=deye2
DEYE_METRIC_GROUPS=deye_hybrid,deye_hybrid_battery
The text was updated successfully, but these errors were encountered: