NanoLeaf Thread Bulbs drop offline

[iGageit]

The problem

I have the SkyConnect and I am using Thread to connected them to HA. It works really fast and well But I occasionally lose connection with some of my bulbs randomly. the last log I get from it is: "NanoLeaf Bulb Provision Preferred Thread Credentials" then it goes offline. the only way to get it back on is resetting the Bulb and repairing it.

What version of Home Assistant Core has the issue?

Home Assistant 2023.3.1

What was the last working version of Home Assistant Core?

Home Assistant 2023.3.1

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Homekit Controller

Link to integration documentation on our website

https://www.home-assistant.io/integrations/homekit_controller/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Living Room Left Tall lamp 1 Provision Preferred Thread Credentials became unavailable
2:52:42 PM - 2 hours ago
Living Room Left Tall lamp 1 Identify became unavailable
2:52:42 PM - 2 hours ago
Living Room Left Tall lamp 1  became unavailable
2:52:42 PM - 2 hours ago
Living Room Left Tall lamp 1 Thread Status became unavailable
2:52:42 PM - 2 hours ago
Living Room Left Tall lamp 1 Thread Capabilities became unavailable
2:52:42 PM - 2 hours ago
Living Room Left Tall lamp 1  turned off triggered by HomeKit send command turn_off to Set state to False for Living Room Left Tall lamp 1
2:48:08 PM - 2 hours ago

Additional information

My thread border routers in my home:

SkyConnect connected to Raspberry Pi 4 8GB with HA installed. (Pi is in a closet but is only about 10 feet away from thread bulb)

HomePod minis

Apple TV 4K with thread.

Eero Routers with Thread support turned off.

[home-assistant]

Hey there @Jc2k, @bdraco, mind taking a look at this issue as it has been labeled with an integration (homekit_controller) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of homekit_controller can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign homekit_controller Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

homekit_controller documentation
homekit_controller source
_{^{(message by IssueLinks)}}

[iGageit]

After a reboot of HA 2 hours later it started working again. So it's not high priority problem but some of my bulbs do go offline for some reason. Thank you for looking into this.

[400HPMustang]

I am also having the same issue.

Edit: I just looked at the bulb and apparently after 22 hours it is back online again without me touching it.

[Benjamin1333]

Same here with Nanoleaf bulbs, eve motion, eve energy

[alkno]

I have the same problem. Eve Switch/Motion are disconnected after a couple of days. These affects only the thread connected devices. Bluetooth Eve Switch stays connected. Sometimes if I see the disconnection early enough and restart HA it recovers. Most of the time a new pairing is needed to recover. Until a couple of days later they are disconnected again.

[dudley-codes]

I'm having the same issue with Eve Motion and Nanoleaf bulbs. It's been going on for a few weeks now. Only way to fix the issue is to restart HA. Things will work again for a while but then disconnect.

[schmuy]

Same issue with Eve Aqua

[Tuckie]

Same issue with Smartwings Nano Blinds. Note: all show up fine in the OpenThread Border Router UI.

[400HPMustang]

How do I access that UI?

[Tuckie]

Under the configuration tab on the OpenThread Border Router plugin, specify a web port and API port. I use 8080, and 8081.

Once enabled you can visit http(s)://[yourhomeassistantdomain]:8080

The map of (not very well described) devices can then be found under "Topology"

[laurentfignon]

I'm having this same problem with my Eve Switches, also running a SkyConnect device alongside an Apple TV thread router.

[F5ancesco]

Same problem with my nanoleaf bulbs and lightstrips. After some time all my nanoleaf essentials products drop offline

[wenstarner]

I’m having this problem too, with Nanoleaf Essentials thread bulbs. Random disconnects using HomeKit integration.

I have to restart HASS to fix it. I have an automation to restart HASS every night, and I still get disconnects even during the day. Very frustrating!

Zigbee bulbs are fine.

[ffedee7]

Exactly the same is happening to me, I've even reseted all my Border Routers (1 ATV 4K 2nd gen and 2 HomePods 2nd gen) and set up all lights again without luck.
I've read that having multiple border routers is not helpful, would't be possible to "disable" their thread capability somehow?

[400HPMustang]

