I'm finding dead ends in my searches. First tried Hub Link but when I tried to load Bravenel's Send Hub code I get an error message. Tried the links for Hub Connect and they were broken.
I'm moving from ST and would like to link the hubs if that is still possible.
It's worth mentioning that SmartThings can remove their Groovy IDE based interface at any moment as they have been preparing for Groovy demise for a while now. Hub Connect also uses legacy SmartThings Groovy, as far as I know.
Where are you installing this code? That is SmartThings code, and there is nothing you need to install on Hubitat for Hub Link/Send Hub Events.
Along these lines, beyond the fact that ST will eventually (soon?) discontinue their classic Groovy IDE and thus both HubConnect and Send Hub Events will no longer work as-is, it should be noted that the latter is one-way: ST events to Hubitat. It doesn't "sync" devices in the other direction, just in case this matters for your use. Some people thus prefer HubConnect.
Node-Red with the Samsung Automation Studio pallet uses the new Smartthings API. If you need long term support this will be your best option. It takes a little to setup though.
The things your need just for polling Smartthings are:
A always on computer to run Node-Red. This can even be a Raspberry pi.
To load the hubitat pallet and Samsung Automation Studio Pallet into Node-Red
A Samsung developer token for your Smartthings account.
If you need Smartthings to send immediate event changes you will also have some additional work
Is there a reason you're looking for HubConnect? The developer left the platform some time ago, and AFAIK, it hasn't received much attention since then, although it is likely to still work (on Hubitat only). If you are using two Hubitat hubs on the same network, I'd suggest Hub Mesh instead.
I have two C-7 hubs in two different locations and would like them to share some devices.
I've been trying to use Hub Mesh with Tailscale, but unfortunately, with firmware upgrades, the IP Address can no longer be manually input for the hubs.
I see! That should work, but I'd say you're unlikely to get much support if it doesn't.
If you don't have a ton of devices, and particularly if you just care about a specific thing or two from each (e.g., switch on/off), something like Maker API or a Rule triggered by "Cloud endpoint" could work using all built-in options (e.g., rule when X happens on hub 1, send HTTP GET to cloud endpoint that triggers rule on hub 2), but I'm not sure how complicated your goal is.
If a notification is all you want, that would be pretty easy to do with a Rule triggered by a cloud endpoint on your hub that has your phone (or whatever) added as as a notification device. On that hub, create a rule and select "Cloud endpoint" as a trigger. For your actions, create a notification (e.g., "Water detected on sensor X.") Make note of the cloud endpoint trigger URL.
On the other hub, the one with the actual sensor, create a rule, too. Add a trigger to this rule for the sensor becoming wet (or whatever exactly you're looking to do). Create a single action that sends an HTTP GET. For the URL, provide the one for the cloud endpoint trigger you created and noted above.
Repeat for your other sensor if you want different notifications for each.
For a single dashboard containing devices from both hubs, you'd need a bit more, and HubConnect could be one solution. Or you could create virtual devices on the hub that has your phone and use rules like the above to manipulate the state of these devices instead of sending a notification, or you could expose them to Maker API and use Maker API cloud endpoints instead of a rule to make things a bit easier (I think) on the hub with the virtual devices -- but I'd maybe see if you can get the other, simpler idea working first and revisit this if you still have need for a "full" device on the other hub.
Thanks for this! I will try the rule triggered by a cloud end point and see if that works.
I have gotten hub connect working also but seeing that there is not much support for it, i may go with you suggestion and see how it develops for the alerts.
In addition to @bertabcd1234’s option above, another possible solution is to use something like Pushover for notifications. I have multiple hubs and use Pushover for all of my push notifications to my phone. It is very easy to configure using Hubitat’s built-in Pushover device driver. It does require a one time ~$5 fee per platform (iOS, Android, Browser), but you can install and use on multiple devices for that one fee. I use the iOS version on two iPhones and two iPads. I have each of these configured as individual devices on my hubs, so I can send targeted notifications as necessary (or even all devices at once via yet another Pushover device on my hubs.)