Incorrect data on Inverter alert message for Sofar HYD

[onetoomany]

I seem to be getting an alert message (_sensor.solarman_inverter_alertmessage) as a proxy for the inverter running state. For example:

• ID16 Input current is not balanced = inverter is charging
• ID32 The Input current is too high = inverter is discharging
• 64 = Standby
• ID96 RTC Clock chip fault = ?
• 160 = ?

Inverter is a Sofar HYD 5000 ES in passive mode. I'm also running sofar2mqtt to control the inverter.

[timlewy]

I am also observing this with my HYD 3600 inverter. Its reassuring to hear someone getting the same

[onetoomany]

Digging into this, it looks like the Solarman add-in is reading a number from a register on the inverter and the code is then adding the error message. This add-in is reading from the wrong register so I'm not worried about all these scary looking alert codes as they are not generated on the inverter. This is how I'm turning this wrong data into something useful:

``

• name: "Sofar Inverter State" state: >- {% set alert = states('sensor.solarman_inverter_alert_message') %} {% if alert == "No error" %} {{"Idle"}} {% elif alert == "ID16 Input current is not balanced" %} {{"Charging"}} {% elif alert == "ID32 The input current is too high" %} {{"Discharging"}} {% elif alert == "64" %} {{"Full - Idle"}} {% elif alert == "80" %} {{"Full - Charging"}} {% elif alert == "ID96 RTC clock chip fault" %} {{"Full - Discharging"}} {% elif alert == "128" %} {{"Flat - Idle"}} {% elif alert == "144" %} {{"Flat - Charging"}} {% elif alert == "160" %} {{"Flat - Discharging"}} {% else %} {{"Unknown"}} {% endif %}

[timlewy]

This can be fixed by updating the YAML definition. The register exists in the spec, but the definition for the values is wrong in the integration. Most of these alerts seem to correspond to reserved values as well, but we can infer their usage. There is a limitation in this integration though - it treats the register values as single integers with decimal mappings, but in reality they are bit fields, with each bit representing a different alert. This allows any combination of the alerts to be represented. For the integration to be accurate, values would need to be provided for all 65535 combinations

[timlewy]

The spec gives us:

• 0: No alert
• 1: Temp high derating
• 2: frequency high derating
• 4: Derated by remote control
• 8: Shut down by remote control
• 128: Battery low voltage

I've never seen any bar the last of those values in real life, so I can only trust the sofar protocol definition.

From my observations I also infer:

• 16: Generation surplus (charge battery)
• 32: Generation deficit (discharge battery)
• 64: Battery max voltage/SOC
• 80: Generation surplus + Battery max voltage/SOC
• 96: Generation deficit + Battery max voltage/SOC
• 128: Battery voltage/SOC low
• 144: Generation surplus + Battery voltage/SOC low
• 160: Generation deficit + Battery voltage/SOC low