Closed WPluim closed 6 years ago
No problem.
MQTT connection works. You confirmed that. Great. Next thing is if you are listening to the correct MQTT topics. The topics are:
Excellent! I set it to DEBUG earlier this afternoon. I could not learn much from the output. It says: 2018-04-09 15:56:43,997 run(56) - INFO: Connected to MQTT 192.168.0.101 2018-04-09 15:56:44,001 resetWait(215) - DEBUG: Wait 0 minutes before next device poll 2018-04-09 15:56:44,050 resetUSBDevice(231) - DEBUG: Found GoodWe Inverter at /dev/hidraw0 2018-04-09 15:56:44,113 openDevice(272) - DEBUG: Connected to /dev/hidraw0 2018-04-09 15:56:44,215 sendData(325) - DEBUG: Sending data to inverter: 0xcc 0x99 0x9 0xaa 0x55 0x80 0xb 0x0 0x2 0x0 0x1 0x8c 2018-04-09 15:56:45,318 sendDiscovery(605) - DEBUG: Sending discovery 2018-04-09 15:56:45,319 sendData(325) - DEBUG: Sending data to inverter: 0xcc 0x99 0x9 0xaa 0x55 0x80 0x7f 0x0 0x0 0x0 0x1 0xfe 2018-04-09 15:56:54,257 handle(655) - DEBUG: State machine time-out. Last state: 3 2018-04-09 15:56:54,258 resetWait(215) - DEBUG: Wait 0 minutes before next device poll 2018-04-09 15:56:54,288 resetUSBDevice(231) - DEBUG: Found GoodWe Inverter at /dev/hidraw0 2018-04-09 15:56:54,353 openDevice(272) - DEBUG: Connected to /dev/hidraw0 2018-04-09 15:56:54,455 sendData(325) - DEBUG: Sending data to inverter: 0xcc 0x99 0x9 0xaa 0x55 0x80 0xb 0x0 0x2 0x0 0x1 0x8c 2018-04-09 15:56:55,559 sendDiscovery(605) - DEBUG: Sending discovery 2018-04-09 15:56:55,559 sendData(325) - DEBUG: Sending data to inverter: 0xcc 0x99 0x9 0xaa 0x55 0x80 0x7f 0x0 0x0 0x0 0x1 0xfe 2018-04-09 15:57:04,498 handle(655) - DEBUG: State machine time-out. Last state: 3
The Solar inverter is not sending any data at all. It issues the Discovery command by sending the bytes 0xcc 0x99 0x9 0xaa 0x55 0x80 0x7f 0x0 0x0 0x0 0x1 0xfe. A confirmation should be replied by the inverter. The state machine keeps trying to Discover your device on the USB port. The device itself is not reporting anything back. How long have you kept it running in this state? What type of inverter do you have? I know that some GoodWe inverters only work using USB when the WiFi module has been disconnected.
Ik ran it two times for about three minutes. Tomorrow I could do that for one hour, several times if necessary. The Inverter is the Gw-4000SS. Indeed it is sending on the WiFi. I hoped I could have it (the data) both ways. That seems to be difficult though. I choose your GoodWeUSBLogger solution, because I did not want to open the Inverter at all. Quarantee-issues etc.
The fact that there is no data coming from the device itself could be related to the WiFi module. You could also try to verify if it is supposed to be working by connecting a laptop (Windows) to the inverter and run the EzExplorer application of GoodWe. If you have trouble finding that tool, please drop me a private message with your mail address and i will send it to you by WeTransfer.
Well, my finding this afternoon are:
Seems the whole USB connectivity is disabled/broken on your inverter. Sorry, but at that point I'm unable to assist.
Hi! Bij GoodWe kwam ik ook niet meer verder. Dus maar Google geraadpleegd. Zeer interessant: www.youless.nlVoor € 100 P1 en panelen monitoren met slechts één luciferdoosje! Op 11 apr. 2018 7:46 p.m. schreef Arjen notifications@github.com:Closed #7.
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
Hi Arjen, Sorry to be back, but there we go. I can see the GoodWeUSBLogger making contact with the MQTT-broker. That is when I subribe to the item '$SYS/broker/clients/total'. The number goes up from 1 to 2 after I give the command (sudo python ./GoodWeUSBLogger.py start) on the Pi connected to the inverter (in the attic). The Pi that I want to get reading the data is near the P1-meter (downstairs). No matter what I try, like subscribing to: