Tibber integration stops working after brief internet interruption

[abremora]

The problem

Every time there’s an internet interruption, my tibber integration stops working. All sensors remain stuck at their last recorded value. After restarting the integration, the values are retrieved again. My internet provider forces a disconnection at least once a day. On some days, I experience multiple interruptions.
I completely reinstalled Home Assistant with version 2026.4.1 (no data import) and have observed the same problem in 2026.4.2 and 2026.4.3.

Logger: tibber.home
Quelle: /usr/local/lib/python3.14/site-packages/tibber/home.py:460
Erstmals aufgetreten: 01:57:15 (1 Vorkommnis)
Zuletzt protokolliert: 01:57:15

Error in rt_subscribe
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/tibber/home.py", line 443, in _start
    async for _data in session.subscribe(
    ...<14 lines>...
            return
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 1426, in subscribe
    async for result in inner_generator:
    ...<13 lines>...
                yield result.data
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 1337, in _subscribe
    async for result in inner_generator:
    ...<11 lines>...
        yield result
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 298, in subscribe
    answer_type, execution_result = await listener.get()
                                    ^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/listener_queue.py", line 35, in get
    raise item
gql.transport.exceptions.TransportServerError: No pong received after 15.0 seconds

Logger: tibber.realtime
Quelle: runner.py:289
Erstmals aufgetreten: 01:57:17 (106 Vorkommnisse)
Zuletzt protokolliert: 09:50:38

Watchdog: Connection is down, 2026-04-18 07:30:27.822147+00:00
Watchdog: Connection is down, 2026-04-18 07:35:32.981688+00:00
Watchdog: Connection is down, 2026-04-18 07:40:38.157042+00:00
Watchdog: Connection is down, 2026-04-18 07:45:43.323766+00:00
Watchdog: Connection is down, 2026-04-18 07:50:48.504349+00:00

Logger: tibber.realtime
Quelle: /usr/local/lib/python3.14/site-packages/tibber/realtime.py:198
Erstmals aufgetreten: 01:57:48 (104 Vorkommnisse)
Zuletzt protokolliert: 09:50:38

Error in watchdog connect, retrying in 300 seconds, 101: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 102: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 103: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 104: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 105: Error trying to receive data: ConnectionClosedError
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/adapters/websockets.py", line 114, in receive
    data = await self.websocket.recv()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/websockets/asyncio/connection.py", line 322, in recv
    raise self.protocol.close_exc from self.recv_exc
websockets.exceptions.ConnectionClosedError: received 4403 (private use) Invalid token; then sent 4403 (private use) Invalid token

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/tibber/realtime.py", line 190, in _watchdog
    self.session = await self.sub_manager.connect_async()
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 782, in connect_async
    await self.session.connect()
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 1851, in connect
    raise e
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 1848, in connect
    await self.transport.connect()
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 402, in connect
    raise e
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 400, in connect
    await self._initialize()
  File "/usr/local/lib/python3.14/site-packages/gql/transport/websockets_protocol.py", line 156, in _initialize
    await self._send_init_message_and_wait_ack()
  File "/usr/local/lib/python3.14/site-packages/gql/transport/websockets_protocol.py", line 153, in _send_init_message_and_wait_ack
    await asyncio.wait_for(self._wait_ack(), self.ack_timeout)
  File "/usr/local/lib/python3.14/asyncio/tasks.py", line 488, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/websockets_protocol.py", line 128, in _wait_ack
    init_answer = await self._receive()
                  ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tibber/websocket_transport.py", line 49, in _receive
    msg = await asyncio.wait_for(super()._receive(), timeout=self._timeout)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/asyncio/tasks.py", line 488, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 153, in _receive
    answer: str = await self.adapter.receive()
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/adapters/websockets.py", line 116, in receive
    raise TransportConnectionFailed(
        f"Error trying to receive data: {type(e).__name__}"
    ) from e
gql.transport.exceptions.TransportConnectionFailed: Error trying to receive data: ConnectionClosedError

Logs from my modem

04/18/26    01:56:55    Internet connection established successfully. IPv4 is being used via DS-Lite. AFTR gateway: XXXXXX.de, IPv4 MTU: 1500, Broadband PoP: XXXXXX, LineID: XXXXXXX   
04/18/26    01:56:55    IPv6 prefix successfully obtained. New prefix: XXXXXXXX	
04/18/26    01:56:55    IPv6 Internet connection successfully established. IP address: XXXXXXX    
04/18/26    01:56:52    Internet connection disconnected.	
04/18/26    01:56:52    IPv6 internet connection disconnected, prefix no longer valid.    
04/18/26    01:56:52    The internet connection is being briefly interrupted to preempt forced disconnection by the provider.

What version of Home Assistant Core has the issue?

core-2026.4.3

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?

Additional information

Another issue is described in #168007. The recommendation was to create a new ticket.

[home-assistant]

Hey there @Danielhiversen, mind taking a look at this issue as it has been labeled with an integration (tibber) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tibber can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tibber Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component, problem in config, problem in device, feature-request) on the issue.

_{^{(message by CodeOwnersMention)}}

---

