yes, I would try that.
Do check v9. There is a new advanced smart car charge driver now
yes, I would try that.
Do check v9. There is a new advanced smart car charge driver now
The prices you see in the flow editor are only example values that Homey shows for every “New prices received” card; they are the same for power and gas. When the card actually runs, the tags hold the real gas prices of your device (TTF LEBA EasyEnergy, per m³). Your gas device is set up correctly.
The next v9 test version will have this. The action card “Find the cheapest block of [6] hours in the next [12] hours, before [06:00]” gets a new tag, “Price limit (separate hours)”. It is the highest price among the 6 cheapest hours in that window, also when those hours are not consecutive. With “most expensive” it is the lowest price among the most expensive hours.
So a flow at a new price period could be: run this card, then send the “Price limit” tag to the Go-e charger. Within that window, the charger then charges in exactly the cheapest hours.
Ok, but also confusing:
In the next version there will be a setting for EV charger: minimum charging time setting; shorter pauses bridged, short sessions extended.
By default 15 minute gaps will be bridged. You can adjust the bridge time.
Thx for the feedback. I will try to make the examples more clear/generic. Unfortunately due to the app architecture and Homey limitations it doesnt get much better.
I don’t think (based on first impression) the somewhat fixed driver can meet the requirements of every user (this should probably result in a huge number of settings). To be honest, I don’t use the PbtH drivers and build my own flows and scripts as the drivers limits flexibility and insight in the processes (behind the drivers) is missing. Moreover, it seems (after a quick look into the driver settings), the function I described is not part of the driver as well and I don’t think the new flow cards covers this. Correct?
New version 9.0.3 is ready as test:
homey.app

Your own energy management system: smart home battery, EV charging and appliances on prices and solar.
I don’t think (based on first impression) the somewhat fixed driver can meet the requirements of every user
Meet every user is impossible. And one of the goals of v9 is to keep it simple (so reduce the number of settings and flow cards). But IMO the ev charger driver does cover a lot, and even more than what you ever can achieve with flows (without using scripts). E.g. the evCharger takes forecasts of solar and in-house-usage into its calculations. Especially with non-symetric import vs export pricing and solar, it will be hard for you to improve the drivers’ in-built planning using flows.
But I do want to keep giving power users like yourself the option to use flows and get more control of what is happening. So if there really is a flow you used to have in v8 that is not possible anymore in v9, let me know. Please include the v8 flow (screenshot) and a description of what you want to achieve.
where the charging must be able to start on every quarter instead of the actual ‘every hour
With a 15-minute price device, all price cards work per quarter, so a block can start on any quarter. What’s there now:
“x cheapest blocks of y duration” is not there. What do you need the block length y for? If it’s to avoid short stops: in 9.0.3 the EV charger driver has a minimum charging time that bridges short pauses.
Thx for the feedback. This is with v9.0.3?
Edit: confirmed. In v9 the chart is drawn a little later than the trigger fires. Will be fixed in the next version.
That card in your screenshot is the right one. What exactly is missing: is your device not in the list, does the card show as unavailable, or are you looking for another card?
Note: there is a new card now, but the name is exactly the same as the old one. So when you are trying to replace the card you just need to replace it with the ‘same’ card.
For test I created a new virtual device but only 2 tariff cards are available:
look one level up. It is under the app, not under device. But I will double check why that is that way again (because I dont remember why I built it that way)
Edit: In the next version the card will be under the device itself.