This has happened on two C-7 hubs. I've added two Third Reality Water Leak sensors (which other people seem to have no issues with) to one and one Turya 4 button to the other.
I get the first update (battery, dry/wet, whatever it is) and then nothing after that. They appear in the Zigbee list but with no update date. They don't show up in the Zigbee map.
Seems I can add Zigbee devices but they're not working past the activation. Removing them and adding them again does the same thing.
I had similar problems. I moved the Hubitat hub away from the WiFi router and all my problems went away. 10 feet or more should be enough. I should say most of my problems went away. Still having trouble with Thirdreality water sensors.
This is a golden rule that must be written with bold letters on the quick start guide - HE hub is a radio device that must be positioned as far as possible from other radio transmitters (such as WiFi routers) !
Somehow that made a difference and seems to have worked. Is it a Third Reality specific thing, a new Hubitat quirk or due to some weakness in my Zigbee network?
So glad it helped. It's from a highly technical dissection by @kkossev and @dandanache regarding some specific hub behavior during pairing and security key exchange, and many details I don't totally understand yet.
Does that mean even if the 2.4 WiFi is a completely different channel from the router wifi, it should still be at least 10 feet (3+ meters) away?
(I currently have mine within 1 foot!)
The WiFi and the Zigbee channels are very close to each other. They are all in the same 2.4Ghz band, so any transmitter that is close to the Zigbee device radio will more or less 'jam' the receiver for the short transmission periods. These conflicts can be seen when using a Zigbee sniffer as multiple quick retries of the same data packet.
The Zigbee protocol is very robust and handles these conflicts very well. Still, a bigger separation between the devices sharing the same radio band is always better than placing them near.