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

[tony.fleisher]

I am running HubConnect v2.0.9801 to get some devices from ST into HE.
This has been running great for awhile, but today I made some network changes that resulted in the IP network of both the ST hub and HE hub changing.

I entered the key into the Server app in ST, and they are connected, but ST is now showing as remote rather than local. They are both on the the same switch, as they were before.

What is the best way to fix this so that they communicate locally?

[csteele]

You have to have selected "SmartThings Connected"

And then the UI changes and you select:

THEN transfer the Key to ST.

[tony.fleisher]

I thought I had done that the first time, but maybe not...
Is there a way to get it changed without having to remove everything and recreate/duplicate the devices that are already in HE?

[terminal3]

FYI, I had to remove all the cameras in ST and relink the arlo service. On the con side Hubconnect no longer sees the cameras as Arlo cameras, I could only add them as motion sensors or switches. Once I added them I could then change the driver on the HE side to the Hubconnect Arlo cameras driver and they seems to be back working as they were.

On the + side I now can use the motion from my Arlo doorbell in HE. Not the button which would have been nice, but motion is something.

[DaisyLee]

Anyone else see this error when trying to ad the AVR driver to Smartthings?

[142.citadelle]

I have followed the instructions to install HubConnect but when i go to smartthings app to configure the remote client to connect to the server hub i cannot enter the IP of the server hub?
What am i doing wrong?

Primary hub is
Hubitat Elevation® Platform Version 2.2.4.158, Hardware Version Rev C-7

Client hubs are ST Firmware Version 000.032.00012
One on the same network as the primary the other one is in a different location

[csteele]

Yes, I can replicate the error. Seems "Universal" is not as Universal as I imagined. We will move that driver to the Hubitat Only directory when v2.0 gets Released. In the mean time, you can replace (in the IDE editor) the Metadata section with:

Metadata Code

metadata
{
	definition(name: "HubConnect AVR", namespace: "shackrat", author: "Steve White", importUrl: "https://raw.githubusercontent.com/HubitatCommunity/HubConnect/master/UniversalDrivers/HubConnect-AVR.groovy")
	{
		capability "Switch"
		capability "Refresh"
		capability "Actuator"
	//	capability "Telnet"
	//	capability "Initialize"
		capability "AudioVolume"

		attribute "mediaInputSource", "string"
		attribute "version", "string"

		command "setInputSource" //, [[name:"Id*", type: "NUMBER", description: "Input ID" ]]
		command "sync"
	}
}

I can't be certain it will work without those commands but it does compile.

Note that the Universal Drivers do NOT have the Tiles section and thus the ST user interface for the device is largely empty, although it will function with automations.

[mavrrick58]

I would suggest you make sure you loaded the 2.0 version of Hubconnect and not the 1.6 version. I first tried the 1.6 since it is stable and it doesn't seem to work in the new Smartthings app. Then also make sure on the hubitat you have it configured and have the key up and copied to your notepad or something that you can use to load it in Smartthings. Then in the smartthings app start configure it. You should be asked for the Key not an ip address. It won't work with the IP on the smartthings side.

[swarga]

Add my voice to the paean chorus: kudos to you csteele for all your fine work! You're definitely a lifesaver! I recently ported all of my devices to HE from ST, only to discover that my Schlage Z-Wave smart locks no longer worked reliably and my ceiling fan controls made Alexa say "I don't know what went wrong" even though the commands were actually working. Thanks to HubConnect I moved my locks and fans back onto my ST hub, linked it to my HE hub, and now enjoy the best of both worlds.

[csteele]

Thanks so much but I did very little of the work.. it's all Steve White's doing (@srwhite) My portion was to be the official PITA. It was my duty to do everything wrong. I believe I hold the record for number of times I installed Server Instance as Server and vise versa. I can reliably report, that doesn't work. See? See how easy I had it?

[toninosamba]

Hi,

My hubitat hub reflects status correctly for all changes done on devices in my remote smartthings hub. The issue that if I try to change a device state from the hubitat hub, its not reflecting in the remote hub. Command just expires in hubitat, but actually the event doesn't reach the remote smartthings hub. Any guide on how to troubleshoot this ?

Thanks!
Tony

[swarga]

My apologies to @srwhite for my noob mistake.

[pacevedod86]

Hi,

I'm relatively new to this and to be honest, I haven't been able to learn how to code in groovy. I was usong the HubConnect to interact with the Arlo Pro cameras until the ST app got updates and now is using SmartThings Schema. Basically, there's native integration with the ST app without using Arlo (connect). The deal is that I had to renew my credentiaks and it forced me to delete the Arlo (connect) and link the account directly. I got the cameras back to ST BUT HubConnect now refuses to detect the cameras with the corresponding driver. I tried everything but I just lost the integration and basically, I had ST just for the cameras.

I'm on the latest HubConnect 2.0 RC2.

Tl;DR: Arlo (connect) app was deprecated in SmartThings and with the new type of integration, HubConnect doesn't detect any Arlo devices.

[terminal3]

Just FYI. I am still using the Arlo cameras with the newest Arlo integration on ST and they are working fine through Hubconnect.

I had to add them as motion sensors and switches in the Hubconnect app on ST and then change the device on the HE side to the Hubconnect Arlo camera driver.

I guess I should also mention I only use HE to turn the cameras and on off and use motion. I use the Arlo app for viewing and setting them up.

[jlauzus]

Hi,
so I got everything installed and connected but none of the devices on my Hubitat hub (the main server hub) are showing up on my SmartThings Hub (the remote hub) I'm using the new smarthings App any ideas why?

[csteele]

@jlauzus

I got everything installed and connected

Did you select devices on your Hubitat hub to send (mirror) to ST?

[jlauzus]

yep I'm trying to to send my RGBGenie remote control to ST and I selected it here

but I'm not seeing any of them in ST. did I add them in the wrong section or can the RGBGenie remote not get mirrored in ST?

[csteele]

I don't have one, but here's what I did...

Created a virtual device and selected the RGB Genie driver:

Then I Selected it in the ST Instance:

Clicked Done and at the bottom of the page is the list of drivers needed:

So then I went to ST's IDE and verified that I had the driver installed:

Then back on Hubitat, I clicked Done all the way out to Apps List and looked in ST's device list:

Like I said, I don't have one so there's no realistic testing I can do.. but as far as it 'showing up" in ST, that part works

[jlauzus]

ooo I wasnt add the drivers in ST I was adding them in Hubitat, that is probably my issue, thanks a bunch I'll make sure the drivers are added in ST.

[csteele]

Hubitat already had a driver for the device... a REAL driver that converses with the physical remote and everything. The ST end tried to create the mirrored device using the HubConnect driver.. that wasn't there.