@abremora Thanks for reporting this issue!

Before we dive in, please make sure this isn't a duplicate by searching through existing issues. Also check recently closed issues, as your problem might already be fixed but not yet released.

https://github.com/home-assistant/core/issues?q=%20label%3A%22integration%3A%20tibber%22%20
_{^{(message by IssueContext)}}

---

tibber documentation
tibber source
_{^{(message by IssueLinks)}}

[MartinHjelmare]

I have a PR open in pyTibber library to redesign the Tibber real-time websocket feature. It handles connection problems better. I'm currently doing long term testing with my production instance. I hope to get it ready within a couple of weeks.

[Odatas]

Might be the same race condition i saw.

Danielhiversen/pyTibber#402

If for some reason the server invalidates the token after the token refresh before the watchdog reconnects it will get stuck to try to connect with that token again and again.

[Thorsten1982]

I have exactly the same problem.

[Thorsten1982]

It hasn't been working at all since this morning. I've tried reloading the integration and restarting Home Assistant, but nothing helps. The log is full of connection errors.

Logger: tibber.realtime
Quelle: /usr/local/lib/python3.14/site-packages/tibber/realtime.py:198
Erstmals aufgetreten: 08:57:32 (70 Vorkommnisse)
Zuletzt protokolliert: 14:39:23

Error in watchdog connect, retrying in 19 seconds, 4: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 33 seconds, 5: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 52 seconds, 6: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 44 seconds, 7: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 70 seconds, 8: Error trying to receive data: ConnectionClosedError
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/adapters/websockets.py", line 114, in receive
    data = await self.websocket.recv()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/websockets/asyncio/connection.py", line 322, in recv
    raise self.protocol.close_exc from self.recv_exc
websockets.exceptions.ConnectionClosedError: received 4403 (private use) Invalid token; then sent 4403 (private use) Invalid token

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/tibber/realtime.py", line 190, in _watchdog
    self.session = await self.sub_manager.connect_async()
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 782, in connect_async
    await self.session.connect()
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 1851, in connect
    raise e
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 1848, in connect
    await self.transport.connect()
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 402, in connect
    raise e
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 400, in connect
    await self._initialize()
  File "/usr/local/lib/python3.14/site-packages/gql/transport/websockets_protocol.py", line 156, in _initialize
    await self._send_init_message_and_wait_ack()
  File "/usr/local/lib/python3.14/site-packages/gql/transport/websockets_protocol.py", line 153, in _send_init_message_and_wait_ack
    await asyncio.wait_for(self._wait_ack(), self.ack_timeout)
  File "/usr/local/lib/python3.14/asyncio/tasks.py", line 488, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/websockets_protocol.py", line 128, in _wait_ack
    init_answer = await self._receive()
                  ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tibber/websocket_transport.py", line 49, in _receive
    msg = await asyncio.wait_for(super()._receive(), timeout=self._timeout)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/asyncio/tasks.py", line 488, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 153, in _receive
    answer: str = await self.adapter.receive()
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/adapters/websockets.py", line 116, in receive
    raise TransportConnectionFailed(
        f"Error trying to receive data: {type(e).__name__}"
    ) from e
gql.transport.exceptions.TransportConnectionFailed: Error trying to receive data: ConnectionClosedError

Logger: tibber.realtime
Quelle: runner.py:289
Erstmals aufgetreten: 07:57:46 (246 Vorkommnisse)
Zuletzt protokolliert: 14:46:15

Watchdog: Connection is down, 2026-04-21 12:42:03.534642+00:00
Watchdog: Connection is down, 2026-04-21 12:43:08.850345+00:00
Watchdog: Connection is down, 2026-04-21 12:44:14.129221+00:00
Watchdog: Connection is down, 2026-04-21 12:45:19.437389+00:00
Watchdog: Connection is down, 2026-04-21 12:46:25.870522+00:00

[Marmelatze]

I just switched to this integration, that uses the local API without cloud: https://github.com/marq24/ha-tibber-pulse-local

[marte3no-del]

I experience the same. Has been working fine then suddenly ConnectionClosedError due to "Invalid token". I uninstalled rebooted then reinstalled yesterday and followed procedure with login at tibber...

Logger: tibber.realtime
Source: /usr/local/lib/python3.14/site-packages/tibber/realtime.py:198
First occurred: 4:18:59 AM (67 occurrences)
Last logged: 9:03:29 AM

Error in watchdog connect, retrying in 300 seconds, 64: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 65: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 66: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 67: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 68: Error trying to receive data: ConnectionClosedError

Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/gql/transport/common/adapters/websockets.py", line 114, in receive
data = await self.websocket.recv()
^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/websockets/asyncio/connection.py", line 322, in recv
raise self.protocol.close_exc from self.recv_exc
websockets.exceptions.ConnectionClosedError: received 4403 (private use) Invalid token; then sent 4403 (private use) Invalid token

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.14/site-packages/tibber/realtime.py", line 190, in _watchdog
self.session = await self.sub_manager.connect_async()

[pergpau]

Same issue on 2026.4.4

About once a day integrations falls out completely and sensor don't update anymore. Reloading the integration makes it work again.

