Sessy v0.5.5 code issue Sensor - Charge power

[dacootmeister]

Hi Pim,

I've seen an issue with one of my 2 Sessy's sensor values. My left Sessy reports Charge power Onbekend

and the right one Charge power 0 kWh

This results in an Energy Dashboard with uknown values: sensor.sessy_battery_links_discharge_power (unknown) sensor.sessy_battery_links_charge_power (unknown)

Any idea how to fix this?

[npostman]

Have you checked your connectivity? Access your Sessys internal web UI and see if you get any errors (<IP>/errors).

And what does accessing <IP>/api/v1/power/status give you? Maybe restart your Sessys by turning off the power supply for a little bit.

[dacootmeister]

v1/power/status

Connectivity is fine, already checked that using web interface and rebooted the dongle via HA. Outcome of the API query: { "status": "ok", "sessy": { "state_of_charge": 0, "power": 0, "power_setpoint": 0, "system_state": "SYSTEM_STATE_STANDBY", "system_state_details": "", "frequency": 49975 }, "renewable_energy_phase1": { "voltage_rms": 229989, "current_rms": 214, "power": 49 }, "renewable_energy_phase2": { "voltage_rms": 0, "current_rms": 0, "power": 0 }, "renewable_energy_phase3": { "voltage_rms": 0, "current_rms": 0, "power": 0 } }

The other Sessy: { "status": "ok", "sessy": { "state_of_charge": 0.00999999977648258, "power": 0, "power_setpoint": 0, "system_state": "SYSTEM_STATE_STANDBY", "system_state_details": "", "frequency": 49987 }, "renewable_energy_phase1": { "voltage_rms": 231412, "current_rms": 0, "power": 0 }, "renewable_energy_phase2": { "voltage_rms": 0, "current_rms": 0, "power": 0 }, "renewable_energy_phase3": { "voltage_rms": 0, "current_rms": 0, "power": 0 } }

[dacootmeister]

I had an eye-opener.. (you'd never expected that...) The API data shows a difference in the State of Charge between my 2 Sessy's. There is where the "problem" lies. I forced a small energy load on the troubled Sessy to say 4%. I noticed that the Battery Charge sensor was being utilized and then switched to NOM to see if the Battery Discharge sensor was also triggered. It was!

So, problem solved and it had nothing to do with Pim's code. :-D