Row 3 should be “If custom Edge driver already installed that matches fingerprint.”
Row 4 should be “Fallback to “base” driver that matches fingerprint.
Row 5 should be your Row 4.
In other words first the migration looks for a custom edge driver that matches the fingerprint, then it looks for a stock edge driver that matches the fingerprint, then it tries to guess based on capabilities.
I don’t know if you need a row 6, which is that if none of the first 5 work, it is just listed as a “thing.”
I like the rules based description of the migration process to keep it straight in my head. I’m formulating what I’m going to do pre migration based on what category my devices fall into. I’d much rather not go thru excluding and re-adding them back in if migration will take care of that for me, provided I prepare for each use case properly.
Alas, I had only one of these devices, and I did not think to take a record of its parameters before exclusion from the old DTH, and so I have no clue what they were before I re-included the device as an Edge one… Potentially changing its parameter settings in the process.
What I will do is factory reset it, re-include it with old DTH, take screenshots of all parameters, re-exclude, then re-include as Edge and check any changes that could have been done. Will leave any results here just in case others have the same problem.
I will check for both, if I can, and let you know. Hopefully, also, it will be able to stay connected to the network for more than 2 days.
Can someone please tell me if I need to do anything about this or do I just need to wait for the rollout? I am mainly using Nue switches and Xiaomi sensors, a few smart apps and webcore
Note that devices vary on what they reset/re-initialize on an exclude vs factory reset. Some reset everything on exclude, others leave parameters alone. Some don’t do a factory reset after a firmware update either, which can lead to all sorts of odd behavior.
Most of the built in device handlers for zwave tend to leave parameters alone except for very specific cases. If its not settable via the App->Settings, its not likely to be modifying the device. Compared to Zigbee, parameter indexes and options vary widely between implementations. Even when handling specific logic of a major player (Leviton for example), it tends to be something non parameter related. Thus why we like using the manufacturer specific drivers instead (Zooz, Inovelli, etc).
Need more details. Are you using standard or custom DTH for the devices? which smartapps? You definitely need to move your webcore automations to other options.
I may be mistaken on this, but regarding row one, my understanding was that if a device is currently using a stock Groovy DTH, the automatic migration will shift it to a custom edge driver if there is one already on the hub that matches the fingerprint. But maybe I’m wrong on that, and a device using a stock Groovy DTH will be converted to a stock edge driver even if a custom driver with a matching fingerprint is present, and then you would have to manually change it to the custom edge driver if that’s what you wanted.
One more thought…I think there are still a lot of open questions about what will happen with devices using the parent/child paradigm in the old architecture.
will the child devices be converted?
will they have the same name they had before the migration?
if the child devices were used in routines, will those routines still work?
will those child devices be controllable by Alexa and Google Home?
if those child devices were used in IFTTT recipes or Alexa routines, will those still work? What about SharpTools rules?
if those child devices were used in scenes, will the scenes still work?
I’ve seen conflicting answers on these.
I believe “zwave switch” is an example of a multicomponent stock edge driver, but I don’t know if the corresponding stock Groovy DTH uses child devices or not.
I have a ton of these child devices. Mostly they are MCOHome 2 or 4-gang switches, but I also have several others, ones that come to mind being Qubino Flush 2 Relay and Aeotec Nano Duo Switch. I am testing at least one of each type before migration, but even if I manage to find a driver that fits and works well, there’s no saying what the migration will do on 30 Sep, and information is way too scarce.
I will convert what I can before migration date, though certainly not all. Wish ST were clearer about this part.
Yeah I wouldn’t mind changing things just now knowing that if I do, they don’t get screwed again come Sep 30th. Some more info would be good to be fair.
This looks to be a custom edge driver. Will the standard edge driver feature this device too?
Also, for multi switch devices will they appear as a single device? And thus only the master device controllable from Alexa?
This is a huge concern for us “Please note that some devices may not transition automatically and will need to be re-onboarded.”
We have custom DTH for smart locks (Yale, Kwikset, Schlage Zwave) and several different contact sensors ( Zwave and Zigbee) and leak sensors (Zwave and Zigbee).
How can we find out which devices need reonboarding, and which don’t? This is such a massive effort that we if we have to reonboard we will just rather switch
Thanks for getting back to me
The DTH are ones that other people have made available from GitHub and I have copied the raw code to make DTH’s. The smartapps are a combination of smartthings ones and others from GitHub. I am comfortable doing that again, however there is no real information on how to access and install the platform we need to install the new drivers on. I was hoping that Samsung would provide some kind of how to guide rather than just getting the community sort it out for them. What alternative options are there going to be for webcore? Will the new platofrm be capable of more complex automations?
I don’t know that these are the best ones, but I got the Zooz ZST10 700 series zwave stick and the Sonoff zigbee USB dongle plus. There are articles spread around in various locations of the Home Assistant documentation and community with lists of recommendations.
@philh30 has added all the zwave fingerprints from all the currently available edge drivers in the Beta channel to the community-created Wiki Table of Edge Drivers.
So if your zwave device currently uses one of the stock groovy DTHs and it has an entry in this table in the “stock ED “ column, it should be automatically converted when the transition occurs. Hopefully.
You can sort this table by any column, so, for example, to see the list of all the fingerprints in a particular driver sort by edge driver name.
We can still use lots more help if anyone wants to enter some of the fingerprints from the community created drivers to help people find those. Even if you just add one or two it will help. Since people can sort the table however they want, you don’t have to put it in any particular order, just leave the sample row at the top.
So I decided to make some time for this one today. Exclusion and re-inclusion did not help. At certain percentage settings. the lights kept going up and down constantly, not just during dimming up/down activity, but long after the switch was left alone. I also tried a factory reset but not sure that one worked - even excluded from the network the lights kept going up and down and effectively rendered that room unusable after dark as it drives you crazy. This happened overnight, immediately upon installation of the Edge driver.
Since I had no other identical dimmer switch to compare settings to, I delved into the settings myself, and from there I:
Enabled Overload Protection
Enabled Overheat Protection
Raised the Minimum dimming from 0 to 10
I changed the Dimming Principle from Leading Edge Mode to Trailing Edge Mode.
To my mind, it seems like the last setting is the one that corrected the problem. Either the Aeotec Nano Dimmer does not handle Leading Edge Mode very well, or else my lights were not too happy with it.
In any case, that must be a parameter change that happened upon installation of the Edge driver.
And that means - I’d hate to think what is going to happen to all the parameters I set up on the many devices over the past several months… I have blinds set to report status every so often, more importantly, I have Qubino Flush Relays set to go off so many seconds after going on (very useful whenever Smartthings fails to turn them off, e.g. irrigation…). Pity that during the migration this will happen and we will be none the wiser until we start experiencing problems like these.
Good work!