Thanks, then it isn’t calibration. This is how v9 works: in a group it uses the battery that is cheapest per kWh cycled first (wear and losses), and of equally cheap ones the least used. With its 87 % round trip that is probably L4, so it discharges first and charges first. The other Sessys take over once it’s at its reserve. Force save up only charges from solar surplus, which is low now, so L4 stays at 10 %. As soon as Smart plans a charge, L4 is filled first again.
Report back when you see that after a week L4 is still never used. Post a app diagnostics report two minutes after doing an app restart.
I’m thinking about it. It is not a priority though. And secondly I think there are already some other apps doing energy dashboards. So I might not implement any, especially because the PbtH app is running into Homey resource limits already.
Energy price in v9.0.x device, there is no setting for a minimum spot price for import, only export.
In Finland import market price may be negative, but energy seller will not go below zero and will charge their margin and VAT on that margin.
The minimum price for import would be useful. I currently have a exception flow doing that to override price when market price is below zero.
Update:
This covers the flooring of market price to zero also:
Would it be possible to add Highest Price and Lowest Price in addition to the Average Price tokens for tha block?
I’m actually looking for any slots that will give me the optimal charging price from “now or start time” until 06:00 where I know that a total of 6 hours is need to charge and it doesn’t need to be a continuous 6 hour window, it may spread a long a longer period of time.
How would this example work when you have the Energy Price Device setup for 15 minutes? Would it evaluate the next 4 quarters at the start of the new price period, or would it calculate withing the current running hour?
Or should we always match the Energy Price Device period (length) with the period (length) we want to evaluate against? (I really don’t want to stop and start my charger at a quarter interval)
But when you have a 15 minute contract, you can still add a second price device with 1hr prices. The 1hr prices always average the 15m prices.
Or use the block cards, that do averaging for you.
So multiple ways of averaging prices.
Oh, and by the way: the new EV charger driver can do smart planning based on your driving profile. Today might be cheap (weekends mostly), so I want to charge extra. Or today might be expensive, so I dont want to charge more than the absolute minimum I need for my next trip. I use the EV driver myself
But is your question because in v8 you could do something you cannot do in v9 anymore?
Not quite, I’m seeking to find the the maximum prices that is need to get a total of X time of charging. This price limit is sent to the EV charger as a setting and the charger takes care of the rest. This keeps the charger independent of Homey and will still allow flexibility.
Ah ok. This might be an edge case for PbtH. One of the goals of v9 is to make it more accessible for ‘ordinary’ homey users. Adding your edge case would complicate things, which I do not want.
I will have another look at it though, and see if I can add it somehow (maybe in the ev driver?)
What brand EV charger do you have, and what app do you use for that?
I’m a little confused and just noticed there is a major update V9 active + installed. I don’t check this forum daily, so I wasn’t aware until I wanted to create a new flow and couldn’t find triggers I used before (e.g. ‘When new prices arrived’ was gone).
I now understand that I have to replace all the devices by V9 devices. Correct?
As I have a lot of flows using the PbtH cards, it takes a lot of time. Which I don’t have right now. So , I installed the production version again (replacing the test version). But now, I get several warnings, like:
To test, I had ‘updated’ (replaced) the 1 hour power tariffs device and then realised the amount of work to change all the flows. After installing the production version again, the new V9 1 hour power device was unavailable (I understand), so I removed. But the old one tells me it’s replaced by a device that no longer exists. So, I worry…
Are the stable version devices and flow cards still working (despite the error messages I get)?
For the future: once the V9 version is stable (and will replace the actual stable version), will it be necessary to replace all devices and rebuild all the flows using it?
I hope there will be a better, more active, way (facilitated by Athom) to inform about impactful changes besides visiting the forum frequently.
The tariffs shown in the newly(!) created gas device, are the tariffs of electricity?!
(I noticed this in the existing device already, so I created a new one, but result is same).
But since you reinstalled the older version again and made changes to devices, I’m not sure what state your installation is in right now. If it works it works…
What do you advise: update to 9.x again, create new devices and update all flows? As in 8.x (see my previous post about gas-prices) I see several strange behaviours now. What’s the best approach (steps) to get PbtH ‘stable’ again?
Improvement(?):
I’ve not checked in V9 (maybe it’s already there), but it could be useful for charging cars to have a flow card that selects the cheapest blocks (of quarters/hours) to charge, not starting at clock hours (10, 11, 12, etc.). For the car switching charging on and off every 15 minutes by selecting the cheapest quarters purely is not recommended. So, I use ‘every hour’. Disadvantage is that only clock hours are considered (so, for example, the car starts charging at 13 hrs and stops at 14 hrs). While the cheapest hour (lowest average of 4 quarters) can be from 13.30 hrs to 14.30 hrs. So, the optimum in this ‘1 hour charging example’ is reached when the car starts at 13.30 hours for 1 hour charge period instead of 13.00 hrs. The card:
… could be extended/changed to something like ‘The price is one of [number] blocks of lowest [x quarters] until [time]’. For example, when settings are ‘The price is one of 3 blocks of lowest 4 quarters until 16.15’, this means that all possible blocks of 4 quarters (= 1 hr) until 16.15 hr are ranked and the 3 lowest (not overlapping) ranks (total of 3 x 4 quarters = 3 hours) until 16.15 hr the condition card output will be positive.
Is this possible/feasible (and clear what I mean?) or already implemented in V9?