Yes, the MSR is the “fingerprint”. If your device isn’t listed, then it will be converted to a generic Thing driver which will I believe will have no capabilities. There are other generic drivers below but I suspect there won’t apply to your device.
Not that many. Over 90% of people using the SmartThings app don’t have a hub: they have Samsung smart appliances or televisions. And the majority of the remainder have fewer than 15 hub-connected devices and never used any custom code. For almost all of those the transition will be invisible.
That’s obviously not the majority of the people in this forum, but we’re a small percentage of a small percentage of a small percentage.
I’m looking for an Edge driver for Leviton Z-wave plug-in and wall dimmers that will allow access to advanced options (fade times etc). There was a previous groovy DTH that allowed this but now it is not available with Edge. Does the “Mariano Shared Beta Driver” provide this functionality? @Mariano_Colmenarejo
Leviton devices in the stock driver and mine have generic profiles with no specific preferences.
To do this, it is necessary to create a specific profile for each device and the code to manage the preferences.
In these cases, what can be done is to use the Z-Wave Device Config Mc parameters configurator driver.
It is paired with it and the necessary parameters are configured according to the manual.
Once configured, switch to the stock Z-Wave Switch driver or the one you are using and the settings will be maintained.
You can switch back to driver configurator when you want to change something. The only thing you have to take into account is that if you have routines where only this device is in the If or then part, they will be deleted and you will have to redo it.
Hopefully this improves in future or you can also add a virtual device in the routines where this device does not get deleted.
This standard configuration procedure is similar to what existed with groovy