my thoughts as well, I have a support ticket into them to verify that it joins securely.
It will join my SmartThings hub immediately,
Garage Door opener is on your list, but you don't mention brand, etc. However, it's the same type of device, probably, A Barrier Device and must securely join.
There are two elements to secure pairing: 1) whisper 2) beaming.
Once upon a time, to prevent Man-in-the-middle problems, they lowered the radio transmit power such that the hub to device distance was inches. The idea was, some bad character out on the street, couldn't sniff the secure key, when the power was so low, during the join.
Obviously that has practical problems since the Assembly Instructions for most Locks begin with "Mount this on your door" -- forcing you to find a 100' Ethernet cable to get the hub close enough.
Beaming was created for battery powered devices, you can't have a battery powered device with the radio on most of the time. You won't have any battery life that way. 
"Z wave introduced beaming to address this. A nearby mains-powered device, typically a wired wall switch or plug-in pocket socket, will keep repeating the same message to the lock until it is received. So it is the wired device that is using power. This ensures that as soon as the lock wakes up to check, The message will be available. "
BTW, you can do all this with LCM. You just need to get the lock working. Here's the module for my lock and the module for your lock. They say they're not interchangeable in the Amazon description (if correct). Yours appears to not be Z-Wave Plus.
Maybe their's a firmware update from Yale? Can it be sent to the lock via SmartThings if there is one?
I did my Harmony remotes this last week and it's way more awesome in HE than ST!
How do you setup LCM to enable a code for specific repeating days (like every two weeks on Wednesday) and time (morning hours only)?
Oh sorry, you're right. The repeating schedule is not yet available. @mike.maxwell did say this in another post. I should have looked at LCM first.
Oh no worries, I just got excited for a sec and tried to figure it out and couldnt which is why I had to ask...looking forward to that feature because I think thats a critical component to making sure transient lock users are properly contained.
It's back on... Testing my Samsung button on ST as that's what it was made for...
Trying to prove if it's something with Hubitat...
Maybe range... That'd be pretty sad if so... It's so close....
My ST hub went in the mail to a new owner Wednesday. Bye Felicia!
2 Likes
I tried pairing my Schlage BE469 and BE468 Zwave locks the other day with similar results. I reached out to @bobbyD in support and he is working with engineering to see what can be done.
My ST is totally shut down now too. Keeping it around for firmware updates to some devices since I'm not sure that HE supports that yet.
1 Like
Not a bad idea. HE doesn’t support device firmware updates.
My ST v2 Hub has been unplugged for about 5 days now. I needed to reorganize some wiring and needed the Cat5 cable it was using for another device. I haven’t missed it at all.
I’ll keep it around as I still support ST_Anything for ST users.
4 Likes
I wasn't using ST with much in the way of custom code, other than a specific device handler for motion dimmers. As soon as I migrated all my z-wave and zigbee devices over I yanked the cord on ST hub and haven't looked back.
Already I am doing things with HE that I never even though to do with ST. Also, wanting functionality is making me learn Groovy which reminds me how satisfying it is to get code to function correctly.
4 Likes
I have new doors with dead bolts being installed in the next week or so, I may go to (i know!) nest's yale lock instead, I use all the cameras and thermostats and nest protects so it would all be in one place.
I believe the NEST Yale is a WiFi lock, so you’d be going all cloud, as all NEST products are, except for communication between themselves over nest thread protocol.
2 Likes
Not sure if you managed to get your Ring Floodlights going, but I just got mine working today. I'm brand new to Hubitat and after trying to figure out Home Assistant, I stumbled across this amazing community.
I just setup my Hubitat and one item on my list was the Ring Floodlight. I came across this post: Ring Floodlight Groovy Code
Using the groovy code from the article I was able to install it as a custom driver in hubitat. I setup a virtual device using the IP for my floodlight and to my surprise the groovy code ported without edit. I added my ring username, password, and device ID and am able to turn the floods on / off from Hubitat.
Warning - getting the Device ID from ring was a little tricky and the directions were not clear (at least for me as a noob). To do it, download an application called "Postman" which will let you call the RIng API. Make sure to setup a new environment in postman to define the global variables the postman script in the article needs. This will give you the device ID for your floods and whatever other ring devices you have on your account.
2 Likes
Interesting. So perhaps arming/disarming the Ring security system from HE might not be too challenging. Thanks for sharing this, and Welcome to the Hubitat Community.
1 Like
I set this up as instructed.
The first 2 POST command execute and generate the necessary token...but when I run the Get Devices, I get a Status:401 Unauthorized.
Username and password are accurate and they generate the token without balking so it's strange that the Get Devices errors out.
1 Like
That happened to me the first few times. I had to click through each tab quite quickly. If you can try to put the three sections (get oauth, get token, get devices) in the tabs above the main section in postman. This way you can select a tab and hit send. I think it's just a timing thing as long as you got the oauth and token successfully.
1 Like
