I have 16 nanoleaf light bulbs on a thread network and I have the SkyConnect mounted pretty high up on a wall in a central room of my one floor house. The house is about 2,500 square feet. I haven't had any pairing issues albeit it taking a while for some of the bulbs and at times taking a second try but I managed to get all of them paired. If I have only that one SkyConnect is this likely a connectivity issue? My house was built in the 50s so it's quite old but it's not big so I didn't think it would be much of an issue.
#SkyConnect issues on Thread network
low garnet
fervent yacht
there shouldn't be any issue connectivity-wise; thread is a mesh network that automatically manages internal routing, so a single thread border router near the center of things should work well.
adding additional thread border routers is possible but shouldn't be necessary for that size of network.
(with currently available hardware, sometimes adding additional thread border routers, depending on the vendor, can cause problems with network routing...)
low garnet
adding additional thread border routers is *possible* but shouldn't be necessary...
Oh I wasn't thinking of adding an additional one, just replacing my current one with one that has a larger antenna
Like a Sonoff ZBDongle-E
I was surprised it was having so many issues considering the fact it's supposed to be a mesh network
If I restart OTBR and Matter Server every few hours though it fixes itself
It seems from these logs it could be related to multicast DNS but this doesn't operate on WiFi so I'm not sure
fervent yacht
yeah, from the otbr logs that definitely looks like thread radio signal issues. what devices do you have connected? lots of people have been reporting issues with inovelli white switches (edit: nvm, you said nanoleaf bulbs) :/
the main things that i'd recommend looking into are the same things as zigbee - make sure the dongle is on a usb2 extension so it's not near any usb3 ports - ensure that you don't have any nearby wifi equipment on an overlapping channel (e.g. if thread is on channel 25, avoid having nearby wifi equipment on channel 11)
the matter controller makes mdns requests to look up the ip for matter devices, but for thread those mdns requests are actually answered by the thread border router. Inside the thread network, devices use a different protocol (SRP) to register themselves to a thread border router.
there is a lot of traffic needed to query and set up all subscriptions on the devices when you restart the matter server, so seeing some traffic issues right after restart might not indicate an actual problem. After restarting the thread border router, it could also take a little bit for thread devices to sort out their service registration, during which time the matter integration will report that it's unable to find them via mdns.
also for nanoleaf essentials matter over thread devices, make sure the firmware is updated to ... 3.6.196 or later. earlier versions have some network stability issues. You might need to use the nanoleaf app to install the updates (which it does over bluetooth).
low garnet
there is a lot of traffic needed to query and set up all subscriptions on the de...
The weird thing is restarting actually fixes it for a few hours
Then they drop off again at random
I'll check the USB and wifi thing though because it is definitely near both I think
low garnet
also for nanoleaf essentials matter over thread devices, make sure the firmware ...
Oh and I do have all of my lights updated past that version, some are even on 4.something but not all of them wanted to update to that for some reason
fervent yacht
Yeah, from conversation in the Nanoleaf discord it looks like there must have been some issue in the 4.x firmware that made them halt the rollout.