I've read that having multiple border routers is not helpful, would't be possible to "disable" their thread capability somehow?

So what I've read is not that "multiple border routers is not helpful" but that Apple's Thread implementation doesn't handle them well. Since Thread is a mesh having multiple TBRs really shouldn't matter at all since they're just acting as another node in the mesh and as a failover in case one goes down.

Also, no, their Thread capability cannot be disabled.

[Germaenace]

I'm having the same/a similar issue.
There are lots of disconnects with my 2 nanoleaf shapes (fw 9.2.0, hw 1.3.0) and my three nanoleaf essentials A19 (fw 1.6.49, hw 2.3.5) all in Thread - Mode and all with up to date firmware with 4 Google nest hub 2 as additional thread border routers. All nanoleaf devices and nest hubs are in the same nest thread network. No Apple TV or eve device in my case.
Especially the nanoleaf essentials A19 bulbs are not reachable from time to time for no obvious reasons. Sometimes reloading of the homekit device helps (but most of the time it doesn't help). Sometimes a reboot of home assistant or the host (raspberry pi 4) helps. But also not every time. It can be, that I have to do several reboots to make it work again. Also some times I do nothing and suddenly everything is back online again.

[MattWestb]

I have 2 EVE Energy and one Nanoleaf light and 3 HA OTBR and can only having one boarder router activated and the other 2 only running Zigbeed or the all thresd devices is timing out in HA (but is online in OTBR GUI and can being manage from it).
Its not one problem with the OTBR mesh network its one problem that HA is using the last accounted rout to the devices and the device is using one other OTBR for communicating with the world.
So in the end HA is not understanding witch rout it shall using to communicating with the devices in the thread mesh the its having all devices and one not working route to them.
Its one fundamental error how OTBR is working and shall not being any problem on the paper then also backbone routers shall being possible with different cites of the same network only with different partitions and devices can moving dynamic between them.
If not possible fixing in the network level i think HA need implanting all OTBR and not only one and checking all of then the devices is using for the moment and forcing the integration using the right rout for communicating with them but im dont have the deep knowledge of IPV6 routing.

[alihamze]

I'm having the same issue with Nanoleaf lights. HomeAssistant and the integrations are fully updated.

Adding to the comments above, the issue is usually resolved by rebooting the Pi HomeAssistant is running on. Restarting HA without a full reboot sometimes, but rarely, fixes the issue.

Not sure if this'll be helpful at all but I'll mention it just in case. I use the Flux integration with 4 Nanoleaf lights and I've noticed that when this issue comes up, 3/4 lights will have been updated to a darker orange color while the last one will have remained the whiter color. It's always the same light bulb that ends up remaining white.

[400HPMustang]

Just wondering if there was any traction on this issue? or if anyone experiencing it has seen different behavior? I personally quit using the Thread/HomeKit integration over it.

[ffedee7]

I continue having these issues, but less than before. I have to manually restart HA every few days. But when it works, it works very good.

[iGageit]

It's been a lot more stable for me the past few weeks. I found instead of restarting HA each time all I need to do is unplug my Skyconnect and plug it back in and boom! thread works again.

[400HPMustang]

It's been a lot more stable for me the past few weeks. I found instead of restarting HA each time all I need to do is unplug my Skyconnect and plug it back in and boom! thread works again.

Hmm...interesting. Every few weeks is definitely more tolerable than the every other day I was having problems. Still having to unplug my SkyConnect and plug it back in means I have to go to my rack and do the thing.

[Jc2k]

I'm one of the homekit maintainers and I quit using it because I was fed up of it falling over. My production Eve devices are all connected by homekit over Bluetooth with a bunch of esphome Bluetooth proxies.

I have little time atm and there are too many bugs that are the networks fault. The last time I thought I'd debug my thread network 1 of my brs had just switched to a different ssid. Because of this I don't think the homekit over thread code has changed since you last tried. I just can't catch a bug in progress that's mine to fix.

For some people on discord it's still multiple times a day things break.

HomePod should be doing better. We have TREL now. That should compensate for mesh partitions.

Skyconnect - the latest multiprotocol firmware crashes fairly often for people on discord.

[400HPMustang]

@Jc2k so are you saying that I shouldn't bother trying to move everything over again? or are you saying if I do, I should try the HomeKit method and not use my SkyConnect for it?

[iGageit]

I think you have to use both if I'm not mistaken. I first connect my thread nano leafs to HomeKit, then remove them so that HA can see it with the Skyconnect. then after connected they get pushed back to HomeKit with the HomeKit integration. It has gotten a lot more stable for me and as long as you dont mind unplugging the sky connect every few days/weeks it's great!

[Jc2k]

@Jc2k so are you saying that I shouldn't bother trying to move everything over again? or are you saying if I do, I should try the HomeKit method and not use my SkyConnect for it?

Lol I will never give you a straight answer like that.

It works well enough for some people clearly. But it didn't for me.

And I mostly deal with the people that have recurring problems. So bias.

Homekit Brs should in theory be better than skyconnect now. Especially if you have a handful running iOS 17 with TREL.

But lol in practice some people still have more luck with 1 skyconnect that's under 50 usb cables than they do with 5 HomePods. They all seem to run proxmox but it's unclear if that's just because proxmox is popular.

[MattWestb]

I think its still the underlying routing problems is have more OTBR for the mesh network.
I running my "Billy RCPs" with only one OTBR activated and its rock solid with the addon and the other 2 is only running Zigbeed in the test network.
Look in the log of HA and in the host system if getting some routeing problem then ts happening (likely at kernel level).
For my is little strange that is no fix from Thread consortium for having more OTBR and also backbone routers that shall fixing all this problems if its working as expected.
For me BT is working very badly with EVE Energy and Nanaoleaf lights but thread is rock solid (all is Thread versions and not update to Matter).

[issue-triage-workflows]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[Tuckie]

Running the latest version of home assistant. Still having issues with my smartwings thread blinds becoming unavailable.

[mvgijssel]

I’m running the latest haos + skyconnect using Kubevirt with a dedicated passthrough usb ethernet with an ethernet attached Apple TV. I replaced my UniFi network with TP-Link Jetstream for proper ipv6 mDNS support to work with Matter as mentioned here, but never got the Nanoleaf Essential bulbs to work reliably.

Tried resetting the bulbs multiple times, reconfiguring haos, resetting HomeKit and disabling the Nanoleaf Cloud sync, but with or without interaction the bulbs would become randomly unavailable. All my sensors are from Eve which don’t have this problem and are very stable, which makes me believe this is a Nanoleaf software issue. I’m (unfortunately) sticking with Philips Hue for lighting until this is solved somehow.

[rapton]

I have the Same Problems with Two lightstrips from Nanoleaf. Every day they go offline and I must restart. I think to change to govee M1 Matter.

[ebertek]

Same here with 3x Nanoleaf Essentials A60 (NL45, without Matter), their status turns to "does not respond" almost every day, and restarting HASS always fixes the issue. Turning off Nanoleaf Cloud Sync and removing their app did not help.

[codyc1515]

This appeared to happen for me with Eve Aqua using a combination of SkyConnect + Apple HomePods / TV, HomePods / TV-only and SkyConnect-only. I am wondering if it is wireless interference. I did not usually see any error messages.

[Jc2k]

The next release (2024.2.0) should help with recovery after devices drop offline.

Crashy devices will still crash and make your mesh unstable, nothing can be done there. But at least things should recover more often.

[wbkang]

Hello @Jc2k I tried NanoLeaf + Thread again after upgrading to 2024.2.1 but my lights are not becoming available again after a power outage. Would there be a specific log that I can enable and provide you to help you diagnose this further?

Power cycling the device or HA doesn't seem to restore the connectivity.

[Jc2k]

If restarts don't help it's a separate issue to what was fixed.

Start by using an mdns tool on your phone and verifying you can see the nanoleaf devices under _hap._udp.local. If you don't then they are not on the mesh any more or there is a connectivity problem with your border router or some network device between your border router and your HA.

Verify that first. Then attach a screenshot of the border routers that HA sees, your diagnostic report for this homekit device, your diagnostic report for the thread integration and turn on debug logs in the UI for homekit for a bit. 5 mins should be enough. When you turn them off again you'll get a file you can attach.