Change of driver leaves child devices

I've just added a couple of Fibaro Smart Implants. I've used these previously and needed the community version of the driver to access some of the additional parameters (decoupling inputs from outputs). On this occasion I don't need any advanced options and want to use the inbuilt Hubitat driver...

On inclusion Hubitat assigned the community driver. I've changed the driver to the Hubitat one and clicked save. Everything is working, however the change of driver has left all 7 of the previous child devices created at inclusion and the delete button is greyed out for each. How can I get rid of the non functional child devices as it upsets my organised brain. The images below show the carnage. The device is 'E7' and all endpoints starting E7 are orphans (for want of a better term) of the driver at inclusion. The working endpoints begin 1869:



Changing a driver will never remove child devices, even if they were created by another driver.

If you want to do so yourself, sometimes you can do so the "normal" way. In your case, you'll have to switch to the "Device" driver and run the command there to delete all child devices, as this driver author apparently chose to make them "component" child devices that cannot be deleted. Then, you can switch back to your normal driver.

1 Like

Thanks @bertabcd1234. What command should I use after changing the driver to 'Device'?

Edit: LOL ignore that question - the answer slapped me in the face as I changed the driver to 'Device' :laughing:

Should be a button at the top like this... While you're here, I'd also hit the "Delete all states", "Delete all current states", and "Delete all scheduled jobs" too -- might as well wipe it all clean for the new driver.

1 Like

Perfect - thanks @bertabcd1234. Did that, switched back and hit 'Configure' - all sorted :+1:

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.