Allow sensors to report delayed data

[benraf]

I’m working on integrating my electricity usage into Home Assistant using my local electricity company’s API, which only reports the previous day’s energy usage (GitHub - benrafshoon/hass_seattle_utilities: Home Assistant Integration for seattle utitlies). Every morning, the sensor reports the new “latest value” which is yesterday’s electricity usage. The result is that the energy dashboard show the electricity consumption shifted forward by one day: the data for “today” in the home assistant graph is actually yesterday’s energy usage, yesterday in the home assistant graph is 2-days-ago usage, etc. As far as I can tell, there’s no way to have a sensor report a value for a time other than right now.

Couple ideas

• Allow sensors to report a “time delay” alongside their value
• Allow sensors to report multiple historical data points

Also possible that this is already supported somehow and I missed it in the Sensor Entity API

[benraf]

I’ve found 3 community threads that I think are also asking for this feature:

1. Energy usage is delayed or shifted in time in the graphs
2. Energy Counter - delayed data

[benraf]

3. Uses for delayed power consumption data from power company

[dbolger (Dylan Bolger)]

+1 here, I have the same integration issue on my end.

[mpschr (michphip)]

Exactly the same scenario here. Getting delayed data, even 10’ updates for energy consumption including timestamp. I am finding no way to use this as a delayed sensor

[mpschr (michphip)]

Oh, maybe I spoke to soon. I just checked out a notification and here is a suggested solution.

Will have to try it out one of these days:

Batch receive time series data

Hi guys, I am working on DIY sleep/breath monitor and figured out that I don’t need to send data from ESP32 in realtime, and decided to implement a batch sync in the morning. Thus, I faced this issue too. And looks like I just found a method to attach a timestamp to a value It looks quite simple - you just have to send a bunch of events like this, with your entity id (which should be already created in system), state value, and last_updated timestamp. event_type: state_changed event_data:…

[jens-markussen (Jens Vedel Markussen)]

How can we get traction on this feature request. I have now several sensors (mostly from utility companies) where data is not immediate, but rather delayed anywhere from a few hours to a couple of days.

With current setup, it is hard to have sensor reporting such data correctly.

[Apoc182]

Just throwing my proverbial hat in the ring. I have exactly the same issue, would like help coming up with a solution if possible.

Integrating delayed energy consumption into the energy dashboard

Hi all. My energy provider has an API that I’ve been able to tap into to get hourly energy usage in kilowatt hours. The only issue is they only provide this data the day after. So for example, if today is Wednesday then if I query at 1:00 a.m. today, the latest data I will have access to is Tuesday’s hourly data. I want to integrate this into my energy dashboard, but I don’t know how to set up a delay like this. Am I just overthinking this? I am not sure exactly what entities I should be using …

[Crash0verride]

Would the more expedient change be to allow backdating energy dashboard statistics based on a sensor, and leave the way the sensors themselves are implemented well enough alone? Whatever sorts this. The untracked energy usage recently implemented further complicates delayed data on the energy dashboard.

[radudorurus]

My opinion is it is simpler to give up searching a solution for this and get shellyEM or other energy monitor which gives real time data locally.

And not relaying on someone else data is better.

[benhdavis (Benjamin)]

Would love a solution here. Sure I can buy more hardware but I’m fine with delayed data by one day if I had a way to input it.