Your Hubs are individual. That switch determines what shows in the logs of that hub.
The message you've pasted in is in the logs of your Server/Coordinator. It's saying it got a ping from Locks. The locks hub would say it got a ping from your server.
Geeze, not sure how I missed that, but that done the trick. Thanks again!
Eureka! @csteele, you may find this hard to believe, but your comments helped me find the avenue I needed to solve the problem. For others that may follow me with the same Issue.....
When you said the problem could be in the network between the two hubs, I confess that I doubted that could be the case since I had HubConnect working between ST and my coordinator HE hub for awhile previously. And my network hasn't changed any. Still, I'm desperate enough that I'll try anything. So I unplugged my ST hub (which I barely use for anything anymore so I don't really care where it's physically located), and I plugged it into the same router that the HE hub is plugged into. I then re-ran the HubConnect setup, and viola, it worked. Proving you were right.
I still don't understand the root cause problem, but I can report it's solved. Thanks again.
@srwhite - I'm not sure if this would be possible, but do you think it would be possible to add openhab devices by modifying this to act as hubconnect server:
In particular this part: OpenHAB-Smartthings/org.openhab.binding.smartthings/contrib/smartthings/SmartApps at master · BobRak/OpenHAB-Smartthings · GitHub
If you just want to turn the on and off, you can set them up in SmartThings via the integration with ST then expose them to HE thru hub connect as a virtual switch. That’s what I have done and they can be turned on and off just like you would a light switch.
RegisterPing and appHealth are the mechanism hubs indicate they are 'alive'.
The words "Online" are a direct result of those 'pings'. (Not a classic ICMP ping, but an http interrogation that is designed to mimic one.)
The errors indicate the communication is functioning poorly. I'd love to know how you're doing that because I have a test build that is intended to make those errors a fraction more readable and I'm unable to test it 
The error won't go away, it's real, but a better message might help 
On the other hand, you've cropped off the App/dev # on the left. I would suggest removing the virtual Hub Device and recreating it. Go to your Device list and find the device identified in the error. I have 5 so I have to be more careful
Go into the device, scroll to the bottom, make note of the In Use By because you'll lose those when you delete this device. Click:
And then go into Apps and select the virtual Hub that was just removed and Click Connect to Client Hub. You don't have to change anything there, just click Done and then Done again and the virtual Hub device will be recreated.
I'm suspecting the virtual Hub device isn't a match for the key that's in use.
Thanks I'll try that.
I have 5 hubs, with one acting as the primary. All five are connected to the same Cisco switch. Two of the hubs experience this issue, while the other two are error free.
Thanks again for the suggestion.
This is a very long thread, but there's a ton of great info here and so I'm going to duplicate this info
One big hint I'll offer is to use the Import feature of Hubitat to install the components of HubConnect.
Here's a quick table of all the Import URLs:
I recently created some very simple screen capture videos on the installation process:
HubConnect Server Install
A 2nd hint is to help understand where the Universal drivers get installed:
Imagine you have a real dimmer or switch. It's mounted in the wall, replacing what was there before. You Join it to a Hub and it's given a 'real driver' on that hub. The OTHER HUB gets the Universal Driver.
HubConnect Success Story. This morning I pulled the plug on my Smartthings for the last time. I have 2 hubs, one running the house and the Master in the office; both acting as one hub. Separate buildings. I was able to get routines, rules running much better using RM and Motion Lights App then I ever had on Smartthings with Webcore. I don't use Webcore with HE, don't need it. With a little work I replaced my ActionTiles dashboard and my wife likes it much better. Speed is amazing!
Very nice, what screen are you using for the dashboard? and what system for you security camera?
There seems to be a glitch after creating a custom driver where it's not going back to the main configuration page. Below is the steps to replicate.
Once creating a device:
Click on Done on this page:
This page comes up asking to configure driver again:
You can't get out of that page without hitting the App List link on the top or actually creating another driver.
Dell P2314T Touchscreen with a Pi, the Surveillance system is Blue Iris.
Personally, I am starting to hate the way custom drivers are implemented but I do think some changes are going to help a bit. The big issue is that I am more or less fighting the Hubitat UI. I'll see if I can replicate it.. I'm working on 1.5 for a pre-Thanksgiving release, if I can easily solve this I'll include the fix.
Is there a way to send a tile from one hub to another. I have Darksky running on my secondary hub, and I dont want to mirror the whole device to the main hub. It is VERY chatty. >3000 pages in a day (in the device history page).
I just want to mirror the tile for the dashboard. Thoughts?
It is certainly possible but remember tiles are just passing device attributes to the user interface. What information (attributes) are you trying to relay to the other hub?
I’m curious, should devices that are shared have events show up in the shadowed version’s log? It does for some of my devices, but for the vast majority they do not. I have deleted and reinstalled multiple times as suggested, but I can’t get it to work consistently. Any suggestions would be appreciated. Thanks.
The events arrive into HubConnect (server instance) and would be reported there IF debug logs are enabled.
Okay. So they don’t show as an event for the device?
Events should always show up in the remote device, IF they're supported in the driver. When selecting devices in HubConnect it lists the attributes that will be subscribed and thus pushed to the remote device.
If nothing is showing in debug logs, and the physical device is located on a remote hub, please enable debugging on the remote to see what might be happening there.
Download the Hubitat app
