New firmware not work #123
Comments
|
Thanks for reporting the problem @Joerglp . It seems like something has changed in version 2 of the firmware. Could you enable DEBUG logs, and try again, so we can see what is returned by the logger? |
|
2023-09-08 04:56:49,420 - DeyeDaemon - INFO - Reading start2023-09-08 04:56:49,421 - DeyeDaemon - INFO - Reading registers [metrics group: micro, range: 003c-0074]2023-09-08 04:56:51,237 - DeyeConnector - DEBUG - Request frame: a5170010450000e0bf1dfa0200000000000000000000000000000103003c003945d4b6152023-09-08 04:56:51,748 - paho.mqtt.client - DEBUG - Sending PINGREQ2023-09-08 04:56:51,749 - paho.mqtt.client - DEBUG - Received PINGRESP2023-09-08 04:56:52,033 - DeyeConnector - DEBUG - Received response frame in 1. attempt: 41542b595a434d505645523d4d57335f3136555f353430365f322e30360d0a0d0a2023-09-08 04:56:52,033 - DeyeModbus - ERROR - Response frame has invalid starting byte2023-09-08 04:56:52,034 - DeyeMqttClient - DEBUG - Publishing message. topic: 'deye/logger_status', value: 'offline'2023-09-08 04:56:52,034 - paho.mqtt.client - DEBUG - Sending PUBLISH (d0, q1, r0, m19), 'b'deye/logger_status'', ... (7 bytes)2023-09-08 04:56:52,035 - paho.mqtt.client - DEBUG - Received PUBACK (Mid: 19)2023-09-08 04:56:52,036 - DeyeMqttClient - INFO - Logger is offline2023-09-08 04:56:52,037 - DeyeDaemon - INFO - Reading completedVon meinem iPad gesendetAm 07.09.2023 um 21:39 schrieb Krzysztof Białek ***@***.***>:
Thanks for reporting the problem @Joerglp . It seems like something has changed in version 2 of the firmware. Could you enable DEBUG logs, and try again, so we can see what is returned by the logger?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
The response "41542b595a434d505645523d4d57335f3136555f353430365f322e30360d0a0d0a" is a hex encoded ascii string. After conversion it looks like this "AT+YZCMPVER=MW3_16U_5406_2.06", so it's a response from the AT command interface. Possible options:
EDIT: |
|
I cannot see any option to enable Modbus/TCP even in the config_hide.html. |
|
Okay, perhaps Modbus/TCP interface has been moved to another TCP port. Can you scan your inverter IP with |
|
No other open port on the inverter. |
|
I can see the Entry Server and Port 8899 in the config_hide.html. |
|
Per Telnet: ����B����X#��&����2211236711�� |
|
The big problem is, that the new SUN-MI-RELAY-01 is automatically updating the inverter to firmware version 2.27. So most of the users will have this problem in the near future. |
|
Maybe these settings are helping to analyse? |
|
@Joerglp @SMCerina Could you please check if the AT interface works with the new firmware as before? If yes, then there is a chance to use for Modbus-over-AT communication. Here are the results I got from my logger running firmware v1
|
|
@carstenfroehlich What are the options available here? |
|
TCP-Server |
Exactly the same options as for my logger running on firmware v1 |
|
maybe the values of the options have changed? |
|
./main -t 192.168.0.71:48899 |
|
@Joerglp Thanks. This looks very promising. |
|
this is from my server: go run main.go -t 192.168.178.108:48899 go run main.go -t 192.168.178.108:48899 -xmb 00280001 |
|
does this help? |
|
Your tests proven, that it's possible to use Modbus-over-AT to read the data. I've started working on that feature. Stay tuned. |
|
It actually works with https://github.com/jedie/inverter-connect via Modbus over AT (SUN-600G3 with 2.27)
|
|
Here is a beta image that uses AT commands for communication with the inverter exclusively. The implementation is very hacky now. Primarily error handling is very poor. However it's ready to start collecting feedback. No extra config changes are necessary. |
|
Now I became that: |
|
With the tool from @maehtricks works InverterInfo(ip='192.168.0.71', mac='E8FDF88E20F6', serial=4196253664) Fetch...PV1 Voltage,PV2 Voltage,PV1 Current,PV2 Current,Daily Production,Daily Production 1,Daily Production 2,Total Production,Total Production 1,Total Production 2,Active Power Regulations,PV1 Power,PV2 Power,Total Power, ──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────── |
|
seems it is not working |
|
Thanks for the logs. They are very helpful. I see where the problem is. My logger appends trailing zeros to the Modbus response. You can see it here #123 (comment) I'm talking about this "+ok=01030204423AB50000" Here is a new, fixed docker image |
|
Thanks a lot. |
|
I would also like to say a big thank you for your quick work. Update has been installed, but we won't see the result until tomorrow morning. It's hard for me to stand on the carport roof with a headlight and illuminate the solar panel... |
|
@Joerglp @carstenfroehlich Here is a new docker image with another bugfix |
|
Maybe I am doing something absolutely wrong, but I have pulled the third patch and restarted my docker container. I have also tried to rebuild the container with the no-cache option without any other result |
|
@carstenfroehlich Pulling is not enough. This image is not tagged as |
OK, thanks, I have to read about this a bit. Until now I always checked out a branch, restart my container and it works. I have currently no idea where to find this docker run configuration. Do you mean the docker compose file? |
|
@carstenfroehlich If you use docker-compose - then yes, you should reference the image like this |
|
Hello, thank. |
|
Hi, |
This is strange. My changes have nothing to do with metrics processing. Perhaps there was an unhandled communication error with the logger, which caused that. Please collect more logs. Nice. It's working for me too. Let's run it for one more day to see if it's stable enough. |
|
Here is another docker image Before using it, you have to update your configuration
For more info read this https://github.com/kbialek/deye-inverter-mqtt/tree/feature/at-interface#installation @carstenfroehlich Please check if it also resolves your problem with influx integration. |
|
sorry, but there seems to be an error in logging Error setting up logging: int() argument must be a string, a bytes-like object or a real number, not 'NoneType' |
|
The problems in influx integration are not solved. |
|
The beta 4 image is working for me. Thank you for your quick support. |
|
@carstenfroehlich Share debug logs and your config.env |
|
@kbialek this is my config.env: MQTT_HOST=192.168.178.113 LOG_LEVEL=DEBUG this is my whole debug log from this container: docker logs deye-inverter-mqtt_deye-mqtt_1 Error setting up logging: int() argument must be a string, a bytes-like object or a real number, not 'NoneType' The error is the only entry in the log, once per minute the result then is, that in MQTT Data no topic deye is existing: |
|
@carstenfroehlich I'm pretty much confident that you are still running the EDIT: |
|
@kbialek |
|
@Joerglp Thanks. Could you please test beta-4 too? Instructions are here #123 (comment) |
you are totally right, sorry for the confusion. 2023-09-10 18:46:17,870 - DeyeDaemon - INFO - Please help me build the list of compatible inverters. #41 Looks good! |
|
@kbialek beta4 ist deployed. I'll see if it's working during the day. Edit: |
|
Now the inverter seems to be damaged... The external relay has worked for one day. Now the inverter shows a permanent red light. So poorly I'm out for testing... |
|
Everything is still going great for me. |
|
It's been working for me without crashes so far |
|
Same for me. It seems like the implementation is good enough. |
|
The latest beta before the release |
|
Ok! Is deployed. What was changed? Ich give answer tomorrow. |
|
I've merged this #125 |
Hardware (please complete the following information):
Software (please complete the following information):
LOG_LEVEL=INFO
LOG_STREAM=STDOUT
DEYE_DATA_READ_INTERVAL=60
DEYE_METRIC_GROUPS=micro
DEYE_LOGGER_SERIAL_NUMBER=4196253664
DEYE_LOGGER_IP_ADDRESS=192.168.0.71
DEYE_LOGGER_PORT=8899
DEYE_FEATURE_MQTT_PUBLISHER=true
DEYE_FEATURE_SET_TIME=true
MQTT_HOST=192.168.0.101
MQTT_PORT=1883
MQTT_USERNAME=mqttuser
MQTT_PASSWORD=#######ä
MQTT_TOPIC_PREFIX=deye
PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
LANG=C.UTF-8
GPG_KEY=A035C8C19219BA821ECEA86B64E628F8D684696D
PYTHON_VERSION=3.10.10
PYTHON_PIP_VERSION=22.3.1
PYTHON_SETUPTOOLS_VERSION=65.5.1
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/d5cb0afaf23b8520f1bbcfed521017b4a95f5c01/public/get-pip.py
PYTHON_GET_PIP_SHA256=394be00f13fa1b9aaa47e911bdb59a09c3b2986472130f30aa0bfaf7f3980637
Error:
2023-09-07 15:33:49,329 - DeyeDaemon - INFO - Reading start
2023-09-07 15:33:49,329 - DeyeDaemon - INFO - Reading registers [metrics group: micro, range: 003c-0074]
2023-09-07 15:33:49,469 - DeyeModbus - ERROR - Response frame has invalid starting byte
2023-09-07 15:33:49,470 - DeyeMqttClient - INFO - Logger is offline
With Firmware 1.57 ist o.k.
Now with the new Firmware are not o.k.
The text was updated successfully, but these errors were encountered: