Let me guess I will need to remove and add it back

🛎️ Get Help Devices
1

Had a ZEN30 get fried last week by an electrician who blew the breaker on the relay circuit for the fan switch. Today I noticed this (I have renamed it to add DEAD):

2022-10-12 12_20_02-Window
2022-10-12 12_20_02-Window2189×166 31 KB

That would be the child device for the old ZEN30 that this new one replaced. As you can see it hasn't been active since last week. I did remove the ZEN30 but somehow I have this left over. :man_shrugging:

Can I get rid of just that child somehow? Doesn't seem to hurt anything it's just weird. I can rename it so it's always at the bottom of my devices list but I'd rather remove it.

Thanks!

2

Not sure it matters as it's not the child that repeats but the parent so as long as the parent is alive you shouldn't have an issue. You can try to change to the DEVICE drive, click save then click delete everything then switch back to the normal driver, click save then configure and that should clean things out.

3

Think I'll just leave well enough alone. :smiley:

4

I don't suppose a stick could remove it? Only used one a couple times so I don't know what all it can do. If we could just delete a child device....

5

See above. Change the driver to device. Click save. Click all the delete buttons for state and what not. Change back to the main driver. Click save, click configure.

6

And now the correct child is also gone.... sigh... now I have no fan control.

7

When you put the driver back and click configure it should come back (make sure you pick multi endpoint)

1 Like
8

Did that and now I have this and neither child will control the fan so it's worse now than it was....

2022-10-12 13_17_42-
2022-10-12 13_17_42-2182×192 31.9 KB

I guess I can repeat the process again. Nothing to lose at this point. Just so many rules on this switch that I don't want to have to edit if I have to remove it and put it back.

9

Worked when I did it again! Whew! Thanks!

10

Any time you do that simply create a virtual device then use the built in swap tool. It will swap the virtual device into all the rules that use it. That way when you get everything fixed you can swap to the fixed/new device

11

Doing the steps you outlined did break all the rules I had for the fan but those were minimal so I got it all fixed now. Will a virtual work for a device with child devices? I somehow thought it would not.

12

No you can't swap out child devices

1 Like
13

FYI for future reference you can create a virtual device to hold its place, then use "swap devices in apps" to replace all instances of the failed device with the virtual device. Then after you get the new device joined, swap again using the swap app to replace the virtual device placeholder with the newly joined actual device

14

That's what I said above :slight_smile: What you can't do is swap out child devices.

15

Duh, sorry it was late and I missed your reply.
In any event I think that feature is really incredible, and don't believe it exists on any other platform.

1 Like
16

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