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



Reverted to the stock Remote Client code (eliminating my questionable modifications :slight_smile: ), updated the ST DTH to the new one, and tried it--seems to work so far! (And I'm pretty confident this fixed it sent it sent the value as 55.0 and not 55, where "55" is the setpoint I chose, which would have likely failed before.)



@srwhite I think I got this puppy up and running finally, awesome app!. I have a question. Does the devices in the "coordinator hub" must use the "HubConnect" version drivers? The reason I ask is My Fibaro Wall Plugs AND the Zooz Power Strips it automatically selects "HubConnect DomeAeon Plug as their drivers.

The problem I'm having is I'm trying to eliminate rule machine on the remote hubs, but with the coordinator hub selecting that driver I'm unable to write a custom command rule that I have in the remote hub that resets the energy meter value to zero once per month. I believe I've figured the driver to be the issue as I have the custom command rule still up on the remote hub that has those devices using their native drivers, but in the cordinator hub with the aeon driver I'm missing the ability to select "reset" on the custom command.


"REAL devices" need real drivers.

If your real devices are joined/paired to 'coordinator (Server) then that's the driver you need.

If your real device is on a Remote Hub, then on 'coordinator' (Server) you need the Universal Driver for that device 'category'. ( Switches need "HubConnect-Switch.groovy", for example. )

HubConnect 'publishes' the standard set of Attributes for that category. If you need another attribute, you may want to explore the Custom Driver feature.



That's what I was afraid of...... well crap, that custom driver thing is beyond my skill set. I guess I can just leave rule machine running on the remote hub with just that one rule to reset energy once a month. Was hoping to eliminate it completely and all rules ran on the coordinator. But it works either way.


Really isn't a need to eliminate all rules from the remote hubs in my opinion, rule machine hardly uses any resources. I have rules setup on all 3 if my hubs over 100 total with the coordinator only running the rules that does TTS.


My experience is that I put the automation on the hub that has the real device. There are cases where I want to 'gather' events scattered across the hubs but 90+% of the time, the rule is going to work more smoothly.

@bfara83 said it first.

The surprising thing for me in this evolution is how few apps I have on a Hub now. One day I wanted to screen cap my Apps page for someone here and I saw so many 'orphan apps' -- that I had installed, and found I didn't need/use. So I did some house cleaning and deleted them and the App Code or Driver code. Now it's almost embarrassing to display my App list... It looks too short for what I'm getting out of it. :smiley:


One note on SYNC on custom drivers. Still doesn't work, as mentioned before, but it is becoming more of a pain than I expected.

There are some values I have configured to come across that just don't change often and are hard to trigger a manual change on. So I'm working a lot harder to get the initial parameters over than I thought I would have to.

So whenever it makes sense to work on that again versus all of the other planned features, it would be great to get that working again.


Happy Friday!!!

SmartThings Remote Client v1.3.2 has been released today! This release brings parity between Hubitat and SmartThings by adding the ability to send mode changes from a SmartThings hub to yourt Hubitat server hub.



Is there a trick to get all hubs to sync "time"? If I reboot all 3 hubs, the one I started with displays the correct "current hub time" in the hub details settings, the 2 new hubs I added show an hour ahead. After each reboot, I must go into the hub settings of the 2 new ones and click the "update time from browser time"?


Oh hell no!!


Three hubs in one house is the same as one hub in three houses. Time is a 'network resource' in the form of an NTP server somewhere. ( I have one in my house, my DHCP issues it's IP on every DHCP response.) There was a discussion in this Forum regarding where Hubitat gets time. I never saw the definitive answer. It came up in terms of Firewall Blocking, if I remember right.

You should not have to be setting Time more than once per home/per hub. (Next time you move to another state and have to change timezone, that will be the 2nd time you should ever have to set time.) If it's not working that way, my first reaction is 'fix it' so it does :smiley:


Phrasing. :slight_smile: We are all here BECAUSE there is no parity. Hubitat rules!


I take it that means I should contact support...lol?


Maybe.. you know your network, better than me. (Ok, wait, yes, I'm in on your network now.. ok, what's that blue box over there doing?) :smiley: :smiley:

If you have a Firewall blocking the Hub(s) from getting internet time: (eg. pool.ntp.org on a C5) then yes, apparently you'll have to set browser time on a hub.


On SmartThings/DeviceTypes didn't have Omnipurpose-Sensor. With motion sensor Aeon Multisensor 6 what the is Device Types I need to choice with 7 current states ? Thanks.


So the Omnisensor type exists as kind of a catch-all for sensors. For the Multisensor 6 you will want to select those devices as Omnisensor. I have a couple of them and it works perfectly with them.


Sorry, on ST device type :

HubConnect/SmartThings/DeviceTypes at master ยท HubitatCommunity/HubConnect ยท GitHub

don't have type for Omnisensor ?


So am I correct is assuming Smart Things will not see devices on the Habitat Server? I was hoping this was 2 way for devices. so that all devices were on Hubitat, but I could do rules on ST so that I could use ST for text messages and complicated rules that Hubitat cant do.


@srwhite I finally installed and configured HubConnect this morning, and removed HubLink. Wow! This is fast! Thank you for your efforts and skill! This is the second user app that I have installed that has been rock solid and functions better than expected. Substantially faster than HubLink, and much more configurable. Thank you again! FYI - the first and only other user app that I have had success with is the new homebridge maker api...


Incorrect, you can share devices between both hubs, ST and HE.

Incorrect too, you can do the same on HE, but only if you are a webCoRE lover then ST cloud is a better place to run webCoRE, but still attached to a cloud and HE is local power, so use it! :wink:


how do i get items from he to show up in st