I’ve updated to the latest version of HA, but a few of my LIFX bulbs are going offline according to HA, however they’re still controllable via the LIFX app.
I’ve since updated all firmware on the LIFX as well as all my network gear, but some bulbs are always offline (yet still controllable via the LIFX app)
Anyone have similar issues, or have any ideas on what I can do to remedy this?
tom_l
June 7, 2022, 1:03pm
2
My 40+ Lifx bulbs are all still available. I occasionally see one or two slow to initialise after a restart but by the time I’ve navigated from the logs to the device page they’re up and working. That has been going on a lot longer than 2022.6.
40+ thats a lot of bulbs : )
tom_l
June 7, 2022, 1:43pm
4
I underestimated:
I also wish I had gone with more smart switches and less smart bulbs. Live and learn.
1 Like
There is an issue with this release and it is being fixed.
opened 09:07PM - 04 Jun 22 UTC
integration: lifx
### The problem
Crux of the issue is, since upgrading to 2022.5 the Lifx integr… ation is now partially broken and putting entries into the log, this never used to occur.
Lights now never become available after being turned off and back on until HA is restarted and the lights are currently on. Seems once they get turned off, HA is no longer able to see them even when they come back on.
I can confirm the lights work from the Lifx app, and they are cloud connected and respond. Other lights that remain with the power on, continue to function.
Only HA reporting the lights unavailable.
Log entries:
1. Updating lifx light took longer than the scheduled update interval 0:00:10
2. Duplicate LIFX discovery response ignored
Evidence of lights as showing unavailable, even though these lights are currently on.
Happy to provide any additional information required to help resolve this one.
Possibly the same as #72120 and #72827
Lifx discovery was of no issue before the refactor, so it is directly related to that update.
Perhaps revert until this is properly tested.
### What version of Home Assistant Core has the issue?
2022.5.5
### What was the last working version of Home Assistant Core?
2022.4.6
### What type of installation are you running?
Home Assistant Container
### 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?
```txt
Issue 1:
Logger: homeassistant.components.light
Source: helpers/entity_platform.py:724
Integration: Light (documentation, issues)
First occurred: 4 June 2022, 02:58:08 (8 occurrences)
Last logged: 4 June 2022, 02:59:18
Issue 2:
Logger: homeassistant.components.lifx.light
Source: components/lifx/light.py:391
Integration: LIFX (documentation, issues)
First occurred: 4 June 2022, 06:30:48 (2 occurrences)
Last logged: 4 June 2022, 06:30:48
Duplicate LIFX discovery response ignored
```
### Additional information
_No response_
1 Like
tom_l
June 7, 2022, 2:34pm
6
Weird. I’ve seen both those errors but my lights are still all eventually discovered after a restart. Mind you, I’m not turning them off like the person who opened that issue.
Luckily I only have 3 LIFX bulbs. 2 of them are affected.
I guess the guy/gal with the most smart bulbs wins : )
zoogara
June 7, 2022, 11:31pm
9
Yes - I thought it was supposed to be fixed in 2022.6.1, but still happening to me.
I dont see anything in the release notes on it. Think its still in the queue.
I’ve just updated to 2022.6.3, i’ll keep you updated.
tom_l
June 7, 2022, 11:52pm
12
There is no merged PR listed in the issue. No fix has been applied yet.
zoogara
June 8, 2022, 12:04am
13
home-assistant:dev ← Djelibeybi:lifx-fix-discovery
opened 07:56AM - 11 May 22 UTC
Signed-off-by: Avi Miller <[email protected] >
## Proposed change
If a bulb fails… to register, we need to remove it from the light of discoveries in-flight so that it can be rediscovered on the next broadcast.
## Type of change
- [ ] Dependency upgrade
- [X] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #71585
- This PR is related to issue:
- Link to documentation pull request:
## Checklist
<!--
Put an `x` in the boxes that apply. You can also fill these out after
creating the PR. If you're unsure about any of them, don't hesitate to ask.
We're here to help! This is simply a reminder of what we are going to look
for before merging your code.
-->
- [X] The code change is tested and works locally.
- [X] Local tests pass. **Your PR cannot be merged unless tests pass**
- [X] There is no commented out code in this PR.
- [X] I have followed the [development checklist][dev-checklist]
- [X] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [ ] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [X] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [X] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
Which Looks like it was in 202.5.5, but if so didn’t fix it.
home-assistant:dev ← Djelibeybi:remove-lifx-duplicate-discovery-block
opened 08:36PM - 19 May 22 UTC
Signed-off-by: Avi Miller <[email protected] >
## Proposed change
Functionally revert… #70458 to allow duplicate discoveries. It's clear from recent issues that some folks rely on this non-standard behaviour and more research is required before the next attempt at a refactor.
## Type of change
- [ ] Dependency upgrade
- [X] Bugfix (non-breaking change which fixes an issue)
- [ ] New integration (thank you!)
- [ ] New feature (which adds functionality to an existing integration)
- [ ] Breaking change (fix/feature causing existing functionality to break)
- [ ] Code quality improvements to existing code or addition of tests
## Additional information
<!--
Details are important, and help maintainers processing your PR.
Please be sure to fill out additional details, if applicable.
-->
- This PR fixes or closes issue: fixes #72120
- This PR is related to issue: #71823
- Link to documentation pull request:
## Checklist
- [X] The code change is tested and works locally.
- [X] Local tests pass. **Your PR cannot be merged unless tests pass**
- [X] There is no commented out code in this PR.
- [X] I have followed the [development checklist][dev-checklist]
- [X] The code has been formatted using Black (`black --fast homeassistant tests`)
- [ ] Tests have been added to verify that the new code works.
If user exposed functionality or configuration variables are added/changed:
- [ ] Documentation added/updated for [www.home-assistant.io][docs-repository]
If the code communicates with devices, web services, or third-party tools:
- [X] The [manifest file][manifest-docs] has all fields filled out correctly.
Updated and included derived files by running: `python3 -m script.hassfest`.
- [ ] New or updated dependencies have been added to `requirements_all.txt`.
Updated by running `python3 -m script.gen_requirements_all`.
- [ ] For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
- [ ] Untested files have been added to `.coveragerc`.
The integration reached or maintains the following [Integration Quality Scale][quality-scale]:
<!--
The Integration Quality Scale scores an integration on the code quality
and user experience. Each level of the quality scale consists of a list
of requirements. We highly recommend getting your integration scored!
-->
- [X] No score or internal
- [ ] 🥈 Silver
- [ ] 🥇 Gold
- [ ] 🏆 Platinum
<!--
This project is very active and we have a high turnover of pull requests.
Unfortunately, the number of incoming pull requests is higher than what our
reviewers can review and merge so there is a long backlog of pull requests
waiting for review. You can help here!
By reviewing another pull request, you will help raise the code quality of
that pull request and the final review will be faster. This way the general
pace of pull request reviews will go up and your wait time will go down.
When picking a pull request to review, try to choose one that hasn't yet
been reviewed.
Thanks for helping out!
-->
To help with the load of incoming pull requests:
- [X] I have reviewed two other [open pull requests][prs] in this repository.
[prs]: https://github.com/home-assistant/core/pulls?q=is%3Aopen+is%3Apr+-author%3A%40me+-draft%3Atrue+-label%3Awaiting-for-upstream+sort%3Acreated-desc+review%3Anone+-status%3Afailure
<!--
Thank you for contributing <3
Below, some useful links you could explore:
-->
[dev-checklist]: https://developers.home-assistant.io/docs/en/development_checklist.html
[manifest-docs]: https://developers.home-assistant.io/docs/en/creating_integration_manifest.html
[quality-scale]: https://developers.home-assistant.io/docs/en/next/integration_quality_scale_index.html
[docs-repository]: https://github.com/home-assistant/home-assistant.io
Is the next attempt.
Meanwhile if you search there is a temporary custom component to fix it supposedly:
tom_l
June 8, 2022, 12:06am
14
That’s the solution for another issue. This one:
opened 10:39AM - 09 May 22 UTC
closed 11:30AM - 13 May 22 UTC
integration: lifx
### The problem
One of my Lifx Clean bulbs is in a toilet, where the light swit… ch is used to control power to the globe.
Before 2022.5 update, I could power on the globe and within a few seconds it would connect to Home Assistant which would fire some automations to control brightness and colour temperature.
Since 2022.5, the bulb is not found by home assistant unless I reload the Lifx integration while the bulb is powered on. Once it is powered off and disconnects, it won't reconnect to Home Assistant.
The bulb works completely fine with my app and there were no issues before the update. I assume this might be caused by the changes in https://github.com/home-assistant/core/pull/70458 but that is only a guess.
There is also a log entry found when searching for Lifx but I'm not sure if this is related to the problem or just normal noise.
### What version of Home Assistant Core has the issue?
2022.5.3
### What was the last working version of Home Assistant Core?
2022.4.7
### 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?
```txt
Logger: homeassistant.components.lifx.light
Source: components/lifx/light.py:391
Integration: LIFX (documentation, issues)
First occurred: May 8, 2022, 12:21:47 AM (2 occurrences)
Last logged: May 8, 2022, 10:34:04 PM
Duplicate LIFX discovery response ignored
```
### Additional information
_No response_
This one has no PR associated with it yet:
opened 09:07PM - 04 Jun 22 UTC
closed 06:05AM - 13 Jun 22 UTC
integration: lifx
### The problem
Crux of the issue is, since upgrading to 2022.5 the Lifx integr… ation is now partially broken and putting entries into the log, this never used to occur.
Lights now never become available after being turned off and back on until HA is restarted and the lights are currently on. Seems once they get turned off, HA is no longer able to see them even when they come back on.
I can confirm the lights work from the Lifx app, and they are cloud connected and respond. Other lights that remain with the power on, continue to function.
Only HA reporting the lights unavailable.
Log entries:
1. Updating lifx light took longer than the scheduled update interval 0:00:10
2. Duplicate LIFX discovery response ignored
Evidence of lights as showing unavailable, even though these lights are currently on.
Happy to provide any additional information required to help resolve this one.
Possibly the same as #72120 and #72827
Lifx discovery was of no issue before the refactor, so it is directly related to that update.
Perhaps revert until this is properly tested.
### What version of Home Assistant Core has the issue?
2022.5.5
### What was the last working version of Home Assistant Core?
2022.4.6
### What type of installation are you running?
Home Assistant Container
### 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?
```txt
Issue 1:
Logger: homeassistant.components.light
Source: helpers/entity_platform.py:724
Integration: Light (documentation, issues)
First occurred: 4 June 2022, 02:58:08 (8 occurrences)
Last logged: 4 June 2022, 02:59:18
Issue 2:
Logger: homeassistant.components.lifx.light
Source: components/lifx/light.py:391
Integration: LIFX (documentation, issues)
First occurred: 4 June 2022, 06:30:48 (2 occurrences)
Last logged: 4 June 2022, 06:30:48
Duplicate LIFX discovery response ignored
```
### Additional information
_No response_
zoogara
June 8, 2022, 12:07am
15
tom_l:
My 40+ Lifx bulbs
Wow - you must have hated power failures in the middle of the night before LIFX released the power restore settings.
1 Like
zoogara
June 8, 2022, 12:07am
16
That explains why it didn’t fix it.
tom_l
June 8, 2022, 12:08am
17
I had an automation to fix that.
zoogara
June 27, 2022, 2:51am
19
I see this was merged a few days after you posted this - any idea when it will make it into prod? 2022.7 maybe?
tom_l
June 27, 2022, 2:53am
20
Yeah Avi said it will be in the next release. Beta release is out this Wednesday if you feel like testing it (I will be).
1 Like
