I was using hublink for a while and tried out hubconnect. Haven't looked back since. No impact in performance that I can see and much more capable. The speed is going to be mostly determined by your mesh as it is the slowest part of the chain.
3 Likes
I think you have answered yourself 
You need Lock Codes and Battery.. HubLink doesn't offer those Attributes. HubConnect offers all Attributes.
HubConnect has a lot of pieces, and therefore the install process is more. IT's not different, it's just 'get the code - paste the code' again and again. Then Add User App vs Add Built-In App from built-in code.
Hubitat isn't offering a mechanism for adding and installing Apps and Drivers in one 'batch' and thus the burden of adding the pieces is on each of us.
The only hints I have are: take it slow, watch the Videos, understand the task of 'building the highway" vs 'cars and trucks ON the highway.' (Cars and Trucks == your devices that are 'mirrored' to the connected hub.)
As to reading this thread.. my suggestion is to read the first 11 messages and then skip forward and read the most recent 30 days worth of discussion. Certainly the first 2600 messages are about versions prior to the current.. and therefore less useful a read. Around Feb of this year, much of the discussion about v2.0 gets interesting. 
1 Like
So I finally took the time this past weekend to upgrade from v1.6.x to v2.0.x but reports isn't reflecting that v2.0 is the newest? Did I miss something?
No. I think that’s due to it no longer being on github. Is there not an Iris V3 driver that’s 2.0?
Nope, that driver isn't even on the site. It seems to be a replaced by the "HubConnect Iris IL071 Motion Sensor" driver.
1 Like
The "Latest" Column comes from a DB on one of Steve's servers..
- I don't have write access to that and thus cannot update.
- The Latest is the v1.6.4 with v2.0 being Beta. Therefore 1.6.4 versions are technically, the latest
I created a GitHub Repo for the v2.0 RCx Drivers and announced it a week ago:
1 Like
My apologies. I did see that, but forgot 
Correct.
You can find @srwhite "Shackrat's drivers" here: Hubitat/Drivers at master · shackrat/Hubitat · GitHub
1 Like
I hate to tell you this, but it gets worse! 
2 Likes
Thanks, I must have missed that post initially. I hadn't been paying much attention to this thread because HubConnect was working perfectly for me so I had no need to mess with it until I upgraded this past weekend.
Chased down something in another thread here:
And then started to think I should look at the original lock driver and NOT the Hubconnect one. It seems the hubconnect driver is missing the "type" from the lock driver.
Original event log in Yale zigbee driver:
Hubconnect driver (2.0)
The type column is missing.
I'm also having problems with Rule Machine or the built in "Notifier" app recognizing when a code is entered...wondering if this has something to do with this integration also?
Here are two 'captures' of the Event Stream for a single device:
This one, above, is the result of automation, so called "digital".
The second one is me, physically turning on the switch:
The data you seek is not included in the Event.
Here are two more Events...
Remember, the Event Stream was 'invented' for Dashboard and contains data useful on the dashboard.
1 Like
ok second question.
So what I think I'm seeing here is that the hubconnect lock driver is not creating the "lastCodeName" event. I have code that when put on the hub with the zigbee lock reacts when the "lastCodeName" event happens:
subscribe(lock, "lastCodeName", lockHandler)
that same code on the remote hubconnect hub connected to the same lock does not catch the event. As you can see here this is the event on the hub with the zigbee lock:
There is a lastCodeName event.
This is the log on the hubconnect lock (same lock):
Notice the event name is now "lock"
HubConnect v2.0 RC Drivers Added to Hubitat Package Manager
This is a HubConnect Drivers for Hubitat Only announcement.
A HPM Manifest has been added for HubConnect's v2.0 (RC2) Drivers. While HubConnect has a set of SmartThings Drivers, there's no HPM for ST and thus this addition to HPM will not help with SmartThings.
Enjoy HubConnect
15 Likes
Can I like this more than once? Amazing @csteele this will make installation from hours to minutes!
1 Like
Thanks again for a brilliant app.
Something I've noticed after the update.
When I do a check it still shows 1.6 for example as the current drivers.
Loaded is showing 2.0.
Just an observation.
it's a dozen or so posts back.
Thanks. I'm up to date but missed the earlier post.
1 Like
I had to make the following changes in the SmartThings HubConnect server SmartApp and button device driver. This was necessary to get HubConnect to send button events from SmartThings to Hubitat properly.
In the HubConnect Remote Client, I modified the deviceEvent() function by changing the event for pushed and held buttons as follows. Previously the code only had the sendEvent in the else clause.
if (event.name == "pushed" || event.name == "held")
{
childDevice.sendEvent([name: "button", value: event.name, unit: unit,
descriptionText: "${childDevice.displayName} ${event.name} is ${event.value} ${unit}",
isStateChange: true, data: ["buttonNumber": event.value]])
}
else
{
childDevice.sendEvent([name: event.name, value: event.value, unit: unit, descriptionText: "${childDevice.displayName} ${event.name} is ${event.value} ${unit}", isStateChange: event.isStateChange, data: data])
}
In the HubConnect button device handler I had to add a "Holdable Button" capability to allow me to choose pushed or held actions on buttons when adding automations in SmartThings.
I'm sure there's a more elegant way to change the code but this works for me
All this was started when an Inovelli switch stopped working in SmartThings and I moved it over to Hubitat. I wanted to replicate as many as possible of the original ST automations but I had issues sending the button states to SmartThings.
My setup is as follows: The Hubitat switch is an Inovelli switch that exposes multi-taps as buttons. I could not find a way to send those button events through HubConnect. I then created a virtual button in Hubitat and added RuleMachine rules to push or hold the virtual button when the corresponding physical button was pushed or held. If there's an easier way to do this, please enlighten me!
