-
Notifications
You must be signed in to change notification settings - Fork 2
Startup Delay / Error #5
Comments
What kind of bulbs do you have? |
Can you bump the message reply timeout to 1 second? You can edit this by hitting the Configure button in the UI. I can't reproduce the issue (and I have almost the identical setup, with a similar network config and collection of bulbs). |
Updated, now getting more errors at restart...
Here's some around activity around 192.168.2.107 which had some issues:
|
Those aren't actual errors, I'm just using the wrong log levels. But it does indicate that your network is very busy, I think. Can you bump the message reply timeout again to 3 seconds? Most of your bulbs are replying, but not within the timeout. |
You'll need to adjust discovery interval as well. I'd put that up at 300 or so. |
I've done that, so now it's waiting until 300 secs after HASS bootup before they're available and HASS flags it's "fully started". I can see the lights registering multiple times before discovery ends though. Do they not register as available entities until that Discovery time has fully completed though? |
That's really weird. I'll have to try and work out what's going on over the weekend. |
I've just double-checked my test/dev instance and all 59 of my bulbs are discovered and active before the timer for the next discovery starts. It also completes the initial discovery in ~4 seconds. That's with a 300 second discovery interval and a 1 second message response timeout. |
This should be resolved by home-assistant/core#70458 when it is merged to the core. |
After restart sometimes there's a delay until light entites are available even though it looks like the integration has discovered them successfully.
Full log attached
hass_lifx_beta_error_logs.log
The text was updated successfully, but these errors were encountered: