PBTH has its own DAP (=spot price) driver. Add it as a device. Use that in stead of Tibber, and you will be able to add fixed and variable markups
Also you will be able to get rid of the flow you now use to update the actual price. And on top of that you will be able to use all the advanced flowcards that come with the DAP device to make optimal use of the knowledge of all coming prices.
Can anyone help me how to get the kWh this month and this year correct by entering the right values in the âThis month startâ and âThis Year startâ in the settings for Solax solar panels?
After a journey with several advanced flows (to control my home battery in relation to my solar panels and my car charger) I have started to use this PbtH app. I got it working.
I stop charging and discharging the battery when the available power is less than 200 Watt. Per battery! I have two of them (Sessy).
I notice that when the demand to deliver from the battery is less than 400 Watt they stop.
It looks like that the setting in the PbtH flowcard (minimum accu power) is multiplied by the number of batteries. I use 200 Watt as setting but it behaves like it was set to 400 Watt.
I expected that only one Sessy is being addressed to deliver the power from 200 Watt up to 400 Watt and that the app switches between the 2 batteries (to keep them more or less on the same level).
EDIT: Yesterday evening I watched the behaviour of discharging the batteries again. To my surprise it now works exactly as I expected.
From 200 to 400 Watt only one battery is delivering the power and they switch alternately. Above 400 Watt both deliver an equal amount of power.
I didnât change anything⌠.
NiceâŚ, so there is no issue here. Lessons learned
Every day at 13:00, when the power price for the next day is set, the price for the current day is messed up. My flows donât work.
Price now is wrong, lowest/highest price this day and more, all are gone.
The screenshot shows average price this day, every day at 13:00 it drops.
It is correct again one hour later, at 14:00. Except yesterday when it reverts to normal at 17:00.
I have noticed that other also have seen this problem
What could cause this?
Edit: the values are changed correctly at 13:00
Two minutes later (13:02), the current âprice nowâ is changed to a wrong value.
Average price goes to ZERO.
Something is wrong here. @Gruijter ?
Period from 12:00 to 13:00
Price now is the same as Tibber, 0,4517 NOK.
Period from 13:00 to 14:00
At 13:00, PBTH change to 0,3913 which is also the same as Tibber, correct so far.
However, 2 minutes later, PBTH change âprice nowâ to 0,4697, which is WRONG.
Also average price today (now set to ZERO) is wrong, and lowest/highest price today is blank.
Any clue?
Thanks!
Wanted to download this app for a few days now, but i canât install it on my Homey. It will be a new install. Tried it via web, via the app. Both say âwill be downloaded on your Homey shortlyâ, but it actually wonât. Tried restarting my Homey and do it all over, wonât work.
@Peter_Kawa
Thanks! Couldnât find the issue myself elsewhere. Tried installing other apps which did work, so thatâs why I thought I let the dev know
Thanks again!
Sorry if Imissed someone else already posting this question, or suggestion, but Iâd really appreciate if the app could allow the user to configure if negative values i.e. solar panels production to grid should be dedudcted from total consumption or not. Currently I get negative totals, which might be an indication of the balancee between consumption and production but itâs not the number Iâm mostly interested in why a configutable option would be ideal! Oh, and Iâm not using a Homey power meter, but a HomeWizard - which I assume makes a difference to whatâs possible..
Thanks, and regardless of this Iâll continue using the app as I think itâs great!
Do I understant it corectly that you want separate summarizers for imported and exported energy from the grid? Thatâs how I like it at least, and those meters are available in HomeWizard.
The only solution Iâve found is to add a layer between HomeWizard and PBTH using the Device Capabilities app. That lets me create two virtual devices that reflect the two meters (Sum consumed and Sum returned) from HomeWizard as power sensors that the PBTH summarizers can pick up individually.
Itâs a roundabout way of doing things, I would have preferred if I could directly pick which meter the summarizer should use, but it works with the virtual devices.
I honestly donât know what Iâm asking But yeah, a separation of the two channels for import and export would probably be the ideal way - and if anyone would have use for the combination, it would most likely be possible to add them up in a flow or a script either directly or using variables. If I look at the HomeWizard app, it seem to separate them why I assume itâs supported in hardware and the P1 interface itself - but then again, Iâm not a developer so this is purely from what I can see in the app.
Homewizard app has a âDaily usageâ capability, this subtracts the delivered energy from the consumed energy.
However, it has no knowledge of solar production, so to calculate the actual daily energy usage of your home:
(
gross generation: total generated solar daily energy, according to the inverter(s) minus
Gross feed-in: delivered (sold) daily energy to the grid, according to the grid operatorâs energy meter ) plus
Gross consumption: consumed (purchased) daily energy from the grid, according to the network operatorâs energy meter
Yep, figuring out the actual consumption of the household is a different kettle of fish. I donât see any âDaily usageâ from my Homewizard P1, but as long as you have access to the meter in the solar inverter(s) calculating the use of your home can be done using only the information from the Homewizard app, but if you want to use a PBTH summarizer for statistics I think youâll need a virtual device for that.
But I think having separate summarizers for import and export makes sense for a lot of users, especially in countries where net metering (salderingsregeling) is less common or non-existent.