I just noticed that Package Manager had an update for most of my Hubconnect drivers. Nothing here or on the Hubconnect site that has anything about these updates. Anyone have any information on these driver updates?
and
I just noticed that our refrigerator and freezer (Samsung, connected to Smart things) stopped reporting. I've tried restarting and resyncing everything with no change. Any thoughts?
Just a general comment about HubConnect and SmartThings. I have devices shared going both ways and have had no issues... I'm using the new ST app and the IDE is still up and running... Now I'll prolly jinx everyone by bringing this up, but I believe HubConnect to be a great piece of code and it is still going strong for me...
@markbellkosel84 I can say the majority of issues I have encountered are because of SmartThings itself... I have had to delete and re-add TV's, washers and dryers, and other Samsung devices periodically as they seem to just stop working... You might have to re-pair your fridge again... Usually these issue show up in the ST app so not sure if you are seeing that or not.
I have full function in the ST app. It's very odd. I'll give re pairing a go.
In early 2019, when Steve White asked me if I wanted to test out his code that became HubConnect, I had already retired my ST hub. Once it became clear that I was going to be the Alpha Tester, I resurrected that ST Hub and did some serious testing and development for a couple years.
When ST announced the end of life, neither Steve nor I had any continued interest in the new ST platform. A few months ago that culminated in me, once again, disconnecting my ST hub and packing it carefully in the Junk Box. Therefore, my ability to refresh my memory on HubConnect for SmartThings is gone and my memory of it is being pushed out by newer items.
What I can remember and mention is that you can dive into the HubConnect Selection menu deep enough to reselect your refrigerator/freezer (but not actually reselect,) and then click Done all the way back out. The remote hub (ST in this case) will resend the list of every mirrored device to the main hub. If there was a disconnect/drop of the mirroring, a new device will be created. Look at the logs to see what action was taken.
Second option is to delete the mirrored device from the main hub. Obviously this breaks any place where the object was in use, but you can create a Virtual Device and swap it into all the in-use places prior to the delete. Then, when you pretend to reselect in the ST App, a new device will actually be created and then you can swap back.
Similarly, you can deselect a device in the ST app and when you Done all the way out, the device will also be removed from the Hubitat side (assuming you have that feature enabled.)
1 Like
Thank you I will give this a try and report back.
Just had to to go through getting my Arlo cameras re-connected this weekend. Everything still showed connected and Hubconnect said it was online but there seemed to be no communication. I just went through the apps on the HE and ST side clicking through to done and it seemed to take care of it.
So hopefully you can do the same.
1 Like
This is a mighty long thread, that Im trying to parse. Im trying to figure out if I can have devices that are in registered in my samsung graph be replicated into Hubitat. The ST hub that these devices belong to are not on the same network. So its almost 'hubless' to that extent.
Thanks
Is HubConnect V2 still available for installation? I don't get the point on how to start the best.
Any help is very appreciated. I think HubConnect could be one of the best ways to start migrating devices from ST to HE and still remain some devices like Arlo Cams on ST hub.
Have ond ST hub and one HE hub and would like to connect.
What's the best starting point?
How to install the necessary apps and drivers
Do I need the server on the Raspi? What is this good for?
Better solution than Hub Connect? Read something about new new ST api, but not sure if I can install all the stuff on my existing RPI, which I use for Sonos httm api and WebCORE
Thanks for any ideas and input
Yes, HubConnect is still available. The question is: Is ST still able to add it?
The very high level recipe for HubConnect is to install HubConnect v2.0 Bundles from HubConnect.TO
Download and install these two Bundles:
That gets the Code onto your Hubitat Hub and the next step is to use the Apps menu to add it.
In SmartThing's IDE, you add one smart app and one DTH from this code:
Then, on your SmartThings App, add HubConnect as an App.
Now it's time to configure both hubs.
Full instructions can be found as:
But the new Hubitat feature of Bundles has not yet been applied to those instructions. Bundles simplifies the installation of code on Hubitat and therefore you can skim past those steps in the Installation Instructions.
No, you don't need it for SmartThings.
No, but that's a biased answer 
People are using SmartThings to Node-Red and Node-Red to Hubitat to accomplish a similar goal. I have not tried it. Node-Red would run on an external, always-on computer. A RaspberryPi is often the starting point for Node-Red.
1 Like
Speaking of the Arlo cams that is the only thing I still have on Hubconnect. It was working great until a couple weeks ago. It's weird as I can still enable and disable cameras through Hubconnect, so the connection is still there, but motion won't pass through anymore. Luckily the Alexa integration is working pretty well. So I can use that to pass motion to HE. If I could figure out a way to turn off cameras outside of Hubconnect I wouldn't need it anymore.
The reason you would want to use Node Red with Samsung automation studio is to prevent a issue with the devices when Samsung turns off the Groove IDE. When they do that Hubconnect integration will stop working. The problem is no one knows when this will really happen, just that Samsung has said that it was coming.
You can use Node-Red with Samsung Automation Studio pallet to send on/off controls to Smartthings and turn the cameras on/off.
Actually the thing I want to quit using is ST, but if that part of Hubconnect stops working then I will look into it.
@csteele: thanks for the fast response. I was able to install the HubConnect Server on my HE. I had to import by using the URL. The strange thing is, I'm not able to download anything from hubconnect.to. Where do I get the smart app and DTH for Smartthing?
If I click on the links on hubconnect.to nothing happens. Never had that before.
Where did you get the screenshots from? Looks different than hubconnect.to.
Any ideas?
Thanks in advance
@mavrrick58: I think I saw a post from you in another thread. I'm interested in setting this up but it looked a bit complicated to me. Just not the expert in Raspi. Just happy getting WebCoRE local to work on my Raspi without crashing my Sonos http api server.
I have to look into this deeper but in the first place I would like to transition all my devices from ST to HE. My opinion was HubConnect could be easier to realize in a first step.
When I first switched from ST to HE this was a good transition tool. I slowly moved devices over. I ran a half ST half HE home for several months until I got my second HE hub and then brought everything over to HE.
1 Like
With as much I have been working with the Node-Red Samsung Autiomation studio stuff i would totally agree with @terminal3. If this is purely for migration I would use hubconnect if it is viable still. Not that setting up this Node-Red option is hard, but Hubconnect should be easier.
If you decide to try to work on the Node-Red option I will certainly help where I can. I wrote up kind of a step by step. It is a bit wordy and i suspect makes it look harder then it really should be. It isn't hard at all, but time consuming. Most of it is running commands and waiting for the pi to complete the needed installs. Node-Red may take a little bit of getting use to though. It did for me.
