The Schlage wave locks aren't overly consistent in how they want to pair. I have 6 and out of them four wanted me to use the push the schlage emblem on the outside keypad and enter the programming code, the other two wouldn't pair with that sequence and I paired them using the red button behind the cover... and the coed is on a sticker on the back of the little instruction manual. I had to exclude them a number of times before they would pair with the hub laying on to of the lock...
Thank you @bertabcd1234 and @douglaspitman - I ended up following your advice and unscrewing the lock to get to the code. Now I have to gather up the courage of unpairing from ST and pairing with Hubitat. This is likely the most critical item in the house so I'll make sure I have a few hours in front of me lest things go haywire.
Can someone help me figure out what I'm doing wrong? I'm trying to install the hubconnect remote hub driver but after I go into drivers code, click import and paste the url of the driver nothing happens, as in the page is still blank. Am I missing something really simple and stupid?
It means the URL is incorrect. Import is expecting a very specific target.
If you're using github for example, then you need to click RAW to see ONLY the code and then use THAT URL.
If you're using HubConnect.TO, then you need to use the long customized URL.
That is the URL from Hubconnect.to
By Coincidence, I've been working on putting the v2 drivers out on GitHub.
If you visit: HubConnect.HubitatCommunity.com I've added a new link to a page of Import URLs specifically for the v2 Drivers. Remember, v2 App Code will reside on HubConnect.TO as always.
It makes it fractionally easier.. fewer clicks, to get the Import URL. Just Copy / Paste... copy a whole line from the page for the specific driver you want, and paste it into the Driver Import URL field on your Hub.
5 Likes
Will HubConnect in SmartThings die when groovy is sunsetted?
I'm sure it will break stuff then someone will come along with a fix.
Don’t forget to do a full reset on the lock between unpairing fro ST before you pair with HE.
There is a video on YouTube with the process.
Also, both times - originally paired with my C5 then with my C7 - about a day later the lock became unresponsive.
Remedy - unplug lock battery for 30 second and replug. It’s magic.
Edit: another note. If you are not using the default code length of four, I was unable to get the driver to bump it to six within HE. I used the lock keypad to change to six and did the same in the driver. Then I was able to program codes from HE.
That is how it works--the command in Hubitat just sets the length Hubitat knows about to whatever you need to have already configured it to manually on the lock. Apparently there is no way to query (or set) this from Hubitat.
I know this because I was also confused about this once and asked. 
Also, I'm not sure about people's experiences with needing to reset vs. just un-pair and re-pair. I never moved these from ST, but moving between Hubitats, I was able to exclude and then join to the desired hub, no full reset necessary. My settings stayed on the lock, I think even including the lock codes, but to be safe, I deleted them all before letting LCM re-make them all. It's historically been picky for me, and I didn't want to do anything that might confuse it. (Bringing this back to HubConnect, I also don't think LCM works if you have code encryption enabled. After testing pairing to a new hub, I used HubConnect to put it back into automations on my "main" hub.)
1 Like
Good to know that I wasn’t the only one expecting a different behaviour - lol. Thank you for confirming that I wasn’t doing anything wrong.
I agree. When I moved it from my C5 to my C7 I did not do a reset and it’s been 4-5 days and it seems ok. I made the note because it was necessary when I originally pulled it off wink.
Hi all,
I've been using HubLink/LinkToHub between my two C-5s for the past year and have a few quick questions about HubConnect that I couldn't find easy answers to in the 3,600 posts in this thread - especially given the rapid pace of development and enhancements over the past 18 months.
Relevant info:
- My 2nd C5 is in my garage running a few lights, a contact sensor, and a single Schlage lock. HubLink/LinkToHub lets me run basic rules to lock/unlock the garage door. It's connected to my home network via a Wi-Fi range extender, so not a hardwired connection, but it's been stable enough over the past year.
- With the latest firmware 2.2.3.148 my primary C-5 with over 100 devices/rules/etc is running super fast, the fastest it's been since I got it almost 2 years ago. I am very happy with the performance right now. The lag between entering a room and the lights turning on from my motion sensors is now always <1 second, which is great!
Why am I considering a switch to HubConnect from HubLink:
- Ability to trigger rules off Lock Codes in garage
- Ability to get battery percentage on my primary dashboards for the door and contact sensor in garage
Question for you:
- If I install HubConnect - is there typically any performance hit on my 'server' hub (which I would expect would be my primary hub where all of my rules, apps, and majority of devices are)? Even a half-second, or weekly required reboot, wouldn't be fun at this point with how stable I've otherwise been.
- Note: I know that TONS of work has gone on for HubConnect, and it's one of the most well-respected community apps there is. I am in no way trying to insinuate that HubConnect is anything less than amazing. WAF is super high right now, and I want to keep it that way.
If you were in my shoes, would you take the plunge with HubConnect, or stick with HubLink/LinkToHub?
Thanks!
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 
