User having difficulty setting up Hub Mesh after using Hub Link

🛎️ Get Help
1

I upgraded both (2) of my hubs to 2.3.3.140 and removed Hub Link after reading about Hub Mesh. I successfully shared devices on hub 1 and got hub 2 to see them in the Hub Mesh window under Linked Devices, but none of the "Linked Devices" on Hub 2 are showing in the device list. When I look at some of the apps on Hub 2, I notice that they are referencing the devices that used to work when I was using Link to Hub., but when I "Refresh" the device list while adding devices within the App, they no longer appear.

I'm stumped, anyone have an idea ? Is this something related to using Link to Hub before ?

2

Have you enabled 'Hub Mesh' on the actual device?
I assume you have as you can see them in your list.
Just thought I'd ask.
image

3

2 things, remove all hub linked devices first
Second make certain you go to Hub Mesh on both hubs and make sure the devices you want show there first>

1 Like
5

Yes. Its enabled on both ends

6

Switch them both to TCP instead of UDP and see if that cures it

7

When I deleted the hub link app, all of my virtual devices disappeared, so there do not appear to be any virtual devices left unless they are orphaned somewhere in the system.

Is there a way to check ?

As I mentioned in there 1st post, I can see all of the devices on hub 1 that I shared on hub 2.

And yes, they are on the same subject... which unless the mesh protocol uses a different method for different communications, since I see the device's and the remote hubs IP address, I assume the network is ok.

1 final thing, i enabled logging and then kicked off a mesh synch, i don't see anything. Is this normal ?

8

Some switches don't properly broadcast... That's why I suggested switching from UDP to TCP then rebooting both hubs.

9

Looks like this is operator error. Apparently you have to hit the plus sign by each device to add it to your local hub, I was under the impression this was done automagically.

I did notice now that my device name is "device on hub2". Is the full name now ? So on alexa, do I have to use the entire string, or will device be sufficient ?

1 Like
10

You can shorten things in device label that will be passed to alexa. So if your shared device name is ZOOZ LIVINGROOM LIGHT SWITCH just put livingroom in the Device Label and hit save

1 Like
11

I didn't know that the Device Label is what Alexa uses, thanks

12

I also noticed that "Rooms" don't get synched. Is this an upcoming feature ? In the interim, I assume I have to create a room locally to reflect the room remotely ?

Thanks,

13

Hub mesh does take some system resources to run, so I generally just mesh those devices I need to mesh, not everything.

1 Like
14

So, some sanity questions here: I assume that for sensors, that they will report to the hub that they are registered on, If I share a sensor through the mesh, does the remote hub now get the updates from the sensor such as movement, temp, battery etc ?

I had heard someone say that they try to run all their routines on a single hub, if so, then that implies the answer to the above question is yes..

Further, are the resources burned all the hub mesh messages from remote sensors worth the savings from moving automations to a single hub ?

15

Correct.

It really depends on your unique situation and why you've chosen to implement a multi-hub solution. There are some folks who do what you suggest - have all their automation on one hub. That's not the approach I take. I have one hub that runs most of my rules and all of my zwave/zigbee devices, a second that runs Envisalink (VERY chatty) and everything related to security, and a third that runs LAN-based integrations and a couple of CPU-intensive rules (mostly pinging the crap out of iPhones to use them as presence sensors) that are inefficient so I just throw hardware at them. I only "mesh" those devices I really need.

16

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.