The End of Groovy Has Arrived

In general ST’s Zigbee and Zwave antennae are both above average. I’ve only heard of Wink’s (ABNORMALLY powerful and borderline out of spec) signal to be stronger. I’ve found almost all others to be less ‘powerful’ But with all things Zwave / Zigbee - more repeaters.

Also if using HA or anything that requires a Pi and Zwave or Zigbee - Assume you need a short extension cable and/or hub to get the stick away from the Pi’s noisy USB3 ports. Trust me. (Edit: Yes, ODroids and most NAS boxes running as Docker hosts too…)


With some Zwave devices I need to get the ST V2 hub within a couple of feet to connect. And since I am on PG&E, one of their frequent power outages can cause these devices to drop off. I even see this with some zigbee stuff directly connected to ST.

But with HUE… not a single issue! Never, ever! And even my decades old x10 devices have never been an issue. Seriously has me thinking Zwave sucks (at least in use with the ST hub), and wanting to replace the few lights I have left on Zwave with HUE.

But I need some switches to do non-light stuff, and when these drop off I am left having to use a long ethernet cable and extension cord to get the hub close enough to disassociate and reconnect (which is a huge PITA). Sure wish Philips would introduce some high AMP outlets… then I could be done with all this crap.

BTW… the HUE API is wonderful, and seamless between both remote and local operation. Everything works when I am away, as well as when I am home and the internet goes down.

1 Like

Early Zwave devices did not support NWI (network wide inclusion) so they always needed to be within hub distance to connect. Add to that reflections, mirrors, appliances and ductwork. NWI was added in the 500 chipset but not all devices implement it. Any routing devices between the device and hub also have to support it. Of course locks and other security devices only support a “whisper” radio mode to prevent eavesdropping during communication.


Yup… and a couple of mine (including the one I use to control my water heater) are that way. But I have had issues with newer ZW devices as well (GE/Jasco) after power failures, which has me wanting to avoid it all going forward.

It’s required beginning with zwave plus. :sunglasses:

Zwave itself is fine (one reason Amazon continues to use it for the Ring Security system). The SmartThings’ implementation of it, however, is…idiosyncratic. :thinking:

I have previously posted a comment on this:

Gaps in SmartThings’ Zwave Implementation (2022)

And for another more recent comment:

This is a nightmare - #11 by JDRoberts


I thought that was the case but its not actually true. NWI was optional on 500 series. You have to check the device certification on the alliance to see if its configured. You can see it in the XML version of the cert:

1 Like

Initially true before the Z wave plus certification standard was finalized, but that was revised in rt:00.11.000A.1.

A Z-Wave Plus compliant node MUST support both Classic and Network Wide Inclusion (NWI).

So it might have been optional for a device using the series 500 chip, but it was not optional for Z wave plus certified devices. Just sayin’… :wink:

Fair enough, but most people (me included) always assumed 500 series and up devices were all branded Zwave plus (certified maybe). My point is it can be murky. :slight_smile:

1 Like

Will the IDE portal be available to retrieve code placed there? or will we have to find a way to back up personal code?

I would recommend backing up any personal code before October 15.

1 Like

I backed up all my SmartApps and DTHs this morning… most likely destined for Hubitat.

1 Like

I have a few Nyce door hinge sensors. Will these convert to just stock open and closed sensors? I assume that there is a stock open/closed sensor edge driver?

there are several Nyce fingerprints in the standard zigbee contact driver, so i’m inclined to believe you’ll be ok


These Edge drivers have gotten out of control. Everyone is out here working on them with no real coordination. Some devices are getting multiple drivers even though the manufacture is active on here releasing an official driver(s) while other devices desperately need attention and get ignored.

SmartThings needs to build an Edge driver store where we can look up Edge drivers by device and have it return all matched driver channels with the driver names. This would help users and developers alike.


Thats the last thing they’d want to do. They’d have to provide a process to get drivers reviewed and approved, provide support for drivers contained within the store (ala Google Play Store or Apple App Store.) By the time they do all that, they’d be better creating the drivers in the first place as part of their Works WIth Smartthings certification.

They’re called Community Drivers for a reason - created/managed/supported by the community.

1 Like

Community developers work on whatever they want to, whether there are other existing drivers or not. People have their own reasons for why they want to do so. And it’s up to them whether they choose to share them with other people or not.

Although there’s no official way of looking things up, we do have two resources in the community-created wiki which can make the search much easier.

First, The quick browse lists should show all of the existing community – created edge drivers that the authors have chosen to share publicly. The lists are divided by device type, so one list for sensors, one list for locks, etc.

There are also links for manufacturer-provided custom edge Drivers when the manufacturers have shared those publicly.

Second, we have a brand new page in the community-created wiki, which will eventually, hopefully, be a table where you can look up devices by model and see both the stock edge driver and any publicly available community-created custom edge drivers. You can sort on different columns if you want to see things in a different sort order

This is brand new, so while everything there is accurate, if a device is missing it doesn’t necessarily mean there’s no edge driver available yet: it may just be that no one has added the entry to the table.

Table of Edge Drivers - Things That Are Smart Wiki

Finally, we do have a request topic in this forum where you can request that a community developer create a custom edge Driver or add the fingerprint to an existing custom edge Driver. Please do everyone a favor and check the quick browse lists first and then if you can’t find a custom driver there, read through the whole request thread to see if other people have already requested that model. That saves the developers time, and we definitely want them spending their time creating new edge drivers, not just reading duplicate requests. No guarantees, but most of the active community developers do read that thread.

Post Requests for Edge Drivers Here (community-created)

Another place you can check is to look in the author thread for the custom groovy DTH you have been using and see if anyone has posted an alternative there.

I know this is a lot of work and I keep hoping that smartthings will come up with the equivalent of our table with an official database, but so far that hasn’t happened. So the community just has to try to fill the gaps as best we can.

(I don’t know what the official process is for requesting an additional fingerprint be added to a production edge driver: if anybody does know, please post.)

1 Like

We can automate our homes but the thought of simplifying finding an Edge driver gets resistance?

I am up to date on the threads requesting drivers and how to find them but I am thinking long term.

Users are going to have to sort through thousands of posts and it is not like the old groovy DTH where you can see the code to see if you device is going to work. There Edge drivers you will have to find the one post that says your device is included in the driver. A wiki is ok but something that is central and searchable would be ideal.


Agreed! Would you be willing to create such a thing?

The only thing I know how to build something like that in is Microsoft Access, LOL. We used to use it all the time for custom programs at work.

1 Like