Z-wave switch driver update broke my SmartThings?

[AlejandroPadilla (Please contact @nayelyz or @Luis_Humberto_Medina)]

Hi @Rigging65 the migration to drivers was announced on 28th Mar and 8 days ago another announcement was created. if your device is a Zigbee thing that means that the device doesn’t match with any generic fingerprint, so the most likely that the device was using a custom DTH. About the virtual device if you create a virtual DTH it must be migrated to a virtual not a LAN for example this is one that was migrated:

We saw your post here about your virtual switch RYAN, we checked that and it’s using a custom edge driver, if this device was migrated recently it must be migrated to a virtual, not a LAN device.

Upcoming Migration for Groovy Devices

As an update and reminder, we will be migrating Groovy DTHs to either a supported SmartThings-owned Edge driver, a community-created Edge driver already installed on your hub, or a “Thing” placeholder soon. The migration process for these devices will take place starting Monday, July 17, and will occur over the course of a week. Devices that migrate to a “Thing” will no longer be functional on the SmartThings Platform. If you need more information on what this means or how to identify a “Thing,” you can check out the FAQ here. If you have an unsupported device still using a Groovy DTH that you expect may be affected by this change, you can still try the options here to move the device to an Edge driver before the migration begins. We will provide another update once the upcoming phase …

Also, I see that you ask something similar on this post Legacy virtual switches stopped working (July 2023) - #38 by Rigging65