An Edge driver has to be on your hub in order to switch drivers. That happens one of four ways:
You install a new device and the production driver is downloaded and used
During the ST migration, a production driver is downloaded and your device is converted
You subscribe to the beta drivers channel and install a driver yourself
You subscribe to a community driver channel and install a driver yourself
So supposing you manually installed a driver, it would theoretically be in the drop down list of drivers that a device could be switched to. Now, that being said, there may be something in the web app that won’t let you select a new driver for a device that is using a DTH or even if you can, it might fail trying to switch over. Worth a try I suppose, but I don’t have any devices left on DTH to test out whether it would work or not.
I have several z-wave lock edge drivers installed, including the ST one. Thanks for the tip about looking for the fingerprint, although I would think it would just work because it’s a common z-wave lock (but who knows if it was dropped). Maybe it’s because I never actually deleted the Rboy lock app. Anyway, I’ll keep trying because it hasn’t converted yet by itself, even to just the Thing driver.
PS. I tried to look at the API+ link in your post and it says it’s private or doesn’t exist. My locks are Kwikset 910s. Shouldn’t they work? However, my ST drivers are from the beta channel of ST. Does that matter? I have the Rboy beta driver installed and one would think that would include the 910 lock. I have a bunch of other devices that have never converted either (like some ZigBee bulbs and Inovelli multi switches). I keep waiting…
I have a Contact sensor _TZ3000_6jeesvrt TS0203 using a Zigbee Contact MC Driver and a second one running on a DTH. I cannot change the DTH device over to Edge using this method. So for now the answer is no you can’t
Devices with the same name can still have different fingerprints. This is why you need to check that your exact fingerprint is included.
The only real difference between the ST beta and ST regular drivers is that some devices might be available in the beta that are not yet available in the regular channel drivers yet needing to be tested.
I am not sure I can offer a ‘why’ as such, but there is nothing new or unusual about it. It is simply that most native tools are Location centred so it is easy not to be aware of the devices that aren’t in Locations.
The ‘mobile as a thing’ device represents your mobile or tablet as a device in itself. It appears to be a ‘User Device’, whatever that means specifically, in the API parlance and sits outside of any Locations. It is the parent device of the mobile presence devices which are created in each Location where presence sensing has been enabled.
Does it have any function apart from being glue in the architecture? No idea.
Excellent point. Very disappointing that we are now just 8 days away from losing access to the old portal and Samsung has still not supplied the ability to run VITAL utilities in the new Web App. Nor are these utilities listed in the latest version of my iOS ST app. Feels like they are abandoning these tools. That will end my 8yr relationship with Smartthings if they do.