core: Tibber integration sensors "freeze"

@chrfo892 The issue that many of us have had is that the tibber websocket for subscriptions to live updates is closing and the connection is “silently” lost. Then the tibber integration in HA is not reconnected by itself. The manual restart or reload, or the automation’s that some have deployed, resolves this by resubscribing. It doesn’t have anything to do with the throttle limit on the web service by the way.

The bug fix that has been implemented by the author is in the GraphQL library used by pytibber (and hence the tibber integration) and resolves this by reconnecting as soon as the dropped websocket is detected. This fix is in the works is for the next release 2022.4 (coming out today I think).

So I’m crossing my fingers that all will be resolved today if the next release of HA is available.

To solve this problem, I have temporary created a automation thats reload the integration. Sure its not the best solutions, but it will do the trick for now.

Automation:

- id: "010420222307"
  alias: "Tibber. Reload integration"
  trigger: 
    - platform: state
      entity_id: sensor.accumulated_consumption_XXXXXXXX
      for: 
        minutes: 25
  action: 
    - service: homeassistant.reload_config_entry
      data:
        entry_id: bcb725d07917eb70a94cbf212b69ced3    
    - service: persistent_notification.create
      data:
        title: Tibber integration frozen
        data: Integration reloaded

Feels like it is happening a lot more to me thatn others. yesterday I had to reload or restart 5 times and unfortunately this morning, causing the energy statistics to be completely wrong since the it froze late last night and then reported the wrong values until I noticed it this morning. The feeling is that I get more and more issues, from the beginning (1-2 weeks ago) is was once a day or every second day and now the last days it’s happening several times per day.

Tibber does not even answer on support regarding this. Time to try something else. Weekendproject https://github.com/iotux/ElWiz or https://github.com/toreamun/amshan-homeassistant looks promising!

Makes the Tibber Pulse local only, probably the best for Tibber and me 🙄

I have created a Node RED flow that restarts the Tibber Integration if no status has been received for 2 minutes. https://pastebin.com/Z24VQG5L

@SebSkarp To get the entry id from devtools. Do the following in Chrome: Navigate to the integrations page in you ha instance. Then press CTRL + SHIFT + i. Devtools should appear. Select the Networks tab. Now you can push the reload button on the tibber integration. In devtools you should now have an request named “reload” select it and under Headers copy the request URL.

The long lived token you get by clicking your username in HA and then create a long lived token.

I hacked up an automation that reloads tibber if needed:

alias: tibber reload
description: ''
trigger:
  - platform: time_pattern
    minutes: /10
condition:
  - condition: template
    value_template: >-
      {{(as_timestamp(now()) -
      as_timestamp(states.sensor.accumulated_consumption_XXXX.last_changed))
      > 100}}
action:
  - service: rest_command.reload_tibber
    data: {}
mode: single

and in configuration.yaml the rest command:

rest_command:
  reload_tibber:
    url: https://[my-ha-instance:port]/api/config/config_entries/entry/[entry id, capture with devtools in chrome when pushing reload button in UI]/reload
    method: POST
    headers:
      Authorization: "Bearer [your very long bearer long lived token generated under your profile in HA UI]"
      content-type: "application/json"

@hnrkp Henrik would you mind to elaborate a bit about what you mean by capturing the entry id using devtools in chrome? 😃 Im still somewhat of a rookie here hehe. Also perhaps the long lived token part. Your automation sounds like something that could be used as a temporary fix until whatever is causing this is fixed for real.

But in the picture you posted there is the tibber integration, how did you get it there because I can’t add it…

This is an open-source project, so anyone can look into it. It only requires that someone has time they want to spend on it.

@JDolven Ah cool. Thanks. Will give it a try later today, since the integration now seems to be freezing multiple times every day 😕