I have the beta running. No issues so far.
I’ve just bumped it to 2023.4.3 which matches the code submitted via https://github.com/home-assistant/core/pull/90891 after @bdraco’s review and assistance with streamlining the refactor. Now with 100% (ish) code coverage and all tests passing! 
1 Like
Looks like 2023.4.3 is less stable than the previous 2032.4.2. If you’re experiencing timeouts using the latest version, please downgrade and see if that resolves things for you.
I have some lights that are offline at the moment. They are logging this every minute:
This error originated from a custom integration.
Logger: custom_components.lifx
Source: custom_components/lifx/coordinator.py:249
Integration: LIFX
First occurred: 18:55:44 (6 occurrences)
Last logged: 18:55:46
Marking 10.1.1.167 (00:00:00:00:00:00) as offline after three failed update attempts
Marking 10.1.1.122 (00:00:00:00:00:00) as offline after three failed update attempts
Marking 10.1.1.124 (00:00:00:00:00:00) as offline after three failed update attempts
Marking 10.1.1.123 (00:00:00:00:00:00) as offline after three failed update attempts
Marking 10.1.1.152 (00:00:00:00:00:00) as offline after three failed update attemptsCan you downgrade to 2023.4.2 and see if still happens? Or if you’re still on it, upgrade and see if it goes away. Tracking this issue down is proving exceptionally difficult, so the more data we can get the better.
Sorry should have said, I was on 2023.4.3.
Downgrading to 2023.4.2 gives this instead:
Logger: homeassistant.config_entries
Source: config_entries.py:425
First occurred: 19:16:15 (6 occurrences)
Last logged: 19:16:15
Config entry 'mstr_bed_1' for lifx integration not ready yet: The device failed to respond after 3 attempts; Retrying in background
Config entry 'mstr_bed_2' for lifx integration not ready yet: The device failed to respond after 3 attempts; Retrying in background
Config entry 'ensuite' for lifx integration not ready yet: The device failed to respond after 3 attempts; Retrying in background
Config entry 'sp_bed_lamp' for lifx integration not ready yet: The device failed to respond after 3 attempts; Retrying in background
Config entry 'spare_bedroom' for lifx integration not ready yet: The device failed to respond after 3 attempts; Retrying in background
And not repeatedly.
removed. totally.
Home assistant OS on an Intel NUC11PAHI7 i7-1165G7 with 8Gb of RAM. It’s way over powered.
Yep, so there goes my low-powered device theory. 
If you’re comfortable editing code (and I’m hoping/guessing/assuming you are), can you uncomment line 248 in /config/custom_components/lifx/config_flow.py:
# device.mac_addr is not the mac_address, its the serial number
-# device.mac_addr = serial or messages[0].target_addr
+device.mac_addr = serial or messages[0].target_addr
await self.async_set_unique_id(
formatted_serial(device.mac_addr), raise_on_progress=raise_on_progress
)
And see if that resolves this issue on 2023.4.2, i.e. the previous version not the latest.
If that doesn’t resolve it, would you be comfortable in emailing me your config.entries file? There is something I’m missing that’s not manifesting in my setup so I’m trying to gather as much alternative configurations as possible. Also, whether the bulbs have static DHCP leases or not would be useful to know.
There’s no problem on 2023.4.2. I obviously have not explained this well. Sorry.
The issue is the log flooding in version 2023.4.3. The devices really are unavailable (my guest has turned off the light switch).
Ah, ok. That matches my experience. I’ll tweak the logging to try and ensure it doesn’t keep repeating itself if the light is actually powered off. The very thought of bulbs being powered off in my house gives me the screaming heebie-jeebies, which is why none of the light switches on the walls actually work. 
1 Like
Yeah I just can’t train my guests properly. They keep removing the sticky labels over the switches. I’ll be moving to smart switches/dimmers and dumb lights next year.
I know I’m the ultimate fan boy, but I’m actually pretty happy with the LIFX Switches via the HomeKit integration. I configure them all as non-LIFX devices (even for the terminals connected to LIFX devices) so they all get exposed to Home Assistant. Then I just map the buttons as I want them. I have a master switch can reset individual bulbs by doing the five-toggle-fandango automatically.
Though, I do wish the Innovelli Blue switches were certified. They look really nice too.
I’m severely limited with switch choice. All my switches are architrave types. Might actually have to put modules in the roof.
FYI folks I’ve revoked the 2023.4.3 release and re-released the previous version as 2023.4.4 so that anyone who installed it will be prompted to upgrade to a known better/more stable version.
Is it possible to make a modification that makes all color and brightness changes to have a default transition time of 1 second instead of the instant change?
It’s certainly possible, though the beta is now archived and I recommend folks use the build-in intgration instead.
Thank you so much for the quick reply! How would I go forward making that modification?
On line 235 of light.py change fade = 0 to fade = 1000. That should set a default transition if one isn’t already set by the request. This is untested though, so let me know if it works as expected.