This version includes the latest refinements of support for reduced electricity tax - the README is here:
Reduced electricity tax is now supported in two ways:
Thing configuration: Used for thing action calculations.
Channel: Used by users by preferring reduced channel over the normal channel.
I don’t think it makes much sense to switch between the two rates when meter hits 4000 kWh.
When you are entitled to the reduced rate, it can relatively safely be assumed that the heating itself will consume those 4000 kWh. So for anything else, it would make sense to use the reduced rate. However, this is now entirely up to the user and can be considered a matter of preference.
I like the idea. But after I have spend a few days thinking whats best option. I have come to the conclusion, thats it all depends on, what the user want to use the info for.
My electricity company calculate my household will consume 333kWh/month with full price, and the rest will be calculated with reduced price, not matter if I use 333kWh/month or not. (12/4000kWh).
In a year my whole household consumes >12.000kWh, (I have an electric car, which consume alot). So their calculation is fair enough. But its impossible to calculate to show the correct price in each hour.
I have a problem getting the Transmision Tarrif. It is just undef. Dont know if this is the right way to comment on it.
I am using “Vores Elnet” with GLN “5790000610976”. I have been debugging a bit, and it seems like a problem with the request to the energidataservice api.
I have mananaged to make a query that resolves the right values for my installation. I think there is a problem when using the filter-option / parameter “start” in the query.
Here you need to find the right period with “ValidFrom” “2023-12-31” and ValidTo “2024-02-01”.
Its really strangely undocumentet the use of the energidataservice api, so I understand why it is hard to work with. Maybe you found some better info than me, or just figured it out.
If I in any way add the parameter “start” to the request. I will not get the right period shown. So maybe you need to just remove it and iterate though the data to find the right dataset?
I can of couse solve it manualy, but it would be of greater value just to be able to use this great binding.
I assume you mean grid tariff (nettarif in Danish). The default filter for Vores Elnet is defined here:
When I created that filter, the tariffs were defined day by day, so it was needed to provide such a limiting filter. Providing start of year, for example, back then, would have resulted in 365 records per year, so it exceeded the number of records allowed resulting in truncation at 200 records, IIRC. It seems that they changed something (for the better), so we can now use a fixed cut-off date, 2023-12-31.
You can configure the channel to get this fixed immediately:
So for the time being I will not update the default filter, since changing it into a fixed cut-off date will not work well when there are many records (i.e. day by day) as previously mentioned. So I would advise to use the custom filter provided above until February and then see if it will start working again without the channel configuration.
Some of you may have noticed service outage between 12th and 15th of April. This exposed a few things in the binding that could be improved. I created this issue to keep track of it, and all is included in 4.2:
