Lifx integration issue (?)

mspinolo · September 21, 2022, 10:11am

Hi,

just opened an issue here:

github.com/home-assistant/core

Issue with Lifx integration

opened 10:08AM - 21 Sep 22 UTC

mspinolo

integration: lifx

### The problem Since the latest integration update I have a lot of occurrences… of LIFX light becoming "not available". This is happening on most (but not all) of them (I have 20+ lights). The behavior is not consistent during the day which makes me suspect there is some relation with the wifi environment (I have 3 AP broadcasting the same SSID on 1-6-11 channel), but by AP logs it doesn't seem to be related to LIFX disconnecting from one AP and reconnecting to the other. Also I see they usually become unavailable for 10s then coming back online: I ask myself if this has something to do with polling rate cycle of the integration as I see from [integration ](https://github.com/home-assistant/core/blob/dev/homeassistant/components/lifx/const.py)discovery interval is 10 (seconds?) ``` """Const for LIFX.""" import logging DOMAIN = "lifx" TARGET_ANY = "00:00:00:00:00:00" DISCOVERY_INTERVAL = 10 MESSAGE_TIMEOUT = 1.65 MESSAGE_RETRIES = 5 OVERALL_TIMEOUT = 9 UNAVAILABLE_GRACE = 90 ``` so could it be that discovery, in my environment, simply can't keep the pace and drops connections? ### What version of Home Assistant Core has the issue? 2022.9.5 ### What was the last working version of Home Assistant Core? the one before LIFX integration update ### What type of installation are you running? Home Assistant OS ### Integration causing the issue LIFX ### Link to integration documentation on our website https://www.home-assistant.io/integrations/lifx/ ### Diagnostics information _No response_ ### Example YAML snippet _No response_ ### Anything in the logs that might be useful for us? _No response_ ### Additional information _No response_

and wondering if someone else is experiencing the same.
Related to the topic does anyone know how to stop HA discovery, in general, to reduce broadcasting traffic?

michaelblight · September 22, 2022, 4:06am

Yeah I have two bulbs that have been going unavailable for the last couple of months, whereas they were stable before that. I might try the workaround suggested in the issue you raised. Not that I really want an integration that only exists to make another integration work.

tom_l · September 22, 2022, 5:06am

I could be wrong but think I read that disconnections weren’t reported before. So they may have been just as unstable before but it wasn’t reported.

Edit: yeah I was right, https://github.com/home-assistant/core/issues/78876#issuecomment-1253491094

mspinolo · September 22, 2022, 6:49am

I am not completely sure about that: for the last year I didn’t have a single issue with commands of automation of LIFX lights, which I should have had if they were disconnected.
Now instead, when unavailable, they obviously do not respond.

Maybe it is just that “disconnections” from wifi are so short in time that previous case was more robust as connection re-estabilished.
I mean to me it looks like the system is better reporting the state but is less robust (?)

Djelibeybi · September 22, 2022, 7:04am

It’s a work-in-progress. The LIFX integration was updated to align with Home Assistant’s device-centric paradigm, which means that each bulb is now it’s own entity and that makes things inherently more noisy. Add to that the additional discovery methods and it all adds up.

As I mentioned in the GitHub issue, using the HomeKit Controller instead of the LIFX integration is recommended as that uses local push instead of relying on polling.