Tibber integration problem

Configuration
1

Hi everybody.
I have a problem with the tibber integration.
The problem is every time i restart Home Assistant the real_time_consumption sensor shows unavailable. and i have to delete the integration and install it again, then it works until i restart again.
But the template sensors that i have maked from real_time_consumption sensor wont show up this way.
I had the problem a few times in 0.111 but now at 0.112 its always like this.
i have another sensor in the tibber intergration called sensor.electricity_price wich there is no problem with.
I have no error in log that indicates there is somethings wrong with tibber.

Can some one help me in the rigth direction for what to do?

My system is:

arch x86_64
chassis vm
dev false
docker true
docker_version 19.03.8
hassio true
host_os HassOS 4.11
installation_type Home Assistant OS
os_name Linux
os_version 5.4.50
python_version 3.7.7
supervisor 228
timezone Europe/Oslo
version 0.112.2
virtualenv false

1 Like
2

I’m having the same problem. Need to remove/add integration every time I restart hassio…

3

I had the same problem… every single time… since I installed it last year.
I’m now on 2021.5.3 and now not even that works… Real time consumption is gone. Tried removing and added both via configuration.yaml and via GUI. This Tibber integration is not very stable, unfortunately…

4

same problem here.

5

I have also problems with Tibber integration after core upgrades in May (neither the real time consumption or the electricity price entity) . Tried to install the integration again with new access token from Tibber. The Tibber app works with data from the TibberPulse, so I believe the problem is in the HA update.

6

Danielhiversen says it will be fixed in 2021.6

7

Hi guys

So this has also been my problem since (I don’t know).
My workaround is …
Settings>Devices&Services>Tibber>Reload
… then it works for about 20-50 hours or something until it freezes on a certain value.

My Questions is simple; Is there a way to Reload programmatically (fail+correct faster) or does anyone else have a more permanent solution to this problem ?

B

8

Same for me, annoying.

9

Same here…

10

Same here…

11

Hi @bgronas and everyone else, try this automation that will reload the tibber automation when it notices stale data. Tibber has added rate limiting to their API, this is why the integration stops receiving data.

1 Like
12

Can you explain how to use this automation. I tried to paste it into HA, but it didn’t work.

E.g. what should be in ?

13

create a new automation from the gui–> edit in yaml and change out the enitities to fit your sensors.

alias: Reload Tibber if we have stale readings
description: ""
trigger:
  - platform: template
    value_template: >-
      {{ now() - states.sensor.YOUR ENTITY.last_updated >
      timedelta(minutes=5) }}
action:
  - service: homeassistant.reload_config_entry
    data: {}
    target:
      entity_id: YOUR ENTITY
mode: single
1 Like
14

Thank you!

15

I cannot seem to find any sensor like “##.last_updated” from my Tibber integration when I look in the developer tools. However I can reload the integration by using the service:

    data: {}
    target:
      device_id: MY DEVICE

Thanks.

16

Yeah, that’s why you use templates.

- platform: template

I stopped using Tibber since they changed the pricing model here in Norway, they did a stunt where they started estimating the power cost and started using their customers as interest-free banks. Now I use the Nordpool integration.

1 Like
17

I have installed tibber integration today. Seems working. Most sensors are populated with valid data. I think some sensors need time to get valid values.

But the integration is flooding my log file with entries starting [gql.transport.websockets].
I get one entry every second.

2023-11-10 17:11:14.012 INFO (MainThread) [gql.transport.websockets] <<< {"id":"1","type":"next","payload":{"data":{"liveMeasurement":{"accumulatedConsumption":4.1999,"accumulatedConsumptionLastHour":0.0027,"accumulatedCost":null,"accumulatedProduction":1.3017,"accumulatedProductionLastHour":0.0015,"accumulatedReward":null,"averagePower":244.3,"currency":null,"currentL1":null,"currentL2":null,"currentL3":null,"lastMeterConsumption":324.332,"lastMeterProduction":8514.6391,"maxPower":3079,"minPower":0,"power":0,"powerFactor":null,"powerProduction":33,"powerReactive":null,"signalStrength":null,"timestamp":"2023-11-10T17:11:13.000+01:00","voltagePhase1":null,"voltagePhase2":null,"voltage

How could I switch of these log entries?

18

Sorry for my nasty question. :innocent:
Log level in the configuration.yaml must be set correctly.
Case closed. :+1: