I've been using HubConnect for years and it has worked well. Are there any advantages of HubMesh over HubConnect other than it being an official app?
Would it be painful to switch?
1 Like
I'd say the most notable advantages are that it's built-in (so you don't need to install any apps or drivers) and works with any device type/capabilties (no custom driver needed on the "remote" hubs--everything gets carried over as-is). Because it works at some sort of "system" level and not as an app/driver combo like other solutions, it's likely also more efficient (and certainly can be if you have multiple remote hubs given that it does broadcasting rather than HTTP to each hub specifically). How much that matters in real life is likely not significant for most users, at least if you aren't having problems.
Unfortunately, switching would be a bit painful. It's just like swapping out any other device: share the device with Hub Mesh, then swap out the HubConnect device in all apps. Then you can remove the HubConnect device. On a related note, Hub Mesh does have a feature that makes it easy to swap out one Hub Mesh shared device for another, but that only works if the existing device is/was already a Hub Mesh device. (You could do that with HubConnect, too, by manually editing the DNI to the correct format and changing the driver if needed, but this will similarly only work within the same HubConnect app/child app).
1 Like
I have been using HubConnect for a little less than a year without any issues or problems. I have 2 C7 hubs on the same subnet....one hub has all my devices (about 60)...the other hub is only running an Envisalink community app that interfaces with my Honeywell Vista panel. This Envisalink app, which uses telnet, is pretty chatty, so it really requires its own hub.
HubConnect has an option for syncing HSM modes which is my whole reason for 2 hubs...I don't believe HubMesh has any HSM options....so I going to stay with HubConnect. If it ain't broke......
Not that painful. Took me all of about 10 minute. I removed HubConnect after installing HubMesh and converting my apps to use Hub Mesh devices.
1 Like
I switched a bunch of devices form Hubconnect to Hub mesh and the way I did it wasn't too bad. A bit tedious but I just did a few at a time.
I would share the device though hub mesh not touching the HubConnect share. Then on the shared hub It would create the device name with a on Hubname extension on it. i.e Living room light on House C7. House C7 being the name of the Hub the original device is on.
Then you go to the shared Hubconnect shared device and in the section that list all the apps it uses you can click each one and swap the Hubconnect device for the hub mesh device.
Once you swapped everything you delete the HubConnect share. I would do a few a day and I eventually got them all swapped over.
Depends on how many hubs are involved. Mine was more time consuming, but it wasn’t painful.
Also, unfortunately, Hub Mesh doesn't support remote hubs. You need Hub Connect for that. I use both, Hub Mesh for local hubs. Hub Connect for a remote hub.
3 Likes
