search

HandyHat / ha-hildebrandglow-dcc

Home Assistant integration for UK SMETS (Smart) meters pulling data from the DCC via the Hildebrand Glow API
MIT License
231 stars 33 forks source link

Stopped working 9am 16 Feb 2022 log warnings #147

Closed thorrrr closed 2 years ago

thorrrr commented 2 years ago

Describe the bug NO data coming through as of 9am yesterday 16 Feb

To Reproduce Easy look at logs and Energy Page no data

Expected behaviour To show data

Screenshots Added

Version

System Health

version core-2022.2.8
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.9.7
os_name Linux
os_version 5.10.98
arch x86_64
timezone Europe/London
Home Assistant Community Store GitHub API | ok -- | -- Github API Calls Remaining | 4854 Installed Version | 1.22.0 Stage | running Available Repositories | 977 Downloaded Repositories | 25
Home Assistant Cloud logged_in | false -- | -- can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 7.4 -- | -- update_channel | stable supervisor_version | supervisor-2022.01.1 docker_version | 20.10.9 disk_total | 30.8 GB disk_used | 16.3 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Samba share (9.5.1), Check Home Assistant configuration (3.10.0), SSH & Web Terminal (10.0.2), Home Assistant Google Drive Backup (0.105.2), Studio Code Server (4.1.0), MariaDB (2.4.0), InfluxDB (4.3.0), Grafana (7.4.1), Mosquitto broker (6.0.1)
Lovelace dashboards | 3 -- | -- resources | 16 views | 75 mode | storage

Debug log https://0bin.net/paste/IA+tJHj1#G7AFdoU5I0K0FZeY2bMHNk+9LZuQHQiFpuvqqhCl0WB

Additional context Add any other context about the problem here. msedge_Energy_–_Home_Assistant_and_15_more_pages_-_Person_2022-02-17_08 58 54 msedge_Energy_–_Home_Assistant_and_15_more_pages_-_Person_2022-02-17_08 59 32 msedge_Configuration_–_Home_Assistant_and_15_more_pages_-_2022-02-17_08 58 27

ColinRobbins commented 2 years ago

Problem is the interfaces between Glow and DCC. Nothing this integration can do, but wait for Glow to fix it.

thorrrr commented 2 years ago

HI Colin When i check my Bright app data is flowing no issues very weird it was finally working with no issues. Seems a very flaky connection i hope they don’t pull it.

gedger commented 2 years ago

I'm in the same situation but by Bright app has-stopped updating as well. I've put a post in the bright forum as well.

thorrrr commented 2 years ago

Mine has now :(

thorrrr commented 2 years ago

Started working then stopped with logs Logger: homeassistant.components.websocket_api.http.connection Source: components/websocket_api/connection.py:96 Integration: Home Assistant WebSocket API (documentation, issues) First occurred: 16:22:15 (2 occurrences) Last logged: 16:22:15

[140320809551664] Received invalid command: energy/info

ColinRobbins commented 2 years ago

This log line above does not come from this intergation.

There will be no logging from this integration, because the intergation is working. The integration contacts GLow ans says give me the latest meter reading. Glow returns the data it has. The problem in DCC are not feeding Glow the lastest data - so as far as Glow is concerned no new electrictiy/gas has been used, so Glow returns the most recent reading it has.

This is why your sensors show "data" - the last reading that was taken.

If the HA to Glow API failed, the Hildebrand component would log, and the sensors show "unavailable".

thorrrr commented 2 years ago

Hi Colin Yes that makes 100% sense now :) Any idea why there is such a problem getting data from DCC?

si458 commented 2 years ago

this should be fixed now, there support emailed me saying the was a boo boo in the system which they have fixed, its been working fine for a few days now for me :)

thorrrr commented 2 years ago

yep same here i wil close it now thank you for your help