can’t that be done on a per device basis?
i still want my bulbs and physical switches to sync, but not the virtual switches that I use to trigger automations.
Maybe. I can see value in selectively disabling synchronization in other scenarios, like with shared mobile devices. Let's see how much work that involves.
3 Likes
I'm having problems with a device's state synching across hub mesh. When I change the value of a GV on hub1, it takes several minutes for the state change to show up on hub2. I assume this is not expected behavior?
I've tried UDP and TDP. Makes no differences. I'm running an Orbi mesh router. I've tried with and without IGMP--also makes no difference.
Any ideas? This is messing with a bunch of my automations....
So does this act like a real mesh and offloads the work to the closest hub or is it literally a mirror of your devices only virtual?
Only Virtual.
1 Like
Hub Mesh does not appear to work if one hub is connected to the network via a Powerline adaptor. I have a C5 and a C7 hub and when they are wired directly to the router both hubs see the other as "Active Hubs". If I move one hub, either the C5 or the C7, to a Powerline adaptor leaving the other one connected directly to the router the C5 will not see the C7 as an active hub. However the C7 will continue the see the C5 as an "Active Hub". Both hubs continue to work just fine, with all network connections, devices etc. no matter if they are wired to the router or the Powerline. Just no Hub Mesh. Any ideas?
I believe that Hub Mesh using multicast packets. And I believe that some powerline bridges restrict multicast.
Switch to tcp?
Thanks for they replies.
Both hubs are using udp.
I don't think the power line is restricting mulicast. The C7 hub can "see" the C5 hub no matter what the configuration but the C5 can only see the C7 if they are both connected directly to the router. Kinda strange and I can't figure it out.
Depends on the make of the adapter a quick Google search for powerline multicast brings up a whole host of issues depending on the brand. Some have resolved the issue flashing openwrt firmware. There are definitely known issues with multicast over powerline.
A possible alternative if running an ethernet cable or wifi dongle doesn't suit your needs would be a moca bridge. Basically bridge over coax. They're probably up to version 3 or 4 by now.
1 Like
It looks like both aalyar and lewis.heidrick were probably right about the multicast. After reading more reviews (TP-Link TL-PA9020P) they seem to have an incomplete implementation of multicast. I will try firmware updates but I don't have much faith it will work.
Thanks for the info guys. A great forum.
5 Likes
The Hub Mesh is not going to work with the powerline adaptors I need to use. However the Hubconnect solution worked perfectly and gave me the ability to sync devices between my hubs.
Thanks again.
2 Likes
I second that.
Well I tried TCP again, maybe for the 3rd time and this time it worked. I was able to share a device from the hub (remote) that is connected to the powerline adaptor. It never worked at all before. However...
I am getting this message in the log on the remote hub every 10 secs. It may work but it sure is generating a lot of traffic and seems to be having problems. It started before I shared any devices.
dev:432021-02-26 09:15:03.340 am warnConnection to Server Hub has failed with error [failure: null: Name or service not known]. Attempting to reconnect...
dev:432021-02-26 09:15:03.290 am infoAttempting websocket connection to Server Hub (0)
dev:432021-02-26 09:15:03.279 am traceInitialize virtual Hub device...
1 Like
Those look like HubConnect messages... did you properly disable it?
1 Like
I disabled HubConnect and you were right, the messages stopped. I was not aware they did not play nicely together. But Hub Mesh still seems to be working so I guess I will test it out. I just finished writing my RM4 rules, bummer.
I wonder why Hub Mesh decided to start working when I tested/rebooted hub and remote everyway from Sunday. Then after sitting quietly for a couple of days it started working. Hmmm.
Thanks for the help again.
3 Likes
It usually takes a few minutes for TCP-based implementation to find other hubs. It has to go around local network and check each possible IP address, including ones with nothing on them. And the implementation can't just try connecting to everything at once, because many routers would consider it a spammer and temporarily block connections. UDP, when it works, is much faster about discovery.
1 Like
I got out my spare C7 about a week ago and moved over my Sensibo, Hue, and Tasmota Integrations from my Primary C7 ... I've gotta say, splendid job Hubitat Crew, Hub mesh is amazing and very simple to use! 
I was also able to use the RM backup and restore functions to duplicate a few rules I needed on the Secondary C7, it was painless! Just a Brilliantly simple, yet powerful, system! Thanks team.
4 Likes
I have a new issue with Hub Mesh. I am already sharing RM variable between 2 hubs. I added another variable to share and for the life of me I can't see it in the other hub. I have tried stopping sharing RM , syncing both sides then sharing RM again. The new variable just doesn't show up but all the others do. Apart from this hub mesh is working very well. Anyone any ideas on how I can resolve this?
