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

I added one from HE Server to ST and installed the HubConnect Fan Control driver to ST, the ST version, with tiles.

Worked for me.

5:15:19 PM: debug Received event from Server/Study Ceiling Fan: [speed, off , isStateChange: null]
 5:15:18 PM: debug sendGetCommand(): Sending http://192.168.7.64/apps/api/582/event/81/setSpeed/%5B%22off%22%5D
 5:15:17 PM: debug sendGetCommand(): Sending http://192.168.7.64/apps/api/582/event/81/setSpeed/%5B%22on%22%5D
 5:15:15 PM: debug Received event from Server/Study Ceiling Fan: [speed, high , isStateChange: null]
 5:15:14 PM: debug sendGetCommand(): Sending http://192.168.7.64/apps/api/582/event/81/setSpeed/%5B%22medium-high%22%5D
 5:15:11 PM: debug Received event from Server/Study Ceiling Fan: [speed, medium , isStateChange: null]
 5:15:10 PM: debug sendGetCommand(): Sending http://192.168.7.64/apps/api/582/event/81/setSpeed/%5B%22medium%22%5D
 5:15:09 PM: debug Received event from Server/Study Ceiling Fan: [speed, medium-low , isStateChange: null]
 5:15:08 PM: debug sendGetCommand(): Sending http://192.168.7.64/apps/api/582/event/81/setSpeed/%5B%22medium-low%22%5D
 5:14:54 PM: debug Received event from Server/Study Ceiling Fan: [speed, low , isStateChange: null]
 5:14:53 PM: debug sendGetCommand(): Sending http://192.168.7.64/apps/api/582/event/81/setSpeed/%5B%22low%22%5D
 5:14:45 PM: debug Received event from Server/Study Ceiling Fan: [speed, auto , isStateChange: null]
 5:14:45 PM: debug sendGetCommand(): Sending http://192.168.7.64/apps/api/582/event/81/setSpeed/%5B%22auto%22%5D
 5:14:38 PM: debug sendGetCommand(): Sending http://192.168.7.64/apps/api/582/ping
1 Like

Does on off work? I can only control speed. And what do you mean with tiles?

1 Like

Well. It works in classic app not new app. Didn't know that. Has anyone got this to work with Google home? Home doesn't recognize hubitat fans as fans but it will recognize smartthings fans as fans. Problem is control doesn't work thru home

1 Like

Yes, HubConnect for ST is Classic App only at this time.

There's just one Tile for Fan Control and it cycles through, Auto, Low, Med-Low, Medium, Med-High, High, On, and Off. The logs above show I rotated through them all.

HubConnect v2.0 works with ST's new App.

1 Like

So when Google home finds this device from smartthings ( which is actually on hubitat) it doesnt work. Think this will work in 2.0?

1 Like

The only Google Home specific work added to v2.0 that I am aware of is Thermostat related. Specifically 'lastRunningMode'

1 Like

I could not find the PDF links clickable or even copy/pasteable so here they are...Apologies if this is a double post:

https://raw.githubusercontent.com/HubitatCommunity/HubConnect/master/Hubitat/apps/HubConnect-Server.groovy
https://raw.githubusercontent.com/HubitatCommunity/HubConnect/master/Hubitat/apps/HubConnect-Server-Instance.groovy
https://raw.githubusercontent.com/HubitatCommunity/HubConnect/master/Hubitat/drivers/HubConnect-Remote-Hub.groovy
https://raw.githubusercontent.com/HubitatCommunity/HubConnect/master/SmartThings/HubConnect-Remote-Client.groovy


1 Like

Yes unfortunately the PDF links aren’t clickable but you can find a list of import URLs here:
http://hubconnect.hubitatcommunity.com/import.php

2 Likes

Anyone get performance issues on their hub using HubConnect? i was using old version 1.4x (trying to hang on for v2) but i had to remove it as i was having issues with my hub and since removing the hub is so much faster on webui and dashboards etc...

I've used every version of HubConnect on the same three hubs since.. well since before there were version numbers. :slight_smile:

v1.4 was superseded by v1.5 and then v1.6 when @srwhite came back from camping in Nov '19. Screen Shot 2019-09-14 at 9.48.58 AM

The current version is v1.6.4 and v2.0 will replace it. One big difference with v1.6 is the use of the Hub Driver on all hubs. Upgrading to v.1.6.4 will put all of the pieces in place for upgrading to v2.0

I doubt there is a package available on Hubitat that hasn't (by now) been presumed to be the reason for this hub's slowdown. Under v1.4, and using HubConnect's EventSocket option, means the App is practically doing nothing. The EventSocket is a feature of the Platform, intended to be used by Dashboard. It's roughly equivalent to an unfiltered MakerAPI. The "other hub" simply listens to the first hub's EventSocket and injects Events as they arrive. Only when you're actively clicking through HubConnect's menus is the App really doing anything. (There is a 'ping' heartbeat that runs, but it's a LAN packet every couple of minutes. HSM and Modes also cause a packet, but again, just a few times per day.)

2 Likes

To be fair i've not seen anyone say they have had issues, that's why i asked @csteele
Maybe mine just got corrupted or something but the speed difference is like night and day after removing.
think i'll hang on for v2 rather installing 1.6 then 2.

When you remove HubConnect, how dashboard works ? ( devices on Hub 1, dashboard on hub 2 ... ? ). I got some error because HubConnect, right now my phone dashboard spinning but I'm not home, can not reboot the hub server.

@csteele @srwhite

I've got this error showing up in the logs of a HubConnect client hub (v1.6.4).

Screen Shot 2020-03-17 at 8.11.33 PM

Does this mean that:

  1. A device being shared by the server is missing on the client?, or
  2. A device being shared from the client is missing on the server?
  3. Something else entirely

I'd like to fix it. I cannot find any HubConnect devices missing in either direction .... so I'm hoping for some guidance.

Thanks!

What is APP:2760 ?

Server Instance or Remote Client... because it's the one displaying the error and thus the one being sent an update from DEV:718 on the 'other hub'.

718 got deleted from 'this hub'. You could try going into 'other hub' and pretending to select a device, then Done out. You should see the message go away, because it got recreated, or you'll see a log saying the Driver for that device isn't found on 'this hub'.

2 Likes

Remote client.

Will do. Thanks a bunch!

1 Like

I have not...yet. I actually switched to using hubconnect with my smartthings hub for "echo speaks" on the smartthings hub. Echo speaks is one app that IS confirmed to slow down your hubitat hub. My hub was locking up every couple of days when that was installed on it.

3 Likes

Can you please post link with thread confirming slowdown.
I have 8 echo devices without slowing

2 Likes

Hi - just setup HubConnect today ... one on each of the three floors of my house. I have a forth hub as the "coordinator hub:" where I will control everything.

I'm noticing the devices on the coordinator are never in sync unless I hit "sync". Example, I turn on a device from the coordinator (hub 1) - it instantly turns on the light at hub 2 - but the "Hublink Device" on hub one still shows "off" unless I hit the sync button.

Is this how it is supposed to work? If not, any ideas as to what I'm doing wrong? Thanks

Is 'coordinator' a Remote or a Server?

Did you install the Hub Driver on all the systems? Are you using http or eventsocket?

Screen Shot 2020-03-20 at 9.17.32 PM

Server should be similar to the above, one Hub device per.

Screen Shot 2020-03-20 at 9.19.00 PM

Remote Hubs should have one too.

"Coordinator" is a Server.

Yes, I'm setup exactly like that... nothing syncs unless I hit "Sync" in the device on the server.