Hub Connected Devices Now Use Edge Drivers

@Khoeye Not sure where to put this but I’d like to make a suggestion.
Since end users are now having some devices use Edge drivers which require the CLI for debugging devices and sometimes removing/udating drivers, ST needs to make a complete tutorial for setting up and using the CLI for Beginners.
This needs to be a step by step tutorial that includes how to install and access the necessary files as well as how to access and use command windows. (I would but I’m still learning myself)


Interesting. I find it perfectly reasonable not to show the button status on the dashboard as most of the time it shows a fake ‘Standby’ status, but why show the battery when the temperature is available? The general trend elsewhere in SmartThings is to consider the battery level as part of the health status of the device.

Yes, the following was added to Edge production 2 days ago:

  • z-wave on/off wall switches, outlets and plugs from GE/Jasco/Honeywell, Zooz, Leviton, Evolve, Enerwave, Eaton, GoControl, Satco, Everspring, Minoston, EVA, Evalogik, Inovelli, Aeotec. Not all models, so still need to validate via fingerprint if your particular model from the above brands will use Edge

  • z-wave remotes from Springs/Bali/Graber window coverings

  • SmartThings/Aeotec zigbee button


Do you know if the stock edge driver for Zooz switches allows use of multitap function? (tap up X times)

Unfortunately it doesn’t have any kind of button capability for the Zooz switches, so it’s only on/off. But @krlaframboise is working on full function Edge drivers for Zooz.

1 Like

Agreed – I too am unclear on what " you would just need to re-onboard the device to have it use the Edge driver" means. Does it simply mean ‘Delete the device from your hub and then re-add it?’
Or is there something I can do in the dashboard to avoid this?

1 Like

@Khoeye , a question: you linked to the ‘production’ branch of this github repo, which appears to be behind the ‘main’ branch. Reason I ask is I have a device whose fingerprint is showing as commented out in the prod branch but it’s active in the main branch.

Which branch drivers get pushed to my hub - main or production?


And, all dimmers are commented out in prod for ZWave…

Guessing that main is for developers/manufacturers to QA/Test the functionality, and as they are confirmed they are un-commented in prod.

I would think the flow probably goes acceptance > main > beta > production with main also being an alpha. Probably pretty much as it always has been with main but now the staging process is exposed and probably more agile.

The commenting in and out in the production branch will presumably be a temporary thing until all the drivers are released, and then an occasional thing if they have to put the brakes on publishing for certain devices.

The FAQ at Edge Drivers for New Devices FAQ – SmartThings Support also uses this poor terminology. It says:
Q: How do I transition my current device to use Edge drivers?
A: If your device has an Edge driver available here, you can re-onboard the device to get it using a new Edge driver.

I realize this might be a dumb question, but could someone (ideally from Samsung) please clarify what is meant by ‘re-onboard’? It’s jargon: do you mean “remove the device and then re-add it”? Or is it something more complicated than that?

i’m not from Samsung, but yes, that’s short hand for remove and re-add. If it’s a z-wave device, you’ll also need to exclude it.

1 Like

When you are deleting a Z wave device, do you have to exclude it before you delete it from the app or delete it first and then exclude it?

When you select “remove device”, the Z-Wave exclusion mode starts in the Hub, so you should do what the manufacturer says to put the device in that mode as well (for example, press the action button once).
If you force the deletion of the device in the ST app, the device will remain in a “connected” state and you need to reset it to be able to pair it again.

Just to confirm, Jimmy is right:


So if I have devices using DTH and want to move to edge drivers that means I will also lose all the routines associated with the device?
That’s a rather painful consequence.
I’d been hoping there would be a route to an “in place” upgrade that switched driver without losing all the routines too.

There will be in the future when Edge is out of beta


the device profile could be different from DTH and it’s not clear what to do with missing capabilities that were parts of your routines