Still problem with Tibber with 2026.4.2

[OleBandole]

The problem

The problem(s) with the Tibber integration should have been fixed with the 2026.4.2 release, obviously it is not fixed.

Over the last 10 years I have gone through Fibaro, HomeSeer, Homey, and now Home Assistant. I started with HA in January/February, and there have been issues with the Tibber integration throughout that entire period.

I fully understand and greatly appreciate that the developers and code owners are volunteers who contribute in their spare time. I’m truly grateful for all the hard work that goes into Home Assistant.
However, I would like to ask what is the expected timeframe for this to be resolved
Even though I have spent a significant amount of time migrating all my devices from Homey to HA, I will now revert back to Homey.

My patience with Tibber is exhausted. I no longer see the value in having a subscription with them, and I will be cancelling my subscriptions.

What version of Home Assistant Core has the issue?

2026.4.2

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

https://www.home-assistant.io/integrations/tibber

Diagnostics information

No response

Example YAML snippet

Anything in the logs that might be useful for us?

Logger: homeassistant.components.tibber.coordinator
Source: helpers/update_coordinator.py:426
integration: Tibber (documentation, issues)
First occurred: 22:15:09 (2 occurrences)
Last logged: 23:15:09

Unexpected error fetching tibber price data
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 426, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tibber/coordinator.py", line 293, in _async_update_data
    tibber_connection = await self.config_entry.runtime_data.async_get_client(
                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        self.hass
        ^^^^^^^^^
    )
    ^
  File "/usr/src/homeassistant/homeassistant/components/tibber/__init__.py", line 64, in async_get_client
    await self._client.set_access_token(access_token)
  File "/usr/local/lib/python3.14/site-packages/tibber/__init__.py", line 238, in set_access_token
    await self.update_info()
  File "/usr/local/lib/python3.14/site-packages/tibber/__init__.py", line 140, in update_info
    if (data := await self.execute(INFO)) is None:
                ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tibber/__init__.py", line 123, in execute
    return (await extract_response_data(resp)).get("data")
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tibber/response_handler.py", line 37, in extract_response_data
    raise RetryableHttpExceptionError(
    ...<3 lines>...
    )
tibber.exceptions.RetryableHttpExceptionError: Unexpected content type: text/html

Additional information

No response

[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)}}

---

@OleBandole 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)}}

[Danielhiversen]

The log indicates an issue with the data from Tibber server.
Are the Tibber sensors unavailable in Home Assistant? For how long?

[abremora]

All sensors remain unchanged in 2026.4.2. The same error occurs in 2026.4.1.
After a reload of the integration everything works fine.

Logger: tibber.realtime
Quelle: /usr/local/lib/python3.14/site-packages/tibber/realtime.py:175
Erstmals aufgetreten: 01:34:51 (72 Vorkommnisse)
Zuletzt protokolliert: 06:49:48

Error in watchdog connect, retrying in 300 seconds, 70: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 71: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 72: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 73: Error trying to receive data: ConnectionClosedError
Error in watchdog connect, retrying in 300 seconds, 74: 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 167, 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

[OleBandole]

The log indicates an issue with the data from Tibber server. Are the Tibber sensors unavailable in Home Assistant? For how long?

Many thanks for your reply!
Yes, the sensors are uvailable in HA.
Since updating Home Assistant at approximately 21:15, I have observed a recurring pattern where the privce sensor become unavailable for roughly 15 minutes at a time, occurring around the 15-minute mark of each hour. This has been consistent throughout the night and into the following morning.
All other sensor are stuck for now and need a reload.

Two distinct HTTP errors are present:
503 Service Unavailable — Tibber's API server is actively refusing connections, typically meaning the service is overloaded or down
504 Bad Gateway — A proxy/gateway in front of Tibber's API is timing out waiting for a backend response, returning an HTML error page instead of valid JSON.
Both errors ultimately trigger the same crash in HA: it seems that the Tibber client library receives text/html instead of JSON during the authentication/initialization step (set_access_token → update_info).

[wwebers]

Same here. When checking the list of created refresh-token in my Tibber account it also looks like this integration requests several refresh token in a row.

I guess this is because I activates an automation to reload the integration as a workaround to this mess.

