Thank you , also maybe some of those āprevā are not so useful, eg. prev day, prev hour - not sure I would ever use them (as insight - but who knows). Just FYI - I was just trying to take a look on this year kWh consumption and calculate/estimate this year full consumption taking āwinterā month consumption into account (I have only Feb for Jan as prev) and I found out I canāt actually.
Btw, maybe the full year estimate based on average consumption from seasons, might be something some people would be looking for, including estimated billā¦ Iām not sure if that wasnāt idea some time ago. Just thinking out loud ā¦
@OysteinEn Could you install test version 4.5.3 and create another app diagnostics reports when you notice a price deviation again? I added additional logging to figure out what is going on there.
Hi Robin, the energy prices during the dayānānight now makes it very challenging to work out flows to concider all scenarioes. in my case, I have great flows to heat water at night, but right now the prices at night are insane, and I do not have flowcards to pick this up. So, what can we work out? Obviousely we need to be able to have variables for all hours between 1300 to 1300 following day, and then a card to pick the x lowest hours the next 24 hrs. What do you think?
I have been testing this for a few weeks now and itās working great. Thanks!!
One thing that I would like to be able to do with it, is to identify when the cheapest consecutive x hours are. āThe price becomes lowest x hours in the period hours before timeāā¦ This would allow me to schedule something like the dishwasher at the true cheapest part of the night. If i was to use the cheapest single hour as a trigger, but it runs for two hours, then I would not necesserily get the best price. likewise, if I use āThe price becomes one of number lowest in the period hours before timeā then this does not guarantee that the two cheapest hours are next to eachother.
Here, as far as I can work out, withthe triggers available and a 2 hour load at 1kw contant, the price paid would be ā¬7. because the cheapest hour trigger would cause consumption also in the most expensive hour of the example. Likewise, if i was to trigger on the cheapest two hoursā¦ well, thatās not how dishwashers work, you canāt just pause like that, but it would presumable trigger on the ā¬2 price, also resulting in a ā¬7 cost.
The actual cheapest consecutive 2 hours would cost ā¬4 starting at 01:00
I hope i expressed my wish clearly. I also understand that perhaps I missed something and there is already a way to achieve this.
Your use case is what I use myself and have already implemented. The trigger card is called āavg price next hours becomes lowestā. It calculates the best consecutive hours. You can choose the best hours for today or for the next 8 hours.
When selecting the next 8 hours it will be a rolling condition. This means that when prices keep going down it will never be triggered. So I might also implement the same function but with a finite end time.
Ahh perfect! Yes this is exactly what iām asking for! I think for most situations it will work out well enough as implemented. But yes, I see that a finite time could be useful for when something must be done by a certain time at the latest.
Hi, very nice app.
But a question. There is trigger cards for lowest prices for to day and lowest prices before a time. Iām missing same function for the highest prices. I would like to make a flow that change the start temperature for my warm water heater to 30 degrees C for de 16 most expensive hours.
I have worked it around with the trigger, changed price and used the and funktion for the most expensive hours. But then the flow will send a command every our to my heater and I wish it didnāt.
//Peter
What app are you using for the BMS? It has multiple Watt meters. PBTH will use the meter that is called measure_power in the source code. So maybe the 0.0287 already corresponds to either consumption or grid.
In any case, if you want to track multiple Watt meters from the same BMS device, you need to make a virtual devices from each of the single values you want to track. You can probably use the GROUP app for that. You then start summarizing that virtual device with PBTH.
, also maybe some of those āprevā are not so useful, eg. prev day, prev hour - not sure I would ever use them (as insight - but who knows). Just FYI - I was just trying to take a look on this year kWh consumption and calculate/estimate this year full consumption taking āwinterā month consumption into account (I have only Feb for Jan as prev) and I found out I canāt actually.
)
