[APP][Pro] Power Price

I’m really a bit stupid and don’t understand what he’s doing. Personally, I find it so annoying to say that I don’t understand. I’ve done everything you tell me and it still doesn’t work.

I now have -849 kWh for the Quooker and I would have spent -1160.24 euros. You understand, something is wrong, although I now have prices, I didn’t have that at all before. Now I don’t know if I should wait a bit until the Quooker has been on again, so that this information will adjust itself?

I also wonder if I’m using the correct #Tariefactief, #Energie, #Power?! I assume so, but I’m not sure because you have so much choice.


To make a proper comparison you need to provide a tariff price (f.e. 0.32) and a kWh meter count (f.e. Energie variable)

Make sure you have selected the correct socket variable (#energie), I had similar issues but that was due to comparing 2 different devices :sweat_smile:.

1 Like

I think I’m doing something wrong. I can’t get it at a normal price. I don’t know what’s wrong, everything is, I think, good. I will send some examples, maybe someone sees what my problem is?!


I’m sorry I can’t help you. There are a lot of variables in these setup, this is only know or visible for yourself.

Seeing the first 2 screenshots are confusing to me as well, I don’t know what kind they are.
Seeing that Power Price device is reporting in MWh I came only suggest to check the data you provide this device. I think there is some configuration wrong in the given data.
Again this is something I can’t see from screenshots only in person for flow config you can check this. Hovering on the variable shows it’s source. (Via web app)

1 Like

What does this setting do? I have read the description, but don’t understand it :blush:.

Which values are updated? Does it retrospectively recalculate the monetary value/session costs on a price change? Or in other words, apply the new price tariff from the start of the session instead of as of the moment the price change occurred?

@SunBeech if you run the update card it will automatically update the sensor values of the device

Normally that only happens when you end the session.

I am comparing the Flow Utilities app (which I currently use for session summaries) with the Power Price app.

I like the simpler flow cards/easier usage, and the fact that you can apply tariff changes to an already running session.

The Power Price app also has this convenient card that formats the kWh cost in the local format. In my case a comma as decimal separator:

If I am correct, there is no such card to format the session usage (kWh) in the local format: it is displayed in the default formatting using a period as decimal separator. Are you considering to also add a similar card for the session usage?

The Flow Utilities app has an additional numeric tag that includes the number of seconds the session lasted. This tag makes it easy to apply own/custom formatting, that deviates from the standard formatted duration. Are you considering to also add a similar numeric tag?

2 Likes

Thanks for your feedback and suggestions.

I didn’t realize until now that (at least in NL) the formatting for kWh is different than we now show. We now show an international standard for number values where “.” Is the decimal separator. But in NL we use “,” as decimal separator.
Since there is no kWh formatting function in JavaScript like we have for currency available. I need to lookup how tos solve this without a lot of code writing with custom values.

The duration in seconds is nice to add indeed, I will add it to our to-do list.

2 Likes

Question regarding the numeric tags available in Power Price. It seems that the # Sessie verbruik and # Sessie kosten tags are rounded. If I format them with additional decimals, they show up as 0 instead of the actual values.

For example I have a session that summarizes kWh. The session result is 0.01 kWh (# Sessie verbruik tag). The energy tariff during the session is 0.22391. Multiplying both yields an expected session cost of: 0.0022391. Power Price indicates in its # Sessie kosten tag a cost of 0. If I format the tag to display e.g. four decimals, the results is 0.0000, while I would expect 0.0022.

Are those tags indeed rounded? And if so, would it be an idea to include an option in the settings to configure the number of decimals stored in the tag? Or perhaps do not round the tag itself, but only use rounding when retrieving the session costs via the dedicated flow card.