Programmatically change component driver of child devices

armand · February 21, 2021, 12:04am

Is there any way to programmatically change the driver of a component child device from the parent app?

I have been playing with minimizing driver features, and came to the realization that what I really need is a way to change the child device drivers based on the features available on the child device (which can change).

armand · May 20, 2021, 12:55am

Checking in to see if anyone know of a way to do this...

bertabcd1234 · May 20, 2021, 1:11am

I'm pretty sure I've seen this done in ST DTHs or SmartApps, but I cannot remember the name of the method that was used. I also don't know if this was implemented in Hubitat. But this memory is pretty useless since I can't remember the name, and a search is failing me...sorry. But maybe someone else will remember, or you could try scouring the SmartThingsPublic repos or other popular sources to see if you're able to find anything...

thebearmay · May 20, 2021, 1:50am

Think you would need to deleteChildDevice and then addChildDevice with the new driver.

bertabcd1234 · May 20, 2021, 2:26am

That would sort of work, but it would create an entirely new device (and so any apps using the device will be affected). I do remember that ST had a way to do this--just wish I could remember what it was (or if it works here)....

armand · May 20, 2021, 2:40am

This creates a new Device ID, and forcefully removes the device from any apps that are subscribed to it. I just want to change a dimmable bulb to a ColorTemp bulb, to an RGB bulb. In this direction, I don't break automations, and can provision devices minimally, and only expand them as their capabilities grow. This is for an integration, so such a scenario could happen.

Exactly why I ask. Thanks for understanding my concern here. I will see if I can find anything in the ST documentation.

martyn · May 20, 2021, 10:25am

SmartThings has "setDeviceType" but I don't think HE supports that.

github.com

SmartThingsCommunity/SmartThingsPublic/blob/a7c980340992ca37508d42a70f354b5fd7d30048/devicetypes/smartthings/smartsense-open-closed-sensor.src/smartsense-open-closed-sensor.groovy

/**
 *  SmartSense Open/Closed Sensor
 *
 *  Copyright 2014 SmartThings
 *
 *  Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except
 *  in compliance with the License. You may obtain a copy of the License at:
 *
 *      http://www.apache.org/licenses/LICENSE-2.0
 *
 *  Unless required by applicable law or agreed to in writing, software distributed under the License is distributed
 *  on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License
 *  for the specific language governing permissions and limitations under the License.
 *
 */
import physicalgraph.zigbee.clusters.iaszone.ZoneStatus
import physicalgraph.zigbee.zcl.DataType

metadata {
	definition(name: "SmartSense Open/Closed Sensor", namespace: "smartthings", author: "SmartThings", runLocally: true, minHubCoreVersion: '000.017.0012', executeCommandsLocally: false, genericHandler: "Zigbee") {

This file has been truncated. show original

I ran into a use case when writing a driver for some ZigBee devices where their fingerprints were problematic. So being able to change the driver once the device had been correctly identified would have been helpful.

armand · May 21, 2021, 7:19pm

I don’t see it in the documentation. I suspect it’s not supported.

bobbyD · September 17, 2022, 12:28pm