Tibber sensors become available - not able to reload integration without a HA restart

[gulli1986]

The problem

Tibber have been very unstable lately. Sensors for the Tibber integration can suddenly become unavailable.

Earlier this could be fixed by reloading the integration. This is not possible anymore, the integration requests to restart HA without having the possibility to reload:

Even after re-start the sensors do not always show up. Tibber is working fine on the iOS app.

What version of Home Assistant Core has the issue?

core-2022.12.7

What was the last working version of Home Assistant Core?

No response

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Logger: tibber
Source: runner.py:120
First occurred: 11:27:38 AM (1 occurrences)
Last logged: 11:27:38 AM

Timed out when connecting to Tibber

Additional information

No response

[RicardP]

@Danielhiversen latest HA 2023.1.7 - Tibber 0.26.11.

Unfortunately at 17:25:50 no data received, at 18:25 I discovered this and manually reloaded Tibber plugin, data came in again:

2023-01-27 17:25:50.656 ERROR (MainThread) [custom_components.hacs] Could not update appdaemon - Timeout of 60s reached 2023-01-27 17:25:50.658 ERROR (MainThread) [custom_components.hacs] Could not update plugin - Timeout of 60s reached 2023-01-27 17:42:42.335 ERROR (MainThread) [tibber] Watchdog: Connection is down, 2023-01-27 17:44:07.427112 2023-01-27 18:25:58.027 ERROR (MainThread) [tibber.tibber_home] Error in rt_subscribe

[Danielhiversen]

@RicardP Have you enabled debug logging?

[RicardP]

@Danielhiversen no sorry, I disabled after your last fix/update. I turned it on now.

[LAPDragnet]

I got a disconnect too today at 1741 CET - restart HA and it was back again.

Home Assistant 2023.1.7 Supervisor 2023.01.1 Operating System 9.4 Frontend-version: 20230110.0 - latest

[4homeassistant]

Get debug logging enabled (see https://github.com/home-assistant/core/issues/84179#issuecomment-1401454330) @LAPDragnet otherwise @Danielhiversen has no chance to get any insights why it happened.

[LAPDragnet]

Get debug logging enabled (see #84179 (comment)) @LAPDragnet otherwise @Danielhiversen has no chance to get any insights why it happened.

Fair point, enabled now, waiting for the next time it happens.

[RicardP]

@Danielhiversen for some annoying reason Tibber Debug logging had disabled itself, at unknown time, before the last failure yesterday 00:02. How do I debug the debug log... 🤣

[LAPDragnet]

@Danielhiversen Mine stopped at 00:02:16 yesterday also, this cannot be a coincidence. (Debug logging went off the day before when I updated the HA OS...)

[4homeassistant]

Got the same problem with debug logging when enabled in the integration menu. Seems only to be persistant when added to the config file.

[RicardP]

@Danielhiversen I emailed the debug log to you yesterday, to the address you make public, did it arrive? :)

[Danielhiversen]

Yes, 👍 Thanks.

I have made a fix that is available in 2023.2. Need some more testing to see if it actually is fixed

[RicardP]

@Danielhiversen Running 2023.2.2. Unfortunately I had interruption in retrieving data from 00:02 CET - exactely same time as last failure... No errors in standard logging, however Tibber debug log NOT enabled. Plugin seemed connected to Tibber but no data came in, as last failure. I manually reloaded 00:36 and it solved the problem.

[Danielhiversen]

I do not have a Tibber Pulse, so I cannot do much without debug logging from someone else.