I am sorry that you experienced this, thank you for your communication. I have a few questions that I would like to ask. When you noticed that the 2 Enerwave motion detectors were not communicating with the hub, did you try to trip the motion sensors?
I will have to look at your account to tell you why specifically the last motion detectors did not migrate. Here are some common reasons:
The device was backed by a non-smartthings owned DTH (more details coming soon).
We aren’t ready to migrate that device to Lua yet, and haven’t attempted to migrate it.
It should have migrated, and it didnt for some reason.
I will look into that for you, do you have the fingerprints for that last device?
We are busy getting Lua Drivers ready for all SmartThings users. We are using this file to communicate fingerprints that belong to DTHs that will be Migrated to Lua Drivers. Please note, we are migrating Hub Firmware Beta users to our Beta Channel, not the default join channel.
I have reported your migration issues to the development team, thanks again for your communication. I will follow up as soon as we know more.
We ran into an issue when migrating Z-Wave devices on this last round. We are aware of the root cause and will reach out again when we re-attempt. Thank you for your communication. This explains why not all of your devices migrated.
Consider something like the ZigBee RGB Bulb DTH. If that has been migrated to the ZigBee Switch driver in the beta channel, doesn’t that mean the user now has an Edge driver installed that has gazillions of fingerprints beyond just the devices that used the ZigBee RGB Bulb DTH and other migrated DTHs?
If a driver is installed on a user’s hub and the driver supports multiple fingerprints (many do), then when a user goes to add a device that is also supported by that driver then the hub will not need to download an additional driver.
What I was getting at was that users might reasonably expect devices using a DTH to be migrated to an Edge driver that only supports the same devices the DTH does (plus any previously migrated ones). Like for like. Instead they are getting an Edge driver that potentially supports dozens and dozens of other devices that they aren’t anticipating and they may suddenly find that when they reinstall another of their existing devices it picks up an Edge driver they aren’t ready for yet.
It doesn’t bother me personally because I am running all the beta Edge drivers I can already, regardless of how broken they are.
Remember there’s a limit on drivers installed (50), if drivers were separated into the same “sections/categories” as the DTHs, then, we would need to install more to support all our devices.
Being in a Beta channel implies expecting this kind of change, if there’s a problem with the driver, users can contact us so the team can review it. (This kind of report helps us improve the drivers’ behavior)
I wasn’t in any way suggesting that should be done. Just pointing out that users may be somewhat cross to re-pair a device and suddenly find it using an Edge driver when the device is neither part of the migration, and nor have they installed said Edge driver themselves.
The users might not have been in a beta channel though.
Look at it another way. If it was suddenly announced that all the beta hub firmware group were getting their hubs enrolled in the beta channel and having all the beta drivers installed, you would probably expect a backlash. Well that is actually the path the migration is treading. To a lesser degree, yes, but it is the same path.
You just have to hope any affected users will be nice about it.