Some devices that were using a Community-created handler started to get migrated as announced here:
That’s why it was suggested that you found a Community driver that would be compatible with your device and install it in your hub so it would be migrated to it.
So, now that is migrated, you can still find a compatible driver to switch the device to it, that’s why, @Declankh asked @Mariano_Colmenarejo for help.
Update about the analysis made with Declan’s case:
This is the expected behavior so far, as the device was connected through a generic fingerprint, we cannot guarantee it’ll work as expected since not all multi-component devices cannot be divided into devices and mapped the same way. So, @Declankh, you’ll need to use a custom driver that is fully compatible with this device.