Last value persistent during inverter switchoff

[Claudio1L]

Ciao Alessandro

some release ago, sensors values were persistent (if not rebooted) during the night. Now they goes in an unknown state. Is it complex to include a setting to choose between persistent and not persistent? I'm still running the ABB integration in a separate instance to avoid upgrading and losing the persistence :-)

[alexdelprete]

when an integration is unavailable, its sensors go in unavailable state, this is how HA works and integrations should work. "unavailable" is a state. :)

Sorry, can't do much to help. I don't understand what you're trying to achieve, if you can explain better I can try to help.

[Claudio1L]

I built a bunch of counters that take in account the integration values as source. As you can see from the attached dashboard, if the source sensors are not persistent, everything breaks. I solved using one of the latest release that were persistent (2.6.6) running in a separate container and then exporting sensors to the main instance I'm able to maintain counters.

[alexdelprete]

Then you need to build a lot of trigger-based template sensors, that are persistent, like this:

template:
  - trigger:
      - platform: state
        entity_id: sensor.abb_vsn300_ac_power
        not_to:
          - unavailable
          - unknown
    sensor:
      - name: ABB Inverter Power Stable
        device_class: power
        state_class: measurement
        unit_of_measurement: W
        icon: mdi:solar-power
        state: "{{ trigger.to_state.state }}"

The "shadow" sensor sensor.abb_vsn300_ac_power_stable will be created, and when the real sensor sensor sensor.abb_vsn300_ac_power has a value, it uses its value, when the state is unknown or unavailable, it uses last known state.

When the real sensor is available, the state is the same:

When the real sensor goes unavailable, you see last known state:

[alexdelprete]

If you don't want to use trigger-based template sensor, but a standard template sensor, here is another example:

template:
  - sensor:
      - name: ABB Inverter Power Stable
        device_class: power
        state_class: measurement
        unit_of_measurement: W
        icon: mdi:solar-power
        state: >
          {% if has_value('sensor.abb_vsn300_ac_power') %}
            {{ states('sensor.abb_vsn300_ac_power') }}
          {% else %}
            {{ this.state }}
          {% endif %}

If you need to create a lot of those, maybe a compact form is better:

template:
  - sensor:
      - name: ABB Inverter Power Stable
        device_class: power
        state_class: measurement
        unit_of_measurement: W
        icon: mdi:solar-power
        state: "{{ iif(has_value('sensor.abb_vsn300_ac_power'), states('sensor.abb_vsn300_ac_power'), this.state) }}"

[alexdelprete]

You can find everything in HA community forum, the examples above are from this thread.

[Claudio1L]

Ok thank you. Something new to study Thanks again Claudio Il giorno sab 9 mar 2024 alle 19:09 Alessandro Del Prete < ***@***.***> ha scritto:

…

You can find everything in HA community forum, the examples above are from this thread <https://community.home-assistant.io/t/support-retrieving-the-last-known-value-in-templates-for-unavailable-sensor-entities/663710> . — Reply to this email directly, view it on GitHub <#120 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AXK6MPTJQSZ4VTNEPLSZ2E3YXNF6FAVCNFSM6AAAAABEOFWH7GVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM4DOMZRGAYDI> . You are receiving this because you authored the thread.Message ID: <alexdelprete/ha-abb-powerone-pvi-sunspec/repo-discussions/120/comments/8731004 @github.com>