new test version 6.2.1: Power by the Hour | Homey
Thx @DirkG for the German translation update!
@Torch1969 @CaptainVoni I created a quick untested fix (I hope) for the missing forecast between 13 and 14 hours. Can you please test?
If the translation is wrong or unclear, please let me know. The latest translations mainly refer to (PV) batteries. As I donât own any myself, Iâm not familiar with the right wording.
Thx!
Installed the test version and checked a few times after 13:00: prices came in early today at 13:03 (of course 
). Until then I saw estimated prices and after that the prices for tomorrow were the actual prices. I never had at any time no prices for tomorrow.
I will keep an eye on this in the next days and try to catch a day when prices come in late.
Iâm trying to understand the âThe price is one of the number lowest in the period hours before time oâclockâ card. Iâm trying to use this to figure out when to charge my car. I only want it to charge after 19:00, and be fully charged by 07:00 the next morning. I might be connecting it before 19, and I might be connecting it after that time. Iâm getting the number of hours of charging needed to reach the cap from another app, and Iâm running the flow to check both once you connect the car, and every hour.
If I do for instance âThe price is one of the 3 lowest in the 12 hours before 7 oâclockâ, will it then look at the price right now and see if it is lower or equal to any of the 3 lowest hours in the hours between 19:00 that night and 7 the next morning?
If yes⌠What happens if itâs 20:00 at night? Will it then only look at the next 11 hours?
If no, what exactly does it do?
Hi @Gruijter
I am wondering if there is a way to have a virtual DAP or a DAP with a virtual (non EU) country (where I can set the current price myself), so its price can be used by the PBTH power summarize devices.
(I hesitate to create a flow where I overwrite the price of an existing DAP that keeps updating hourly.)
For âexternalâ sources you can only send the current price to a price group via a flow. And you can do that as often as needed (e.g. every hour).
But there is no way to use future prices. Only the EU (ENTSO-E) can be used as source for that.
What is a price group?
That is exactly what it does. The card will be true during the 3 lowest hours in the 12 hours before 7 oâclock 
12 hours before 07:00 starts at 19:00 (in the evening), and includes all hours untill and including 06:00 next morning. So the card will give âtrueâ if the price of the current hour is one of the 3 lowest.
No. It looks at the 12 hours starting at 19:00
You can set every summarizer (e.g. a power socket or your main meter) to be part of a price group. By default that price group is â1â. A DAP sends its current price every hour to a selected price group (By default it is disabled, so you need to set it to â1â when you want all summarizers to use the DAP price).
Alternatively to using DAP you can send any price to any price group via a flow. So that is what you need to do to use your external source.
Found it. I am sorry that I did not see it before. Thank you.
I will keep an eye on this also, but as @CaptainVoni says, we have to wait until this specific situation occursâŚâŚ
So itâll look at the previous hour as well then? So if I want to know the lowest in the coming hours Iâll need to do some math to count the number of hours until 7 and then add that into the place where I had 12 in the original post?
Hello! Iâm looking for this use case: every morning at 9am send an email (or telegram) the graph insight of per-hour usage of the previous day as per below. Is it something feasible?
@Torch1969 @CaptainVoni I created a quick untested fix (I hope) for the missing forecast between 13 and 14 hours. Can you please test?
@Gruijter Today prices came in late. Shortly after 13:00 I saw the following:
Take a close look at the prices for âtomorrowâ in the chart for âNext hoursâ.
I requested also the JSON for the next hours:
{"0":0.1274,"1":0.1521,"2":0.1777,"3":0.1875,"4":0.1965,"5":0.2026,"6":0.1965,"7":0.1915,"8":0.1821,"9":0.1734,"10":0.1616,"11":0.1818,"12":0.1576,"13":0.1534,"14":0.1512,"15":0.1538,"16":0.1623,"17":0.1745,"18":0.1856,"19":0.191,"20":0.189,"21":0.1816,"22":0.1733,"23":0.1683,"24":0.169,"25":0.175,"26":0.1842,"27":0.1935,"28":0.2,"29":0.2015,"30":0.1976,"31":0.1897,"32":0.1806,"33":0.1728,"34":0.1673}
At 14:03 the prices were updated:
And here is the JSON for the next hours requested shortly afterwards.
{"0":0.1521,"1":0.1777,"2":0.1875,"3":0.1965,"4":0.2026,"5":0.1965,"6":0.1915,"7":0.1821,"8":0.1734,"9":0.1616,"10":0.1524,"11":0.1483,"12":0.1619,"13":0.1457,"14":0.1355,"15":0.1497,"16":0.1869,"17":0.1965,"18":0.1923,"19":0.1826,"20":0.1733,"21":0.1619,"22":0.1513,"23":0.15,"24":0.1594,"25":0.1727,"26":0.1797,"27":0.1903,"28":0.1915,"29":0.1915,"30":0.1867,"31":0.1811,"32":0.1694,"33":0.1622,"34":0.1818,"35":0.1576,"36":0.1534,"37":0.1512,"38":0.1538,"39":0.1623,"40":0.1745,"41":0.1856,"42":0.191,"43":0.189,"44":0.1816,"45":0.1733,"46":0.1683,"47":0.169,"48":0.175,"49":0.1842,"50":0.1935,"51":0.2,"52":0.2015,"53":0.1976,"54":0.1897,"55":0.1806,"56":0.1728,"57":0.1673}
So when prices are late:
Hope this helps.
Would it be possible to indicate somehow from which hour on prices are just estimates, i.e. as additional flow tag returned by âProvide prices JSON for XXXâ?
Good morning
I want to change the fixed price per flow on several Power by the hour devices.
I use the flow card for each device.
But I see that not all of them are updated.
What could be the reason?
Best regards
In the advanced settings of the PbtH devices, the same number of the Update group of the Flow card Set electricity tariff to must be filled into the menu item Tariff update group (Flow or DAP)
Itâs OK
Thank you so much
Best regards
Hi,
I am still having issues with both negative readings a few times a week and lost connection to the unit. I have 9 different units connected to a PBTH Summarizer. They all lose connection and stop reading. Leaving the small text under the reading saying â2 days agoâ for example. Even though the unit is still working and a reboot of POTH or the Homey fixes the issue. Then it works for a few days then stops again. This goes for both Tibber Pulse and a Shelly devices.
I have created a virtual unit that update from the same unit but from a flow and this never has any issues, keeps working even if the other stops.
So to my questions since I have found a work around. I donât want to discard over 1 year of data. Can this data be âmovedâ to the virtual unit? Or can it be possible to disconnect the POTH unit from for example Tibber Pulse and start to update the reading from a flow instead? Change the source from Homey unit to virtual?
