[APP][Pro] Power by the Hour: Insights per hour, day, month and year

I have this flow running in the background to report me the lowest average rate window for 6 hours over a time period (18:00-06:00). The result yesterday gave a window of: 21:15-03:15.

With yesterday’s prices:

and today’s prices:

And looking at the graphs that windows should be correct.

Now for the new cards:

The 4-period average price is lowest between 06:00 and 12:00 matched today first at 06:15 and every 15 minutes up till 10:07 for the last match. I was expecting to see an hour’s period around 09-10. Instead I got four hours of matches.

And, The 24-period average price is lowest between 18:00 and 06:00 did not give a match at any time for the expected 21:15-03:15 window calculated with my script. The card is probably looking at N-periods in hours as the fist 4-period test would suggest.

Does the card take into account the day change? And if so, does it take into account that it should look at rates:

  • for today and tomorrow when the time now is before midnight
  • and for yesteday and today after midnight?

Couple of other things I noticed:

  1. New price period starts - the first quarter period is delayd by 5-6 minutes. Causing the actual rate to be used for almost half of the quarter hour until recognized that it wasn’t a rate to be used due to being too high.
2026-03-14 18:06:41 Price now: 0.038
2026-03-14 18:15:16 Price now: 0.0387
2026-03-14 18:30:05 Price now: 0.0401
2026-03-14 18:45:20 Price now: 0.0393
2026-03-14 19:06:17 Price now: 0.0401
2026-03-14 19:15:13 Price now: 0.0384
...
  1. New prices received for *tomorrow* is triggered at midnight. This triggers some unwanted flows when one is expecting to really have tomorrow’s rates available. I guess the New prices received gets triggered since tomorrow’s prices are populated for the first hour of the day? Workaround now is to check the time when the card was triggered and skip midnight.
2026-03-15 00:05:13 New rates received.

All times are EET.

1 Like

Correct.

And thx for the detailed feedback! Really useful to fix the issues you found.

1 Like

Ok, so I need to filter that out in the flows to trigger only at when the really new prices arrive after midday.

A period in the new flow cards is 15 minutes? So if your energy provider still works with an hourly rate, is it better to use the old cards? (that would explain why my flow was acting a bit weird just now)

That should only apply to the 15min DAP and not the 1 hour DAP device.

1 Like

@Gruijter

Found the little thing.

On Homeys in Dutch:
On the 2023 model, you have the “Verwachte opbrengst vandaag” sensor twice.
On a 2019 model, there are “Prognose vandaag” and “Prognose dit uur”.

I prefer “Prognose vandaag” and “Prognose dit uur” for use on a dashboard.

Thanks!




Hi! First of all, thanks for this great app — it’s really useful for monitoring energy usage.

I noticed a small issue when checking the daily consumption of one of my devices. I’m using an Aqara Smart Plug with a freezer, and normally it consumes around 0.42–0.43 kWh per day, which the app usually reports correctly.

However, sometimes the daily graph shows very large spikes that don’t seem realistic. For example, on March 12 the hourly view shows a 20.5 kWh spike in a single hour, which is clearly impossible for a freezer.

When I check the actual total daily consumption for the same day, it still shows about 0.43 kWh, so the measurement itself seems correct. Because of this, it looks like the issue might be in the hourly/daily calculation or visualization in the app, rather than the device data.

I attached a few screenshots that show the normal day and the buggy day.

Thanks again for the great work on the app, and I hope this helps track down the issue! :blush:

1 Like

Dear Gruijter

Thank you for your app, it makes a world different. BUT, regularly, the app does not take in tomorrow’s prizes. AS it did not today. This makes that the x-amount hours with lowest prise before tomorrow 7 o’clock does not work as intended because the app only sees the hours until midnight. Could you please fix this bug.

Thank you very much!

regards from Norway :slight_smile:

That happens when the data source does not have prices for tomorrow. Please check if Nordpool and/or ENTSOE has the data for tomorrow. If not, there is nothing PbtH can do about it.

I think I found the issue. Fix is coming in next test release.

1 Like

When you are using the same PbtH app version on both Homeys, they should have exactly the same capabilities. Did you try rebooting your Homey’s?

Forgive me if addressed already, but it still shows some serious spikes next to the slight averaging.
Just FYI!

All in all the forecast is pretty accurate already!

1 Like

Same for me…

Think I solved both issues. Please check upcoming test version.

1 Like

Yes, already found the issue. Should be solved in next release.

1 Like

v8.7.3 is ready for testing: https://homey.app/a/com.gruijter.powerhour/test/

  • Improve SolarForecaster strategy.
  • Fix power spikes in SUM and SOLAR device.
  • Fix several flow cards.
  • Code refactoring.
2 Likes

Every day at 13.00 tomorrows’ prices are released. When I check, and also when I registered this case, it was later in the afternoon. So yes, the prices are available and no they are for some reason not collected and imported into the app.

Mvh
Bram

Restarted both Homeys. They are now both showing “Verwachte opbrengst vandaag” sensor twice. Still, I prefer “Prognose vandaag” and “Prognose dit uur” for use on a dashboard.

This is also on 8.7.3

Otherwise, everything is running fine here. Haven’t seen any spikes. The morning forecast is still a bit off on both systems. But I think that will sort itself out with data over several days? Measuring all arrays (three) with one kWh meter works fine too. So that’s a tip for people with multiple arrays: put all output through one kWh meter. The one from Homewizard, for example, can handle 100 Amperes, so that’s no problem.

3 arrays on one kWh meter.

Ey morning,
I have a battery interfaced by homey.
The power measurement is:

  • positive when charging
  • negative when discharging

I added the PBTH battery monitor and linked it to this battery. However the Energy is calculated the opposites way. Total charged energy is increasing, when discharing and vica versa. Is there a way to invert this? I can’t find a setting in the config.

Thanks