I can say Im rather happy here. the errors:
2019-01-03 21:35:53 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 192.168.1.212
2019-01-03 21:35:54 ERROR (MainThread) [homeassistant.components.hue] Error connecting to the Hue bridge at 192.168.1.212. Retrying in 2 seconds
which have been perstering my HA setup ever since Hue went asyncio in april/may 2018 , and been the cause for the Hue lights going Unavailable all the time (see: Philips Hue changed to unavailable - #30 by Mariusthvdb, All my hue lights randomly becoming unavailable - #6 by Mariusthvdb, Philips Hue changed to unavailable · Issue #16689 · home-assistant/core · GitHub to name a few)
have disappeared completely following suggestions by @yottatsa testing his new async version of @robmarkcole 's CC for the Hue sensors!
Added to that, there’s no more lag after startup in initializing the sensors, And Lights, and they don’t randomly and frequently show unavailable any more. I have been testing and resetting HA for almost 9 months now, and this must be the biggest leap forward.
I know the HA founder doesn’t want an upped timeout in the Hue components, stating if that’s needed, something else is going on in the setup that needs fixing, not the Hue component. I respect that, but no other solution has been suggested…
this is what I did:
by dl ing the files from the Ha repository, adjusting these timeouts, and loading the files in the custom component folder.
The new component also took care of these messages:
all gone.
Summarizing:
no more hue sensor took longer errors
no more error connecting to the Hue bridge error
no more flapping hue lights
immediate initialization of the lights and sensors
big speedup in startup HA.
not sure yet, but my processor use has gone down significantly also
Couldn’t be happier for the moment…