Hello Erik, and welcome.
AFAIK you should use the number for the tariff update group, probably 1.
Now all summarisers with tariff update group 1 will be updated with the new price.
That worked perfect!
Sorry about the Swedish text in the picture from my Flow. But it basically says “Update group 1 and group 2 with the tariff for the hour.”
I also found a place to add the fixed fee for each month…
1 Like
Hi,
I noticed that (since a couple of days?) the outcome of the next (demo) flow is independent of the actual price level:
As you can see I tried in two ways to use ‘lowest price in next 5 hours’, but no matter what I use as test value (I tried from 0 to 2 and both values with . and , for decimals), the result always is negative (the ‘yellow’ line). In other words, the condition is always false for every value the variable ‘Price now’ has. Until a couple of days ago it worked as expected, so did anything change (and how to use correctly now)?
The test price is not used in the AND cards. They use the actual price. So testing this flow doesnt work like you think.
In PBTH nothing changed by the way.
Ok, thanks!
1 Like
First question, my zendure battery show me how many input and output.
But the power by the hour app shows only the input, and no output. How can i fix that?
Second question: When I fill in the minimum price difference of 0,08 euro the chart not showing up the current hour:
When using the flow with the same strategy:
Its starting to output power.
How can I fix both issues??
How dit you connect the Zendure?? There is no app for….
Using a broker, using mqtt.
1 Like
Just now have it the otherway around, the chart tells me to export.
This is the setting of the chart.
And the flow is telling NO:
Hi.
I have a request for a flow card
And: Current price is X% lower than the next x hour(s).
I can’t find a way to do this now. It woud be a great card to use for boosting the heat in the hour right before a high peak.
1 Like
Thanks for the example. However I don’t think this would be the same.
I would like to be able to select less than 8 hours.
This is possible using logic cards
Compare with the avg price of next 3h
Compare with the price of the next h
2 Likes
Maybe this is already handled. But after a restart of homey there is a 50% change that the app has crashed and that i must restart the app.
I think @Gruijter is happy if you allo send a him a Diagnostic report that he see something in your log.
So if it 's happen again before you restart the app first make the report
And then make somthing like this in the build a flow with the next:
if system homey is started
then system restart app “Power by th Hour”
delay on xx min
xx is time what is needed to start your Homey totaly
as a example for me between 10 en 15 min
It’s a work arround, not the solution
You could all so make a flow like if a App is crached then restart
But then you must let in run every 10 minute’s
I should go for the flow with if Homey restart
1 Like
The only crash reports I have received have to do with Homey’s flash memory being full. Could it be your flash memory is full?
@johan_W and @Gruijter. Thanks guys. I must say that the internal memory is far full. At 1.8 of the 2gb.
And you are right. I should send him a diagnostic report.
And i will try your suggestion.
f78cf715-7f7a-43ec-9183-cc928971175e
So ordered.
It’s about flash memory. The “disk” 
Aaaaah. Thanks. This has used 1.8 gb of the 2.7 gb.
1 Like
All looks normal.
Can you define what you mean when you say ‘the app crashes’? How can you tell the app has crashed?
