How to speed up Home Assistant boot time when using this integration?
bertybuttface opened this issue · 18 comments
Hello,
I've found when booting Home Assistant this integration is always the last to load and slows down the rest of the boot process. I know this is probably quite a minor issue but is there anything we can do about this?
Cheers
To be honest, I have no idea...
I second this. Its the one component that sits and takes forever at startup
Any support in debugging this would be appreciated
Does anyone know how to profile a home assistant extension?
We can use this but we need to work out how to make it run on startup: https://www.home-assistant.io/integrations/profiler/
I found two kinda dumb work arounds, pick one of them:
-
disable this integration before restarting HA, then enable it back after restart is completed. This way HA will reboot normally and doesn't wait for this integration to start.
-
once HA begins to start and hangs trying to start this integration.. if you open the Air+ app and do any command (i personally toggle the beep sound) then the integration will start right away, and HA complete loading the other stuff.
@kongo09 i don't know if this behavior can give you a clue on why this issue could happen in first place.
But to me it looks like the integration wait for a response from the device, which takes a lot of time to happen in most cases.
Maybe there is a way to be more efficient with the initial data requests. If someone could look at that, I'd appreciate it.
I found two kinda dumb work arounds, pick one of them:
- disable this integration before restarting HA, then enable it back after restart is completed. This way HA will reboot normally and doesn't wait for this integration to start.
- once HA begins to start and hangs trying to start this integration.. if you open the Air+ app and do any command (i personally toggle the beep sound) then the integration will start right away, and HA complete loading the other stuff.
@kongo09 i don't know if this behavior can give you a clue on why this issue could happen in first place.
But to me it looks like the integration wait for a response from the device, which takes a lot of time to happen in most cases.
Is there a way to automate disabling of the integration prior to a restart and then reenable after startup?
I'm also having issues with startup of Home Assistant.
It says the "Air Purifier" addon is loading and stays there for a long time.
Don't know why. If i can provide any logging, please let me know what you need.
Same here. Workaround is to open the Philips app on my phone as HA tries to connect to the purifier during start up