Anyway, the usual way to deal with access and refresh tokens would be to rotate refresh tokens when exchanging them to access tokens. That is obviously not done, all the refresh tokens are the same. I'm not sure if that's a bug in this integration or if Tibber messed up. That demand a deeper look as their documentation really suck when it comes to security question (but they're not alone with that).

Before forgetting this: It's not o.k. to demand ALL scopes for the tibber integration. Please make sure that the user is able to revoke some scopes allowing access to sensitive API endpoints. I tried that and this make the integration unusable.

UPDATE: I revoked all those tokens and started from scratch. That triggered a new authentication of the Tibber integration of course, so I was able to revoke some of those scopes. Will see how this works out.

[Afrouper]

Same for me.
After updating to 2026.4.2 it seems that the error occurred faster than with 2026.4.1

I got some errors in the logs.

Logger: homeassistant.components.tibber.coordinator
Quelle: helpers/update_coordinator.py:426
Integration: Tibber (Dokumentation, Probleme)
Erstmals aufgetreten: 00:00:10 (5 Vorkommnisse)
Zuletzt protokolliert: 09:00:10

Unexpected error fetching tibber price data
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 426, in _async_refresh
self.data = await self._async_update_data()
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/src/homeassistant/homeassistant/components/tibber/coordinator.py", line 293, in _async_update_data
tibber_connection = await self.config_entry.runtime_data.async_get_client(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
self.hass
^^^^^^^^^
)
^
File "/usr/src/homeassistant/homeassistant/components/tibber/init.py", line 64, in async_get_client
await self._client.set_access_token(access_token)
File "/usr/local/lib/python3.14/site-packages/tibber/init.py", line 238, in set_access_token
await self.update_info()
File "/usr/local/lib/python3.14/site-packages/tibber/init.py", line 140, in update_info
if (data := await self.execute(INFO)) is None:
^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/tibber/init.py", line 123, in execute
return (await extract_response_data(resp)).get("data")
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.14/site-packages/tibber/response_handler.py", line 37, in extract_response_data
raise RetryableHttpExceptionError(
...<3 lines>...
)
tibber.exceptions.RetryableHttpExceptionError: Unexpected content type: text/html

All sensors stopped working and are freezed with the old values. This is a problem for my DIY-EMS which needs the correct data. After a reload of the integration everything works for some time.

[wwebers]

@Danielhiversen : The "documentation" of the Tibber API, specifically the security part is crap. Som my question to you is: where did you get the documentation of their OAuth "client credential flow" from? BTW: Their documentation doesn't even mention this term, but is chattering around it without giving clear instructions about the client registration process.

[wwebers]

So, after revoking all tokens and do a clean start by authenticating the integration as well as my Tibber App on my Android phone my IP-address is blocked by their rate-limiting.

Awesome.

[Bertk]

I also noticed errors after the HA 2026.4.2 update. The tibber integration now shows the price value which failed before but the connection is lost after some time.

There is also an unexpected message AttributeError: 'Client' object has no attribute 'session'

@Danielhiversen Please notice the root-cause analysis of tibber_stability_issue.md. Some parts are still valid and not resolved.

 Logger: tibber.realtime
Quelle: /usr/local/lib/python3.14/site-packages/tibber/realtime.py:159
Erstmals aufgetreten: 07:16:21 (2 Vorkommnisse)
Zuletzt protokolliert: 09:01:04

Error in watchdog close
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/tibber/realtime.py", line 156, in _watchdog
    await self.sub_manager.close_async()
  File "/usr/local/lib/python3.14/site-packages/gql/client.py", line 800, in close_async
    await self.session.close()
          ^^^^^^^^^^^^
AttributeError: 'Client' object has no attribute 'session'

Logger: tibber.realtime
Quelle: runner.py:289
Erstmals aufgetreten: 06:43:51 (85 Vorkommnisse)
Zuletzt protokolliert: 09:58:19

Watchdog: Connection is down, 2026-04-12 07:52:27.459229+00:00
Watchdog: Connection is down, 2026-04-12 07:53:43.060721+00:00
Watchdog: Connection is down, 2026-04-12 07:56:18.687644+00:00
Watchdog: Connection is down, 2026-04-12 07:57:24.271802+00:00
Watchdog: Connection is down, 2026-04-12 07:58:29.877895+00:00

Logger: homeassistant.components.tibber.coordinator
Quelle: helpers/update_coordinator.py:426
Integration: Tibber (Dokumentation, Probleme)
Erstmals aufgetreten: 09:00:20 (2 Vorkommnisse)
Zuletzt protokolliert: 10:00:10

Unexpected error fetching tibber Data API data
Unexpected error fetching tibber price data
Traceback (most recent call last):
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client_reqrep.py", line 539, in start
    message, payload = await protocol.read()  # type: ignore[union-attr]
                       ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/streams.py", line 707, in read
    await self._waiter
asyncio.exceptions.CancelledError

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/__init__.py", line 114, in execute
    resp = await self.websession.post(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
    ...<7 lines>...
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client.py", line 788, in _request
    resp = await handler(req)
           ^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client_middlewares.py", line 36, in single_middleware_handler
    return await middleware(req, handler)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 72, in _ssrf_redirect_middleware
    resp = await handler(request)
           ^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client.py", line 766, in _connect_and_send_request
    await resp.start(conn)
  File "/usr/local/lib/python3.14/site-packages/aiohttp/client_reqrep.py", line 534, in start
    with self._timer:
         ^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/aiohttp/helpers.py", line 713, in __exit__
    raise asyncio.TimeoutError from exc_val
TimeoutError

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 426, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tibber/coordinator.py", line 403, in _async_update_data
    client = await self._async_get_client()
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tibber/coordinator.py", line 389, in _async_get_client
    return await self._runtime_data.async_get_client(self.hass)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/components/tibber/__init__.py", line 64, in async_get_client
    await self._client.set_access_token(access_token)
  File "/usr/local/lib/python3.14/site-packages/tibber/__init__.py", line 240, in set_access_token
    await self.realtime.reconnect()
  File "/usr/local/lib/python3.14/site-packages/tibber/realtime.py", line 86, in reconnect
    await self._resubscribe_homes()
  File "/usr/local/lib/python3.14/site-packages/tibber/realtime.py", line 190, in _resubscribe_homes
    await asyncio.gather(*[home.rt_resubscribe() for home in self._homes])
  File "/usr/local/lib/python3.14/site-packages/tibber/home.py", line 472, in rt_resubscribe
    await asyncio.gather(
    ...<5 lines>...
    )
  File "/usr/local/lib/python3.14/site-packages/tibber/home.py", line 198, in update_info
    await self.update_info_and_price_info()
  File "/usr/local/lib/python3.14/site-packages/tibber/home.py", line 202, in update_info_and_price_info
    if not (data := await self._tibber_control.execute(UPDATE_INFO_PRICE % self._home_id)):
                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tibber/__init__.py", line 126, in execute
    return await self.execute(
           ^^^^^^^^^^^^^^^^^^^
    ...<4 lines>...
    )
    ^
  File "/usr/local/lib/python3.14/site-packages/tibber/__init__.py", line 123, in execute
    return (await extract_response_data(resp)).get("data")
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.14/site-packages/tibber/response_handler.py", line 37, in extract_response_data
    raise RetryableHttpExceptionError(
    ...<3 lines>...
    )
tibber.exceptions.RetryableHttpExceptionError: Unexpected content type: text/html

Logger: homeassistant.components.tibber.coordinator
Quelle: helpers/update_coordinator.py:497
Integration: Tibber (Dokumentation, Probleme)
Erstmals aufgetreten: 10:00:10 (1 Vorkommnis)
Zuletzt protokolliert: 10:00:10

Error fetching Tibber XXXXXXXXXXXXX data: Error communicating with API (504)

[OleBandole]

Same for me. After updating to 2026.4.2 it seems that the error occurred faster than with 2026.4.1

I agree, the error occurs more frequently after the attempt to fix the problem.
This is actually unbelievable.

I have now disabled the Tibber integration, it simply doesn’t work.
Seems that my “career” with HA will be short-lived.

[jochristian]

Same here.
After updating to 2026.4.2 it's more unstable than ever. I have done a "Reload" 3 times the last hour after statis not updating.

[sepperlot]

After update to 2026.4.2 Tibber integration stops working every hour basically exactly on the full hour.

Reloaded via the automation posted here a while back which reloads when no data is received for 5 minutes. Can't find the link right now.

[db-EV]

The error isn't in the component itself, it's in the pyTibber library which is used by the Tibber component. It has been like this for weeks now. I had a solution with the help of Claude AI but my pull request was closed; now other people are trying to resolve this error — see https://github.com/Danielhiversen/pyTibber/pulls.