This question seems to have nothing to do with the device or driver in the original topic, so it may have been better to start a new one. (But don't now; once again, I suggest you only post your question in only one place. It seems you may be starting to again for the device in question based on posts I've read in the last few minutes. Besides being in line with the Community Guidelines, this will also be much easier for you to get help and other people to help since bits and pieces of information will not be scattered all over.)
That being said...
Changing a parent driver can have consequences for child devices, which typically use a driver that expect the parent driver to behave in a certain way. Same thing with swapping a child driver. Sometimes, you can find the right child driver and switch to it. Other times, something like a "Configure" or "Save Preferences" on the device detail page will create the necessary child devices for you. I'd suggest removing the child devices the original driver created -- after making sure they are not in use by any apps, of course -- and then trying one of these things to let your new driver create them on its own in the format it expects. (There is often more than just the driver that matters, typically also the DNI, but it depends on the driver and device.)
You might be thinking of Zigbee, where if you don't delete the device, it will use the currently selected (so possibly "new" in some sense, with respect to the initial pairing) driver. However, Z-Wave can't do this--it's not able to match up devices it already knows about based on a MAC address/long ID like Zigbee can. It only knows the node ID, which is assigned by the hub upon pairing (though maybe a Z-Wave Replace would work...I forget what commands, if any, it runs upon inclusion that way). The Inovelli device in question appears to be Z-Wave, from the other post.
