Am getting frustrated... I have two C-7, SW rev. 2.2.4.153. The first one has currently everything on it and was running for a few weeks now without major problems. I added the second yesterday with the intent to use one for devices and the other for all automation (and to have a spare one that could take it all if needed).
So, went through the so called documentation and the problem starts with the hubs not realizing that there is a second one on the same subnet, same switch and both being accessible from the PC on the same subnet. Both hubs are connected to the cloud with the same account and are both listed in the portal correctly as well.
Rebooted several times, switched from UDP to TCP and .... nothing.
I understand that this is a new functionality, but it for sure is more than frustrating if not even the basics seem to work.... Any thoughts on what I may be doing wrong?
I haven’t read all the hub mesh threads closely, since I haven’t tried out the feature myself yet.
But I believe it requires multicast, or the initial version does at least (there may have been a subsequent update to allow for alternative communication between hubs, but again I might be mis-remembering since this hasn’t been a priority for me).
What kind of router are you using, and does it allow multicast packets on the LAN?
The UDP discovery part can be tricky because it relies on multicasting, and there's a million possible router/switch configurations out there.
If UDP doesn't work, switch both hubs to TCP and give them ~5 minutes to find each other. TCP uses basic HTTP calls for initial discovery, but it also has to traverse the whole subnet. Following handshake is much slower over TCP as well. None of this should need a reboot in 153. If that doesn't work, let me know, I can ramp up logging and see what's going on.
Edit: There's no difference in hub mesh discovery/handshake between 148 and 153. Rolling back will not make a difference. Just make sure both hubs run the same version - 148 and 153 will not talk nicely to each other.
Thanks for checking! Yes, they are both on the same (latest) version and had "enough" time to find each others over night via TCP - which did not happen. Prior to that, I had them communicating via UDP for several hours with the same result. UDP traffic is fully supported by the switch they are both on.
While you're waiting, if you haven't already seen, there is a Hub FW update to .156. Probably won't connect your two hubs, but it can't hurt, and it has some general improvements on .153.
@TheGerman, could you please update to 2.2.4.156 when you get a chance?
I looked at the logs, and there's an error popping up on Home2 while trying to sync Office bulb on Home. I think it's because of a mesh bug that's fixed in 156, though. Please let me know.
I reset the second hub a few times, added it back in and suddenly, they saw each other, It was 100% not network related, so I simply assume it was simply related to the early version of the mesh software...
The office bulb error is normal as it is offline most of the time (connected to a light switch).
I had issues with getting my second hub to detect but sorted it out by setting a DHCP reservation for the new HUB's IP and using the advanced function to find it via the MAC address.
.
