I didn’t check. Will check next time when the graph is emtpy.
Edit: in the same flow Ill send a message to myself:
This is the message:
So I think there where no prices available at 20:01.
Oh, I love this. Will this work with Solcast data? Or will it be developed in-house? And where can I find the SolarForecaster? I don’t see it when creating a new device. (v8.6.4)
I hereby request in advance for an if and and card.
SolarForecaster
if: Remaining before [time] is less then [ x ] kWh
SolarForecaster
And: Remaining before [time] is less then [ x ] kWh
I’m currently using the Solcast app. But if SolarForecaster calibrates itself to my own PV system, that’s absolutely fantastic.
I mainly use PBTH to manage my Homewizard batteries. See my flow:
Nice ideas!
It works fantastically if you build in some tolerance in your flow to charge your batteries or not. And the forecast is reasonably accurate. But my mother’s panels are partially in the shade, and then the Solcast forecast is messed up. So if you built something that’s self-learning and constantly adjusts, that would be fantastic.
By the way, yesterday I forgot to mention one card.
SolarForecaster
And: Forcast between [time] and [time] is above [ x ] kWh
Made a PR#340 about the JSON cards and the examples they show. The actual output from those cards is an array, but the example shows an object.
Another thing I noticed, at midnight, when tomorrow’s prices go away as they have not been received yet, the New prices received card is triggered. I believe it shouldn’t be triggered when the real tomorrow’s prices arrive some 12 hours later.
In Finland I get a trigger for the first 0:00, 0:05, 0:15, 0:30 and 0:45 on the 15min DAP.
Super, thx for the feedback ![]()
Thx! I added the changes to the new release.
And you do not have forecasting enabled? Edit: I removed the ‘forced’ new prices trigger at midnight in the next release.
Can you elaborate on this? What exactly happens when?
Prices are a mess again (not in PbtH, but in EU). That is why also Homey itself had no price info for certain regions this morning.
Today the prices are not in sync;
The cheapest hour is (again) different.
Maybe an idea, but what is the calculation to calculate the hour price from the 15 min prices? Maybe something there is triggering it
I enabled the lowest time myself on 13:44. The flow 19, didn’t trigger
–
Edited:
Some more info:
Tag “lowest hour day” = 12. With this extra info, I think the problem should be inside the trigger: “The price becomes one of # lowest in the # hours before #” flow. (also see screenshot)
Thanks!
Above your post, this was mentioned:
I have this flow:
And last night I received all these triggered by that. (Times in EET)
[11. Mar 2026 at 0.00.19]: New prices received for tomorrow: [0.0251]
[11. Mar 2026 at 0.05.18]: New prices received for tomorrow: [0.0251,0.0189,0.0156,0.0137]
[11. Mar 2026 at 0.15.16]: New prices received for tomorrow: [0.0251,0.0189,0.0156,0.0137]
[11. Mar 2026 at 0.30.17]: New prices received for tomorrow: [0.0251,0.0189,0.0156,0.0137]
[11. Mar 2026 at 0.45.05]: New prices received for tomorrow: [0.0251,0.0189,0.0156,0.0137]
Since we are one hour ahead of CET, there is one hour’s worth of prices
And at the time of really receiving tomorrows prices which is correct:
[11. Mar 2026 at 14.03.59]: New prices received for tomorrow: [0.0251,0.0189,0.0156,0.0137,0.017,0.0158,0.0141,0.0115,0.0132,0.0111,0.0107,0.0111,0.0075,0.0085,0.0081,0.0088,0.0073,0.0073,0.0081,0.0098,0.0071,0.0086,0.0104,0.0123,0.0097,0.0125,0.0221,0.0315,0.0152,0.0191,0.0253,0.0317,0.0216,0.0266,0.0326,0.0337,0.0325,0.0327,0.0326,0.0336,0.0371,0.0343,0.0288,0.0303,0.0395,0.034,0.0135,0.0075,0.0165,0.015,0.0133,0.0122,0.0137,0.0125,0.0119,0.0107,0.0122,0.0123,0.0123,0.0122,0.0126,0.0119,0.0095,0.008,0.0089,0.0078,0.008,0.0081,0.0086,0.0098,0.0109,0.0117,0.011,0.012,0.0122,0.0125,0.0127,0.0127,0.0121,0.0117,0.0119,0.0116,0.011,0.0094,0.0085,0.0089,0.0076,0.0063,0.0076,0.0064,0.0056,0.0047,0.0053,0.005,0.0036,0.0034]
Ah ok. Very helpful screenshots! Will dig into this. The ‘new prices’ trigger at Midnight will be removed in the next release by the way.
Thx for the screenshots. Does indeed not work as the images would imply. Will look into this.
New version 8.7.0 is available for testing: https://homey.app/a/com.gruijter.powerhour/test/
This test release can be seen as PbtH v9.0 RC1 ![]()
The price/charge chart generation and handling has been completely overhauled. It now works with a new external service called QuickChart.io . This service suffers less from rate limiting. Also the internal image streaming in the app to your mobile app / web interface has been overhauled. I hope this solves image issues that some of you experienced. (please test @Robkrekel and everyone).
Secondly some new flow cards were added to simplify the use of day ahead prices. (please test @OH2TH @Daderu )
And the most important / big update is the new Solar Forecaster driver
. It is a (almost) zero-config device. No need to configure layout, location, size, type, tilt, etc etc.
The Solar Forecaster learns the unique characteristics of your solar panels (orientation, shading, efficiency) over time. To use it, simply add a `Solar Panel` device. During setup, select the device that measures your solar production (e.g. an Enphase, SolarEdge, or Shelly device).
The forecaster will automatically analyze the last 14 days of power history and combine it with local weather data to build a custom model for your array. It updates this model continuously. You can view the forecast for Today and Tomorrow, as well as the ‘Yield Distribution’ curve which shows your array’s efficiency throughout the day, directly on the device interface. And @Johan_Bruyn your flow card suggestions were implemented.
Please test and give feedback!
Edit: there was an issue in initial solar learning. That has been fixed in v8.7.1
Great, I’m going to test it right away on a Homey 2019 & 2023. (The 2019 is my mother’s, I have the 2023 myself.) The new flow charts look good too. I’ll let Solar Forecaster run in parallel for a while until it’s learned enough. Then I’ll do further testing.
But if Solar Forecaster is self-learning, could you combine two inverters? My mother has three arrays, two connected to one inverter. But the total yield comes from the Homewizard kWh Meter. And it provides much better data than the inverters themselves. (MID approved) It’s also easier to work with a single data source in my flow.
Just try. But it also needs Watt for better learning
That is an artefact of how graphs are drawn. When you have fast power ramp up or down the graph extrapolates. But you can ignore that. It is not used as real data and it will be corrected on the next sample
Ow weird. That panel reports its power inverted from the Homey standards. Is it setup/compliant with Homey Solar panel class? How does it show up in Homey Energy?
Both use a Homewizard meter with the same settings. Both are connected as solar panels. The only difference is that one Homey is a 2023, and the other a 2019. In energy, the kWh meter is shown under solar panels with a positive value. The graph is currently positive, though. So I’ll leave it as is for now. I’m just missing the forecast in the graph. I’ll wait and see what happens tomorrow.