I just got a Linkind RGBW Matter light bulb that I don't really need. It successfully added with Alexa. However, when it wouldn't add into HE, the HE message asked if device was on same LAN. Before I try adding an opening in the Firewall for the light bulb(s) to HE, will HE find it when pairing or will HE only look on it's network for Matter devices? All of my Alexas and this bulb are on my IoT network which is exclusively 2.4Ghz. My main wifi is dual-band and it looks like the bulbs won't connect to a dual-band nor would I want them on my main.
Matter requires mDNS, and this tends to be a problem if you have multiple vLANs. I suspect that is the root of the problem you are running into. I don't know that dual-band is a problem (as long as they are, in fact, the same network), though some (many? most?) Matter Wi-Fi devices might only support 2.4 GHz.
1 Like
That's what I was afraid of. That made for a short Matter experiment. I guess the bulbs are going back to Amazon.
1 Like
I get this same error re: "...be on the same LAN"
I'm pretty sure I don't have multiple vLANs. I do have a dual band Orbi, but nothing special in it's configuration.
Are there some other quick things I could check to see about my LAN?
Matter is turning out to be a big bust unless I can get past this. Should be easy, yeah? 
Thanks,
Hubirat 
Are there mDNS options in your router you can make sure aren't disabled?
And I assume you were able to get your Matter device commissioned via some other means and then generated a paring code using that system (not the one that came with the device)?
I can't even find the mDNS settings in my router. Been through every setting looking for mDNS or Multicast. Nothing that I can find. I feel like networking stuff always has a hundred names for the same functionality, is there something else I can look for? IPv6? (I'm suuuper network dumb)
I was able to pair the Matter bulb via the Alexa app. When going into the app to get the new pairing code, it fails with "Alexa can't connect to your device. Make sure it's powered on." It's on and is within 2 feet and the Alexa app can control it... 
RFC 6272, maybe, but not sure I've ever seen that in the wild? Otherwise, Bonjour (Apple) or zeroconf are related, and Matter might also need DNS-SD if you see anything about that. Grasping at straws now, though...
IPv6 on your LAN shouldn't matter since Matter will form its own network with link-local addresses (not assigned by your router), but maybe there are odd things with certain network setups compared to others.
This seems like the problem, then. You need a code to pair it to Hubitat, which would be generated in this step. How are you getting it without getting this far? (Again, the code on the box or device won't work.)
To fix this problem, restarting the device itself, the Matter controller you're using, or your Thread Border Router (if applicable) are good first steps. I've also found that Apple Home (not sure about other controllers) gives a weird error like this but not a helpful error if you try to put it in paring mode too quickly twice in a row, maybe if the first attempt hasn't "expired" yet (even if you've long lost the code!).
Restart then recommission via the Alexa app? I've done this several times. So I can t just reset the device, take the 11 digit code from the box, not commissionit thru Alexa, and then just use the code in Hubitat?
I mean if I have to work this hard to make it work, I don't wanna. 
No, Hubitat cannot currently commission a Matter device; you need to get it on a Matter Fabric first, then put it in "pairing mode" to get it on Hubitat (see: How to use Matter on Hubitat Elevation | Hubitat Documentation).
I wouldn't suggest re-commissioning, though it can't hurt (probably--unless this is what the device has problems with afterwards), just restarting the device and try putting it in pairing mode again (via Alexa) to see if that alone helps. (If that is all you meant, note that commissioning and pairing are technically separate processes, though the former -- necessary once only -- is almost always immediately followed by the latter.)
That being said, if you don't have anything set up in Alexa for it yet, removing it from Alexa, re-setting and re-commissioning the device, and then trying Hubitat again might work. (I don't want to say anything bad about any particular controller but do think this is the one people had the worst luck with during testing. Also, if your device rhymes with Schmanoleaf.)
This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.
