[APP][Pro] Power by the Hour: Insights per hour, day, month and year

Apps
,
3894

v8.9.2 is ready for testing: Power by the Hour | Homey

  • Improve import/export detection and price usage
  • Fetch DAP prices immediately after new device pair
  • Refactoring and stability improvements
3895

Someone could you share a tutorial to create. Virtual device where I can see my remuneration from tso? Quarter price (north Italy price) x quarter volumes? Many thanks

3896

To increase accuracy in the game of managing solar panels and charging batteries at negative market prices, I requested an ENTSO-E API key. Looking at the documentation, it shouldn’t be a problem to run two Homeys on the same API key. Surely PBHT doesn’t request data 400 times a minute?

https://transparencyplatform.zendesk.com/hc/en-us/articles/12783148966036-API-Rate-Limit-Part-1

3897

Not an issue at all. Why do you ask?

3898

Because I run two Homeys via PBTH. An HP’23, and my old HP’19 which is currently handling things at my mother’s place. Some APIs are more limited. Solis, for example, can be called once every 3 minutes. Solcast can be called 10 times a day. So that is why I was wondering.

3899

My gas prices are back :clap: since version 8.9.2

3900

Thanks for all your good work w.r.t. Homey apps. PBTH is a really useful add-on to the Homey functions.

Now more and more Homey users (at least in the Netherlands) are faced with asymmetrical pricing (Tibber does not return the €0.0248 markup when uploading energy from the solar panels. Next year when the ‘saldering’ ends the tax of €0.1108 is not returned either. Could it be an option to have an extra parameter in the price calculation (if{@P1>0;0.13256;0}) or choose in each PBTH device which tariff function to use?

Or has this situation been solved already in another way?

3901

Is already in it. Price now, and price now (export)

IMG_4284
IMG_42841179×2556 248 KB

3902

Thanks. Good to know. I’m affraid I missed it before.

3903

However, the summarised money calculations (daily, monthly, etc.) are not using the ‘export fixed markup per kWh’ (Export vaste opslag → ‘teruglevergoeding’) correctly. I checked since 1 May and every day the difference between the ‘money per day’ my energy company calculates and the PbtH app calculates is exactly equal to the difference between the import and export price (multiplied by the corresponding kWh).

To check if my energy company is wrong or the PbtH calculations are wrong (or my settings in PbtH were wrong), I created a flow that’s also calculating the daily/monthly/yearly cost (just math: € x kWh per 15 minutes, import and export and summed per day, month and year) and the results are 100% equal to the data my energy company reports. I shared my settings and results with @Gruijter, but he can’t find anything wrong in my settings or in his code. Weird, but I’m 100% sure my calculations are mathematical correct and, again, matches 100% with the energy company data.

If you don’t use a ‘export fixed markup’ (in order to include a ‘teruglevergoeding per kWh’), I think the PbtH calculations are correct (and should match 100% with the data of any energy company).

3904

New version 8.9.3 is ready for testing: https://homey.app/a/com.gruijter.powerhour/test/

  • Fix export monetary values
  • Reduce persistent power writes
  • Stability improvements
  • Homey-api@3.19.0

@Marcel_R I eventually did find something in how export prices are handled. Can you check if this version results in correct monetary values for you? It now will net the total exported kWh and imported kWh per 15 minute period, and then uses either the export or the import tariff. This is how (I hope!) all (or most?) power companies bill. But if the energy company bills the imported and exported kWh meters completely separate from one another, I would need to implement a big change in the architecture of PbtH. So I hope this fix works for you!

3905

First test (=1 day) results are positive! :smiley: Monetary calculations PbtH makes now do exactly match with my calculations and calculations of energy company.

In theory they should all measure (and calculate €) the same way. There is basically only one correct way: usage&return kWh x tariff € (usage&return) = invoice. Of course (only!) a few cents monthly can be explained by rounding off differently.

The way energy companies report the data can differ. My energy company doesn’t report the nett usage, but the used and returned power separately, so a simple calculation is required for the nett usage/payment (whoever wants/needs can create flows/scripts for this, in my opinion no need to change PbtH). However, the nett usage/due payment (= calculated by PbtH) is ‘universal’ and seems to be correct in this new release (and wasn’t in previous releases). Thanks!

3906

Are you sure this is done by ALL energy providers in ALL EU?

3907

Not ALL EU (well, in theory, it should, but I don’t know for all EU countries), but energy companies in Netherlands are monitored (ACM). The calculation should be same, the tariffs (flex per kWh and fixed, like daily costs, etc.) of course can vary (but all tariffs charged must be available for customers).

3908

@PvWoody many Thx for you donation. Much appreciated! :heart::clinking_beer_mugs:

3909

I have constant problem with prices. At midnight it resets all hourly prices to one lowest price of a day and thats it!

image
image498×777 32.3 KB

3910

Here also problems. I think after the update of Homey today

IMG_1296
IMG_12961179×2556 191 KB

IMG_1295
IMG_12951179×2556 142 KB

3911

I think it’s not the Homey update. I have a 2019 Homey pro and didn’t installed the new firmware yet. And i have the same issue. Maybe something with the Homey API.

3912

I noticed it few weeks ago and now i just keep an eye on that and it happens pretty often
right now i disabled all flows using it


3913

I use my own ENTSO-E API key, no problems noticed same price as Zonneplan gives me.