home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
73.65k stars 30.8k forks source link

False Values for 1st of Every Month in Energy Dashboard using Tibber Integration #87290

Closed MichelFR closed 1 year ago

MichelFR commented 1 year ago

The problem

I'm getting false values for the 1st of every month. I'm not using Tibber Pulse. I could identify the same problem in another running HomeAssistant instance with nearly the same configuration and a separate contract in Tibber. Both contracts are'nt older than a month. For now, the 2nd of February seems to be fine.

In the Energy Dashboard, I'm using:

tibber:energy_consumption_<home_id>

This is how it looks: image

And this is the correct value in Tibber: image

What version of Home Assistant Core has the issue?

Home Assistant 2023.2.1

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

{ "home_assistant": { "installation_type": "Home Assistant Container", "version": "2023.2.1", "dev": false, "hassio": false, "virtualenv": false, "python_version": "3.10.7", "docker": true, "arch": "x86_64", "timezone": "Europe/Berlin", "os_name": "Linux", "os_version": "5.15.83-1-pve", "run_as_root": true }, "custom_components": { "dreame_vacuum": { "version": "v0.16.3", "requirements": [ "pillow", "numpy", "pybase64", "requests", "pycryptodome", "python-miio>=0.5.6", "py-mini-racer" ] }, "ble_monitor": { "version": "11.5.2", "requirements": [ "pycryptodomex>=3.14.1", "janus>=1.0.0", "aioblescan>=0.2.14", "btsocket>=0.2.0", "pyric>=0.1.6.3" ] }, "hacs": { "version": "1.30.1", "requirements": [ "aiogithubapi>=22.10.1" ] }, "mbapi2020": { "version": "0.8.1", "requirements": [ "protobuf>=3.19.1" ] }, "nodered": { "version": "1.1.2", "requirements": [] }, "better_thermostat": { "version": "1.0.0", "requirements": [] }, "powercalc": { "version": "v1.3.2", "requirements": [ "numpy>=1.21.1" ] }, "alarmo": { "version": "v1.9.7", "requirements": [] }, "tibber_data": { "version": "0.6.0", "requirements": [ "pyTibber>=0.25.2" ] }, "mass": { "version": "2023.2.1", "requirements": [ "music-assistant==1.8.7.4" ] } }, "integration_manifest": { "dependencies": [ "recorder" ], "domain": "tibber", "name": "Tibber", "documentation": "https://www.home-assistant.io/integrations/tibber", "requirements": [ "pyTibber==0.26.12" ], "codeowners": [ "@danielhiversen" ], "quality_scale": "silver", "config_flow": true, "iot_class": "cloud_polling", "loggers": [ "tibber" ], "is_built_in": true }, "data": { "homes": [ { "last_data_timestamp": null, "has_active_subscription": false, "has_real_time_consumption": false, "last_cons_data_timestamp": null, "country": "DE" }, { "last_data_timestamp": "2023-02-04T23:00:00+01:00", "has_active_subscription": true, "has_real_time_consumption": false, "last_cons_data_timestamp": "2023-02-03T00:00:00+01:00", "country": "DE" } ] } }

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

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` Change the title of 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.

(message by CodeOwnersMention)


tibber documentation tibber source (message by IssueLinks)

issue-triage-workflows[bot] commented 1 year ago

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.