#NL matter unresponsive
1 messages · Page 1 of 1 (latest)
I assume you added to HK first then HA second?
Also fully reset is a power cycle or a re-pair?
Fully reset being power cycling the bulb rapidly until it flashes red, then allowing it to do a full power cycling after.
This is after removing the bulb from HomeKit
- Current setup process that seemed to work
- Remove bulb if in any apps.
- Reset Bulb.
- Wait 30 seconds
- fully reboot bulb.
- pair to HomeKit in home app
- Open Nanoleaf app and continue setup
- Apply updates
- Back to Home app, click set device to pairing mode and copy the code
- Add to HA
- Repeat entire process if it fails, seems to randomly decide to work.
Then after a while it just stops working universally and rebooting the matter server or the fixtures doesn’t seem to help.
Just tried a day later and somehow a full reboot of the borders and fixtures did it, I’m terrified to get the recessed fixtures but I dont think there’s another high cri option whatsoever for low profile recessed units, I have quite a few on order and this is making me kinda regret my decision, at least HomeKit has been stable
That generally sounds right to me. I would read the pinned posts to make sure you don't have any unstable hardware configs (like a skyconnect)
The only other thing I can say is that NL is known to have some issues on the current firmware and that NL is aware and preparing an update but unclear when that will be ready
Yeah, I’m using an ATV and 2 HomePod mini’s as borders set up with HomeKit. Good to know it might be a firmware thing, is there any way to properly snoop thread traffic and see what’s happening?
Yes you can check with @olive stump who is a bit more knowledgeable about that.
There's two known issues, one is the resubscribe behavior and the other is that they die and restart periodically
You can but it’s a PITA
You can use vanilla tcpdump with a filter for the devices ipv6 address
If you have unifi I think they actually have tcpdump on them, but you need a vantage point where all traffic definitely passes. So if you have a single WiFi AP you can do it there
Otherwise you have to do it on haos which involves getting access to the HA container