You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The value int16 is incorrect, needs to be changed to 32 but there is a mistake in sungrow protocol which calls for it to be uint, that is a mistake, the final result should remain int32
- name: Total backup power
device_address: !secret sungrow_modbus_slave
unique_id: sg_total_backup_power
address: 5725 # reg 5726
input_type: input
data_type: int32 # as per sungrow register list
precision: 1
unit_of_measurement: W
device_class: power
state_class: measurement
scale: 1
scan_interval: 10
Logic here is - if you see sensors above, 5724, 5725 etc. they are all to do with backup power and they are all signed.
Total Backup power should be also signed - pretty sure Sungrow confirmed it was a bad translation error.
This correction is also slated to be in the next Sungrow modbus register specification (1.1.5), according to the Sungrow Germany product management team.
I've requested the new version of the document but have not received it, yet. 😢
Yup.
This error was shown to their r&d team live at my house some 3-4months back.
Lol. Still have notes.
Cos we have gone through the protocol page by page and they were a touch surprised anyone would pick them to pieces.
We also discussed how chaotic their translation and application of modicon convention was but thats a whole different story.
I do have a particular issue Im trying to solve or improve and I would not mind running past u, so discord would b a perfect place to start. If u have any time left for discussions.
Message ID: ***@***.***>
The value int16 is incorrect, needs to be changed to 32 but there is a mistake in sungrow protocol which calls for it to be uint, that is a mistake, the final result should remain int32
Sungrow-SHx-Inverter-Modbus-Home-Assistant/modbus_sungrow.yaml
Line 337 in 9e9859d
The text was updated successfully, but these errors were encountered: