[RELEASE] HubConnect - Share Devices across Multiple Hubs (no longer SmartThings!)

csteele · December 29, 2019, 12:15am

Will you remember you did that next year?

Try reselecting correctly. When you "Done" out, the full list will be sent again and I presume they will all get skipped (not rebuilt). Then you can swap HubConnect driver X for HubConnect driver Y and it should work.

I remember testing driver swapping a very long time ago.. from the pre-EventSocket days. I'm dredging up some pretty antique memories.. accuracy is a question

Rxich · December 29, 2019, 12:16am

Thanks for replying. Yes I have 2 remote hubs, ST & a C5, updated drivers on all and driver report shows latest version of everything. Updated all drivers/apps and rebooted after applying all updates

njanda · December 29, 2019, 5:22am

There's a thread on the Heiman Zigbee Gas Detector here.. or were you referring to using them via HubConnect ??

kilowatts · December 29, 2019, 5:39am

Yes specifically with HubConnect, as it's an entirely new attribute and now supported by Hubitat.

storageanarchy · December 29, 2019, 2:06pm

I am also seeing this same error:

[app:1959](http://192.168.1.77/logs#app1959)2019-12-29 09:01:12.844 am [error](http://192.168.1.77/installedapp/configure/1959)groovy.lang.MissingMethodException: No signature of method: user_app_shackrat_HubConnect_Server_Instance_66.getSelectedDeviceIds() is applicable for argument types: () values: [] on line 191 (getSelectedDeviceIds)

srwhite · December 29, 2019, 7:56pm

HubConnect 1.6.4 has been released!

I have been having issues with git hub messing up my local repos on my home laptop when switching branches which has caused a some code to randomly disappear at times.. Hopefully I've got that issue fixed.

I'm also giving a sneak peak at a new feature that's going to be part of HubConnect 2; DeviceMatch. DeviceMatch is a concept where a user can select devices based on a physcial driver, a HubConnect driver, or a primary attribute.

Physical Driver: Select devices based on the actual driver assigned to the physical device.
HubConnect Driver: Select devices based on the name of the synthetic HubConnect driver. This is useful for selecting virtual HubConnect devices on the server to another remote hub. (i.e. Remote A -> Server -> Remote B)
Primary Attribute: Selecting based on the main device attribute.. (The way devices are selected now)

What's New?

Support to Netatmo Weather Stations
Sneak preview of HubConnect 2.0 DeviceMatch feature for Netatmo weather stations.

What's Changed?

No other changes.

What's Fixed?

Hubitat: Fixed error missing method "getSelectedDeviceIds()" due to bad git commit.

SmartThings: Fixed potential error when saving devices to server.

New Drivers (Hubitat):

Netatmo Basestation - A virtual driver for the Netatmo weather base station.
Netatmo Additional Module - A virtual driver for additional Netatmo indoor sensors.
Netatmo Outdoor Module - A virtual driver for the Netatmo outdoor sensor.
Netatmo Rain - A virtual driver for the Netatmo outdoor rain gauge.
Netatmo Wind - A virtual driver for the Netatmo outdoor wind gauge.

New Drivers (SmartThings):

Netatmo Basestation - A virtual driver for the Netatmo weather base station.
Netatmo Additional Module - A virtual driver for additional Netatmo indoor sensors.
Netatmo Outdoor Module - A virtual driver for the Netatmo outdoor sensor.
Netatmo Rain - A virtual driver for the Netatmo outdoor rain gauge.
Netatmo Wind - A virtual driver for the Netatmo outdoor wind gauge.

Note: With this release, the HubConnect server code did not change, so that version remains at 1.6.3

Simply import the code for all files and save. There is no need to visit each app and click Done with this release.

Files Changed: Server Instance, Remote Client (ST & HE)

JasonJoel · December 29, 2019, 8:41pm

Upgrade to 1.6.4 went fine for me.

One comment on the device report... It would be cool if it listed the devices based on Device Label, not Device Name...

Otherwise for some compound/parent-child devices you get this, which isn't as useful:

srwhite · December 29, 2019, 10:13pm

Glad the upgrade went well.

Using label when available is coming in the next release as is support for running the report on hubs that have security enabled.

And of course normalizing the color codes (i.e un-decorating the Christmas theme).

woodsy · December 29, 2019, 10:16pm

I have not upgraded to the 1.6.4 version. Would this give me the Christmas effect?? So far it only reports Red, not Red and Green.
And thank you for an incredable add on to Hubitat.

srwhite · December 29, 2019, 10:18pm

Yes, this one fixes cases where the remote devices do not show in the report. You’ll get both Christmas colors. For now.

woodsy · December 29, 2019, 10:26pm

Its starting to look a lot like Christmas! Wow that feature helps a lot.

Thank You, and Happy New Year!

storageanarchy · December 30, 2019, 12:59am

FWIW: on SmartThings, displayName is generally provided for all devices (and device-related events), where:

     device.displayName = device.label ?: device.name

thiago · December 30, 2019, 3:37pm

Hi @srwhite ,

I just installed HubConnect and I'm struggling with a few things.

First, I don't know why but the app running on Smartthings Classic won't let me add my Ring Doorbell to the list of devices to synchronize. Also, I have Arlo devices shown 3 times in the app (but only one will go to Hubitat as it should) Check out the image attached.

Another thing is I cannot share the devices from Hubitat to Smartthings, just ST -> Hubitat. It tells I don't have anything to share. What am I missing?

Thanks a lot for your work on this app. Always wanted to have my Arlo cameras and Ring doorbell integrated to Hubitat.

kilowatts · December 30, 2019, 4:49pm

New Server Container still says 1.6.3?

dan.t · December 30, 2019, 4:50pm

Yup:

kilowatts · December 30, 2019, 5:13pm

Got it! I was in fact prompted to hit "Done" in the apps, whether required or not.

Thanks, Christmas looking good here, even though I only have 1 outgoing device on my server.

srwhite · December 30, 2019, 5:29pm

The prompt will still pop up the next time you open an instance or remote after the update. It's just a formality since there's nothing in the 1.6.4 update that needs to be reinitialized.

cstory777 · December 30, 2019, 6:28pm

I just upgraded to 1.6.4. After upgrading to 1.6.4 I added 2 new devices to one of my hubs. When I went to share them with my Server Hub they weren't there. They are the exact same leak sensor as the one you see listed. I've rebooted the hub, no change.

UPDATE: None of my hubs are listing devices I can share other than the ones that are already shared.

UPDATE2: I went back to 1.6.3 and I can select devices to share and unselect devices I no longer want to share again.

Ken_Fraleigh · December 30, 2019, 8:06pm

I was afraid it was just me! I’m not able to make any changes to device selection on any of the hubs. @srwhite or @csteele any idea what’s going on?

jesse.fetterman · December 30, 2019, 8:22pm

I have some questions with HSM pushing from main hub to remote hub. I can chance the arming state of HSM on the main hub from a remote hub, no problem. My problem is if I push the armed state to the remote hub, where i have Webcore running, the hub receives the change via the log but does nothing with it unless I setup a dummy instance of HSM on the remote. Is there any other way to accomplish this? The problem I ran into is after a reboot of the remote caused by a power outage it pushed HSM armed to my main hub and as you can imagine caught everyone off guard. Id like to keep this setup but without having to keep the HSM app on the remote hub. Thanks!