Tibber price level just showing HIGH #130113
Comments
|
Hey there @Danielhiversen, mind taking a look at this issue as it has been labeled with an integration ( Code owner commandsCode owners of
(message by CodeOwnersMention) tibber documentation |
|
This works fine for me. And also, what does the action On another note, this was a breaking change that caused some headaches that price_level is now LOW/NORMAL/HIGH instead of the more detailed |
|
Thanks for fast respons! action: tibber.get_prices return:
|
|
Probably not coming back, it was a change in pyTibber Danielhiversen/pyTibber#317 that wasn't marked as breaking. But yes, it broke my automations too. template:
- sensor:
- name: Electricity Price Level
unique_id: electricity_price_level
state: >-
{%- set price = float(states('sensor.electricity_price_infinity_8'), default=-10000) -%}
{%- set avg_price = float(state_attr('sensor.electricity_price_infinity_8', 'avg_price'), default=0) -%}
{% if price > -10000 %}
{{- 'SUPER_CHEAP' if price <= avg_price*0.4 -}}
{{- 'VERY_CHEAP' if price <= avg_price*0.5 and price > avg_price*0.4 -}}
{{- 'CHEAP' if price > avg_price*0.5 and price <= avg_price*0.9 -}}
{{- 'NORMAL' if price > avg_price*0.9 and price < avg_price*1.15 -}}
{{- 'EXPENSIVE' if price >= avg_price*1.15 and price < avg_price*1.4 -}}
{{- 'VERY_EXPENSIVE' if price >= avg_price*1.4 }}
{%else%}
unknown
{%endif%}Adjust interals as needed. Below is the Tibber definitions: |
|
Okey! Thanks for the help:) |
|
I did not know Tibber has two different price levels :( So now I am unsure what to do. Changing it back will be another breaking change :/ |
|
For me, the solution above seems to work. Less work to change the automations. Also didn't know they had several price levels. |
|
yeah something is broken. PriceLevelPrice level based on trailing price average (3 days for hourly values and 30 days for daily values)
PriceRatingLevel
|
|
@Danielhiversen and @perosb
|
|
yes I know. The old priceInfo would have given you the below for today and basically the same for tomorrow which is even cheaper ~0....so it depends. "today": [
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "CHEAP"},
{"level": "CHEAP"},
{"level": "CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"},
{"level": "VERY_CHEAP"}and this is with priceRating today: {"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"},
{"level": "LOW"}, |
|
@perosb : in my case (see price diagram i posted, it is today) i would have NORMAL over the whole day with the custom sensor which makes it impossible to control your consumers. Maybe your regional price is lower (?)
|
|
Because: Price Level provides a simple categorization of the current electricity price compared to the average of the last three days (e.g., “cheap”, “expensive”). |
|
@Danielhiversen |
|
Meanwhile you can just create a statistical helper calculating whatever mean/average for any period and use that in the template. |
Seriously, you work as a "data scientist" at Tibber and claim that you don't know that your company maintains and provides different attributes at the price? Somehow I can't believe that. But anyway, thanks for your work on the Tibber integration. Is Tibber actually paying you for this? Or are you allowed to work on it during your working hours? |
|
I vote for bringing back the price level as provided by the Api. Let's see if I find some spare time to propose the necessary changes. |
|
I only work on this in my spare time, and I have nothing to do with the api for my work. I should still have read the documentation before I changed it. Any contribution is much appreciated |
|
I asked the Tibber support about this Issue and they stated that all values of PriceLevel (CHEAP, EXPENSIVE...) are still active and nothing was changed there. They expect the issue in the HomeAssistant tibber integration. Could it be that the Integration takes now PriceRatinglevel (LOW, HIGH..) and assigns it to PriceLevel? The enity PriceRatinglevel is also not present at all in HA. I can also ask the tibber support for additional details about the API if somebody tells me what to ask :) |
That is correct, as written here: #130113 (comment) |
|
Oh sorry, this comment I didn't got. But why would it be a breaking change to put the Entity Price_Level back to PriceLevel and create a new Entity for PriceRatinglevel? Then both is in and PriceLevel is same as before. |
It will be a breaking change for those who now have started to use the new PriceRatinglevel, they would need to update their automations again |
|
I would love to change my automations back to the price level with 3 day rolling average. The price rating level is too insensitive especially in the last weeks my automations did not work very well. Most of the time showing HIGH. Everything worked flawless the whole year and now I need to manually interact on and on due to this change. I think the Tibber price level with 3days rolling average was very well thought out by the programmer and makes a lot of sense. I still can’t understand why we at least can’t have this back as an additional attribute if the price rating needs to be kept. |
We can for sure. But someone need to do the job :) |
|
First of all, thanks to whoever programmed it. However, I think that when such a major change is made, and it leads to problems, it should be reversed immediately, and you shouldn't wait until everyone comes up with their own solution, because that leads to a loss of trust and also means that support is reduced. The old parameters had 5 distinctions and not just 3, which allowed for better control. Therefore, the old state should be restored as quickly as possible and, if necessary, an additional sensor should be provided that only has 3 parameters. |
|
It can not simple be reverted, since it was part of bug fix. |
|
What are the options? |
|
I would suggest to make a fix to use PriceLevel instead of PriceRatinglevel for the price attribute |
There was no big change nor a change on Tibbers API. Just a bug since HA Core handle stuff different. Only the reference to the an API response changed here. |
|
I don't want to put pressure on you, but is there a schedule for the adaptation? |
|
@ansgarkewitz Maybe you can revert your home assistant to 2024.9.3 until this is fixed - I just did. |
|
Hello i already configured a solution based on the above template and calculating an average over 72h. So i dont need any amendments |
|
Any updates? is the 5-level price information coming back ? my automations depend on this |
I have this code but stays at 'NORMAL' but the the price is high now, does it take a while to build the average and showing correct? |
The problem is it uses the average of the day and not the average of three days which the price level attribute of Tibber does. I was already pointing to this in this thread (see above) . As many others I would like to have the original Tibber attribute back and not the erroneously added attribute which still is wrong and wrongly named in the Homeassistant integration. The only sense using the Homeassistant Tibber integration is to automate your consumers depending on price level attribute without need to write your own code to query the API. Without having the attributes identical matched to the Tibber API the whole thing makes no sense. |
|
yes, you are right. I will call them tomorrow, see what happens |
You wanna call Tibber? That's useless. Their API offer both price levels. And you choose with your API call which price level you like to get. So what should Tibber do there? The one and only developer here didn't know that there are to price levels and changed it by mistake. |
|
Thank you TylonHH
I misunderstood.
How to get the 5-level price back from the API ?
thanks
From: TylonHH ***@***.***>
Sent: zaterdag 14 december 2024 10:05
To: home-assistant/core ***@***.***>
Cc: madebywitteveen ***@***.***>; Comment ***@***.***>
Subject: Re: [home-assistant/core] Tibber price level just showing HIGH (Issue #130113)
I will call them tomorrow
You wanna call Tibber? That's useless. Their API offer both price levels. And you choose with your API call which price level you like to get. So what should Tibber do there?
That's why we have here workaround with the correct API call.
The one and only developer here didn't know that there are to price levels and changed it by mistake.
That's how I understand the situation here.
—
Reply to this email directly, view it on GitHub <#130113 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/APEZVYXD27UNVCYIV67NAAT2FPYCTAVCNFSM6AAAAABRNAI3EGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBTGAYTINRVGA> .
You are receiving this because you commented. <https://github.com/notifications/beacon/APEZVYVICGIQ3OVIH7W3L7T2FPYCTA5CNFSM6AAAAABRNAI3EGWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUXSNJPU.gif> Message ID: ***@***.*** ***@***.***> >
|
|
For those who only need the original (3 day average price based) price level for their automations here my code for the API query sensor. |
Better solution (less API req and faster change each hour) is to change |
|
@james-1987 : thanks for your input. What time are you using for scan interval in the sensor? Do I understand it right that you use a very long scan interval say more then one hour. But your automation triggers the sensor update over the automation hourly? |
|
@Arturfrain I use 99999 as value, it doesn't really matter. All request is pushed from the automation and not the RESTful sensor. The Best approach without automation is to have a really slim 360 second/6 minutes is to long time to change to new value. Bad hit and your heavy electrical load can be ON to an old value for 6min. With high value like 3600s/1h it can hit "sometime" every hour, it can trigger on the 59 minute (BAD), then you only having right value 1 minute and bad value the rest of the 59 minute. No problems. |
|
@james-1987 : thank you, that makes absolutely sense. I will change my setup now 😀 |
The problem
Price level in Tibber has started to show only HIGH regardless of price.
What version of Home Assistant Core has the issue?
core-2024.11.0
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
Tibber
Link to integration documentation on our website
https://www.home-assistant.io/integrations/tibber
Diagnostics information
No response
Example YAML snippet
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: