This has happened temporarily after updating (for twenty minutes or so), but now it seems stuck since last night.
Since updating one of my three meshed hubs is offline. I've tried rebooting them all, refreshing on the mesh page, I can't get it back. This isn't fun please help.
I may be having a similar issue that I'm waiting for support to get back to me on. All I know is that it was apparently obvious what had caused it. Have you tried disabling scheduled full mesh sync from the hub mesh page? Then reboot the offline hub.
I will try now, thank you.
I had some devices drop off with the update, but I re-copied the security code from each hub to the other and re-started. The devices showed back up again. I haven't had any other issues from this update.
One of my three hubs is still not showing up on the other two. I've tried disabling and enabling hub mesh. What else can I try to get things up and running again.
If they're persistent about not seeing each other, try switching hub mesh on all three from UDP to TCP in Settings - Hub mesh.
Please give them a few minutes to find each other afterwards, TCP discovery is slow.
TCP got things up and running. Is it just slow to discover at first, or is there an overall performance hit using this protocol? ie. is there any reason to go back to UDP? FWIW, UDP had been working perfectly up until last nights update. Today's update didn't fix it.
It creates more network traffic than UDP, and response time is slightly worse (by milliseconds).
If it suddenly breaks like it did, no.
The discovery part for hub mesh hasn't changed. We added TCP based implementation because the slick UDP based one didn't always work or worked unreliably for no apparent reasons. There's just no practical way to troubleshoot individual networks.
Download the Hubitat app
