Closed d-eggert closed 6 months ago
Hi @d-eggert,
client_example.py
is just that, an example. You'll need to amend the Modbus registers to suit your own specific inverter. (As it happens, it contains valid Modbus registers for a Solis Hybrid inverter, as that is what I have myself).
Based on the DEBUG logs you've posted above, you sent a Modbus RTU request of 01 04 80 fe 00 06 38 38
(I've decoded it below using this tool) and received an invalid response from the inverter of 05 00
. Based on this, pysolarmanv5
appears to be functioning as per spec.
Cheers, Jon
Part of Data Package | Description | Value |
---|---|---|
01 | Slave address | 0x01 (1) |
04 | Function code | 0x04 (4) - Read Input Registers |
80 FE | Starting address | Physical: 0x80FE (33022) Logical: 0x80FF (33023) |
00 06 | Quantity | 0x0006 (6) |
38 38 | CRC | 0x3838 (14392) |
I setup the all-in-one deye solution DEYE-AI-W5.1-12P3-EU-ESS (LV). It also included a wifi datalogger for solarman. So I tried to integrate it into homeassistant via the solarman HACS integration. While the entities are created, the values are not updated.
After some research I ended up in this repo and tried the
solarman_scan.py
util, which successfully found the data logger. I also ran theclient_example.py
but got the following traceback:Looks somewhat similar to #18 . Is there a chance we get this fixed? I'm happy to assisst.