Deleting child devices

[xAPPO 18]

I have created a QA that discovers all the devices on my home C-Bus network , mainly lighting.  After a few false starts it's correctly added about 200 child devices and it's working well.   However I have about 50 mistakenly created devices I would now like to remove.   If I click the delete (wastebin) icon on any of those children it warns me accompanied by a list of all the children, that it's going to have to delete every child device which was a surprise. 

 

So I haven't done that and instead was considering using the api to delete a child. But I'm worried it might delete them all as well.  Why is this happening from the web UI and will delete via the api just delete the one specific device ?

 

I realise I can hide or disable the unwanted devices but I would prefer them gone totally.

 

I created a backup as a fallback but was a bit alarmed to see this....

 

Please login or register to see this image.

/monthly_2020_08/image.png.522af6e603ae06ed3d6186129b6c3ba7.png" />

 

 

I have way more than 2 devices on my system not counting child devices. The scenes and rooms are correct

[10der 832]

if you delete the main device if should be remove 100500 child devices

[xAPPO 18]

.. sorry ? I miss the point of this reply.   I want to delete one child devices and it says it will delete them all within that parent. I am not deleting a parent device.

[SmartHomeEddy 912]

If you delete the parent, all the childs, also the 50 mistakenly are deleted. 
 

Then let the parent create the childs again.

 

Don’t forget to download the quickapp. 
 

 

 

Edited August 8, 2020 by SmartHomeEddy

[xAPPO 18]

Ahh yes - I considered that but it took quite a bit to create them - lots of manual name edits for example - and I really didn't want to create a big deviceID gap either - so I guess the question is can I delete a single child device via the api ? 

 

Easiest way I suppose is to create another parent with just a few children and try it...

 

Kevin

Edited August 8, 2020 by xAPPO

[rangee 32]

After this.

self:initChildDevices({--[[something]]})

 

try

self:removeChildDevice(id)

or

api.delete("/plugins/removeChildDevice/" .. id)

Edited August 8, 2020 by rangee

[SmartHomeEddy 912]

Will it work with the API?

 

Please login or register to see this code.

 

Please login or register to see this attachment.

[jgab 2,203]

26 minutes ago, rangee said:

After this.

self:initChildDevices({--[[something]]})

 

try

self:removeChildDevice(id)

or

api.delete("/plugins/removeChildDevice/" .. id)

The api.delete doesn’t update the self.childDevices list. That’s the role of self:re moveChildDevice. The only trick is if you have some mapping variable that you need to keep in sync. I assume that some of the plugins could be confused if their children were deleted without their knowledge....

Edited August 8, 2020 by jgab

[rangee 32]

3 minutes ago, jgab said:

The api.delete doesn’t update the self.childDevices list. That’s the role of self:re moveChildDevice. The only trick is if you have some mapping variable that you need to keep in sync. I assume that some of the plugins could be confused if their children were deleted without their knowledge....

That doesnt matter

just restart parent QA

[jgab 2,203]

5 minutes ago, rangee said:

That doesnt matter

just restart parent QA

Well, I wouldn’t bet that it’s true for all QAs. In Fibaro’s example for childDevices they store the map in a quickAppVariable, and They read it back at restarts... If one forget to resync that to reality....

Much better then to only rely on the childDevices list and store mapping data in the child devices themselves.

[rangee 32]

1 minute ago, jgab said:

Well, I wouldn’t bet that it’s true for all QAs. In Fibaro’s example for childDevices they store the map in a quickAppVariable, and They read it back at restarts... If one forget to resync that to reality....

Much better then to only rely on the childDevices list and store mapping data in the child devices themselves.

 yes. case by case.

But  key point is that.

self:removeChildDevice

 

 

ps. I store data in child device's information. So in my case, just do self:removeChildDevice  make sense.

 

[xAPPO 18]

2 hours ago, jgab said:

Well, I wouldn’t bet that it’s true for all QAs.

  .. and indeed it isn't true of mine !   But I can of course remove the mapping as well.  I was just establishing it worked for a single child device.

 

Why does the web UI 'delete' on a child device delete them all ? Is that a bug ?  It seems they've considered the result because they warn you and give you a list of the child devices so they intend, or know it will remove all

[DPB 0]

I had the same Problem, a lot of virtual junk child devices added to a quick app device erroneously generated by a constructor code. Then I renamed that Child Devices "toDelete" in the device list manually, filtered them by name, and after rename I was able to delete them manually with the waste bin symbol, they were also removed from the device tree in the master device ....