@Emil said in Matter devices showing offline:
@buckyswider _matterc._udp is for commissioning, so that one is only present while the device is "pairable", typically 15 minutes after boot when the device is factory reset (i.e. no Matter pairings yet).
_matter._tcp shall be advertised after the device has been commissioned (paired), one service per "fabric" (i.e. per "hub" it has been commissioned to), as long as it is powered on and connected to the network. If it does not advertise this service, it will not be possible to reach it by Matter controllers. If you don't see this service when you expect to, it seems like a bug in that device.
Maybe you have devices from other Matter brands you can test with?
Thanks @Emil ! I think we posted about the same time, but in case you haven't seen mine I rigged up a Tapo (TPLINK) switch to test. When it powered on, it advertised both TCP and UDP matter protocols. When I connected it to the FLIC hub, neither was showing anymore. I now saw this note, so I powered up the switch again, and it it showing both _tcp and _udp. Now an hour later...it is not showing either. I wonder if this is some anomaly of the scanner app? Oddly, I do now see another device showing _matter._tcp- but that appears to be an Amazon Echo. (IP matches that, but it looks like the scanner is showing a MAC, which doesn't match...aye karumba).
I will keep looking at the services scanner occasionally to see if anything else show up. Maybe I'll pick up a third manufacturer's matter wifi device to see how that behaves.