Limitation.. swap devices doesn't show hue bulbs, or any child device

[kahn-hubitat]

the built in swap apps apparently will not work with hue bulbs? Using the built in hue integration

@bravenel

[bravenel]

You can't swap child devices. They have an intimate relationship with their parent device or app, that swap cannot deal with.

[kahn-hubitat]

@bravenel

can't swap child devices. They have an intimate relationship with their parent device or app, that swap cannot deal with.

ok thanks.. but they dont show as child devices in the device list.. must be a special case where they actually are but appear different..

[kahn-hubitat]

they show as having a parent app. but not a parent device?

[bravenel]

@kahn-hubitat

they dont show as child devices in the device list

App child devices don't show separately. Device child devices do.

[bertabcd1234]

Since you mentioned that these are Hue Bridge Integration devices, there is an unofficial workaround: you can modify the last part of the DNI to swap the Hue ID of the old device and the new one. In my testing a while back, that seems to be the only thing the app (and driver) uses to match up devices when parsing states, sending commands, etc. Of course, you can also do things the "old fashioned" way and just swap the device out in all apps, too.

The parent/child thing limitation with Swap Apps Device applies to all child devices, regardless of whether they have a device or app as a parent.

[kahn-hubitat]

@bertabcd1234

workaround: you can modify the last part of the DNI to swap the Hue ID of the old device and the new one. In my testing a while back, that seems to be the only thing the app (and driver) uses to match up devices when parsing states, sending commands, etc. Of course, you can also do things the "old fashioned" way and just swap the device out in all apps, too.

Thanks wish i had posted earlier.. just swapped out 5 bulbs and had a lot of automations i had to manually fix.. probably 10,

I got newer bulbs as i had gen 1s and got tired of not really having any blue and poor green to speak of as i use the colors for various alerts.

I should have remembered that work around as that is what i used to do before the tesla integration/login was fixed and the car would disappear and create a new one with a different dni.

When you can use the swap device it is pretty slick and saves a bundle of time..

[bertabcd1234]

@kahn-hubitat

s that is what i used to do before the tesla integration/login was fixed and the car would disappear and create a new one with a different dni.

Note that this won't necessarily work for all devices, only ones that look for child devices based on DNI. It's possible some could use the (hub-assigned) device ID or some other method of looking them up. If it's an integration you wrote or one you can look at the code for, then you'll know for sure; built-in ones may vary, but this is just something I did a while back that worked for me in this case.

(Having written a Hue Bridge integration myself now, this is really an easy way for this type of app to handle these lookups IMHO, and it's how I do it with mine; I'm guessing we both do something similar, but no guarantees.)