Bumping this post for any takers….please!
Yes when groovy goes away all DTHs stip working. Even the default ones provided by SmartThings. But AFAIK, SmartThings already has an edge driver replacement for most of the default DTHs already… The folks on this thread are making fast progress for other common devices.
Thanks for the clarification! In the meantime I had tome learning to do … how to change device type in Groovy IDE and differentiate between stock (ST default) and custom (either generic or for specific device) DTH.
But I’m aware now that DTH’s are gonna get retired, and it is to be replaced with Edge drivers!
Any roadmap on when will Edge final be released? Will there be any grace period in which DTH’s will still be working?
I would humbly want to request Edge driver for the following device:
Heatit Z-TRM3 Z-wave Thermostat
I have a Zigbee Smart Knob I want to use as a on/off switch as well as a dimmer.
I need a driver for Smartthings as I don’t have a Zigbee hub. Would any of you be able to help please?
Brand Name: Aubess
Data * application: 43
- endpointId: 01
- manufacturer: _TZ3000_4fjiwweb
- model: TS004F
- zigbeeNodeType: SLEEPY_END_DEVICE
Raw Description 01 0104 0104 01 06 0000 0001 0003 0004 0006 1000 08 0019 000A 0003 0004 0005 0006 0008 1000
Thanks in advance!
This should help. The exact description may be out of date, but the basic process is the same for today’s Groovy DTHs.(Edge Drivers, of course, are installed differently.)
Thanks, the things you quoted are the ones I figured out so far
But I learned many more tricks from the topic provided! It’s like a nice basic summary of getting started with device handlers and apps.
Nobody ask for Belkin wemo .
Also waiting for zwave lock , be469 Schlage.
Need an Edge Driver for ZWave Locks - Yale specifically but a universal would be fine.
What’s the hold up on this? A zigbee driver exists.
Excuse me, I had not seen this topic, and I had created a topic for my particular request:
No problem, this topic is just to help keep the requests organized and avoid too many duplicate topics. but if you get a response in your own topic, that’s good, too.
I’m not really sure what you’re basing this statement on - perhaps you could provide a source if you believe this to be true. There’s nothing stopping someone from writing a custom edge driver for a z-wave device of any type right now.
I would think it’s just a matter of someone making one, but I’m not an expert.
It does seem that Z-Wave drivers are lagging behind.
I wonder if that is a result of Z-Wave seemingly being left out of Matter.
I was going by what staff have told me previously regarding Zwave security and edge drivers in the current Beta, but I may have misunderstood. I’ve withdrawn my post above.
Do you know of anyone who has a working edge driver for a Z wave lock?
You can use the search feature at the top of the page to search for what you’re searching for.
Yes. My Kwikset 910 is unlocking and locking happily on an edge driver that I threw together in five minutes this morning. ST has defined the default z-wave behaviors for the
lock capability, so the most basic shell of a driver that does nothing but declare capabilities is enough to have a working z-wave lock driver.
Awesome, thanks for the correction!
That model doesn’t support S2 security, right? The S2 process is a little different for locks than other device classes, I’m just wondering if that has anything to do with the holdup on the official driver. Or if it’s just a case of too much to do and not enough time to do it in.
Nayelz is going to track the official version for us, I’m sure they will have one eventually.
It doesn’t, and I don’t have a newer S2 model to test on. I can’t say I’m up to speed on the specifics of S2 Access Control vs the implementation for other devices, but S2 works on other devices and non-S2 locks work, so I currently have no reason to doubt.
I think it’s just too much to do, and locks being toward the end of the list. There are signs that development is still happening on them - the default handler file for the lockCodes capability is date stamped 1/26, the same day that the latest Lua libraries were posted. The lock default handler file also is one of the more recently updated. No new ST drivers have been posted since 1/26, so we’re probably due for some more to drop.
Keep calm… They’re coming.
would you care to share your driver?