Logs (this repeats over and over again on each retry indefinetely)

2026-04-29 15:33:15.828 ERROR (MainThread) [tibber.realtime] Watchdog: Connection is down, 2026-04-29 13:33:25.828041+00:00
2026-04-29 15:33:15.991 ERROR (MainThread) [tibber.realtime] Error in watchdog connect, retrying in 7 seconds, 2: Error trying to receive data: ConnectionClosedError
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/adapters/websockets.py", line 114, in receive
    data = await self.websocket.recv()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/websockets/asyncio/connection.py", line 322, in recv
    raise self.protocol.close_exc from self.recv_exc
websockets.exceptions.ConnectionClosedError: received 4403 (private use) Invalid token; then sent 4403 (private use) Invalid token

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/tibber/realtime.py", line 190, in _watchdog
    self.session = await self.sub_manager.connect_async()
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 782, in connect_async
    await self.session.connect()
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 1851, in connect
    raise e
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 1848, in connect
    await self.transport.connect()
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 402, in connect
    raise e
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 400, in connect
    await self._initialize()
  File "/usr/local/lib/python3.14/site-packages/gql/transport/websockets_protocol.py", line 156, in _initialize
    await self._send_init_message_and_wait_ack()
  File "/usr/local/lib/python3.14/site-packages/gql/transport/websockets_protocol.py", line 153, in _send_init_message_and_wait_ack
    await asyncio.wait_for(self._wait_ack(), self.ack_timeout)
  File "/usr/local/lib/python3.14/asyncio/tasks.py", line 488, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/websockets_protocol.py", line 128, in _wait_ack
    init_answer = await self._receive()
                  ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tibber/websocket_transport.py", line 49, in _receive
    msg = await asyncio.wait_for(super()._receive(), timeout=self._timeout)
          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/asyncio/tasks.py", line 488, in wait_for
    return await fut
           ^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/base.py", line 153, in _receive
    answer: str = await self.adapter.receive()
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/gql/transport/common/adapters/websockets.py", line 116, in receive
    raise TransportConnectionFailed(
        f"Error trying to receive data: {type(e).__name__}"
    ) from e
gql.transport.exceptions.TransportConnectionFailed: Error trying to receive data: ConnectionClosedError
2026-04-29 15:33:27.998 ERROR (MainThread) [tibber.realtime] Watchdog: Connection is down, 2026-04-29 13:33:37.998726+00:00
2026-04-29 15:33:28.162 ERROR (MainThread) [tibber.realtime] Error in watchdog connect, retrying in 11 seconds, 3: Error trying to receive data: ConnectionClosedError

[milchmannverleih]

I can confirm this on Home Assistant OS 2026.4.4.

My setup:

• Installation method: Home Assistant OS
• Core: 2026.4.4
• Supervisor: 2026.04.0
• OS: 17.2
• Tibber configured via Application Credentials (OAuth)
• Tibber Pulse enabled

What I tested:

• Removed and re-added the Tibber integration
• Created new Tibber application credentials / new client in the Tibber API portal
• After a full Home Assistant restart, Tibber works for a while, then stops again

Observed behavior:

• tibber.realtime starts failing repeatedly
• watchdog reconnect retries increase up to 300 seconds
• logs show ConnectionClosedError with 4403 Invalid token

I can provide redacted debug logs and diagnostics if helpful.

[Danielhiversen]

An error log from 2026.5 (currently beta) would be useful

[Odatas]

An error log from 2026.5 (currently beta) would be useful

I haven't tested the 2026.5 beta myself yet, but looking at the logs from @pergpau , this seems to be the exact 4403 Invalid token watchdog loop I investigated a few weeks ago.

Reloading the integration temporarily fixes it because HA fetches a completely fresh token on startup. However, during runtime, the realtime watchdog catches the 4403 close code merely as a generic ConnectionClosedError. Because set_access_token currently overwrites the token state before validating it, the watchdog gets stuck in an infinite loop, constantly retrying to reconnect using the invalidated token that is still stored in memory.

I built a targeted fix for this exact race condition over in (introducing a pre-validation HTTP guard and state rollback). Feel free to check the code or cherry-pick the logic from there if it helps to patch this up!

https://github.com/Danielhiversen/pyTibber/pull/402/changes#diff-77c84b87c9a59562eefa1e142d347b64bbcaab889c944c198eb0a81f08255e72

Running 3 Weeks without issues at the moment.

Let me know if you have any questions or need more details.

[MartinHjelmare]

I don't think the problem is that Tibber.set_access_token is called with an invalid access token. It should only be called with a valid access token and preferably only if the former access token is no longer valid or about to expire. So we should never need to roll back the access token.

I think the problem comes later, that we don't properly reconnect with the fresh access token. The current logic is too convoluted and does not properly control the state of the connection without races. Eg there are multiple places that can close and connect the websocket client instead of that being handled in a single place.

I don't have the problem that the websocket connection uses a stale access token in my branch that has removed the watchdog task and simplified the connection state handling. The connection is re-established every hour with the fresh access token.

[Danielhiversen]

And I dont have any issue with the version used by Home Assistant 😅