When inverters are off, inverter sensors entities should not update

[wildekek]

When the inverters are off, the following sensors report a value of 0:

• sensor.inverter_xxxxxxx_power_ch_1
• sensor.inverter_xxxxxxx_power_ch_2
• sensor.inverter_xxxxxxx_frequency
• sensor.inverter_xxxxxxx_voltage

The following sensors report their last know state:

• sensor.inverter_xxxxxxx_signal

The correct behavior is not updating the state, like the temperature sensor:

• sensor.inverter_xxxxxxx_temperature

Wrong:

Expected behavior:

[HAEdwin]

The temperature sensor(s) of the inverter(s) also reported zero when switching off the inverter(s). This zero value does not reflect the actual temperature of the inverter. That is why the preference arose not to update these graphs.

[wildekek]

Yes, that makes total sense. So you agree this behavior should apply to the other graphs as well? (Since the inverter has no idea what the Signal, Frequency, Voltage are, Power is debatable.)

[HAEdwin]

I created a poll to see how others think about this idea: https://github.com/ksheumaker/homeassistant-apsystems_ecur/discussions/215

[HAEdwin]

I'll try to make it optional like so:

[wildekek]

Sweet, that we would be a great addition!

[HAEdwin]

@wildekek I'm currently testing... If you would like to test, you can find the sources here: https://github.com/HAEdwin/homeassistant-apsystems_ecur.

Personally I like to update the graphs when the inverters are offline because this morning it showed power being zero on two channels with the inverter online, showing that these parameters are indeed zero and not a guess.

[HAEdwin]

@wildekek With some delay due to the busy Christmas holidays and a software bug the 1.3.0b version includes the feature - ready for further testing 🎉

[wildekek]

Nice work @HAEdwin ! I've installed it and will check out the results in 24h. Thanks a bunch and happy holidays to you.

[HAEdwin]

Fixed: Caught a bug on a fresh install; when configuring the integration it throws an error on the no_graphs because there was no default so the key and value (False) could not be created.

Release was updated just now. @wildekek, All is in working as expected?

[wildekek]

Yep, thanks for your work!