The End of Groovy Has Arrived

Announcements
2048

Good point, but scenes currently require the cloud as well.

There are definitely simple automations that can run locally when triggered by a button press, and that may be all that many people need. :sunglasses:

5 Likes
2049

I was really disappointed when I learned Zwave was effectively being deprecated from ST’s newer hubs. While I may not fully understand all of the technical or political pros/cons, I’ve yet to change a single battery in ANY of my Zwave sensors in 4 YEARS!! (They’re also placed at much further distances from my router with far more physical barriers.) Contrast that with the 2-3x annual battery replacements I’ve had to perform with my functionally equivalent Zigbee sensors which mostly sit within spitting distance of my hub. :face_with_raised_eyebrow: My zigbee devices also seem to cause occasional ‘hiccups’ (congestion/interference) with my WiFi; not so much with the Zwave ones.

I know Zwave isn’t perfect by any means, but I think there are still some very strong use cases for it. Switching to a v3+ hub would’ve meant dumping tons of devices, replacing them with thread/zigbee equivalents, and potentially winding up with less performant WiFi and even more battery replacements. No thank you! :rofl: Not a fan of planned obsolescence, especially when it’s arguably regressionary.

I’m glad ST didn’t deprecate the v2 HUB and that we basically achieve (better than) v3 feature parity by simply adding a thread border router onto our network. Easy peasy. ¯_(ツ)_/¯

2 Likes
2050

You got the Quirky Tripper working? I been off here for a year or so. Now i’m confused on whats going on. lol. all i want is my Quirky Tripper to work again.

2051

Looks like @Mariano_Colmenarejo added the fingerprint to his driver.

3 Likes
Quirky Tripper Support?
2052

I have several devices that still have not changed over to Edge drivers, including a Kwikset lock (Smart Code 910). I am reluctant to remove the device because I don’t want to lose functionality if it won’t re-add. Any help would be appreciated.

1 Like
2053

For your peace of mind 
 you may want to go ahead and rip the bandage off. Exclude the lock and add it back. Of course, you may need to recreate any Routines that it was associated with. If there are issues, community members will always assist.

OR wait until ST migrates it when you least expect it. Nothing will go wrong
 right? :wink:

3 Likes
2054

If you do delete and add it back, create a virtual device to use as a placeholder in your routines which you can delete when you add your locks back to the routine. This way the routine won’t get deleted when you delete the lock.

4 Likes
2055

I have Kwikset locks but there all Zigbee and they work perfectly with Mariano’s Zigbee Lock MC. I have heard the Zwave Kwikset locks work with Philh30’s Zwave Lock driver but I don’t have any Zwave units so no way for me to say for sure. I would find the fingerprints for your lock first and then check the appropriate driver yml file to make sure your fingerprints are included.

2056

I got it changed over! Thanks for all the help! It was a Z-wave lock and everything works but there are no additional features/options when I look at the device in ST.

2057

I have read that the Philh30 Zwave driver has extra functions. @h0ckeysk8er knows a little more than I do about this.

1 Like
2058

There doesn’t seem to be a separate profile for Kwikset locks, but for Schlage you get quite a few more settings. Additionally, his beta version exposes unlockCodeName in the device panel and in Routines as a trigger.

  Capability                                  Attribute               Value          
 platinummassive43262.schlageInteriorButton  interiorButton          "enable"       
 platinummassive43262.keypadBeep             keypadBeep              "beep"         
 platinummassive43262.autoLock               autoLock                "off"          
 platinummassive43262.schlageLockAlarm       alarmMode               "off"          
 platinummassive43262.schlageLockAlarm       activitySensitivity     3              
 platinummassive43262.schlageLockAlarm       forcedEntrySensitivity  3              
 platinummassive43262.schlageLockAlarm       tamperSensitivity       3              
 platemusic11009.deviceNetworkId             deviceNetworkId         "[71]"         
 platinummassive43262.lockAndLeave           lockAndLeave            "lockandleave" 
 platinummassive43262.vacationMode           vacationMode            "off"
1 Like
2059

Yes, I tried that driver but there were no additional options.

2060

From what I understand, if it’s a Schlage 468 or 469 lock, then you need to load the Z-Wave Lock PH Beta driver not the Z-Wave Lock PH v1.00 driver for the additional features.

2061

1.00 has the additional lock settings. The beta version fixed a bug in the default lock handler that caused the lock code names to be reset. It also added and exposed the unlockCodeName attribute.

1 Like
2062

Has anyone had their zwave go control garage door controller migrate yet?

2063

Yes, two of them quite some time ago.

1 Like
2064

Arghh
 Now I need to open ANOTHER ticket with Samsung.

2065

No need to open another ticket because another member’s device was migrated before yours. There is no set schedule that devices of a particular brand are migrated at the same time for everyone.

5 Likes
2066

OK. So the wait game continues.

1 Like
2067

Yes. In fact it was perhaps the very first migration that happened automatically a while back. The name of the edge driver is z wave garage door opener. Developer is listed as smart things. Version is 2023-01-17T21:46:54.400442271.

1 Like