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.
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)
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?
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?
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.
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.
I did some investigation and found out that this is default Homey behaviour. See screenshot below on a log from our stored data where we do calculations with:
It’s in the Homey UI where the rounding takes place. So this will show in the device capabilities and the variables.
Homey does supply a capability decimal setting for number type values, however I didn’t get this to work in the UI
Also this is a fixed setting and can’t be configured via device settings.
The screenshot shows a running/active session on Jan 18th. The data included is of the last completed session (on Jan 14th), while the timestamp is of the last update of the active session (Jan 18th). This might be confusing. Would it not make more sense to display the timestamp of the last completed session? So all data elements relate to each other.
The duration field is capped when the icon is displayed.
The timestamp is representing the last update of the widget, since this is live updating when this device setting is set and device is running. When this is not set by the user it makes sense to reflect the last end of a session.
If I would enable it, will the session values/capabilities be updated continuously while a session is running? Or only after a tariff/price change, as the setting’s description indicates?
Devices that not have triggered the update/end session cards yet show still the current date from updating the widget. Since this data will be stored from version > 2.1.1.
Also when a new device is added without having a updated or completed session this will be the default behaviour.
If I look at the insights in the Power Pro device, it seems like the last session’s kWh value is continued until the start or end (not sure) of the next session. The result is that if, for instance I watch TV for 1 hour and then don’t watch TV for the next 2 days, the kWh value of the 1 hour session keeps being reported during the next days until I start a new session. This way it seems like I had that energy consumption during those 2+ days.
I would expect that the kWh value is only reported between the start and end points of a session (or only at the end point, as it is an accumulation). And that between sessions the kWh is 0.
But maybe I am misunderstanding how these insights work . Perhaps you could explain.
.
.
TEST: 
