Tibber has become very unstable over the past week #100410
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 |
|
Is it the data from Tibber Pulse that is unstable? |
|
has_real_time_consumption": null So the api report that you do not have any connected pulse |
|
I had the same problem for a long time but it has become unbearable since 1 or 2 weeks. Today, the integration has not reported new Pulse values for 16 hours until i reloaded it. The Tibber app still had live data. Taken from the log, right when the connection broke: After that, and even after reloading the integration, the log is spammed with this entry every 10 seconds: The diagnostic information reports Please note that the initial connection problems might be on my end, so maybe the integration never recovers from that. |
|
@0x442E472E You are not using the latest version of pyTibber, so please upgrade. |
That's not the case. I have real-time data in the app. |
|
Im also having a lot of instability with the readings from my tibber pulse. the data is showing unavailable a lot. and sometimes is just does not update the data for a long time. Diagnostics data:{ And i activated debug log for tibber and this is what im getting in the log: |
|
@zimm-se The logs says Home Assistant lost connection with Tibber server and then it reconnects, so I think it is either unstable network connection at your place or issues at Tibber. It always reconnects by itself? |
|
@Danielhiversen thanks for responding. I have no other network stability issues. The internet connection is a 250 Mbit/s fiber connection. The Wifi AP's im using are TP-link Omada EAP653's, the one its connected to is 2 meters from the pulse in the same room. Its showing -36 dBm signal strength atm. Even if im not home when it messes up i have no issues doing other stuff from my home network and my home assistant. Like watching live feeds from survailance cameras and so on. I cant say for sure that it will always reconnect. Its been that much of an issue for me that i put a automation to notify me on my phone when it has lost the pulse data for 20 minutes. Then i usually go in and restart tibber. That will bring it back most of the time. Im also counting every time its showing "unavailable" even if it happens for a short time and recovers. Yesterday that happend 10 times. Today its happend 1 time so far. Is there anything else i should put in place to isolate the issue? or is there a known issue at tibbers end? |
|
Hi @Danielhiversen got my tibber itnergration running since 4 days, and can confirm the issue, tibber lost conntion to its server and did not update any entities for the whole night. For me I looks like the issue is somehow that the tibber integration is not able to reconnect if the connection lost once. And same here, tibber app i showing the value also during the downtime phase in HASS, rssi is fine and not other device are complaining about a lost internet connection As soon as I reloaded the integration withing HASS settings the entity values came up again as expected. |
|
Same problem here as other users reported. Very unstable, no values from sensors in the energy dashboard for hours until restart home assistant. Network and pulse connected permanently. This is NOT the problem. This way the Integration is practically useless for energy dashboard. Maybe tibber has an API limit which is exceeded when using sensors in Energy Dashboard? |
An API limit might be a cause. I can confirm using the tibber values direct in Energy Dashboard. |
|
I also have this problem. The Tibber Integration looses connection about 2-3 times a week for me. Most disconnects seem to happen in the later evening, although that is not exclusive. |
|
Could someone share some logs? |
|
This is what I can find in the logs (log is full of similar entries). What I can see there is a 504 returned from tibber. `2023-10-18 21:20:07.081 ERROR (MainThread) [tibber] Timed out when connecting to Tibber During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): 2023-10-18 21:21:27.496 ERROR (MainThread) [tibber] Timed out when connecting to Tibber |
|
That is a server error at Tibber, and not possible to fix from Home Assistant |
|
As soon as I reloaded the integration withing HASS settings the entity values came up again as expected. Isn't it possible to handle the 504 (or what else might cause the problem) in this way? |
|
Hmm, strange that reloading the integration solves it |
|
Sometimes it is 503... 023-10-18 21:14:51.769 ERROR (MainThread) [tibber.realtime] Watchdog: Connection is down, 2023-10-18 21:15:01.768955 |
|
This is what tibber API Docs say. No other idea from my side. https://developer.tibber.com/docs/guides/calling-api When implementing a client for subscribing to live data there are a few scenarios to consider: No data due to networking issues: it may be wise to implement reconnect mechanism in case no data has been received for several minutes. During a retry, the old websocket connection must first be destroyed and proper jitter and exponential delay implemented. |
|
My integration and consumption value actually get stuck every day and I have to restart HASS. Then the value changes again ... |
|
@Danielhiversen so it happend again, here are to logs you asked for, as the others told it happens mostly during evening time. And i can confirm my internet connection was up, cause I was watching neflix till midnight ;) 2023-10-24 12:17:13.256 ERROR (MainThread) [tibber.realtime] Watchdog: Connection is down, 2023-10-24 12:17:23.256118 During handling of the above exception, another exception occurred: Traceback (most recent call last): During handling of the above exception, another exception occurred: Traceback (most recent call last): |
|
Did restart the integration solved the problem? |
|
Same problem here also again: Logger: tibber Fatal error interacting with Tibber API, HTTP status: 504. API error: UNKNOWN / Unexpected content type: text/html Since yesterday sensors didn‘t work. Restarted a few minutes ago, sensors are receiving data again. What I dont know is if restarting immediately after the error also solves the problem. I think when the server no more sends 504 and then retrying will solve the problem. |
|
Same here, I just had a local network issue, after restarting the AP the Tibber app started to work by itself again but the HA integration needed a restart too. |
|
Is someone also using the evcc add-on (with tibber prices) in home assistant? Seems that there are also no price updates during that time. |
in the tibber settings page I did a disable and then enable the plugin once, this brought the connection up again, but it was around 9h later. interestingly the times from the failure at my HASS and the time @ignazhabibi are very close, might be some server side issue but I have no clue why the tibber Integration then is not aber to reconnct after a certain time |
Today I did a FW update of the AP (to which the Pulse connects) and when the Pulse reconnected no restart of the integratration was needed. |
|
again server side failures, timber integration stopped working over night, time similar between 20-21 in the evening o real time device for 034810db-7aca-44d1-979f-7847dce2edd4 |
|
Happened again. I will try a workaround and reload tibber integration via automation script when it is not available. alias: Reload tibber
|
|
Tibber has a bit of general issues right now, thats for certain. |
|
Here's my DIY Automation, seems to work so far: |
|
Similar problem here: sensor.power_production_xxx freezes from time to time which makes a restart of the integration necessary.
|
|
|
I wonder if there’s been a change in the way Home Assistant handles errors recently? I also get this issue with the Tibber integration but when Tibber becomes unavailable, simultaneously Local Tuya does as well (rospogrigio/localtuya#1531). I assume there’s a glitch in the network that causes both integrations to fail but for some reason they don’t recover like they used to. For now I’ve set up an automation that reload both integrations when their entities become unavailable. Edit: Another interesting fact is that I’ve setup custom queries to the Tibber API via RESTful sensors and they do not go unavailable. So I know that the issue is not on Tibbers end. |
|
For me, Tibber currently stands still once a day. For me the values come every 1-2 seconds. That inevitably leads to the permissible calls being exceeded, right? Is it possible to limit the query to 3 seconds? Thank you, Martin. |
|
I have made the following observation: As soon as sensor.power_XXX is greater than zero, i.e. power is drawn from the grid, sensor.power_production_XXX remains at the last current value and is not set to zero, which would be the correct value if power is drawn from the grid. I will now try to adjust this using automation, although it is not that easy to assign a different value (0) to a sensor. At least not for HA beginners :-) |
|
I just installed my Pulse yesterday and immediately ran into this issue. This morning the data in HA was stuck, the Tibber App was working fine. Restarting HA solved the issue. I don't think it's an API limit, this extension is using the graphql subscription, right? |
|
I am not sure that this will help someone out. But I also experience this issue and for me this is probably what causes my frontend to crash (tried to investigate this past few weeks and only issue I see now in my logs are Tibber), however I don't know why, so I can't be 100% sure. The frontend crash might not be caused by the Tibber integration itself, but it might be something that I have done related to Tibber that crashes my FE when Tibber is being unstable. But just want to put it here incase someone else experience similar issues. This morning it was crashing just a minute after restarting ha core and the only errors I got was from Tibber and by disabling the Tibber intergration it stopped crashing. My hardware is Home Assistant Blue (ODROID-N2/N2+) |
|
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. |
|
Still occurs. Freezes for a day or two then it goes back to normal. |
|
Trying to get this to work too, but I don't understand, how this line works:
What is XXX supposed to be? Is that some device or entity ID? |
|
Could someone try to enable debug logging and share the logs? |
|
I just found the issue and want to provide help and some data for resolving it. here is the log of the last minutes |
|
I have the Same Problem since months and with the Last ha Updates i have to restart tibber addon every week. After restart IT geht live Data again. Here my debug logs with active Problem |
|
Same here. It stucks even more often than before. In the past, if sometimes helped to restart the configuration. Now, I have to restart HA several times a day. Just implemented an automation for this. I really hope this issue can be solved soon. |
|
Hi,
and where can I actually see the version number of the Tibber integration? |
|
Does anyone have any idea why the Tibber integration keeps breaking down connections and why this can only be resolved by restarting Home Assistant? I just had another connection break, but strangely enough the data was still available in the Tibber and EcoFlow app. I would therefore rule out the TibberServer as the source of the error. |
|
It happens to me now maybe "only" every other week and it is enough in my case to reload the integration. Still annoying though. |
|
Reload don´t helps here, only restart Home Assistant :-( |
and others
The problem
Over a long time the Tibber integration was very unstable, at some point that was fixed and only few dropouts happened. Now since about a week or so I'm getting more issues, today the integration have been offline most of the time. I've reloaded it multiple times but it just won't come back.
All this time I get live data in the Tibber app from my Pulse.
What version of Home Assistant Core has the issue?
core-2023.9.2
What was the last working version of Home Assistant Core?
Not sure
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Tibber
Link to integration documentation on our website
No response
Diagnostics information
{
"home_assistant": {
"installation_type": "Home Assistant OS",
"version": "2023.9.2",
"dev": false,
"hassio": true,
"virtualenv": false,
"python_version": "3.11.5",
"docker": true,
"arch": "aarch64",
"timezone": "Europe/Stockholm",
"os_name": "Linux",
"os_version": "6.1.21-v8",
"supervisor": "2023.09.2",
"host_os": "Home Assistant OS 10.5",
"docker_version": "23.0.6",
"chassis": "embedded",
"run_as_root": true
},
"custom_components": {
"lametricboot": {
"version": "1.0.0",
"requirements": []
},
"hacs": {
"version": "1.32.1",
"requirements": [
"aiogithubapi>=22.10.1"
]
},
"nordpool": {
"version": "0.0.14",
"requirements": [
"nordpool>=0.2",
"backoff"
]
},
"home_connect_alt": {
"version": "0.6.3",
"requirements": [
"home-connect-async==0.7.8"
]
},
"daikin_residential": {
"version": "2.3.1",
"requirements": [
"oic==1.6.0"
]
},
"watchman": {
"version": "0.5.1",
"requirements": [
"prettytable==3.0.0"
]
},
"sensorpush": {
"version": "0.1.4",
"requirements": [
"pysensorpush>=0.1.7"
]
},
"duet3d": {
"version": "v0.1.3",
"requirements": []
}
},
"integration_manifest": {
"domain": "tibber",
"name": "Tibber",
"codeowners": [
"@Danielhiversen"
],
"config_flow": true,
"dependencies": [
"recorder"
],
"documentation": "https://www.home-assistant.io/integrations/tibber",
"iot_class": "cloud_polling",
"loggers": [
"tibber"
],
"quality_scale": "silver",
"requirements": [
"pyTibber==0.28.2"
],
"is_built_in": true
},
"data": {
"homes": [
{
"last_data_timestamp": "2023-09-14T23:00:00+02:00",
"has_active_subscription": true,
"has_real_time_consumption": null,
"last_cons_data_timestamp": "2023-09-13T21:00:00+02:00",
"country": "SE"
},
{
"last_data_timestamp": "2023-09-14T23:00:00+02:00",
"has_active_subscription": true,
"has_real_time_consumption": null,
"last_cons_data_timestamp": "2023-09-13T21:00:00+02:00",
"country": "SE"
},
{
"last_data_timestamp": "2023-09-14T23:00:00+02:00",
"has_active_subscription": true,
"has_real_time_consumption": null,
"last_cons_data_timestamp": "2023-09-13T21:00:00+02:00",
"country": "SE"
},
{
"last_data_timestamp": "2023-09-14T23:00:00+02:00",
"has_active_subscription": true,
"has_real_time_consumption": null,
"last_cons_data_timestamp": "2023-09-13T21:00:00+02:00",
"country": "SE"
},
{
"last_data_timestamp": "2023-09-14T23:00:00+02:00",
"has_active_subscription": true,
"has_real_time_consumption": null,
"last_cons_data_timestamp": "2023-09-13T21:00:00+02:00",
"country": "SE"
}
]
}
}
Example YAML snippet
No response
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: