You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have some devices that does report Total Energy utilization but not Current Energy. So to be able to track real-time power, i created some derivative sensors and was able to get current power draw.
But the problem is that the derivative helper only updates it's value when source sensor updates itself. It looks like when i power off the AC the sensor does not update anymore and my derivative sensor is stuck with the last reading in watts.
Would it be possible to force sensor update within a given timeframe, let's say 1 min?
Cheers, Tabascoz
The text was updated successfully, but these errors were encountered:
Thanks for the suggestion. I'll have to think about this one. I know an entity can be configured to force updates to the state even if the value doesn't change, but I believe this has a side effect of causing it to take much more room in the database as each (identical) state is written.
And I'm only considering that as a potential problem as the state would be updated approx. every 15 seconds.
That would be a very good solution. My discharge sensor and the energy socket match quite well. But i can no longer select the time window in the sensor; this would lead to a smothered line, but then the problem described occurs.
Hi there
I have some devices that does report Total Energy utilization but not Current Energy. So to be able to track real-time power, i created some derivative sensors and was able to get current power draw.
But the problem is that the derivative helper only updates it's value when source sensor updates itself. It looks like when i power off the AC the sensor does not update anymore and my derivative sensor is stuck with the last reading in watts.
Would it be possible to force sensor update within a given timeframe, let's say 1 min?
Cheers, Tabascoz
The text was updated successfully, but these errors were encountered: