home_assistant_solarman: Querying [3 - 128] failed with exception [IllegalDataValueError]
Hi,
I have a few microinverters which used to work with the 2mptt yaml file. Since a few days they no longer work and provide the following error:
2023-08-13 17:10:37.318 DEBUG (SyncWorker_2) [pysolarmanv5.pysolarmanv5] Socket setup completed... <socket.socket fd=27, family=2, type=1, proto=6, laddr=('192.168.xxx.yyy', 60194), raddr=('192.168.yyy.zzz', 8899)> 2023-08-13 17:10:37.318 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.321 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [5] retry attempts left 2023-08-13 17:10:37.323 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.325 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [4] retry attempts left 2023-08-13 17:10:37.327 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.329 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [3] retry attempts left 2023-08-13 17:10:37.331 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.332 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [2] retry attempts left 2023-08-13 17:10:37.333 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.336 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [1] retry attempts left 2023-08-13 17:10:37.338 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed with exception [IllegalDataValueError] 2023-08-13 17:10:37.339 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying [3 - 128] failed, [0] retry attempts left 2023-08-13 17:10:37.340 WARNING (SyncWorker_2) [custom_components.solarman.solarman] Querying registers [3 - 128] failed, aborting
I really haven’t a clue where to start looking. I updated to the latest ‘Main’. (I was back an x-number of versions of the ‘Main’. I don’t know which moment did work)
Edit: I ‘downgraded’ to 1.4.3. I made a copy of the current deye_mppt2.yaml from Github and copied it to custom_parameters.yaml adjusted my configurations to use that file.
It works now for me, but the current Main does not.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 3
- Comments: 57 (4 by maintainers)
Es gibt inzwischen die 2.30 und 2.31, die werden vermutlich ähnlich zur 2.27 sein und man kann sie vom FW-Server downloaden.
the problem is, both files 2mppt and 4mppt have a ending value of 0x0080.
In the PDF of the inverter the say: 0x0001~ 0x007D
my guess is:
requests:
may fix it. you can give it a try, i cant test because around 2000 the thing went offline.
Result: 2023-09-04 07:57:50.515 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] Querying [3 - 112] succeeded 2023-09-04 07:57:50.515 DEBUG (SyncWorker_9) [custom_components.solarman.solarman] All queries succeeded, exposing updated values.****
looks good for far, have no time to check the entities right now
meinst du mit 3 und 4 die von PV-3 und PV-4 ?
hier ist die PDF die ich nutze Deye_Modbus.-.-.V118.pdf
@niclas911 Change the first lines of /config/custom_components/solarman/inverter_definitions/deye_2mppt.yaml:
Restart home-assistant. Works for me.
Yep, all values are shown and seem to make sense.
With these changes, it also works for the Deye SUN-M60G3-EU-Q0
start: 0x0001 end: 0x007D mb_functioncode: 0x03With Deye Sun800 G3 EU and FW 2.06
My Serial starts with 39xxx
hf!
Edit: pretty odd… i just updated a component, and had to restart HA… and zing this pops up again:
no values are exposed. i would say my logger is not on v5 or something, but then it works somehow.