search

home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.68k stars 29.95k forks source link

Tibber integration is not updated / devices removed #81037

Closed unik42 closed 1 year ago

unik42 commented 1 year ago

The problem

Tibber does not update any sensors. After removal of Tibber and reinstallalation, no devices or entities are populated. It is quite simply blank. 2022-10-26 (2)

What version of Home Assistant Core has the issue?

Home Assistant 2022.10.4

What was the last working version of Home Assistant Core?

Home Assistant 2022.10.4

What type of installation are you running?

Home Assistant OS

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

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

unik42 commented 1 year ago

Side note, does anyone that has a functioning Tibber integration have anything in this line, "homes": [, when running Homes in Tibber API explorer?

image

Stormbringer-67 commented 1 year ago

Nothing in "homes" here, Tibber integration working as it should in HA.

image

LAPDragnet commented 1 year ago

When I enable Tibber the integration runs fine for a little while (10-30 min?) and then HA core grows sluggish, sensors not shown on dashboard, history not loading etc, When I disable Tibber everything comes back to life again. If I wait "too" long I cannot use the web interface but I have to go to the console and reboot the core (and then, quickly, disable Tibber). The Tibber-app works without issues.

unik42 commented 1 year ago

Nothing in "homes" here, Tibber integration working as it should in HA.

image

Thank you. At least that is not an issue.

VikingKing commented 1 year ago

Seems like we have several issues here. My problem is that the integration loses contact with tibber on average every 9 hours. When this happens I have to restart the integraton. This is a problem for me as I use the power values in automations.

As a workaround I have made a automation that restarts the integration if the values have not been updated for the last 3 minutes.

unik42 commented 1 year ago

Quick question, if the log says 429 error, is the problem at Tibber or at my end? It seemed from Tibber that this was entirely my problem.

Logger: tibber Source: components/tibber/init.py:55 First occurred: 14. november 2022 kl. 10:25:57 (1157 occurrences) Last logged: 12:08:54

Error connecting to Tibber, resp code: 429

ztamas83 commented 1 year ago

It's the server telling you that you are sending too many requests and should back off. Normally this should be temporary. If Tibber puts a ban on your IP permanently it's another issue.

So normally 'your problem'

On Tue, 15 Nov 2022, 12:10 unik42, @.***> wrote:

Quick question, if the log says 429 error, is the problem at Tibber or at my end? It seemed from Tibber that this was entirely my problem.

Logger: tibber Source: components/tibber/init.py:55 First occurred: 14. november 2022 kl. 10:25:57 (1157 occurrences) Last logged: 12:08:54

Error connecting to Tibber, resp code: 429

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/81037#issuecomment-1315157565, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARB36Q2WAH4TAKLOMJRVLOTWINVTVANCNFSM6AAAAAARPH4UPA . You are receiving this because you were mentioned.Message ID: @.***>

unik42 commented 1 year ago

Noted. It never goes away. I can delete the Tibber integration for several days but still its the same error when I reinstall it. The only thing left is Tibber Pulse, maybe I should disconnect it and see if the problem fixes itself.

ztamas83 commented 1 year ago

some people report that Tibber permanently banned their IP. Worth to contact their support and ask.

On Tue, Nov 15, 2022 at 1:02 PM unik42 @.***> wrote:

Noted. It never goes away. I can delete the Tibber integration for several days but still its the same error when I reinstall it. The only thing left is Tibber Pulse, maybe I should disconnect it and see if the problem fixes itself.

— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/81037#issuecomment-1315212373, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARB36QZJRUKW2FF6TV5V7ODWIN3VNANCNFSM6AAAAAARPH4UPA . You are receiving this because you were mentioned.Message ID: @.***>

JBO-Home22 commented 1 year ago

I have same problem described before. When Tibber integration in HA is activated it will work for some hours (sometimes less a hour) than error 429 occurs and HA is raising CPU up to 80-100%. In this state its is not possible to login into the HA frontend. After restart it will work for some hours. I deactivated tibber integration for now. I am using Tibber with Tibber Pulse.

Is there any possibility to reduce frequency of API request in HA Integration ? Normaly once a minute should be enough .

Do you have an idea @Danielhiversen ?

Danielhiversen commented 1 year ago

@JBO-Home22 The integration is only supposed to do a few requests per day, so not sure what is wrong. I am currently not prioritizing this integration, so I have not spent any time looking at it.

JBO-Home22 commented 1 year ago

Thanks for the quick response.

Too bad it doesn't work anymore. I found this good to feed the energy dashboard with. so now there is no more possibility to do so. Maybe there is the possibility in a quieter phase to look here again.

Are there any users here who can use the tibber integration with tibber pulse in HA without problems?

dowermyr commented 1 year ago

@JBO-Home22 The integration is only supposed to do a few requests per day, so not sure what is wrong. I am currently not prioritizing this integration, so I have not spent any time looking at it.

HI! But polling a few times a day does not include Pulse, right? Is there anybody else who can help with this integration?

mariusjell commented 1 year ago

Seems this also causes a crash / reboot https://github.com/home-assistant/core/issues/81904

unik42 commented 1 year ago

I feel really stupid, but apparently I am unable to use Tibbers API explorer at home when I am not using VPN (Network error: Failed to fetch). But with VPN and from my office it works fine.

That should mean there is an IP ban?

ztamas83 commented 1 year ago

Yes, it really sounds like an IP ban. Contact TIbber.

unik42 commented 1 year ago

My problem has now been fixed. It seemed it was a two parter: 1) I created a second home in my Tibber app, which somehow messed up the integration. 2) I am guessing that during my problemsolving I probably triggered an IP ban.

It seems Tibber has removed the "home assistant" power up in the app. I can no longer find it.

corvy commented 1 year ago

Just for those that might be looking for an alternative, I am using this:

https://flows.nodered.org/node/node-red-contrib-tibber-api

In combination with this https://powersaver.no/ to get the live data now. Using the flow described here https://powersaver.no/examples/example-grid-tariff-capacity-part.html#get-live-data (you have to follow it to the bottom and establish the Node Red custom integration (https://github.com/zachowj/hass-node-red/blob/main/README.md#installation). This way I am back in business #76526

If you are not using powersaver to control consumption I would suggest you read through the examples on the powersaver.no page. This workaround seems to be working stable for me right now at least. And it has worked while the integration here has frozen and not updated data.

image

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

klokie commented 1 year ago

latest Home Assistant seems to have fixed the issue! Thanks

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.