ha-hildebrandglow-dcc: No longer working?
Describe the bug The integration seems to no longer be connecting to the Glow API to retrieve data - it just errors in the HA log file.
Is it just me?
Version Glow - v0.5.0 HA - 2022.2.0 and 2021.12.x
Debug log Debug logging enabled, but no additional error messages shown other than:
2022-02-03 09:42:38 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration hildebrandglow_dcc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2022-02-03 09:43:13 WARNING (MainThread) [homeassistant.components.sensor] Setup of sensor platform hildebrandglow_dcc is taking over 10 seconds.
2022-02-03 09:49:51 WARNING (SyncWorker_1) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-03 09:49:51 WARNING (SyncWorker_9) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-03 09:49:51 WARNING (SyncWorker_5) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-03 09:49:51 WARNING (SyncWorker_6) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
2022-02-03 09:49:51 WARNING (SyncWorker_8) [custom_components.hildebrandglow_dcc.glow] Error connecting to Glow ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 22 (8 by maintainers)
Hey all, apologies for the delay. Just looking at this now - as pointed out, simply increasing the polling interval will often mean data is out of date. I think the solution in #136 and #138 is going to be the best one, so I’ll be testing that before releasing it, most likely later today. Thanks for all your input, both here and on the glow forums!
Your PR for this seems reasonable to me - need @HandyHat to come online a accept it.
Hoping https://github.com/HandyHat/ha-hildebrandglow-dcc/pull/80 can be accepted too, as this will further reduce server load when tariff data is unavailable.
I’m going to change the sensor.py file in my local installation for now.