How to maintain the last value of an entity when become unknown

[Claudio1L]

Hi there, I would need your help.
I have a bunch of templates doing calculation based on AC Power, AC energy, DC energy etc. entities exposed from the Solar inverter.
The problem is that all calculations went broken when the inverter power off, during the night.

I’m asking if there is a way to derivate entities that maintain the last value. I’m trying using the utility meter helpers, selecting the maintain last value flag, but is not working fine with real time sensors as AC power. Any alternative way to do it?

[Claudio1L]

When I say that utility meter is not working fine, I mean that also having high source value, the entity value increase slowly, not following the source status:

[Sir_Goodenough ((SG) WhatAreWeFixing.Today)]

Hi Claudio1L,

Not long ago I heard this question, and I believe there was a solution.

Please search for it. I am not able to at this moment.

Tips on Searching for Answers & Duplicate Topics in the Forum

Sometimes searching for what you want to find here in the Community Forum can be frustrating. The Forums base software (Discourse) has a search tool that is somewhat effective, but it relies on only the answers provided by other users in the app to answer your question. It does do a good job of popping up similar topics when you are starting a new topic however. (So please pay close attention to the side panel when you are adding a new topic) If you use a search engine like DuckDuckGo or Googl…

[jackjourneyman (Jack)]

Do you mean here?

Strategy for creating last value 'cache' versions of sensors in case the sensor becomes unavailable

I have automations that trigger when time is equal to a timestamp-class sensor. In this case, it’s a sensor managed by an integration that tells me the start time of my free power for the day. sensor.hour_of_free_power_start The sensor occasionally becomes unavailable, like when the integration wants me to log back in. If the sensor is unavailable at the time the automation would otherwise trigger, the automation doesn’t trigger. No surprises there. The sensor is a device_class: timestamp and …

I haven’t read the thread closely, but they seem to be talking about general solutions for large numbers of sensors. Not sure this is a good idea.

For specific sensors, I personally use the custom integration Variables+history:

GitHub - enkama/hass-variables: Home Assistant variables component

[Claudio1L]

Thanks @jackjourneyman

looks promising. I’m checking

Thanks again