Deconz-rest-plugin: Deleted Devices still visible in Deconz

[zigistar]

Hi,

some of my devices are still visible in Deconz despite they are removed 5 month ago and has been flagged as deleted in zll.db database (see screenshots). I also removed them multiple times in Deconz manually (Edit-Menu -> Delete selected Nodes). This removes the nodes only temporarily, they come back again when I reboot the Raspi.

What shall I do to make them disappear permanently? Shall I modify the zll.db with sqlite3?
Any recommendations?

Thanks a lot for your help.

I'm running 2.05.69 and firmware 26330500 on a Raspi 3+

[Pirol62]

Same issue but mine is connected to an osram plug 01.
Not visible in Phoscon.

[ryancasler]

I have been having the same problem. With 1 Tradfri Remote, 1 EcoLink Remote and 1 Lutron Connected Bulb remote. No matter how many times i delete them they come right back. Where else can I delete them from? They have to be in a database table somewhere.

[realwax]

Same issue here...
As there is no active bulb or sensor numbering it can't be deleted via deconz rest api. Please fix!

[lensherm]

Has this been or is planning to be addressed?

[Buzztiger]

Same problem. They keep coming back after a restart. Anyone figured out how to remove them for good?

[ebaauw]

So one of my innr SP 120 plugs kept a Hue button end-device in its neighbour table, even though the button had left the network weeks ago. Even after removing all references to the button from the database, deCONZ would re-create a node for the button, every time the plug's neighbour table was read. Once you've ended up in a situation like this, there's nothing deCONZ can do. I had to reset and re-pair the plug to remove the neighbour table entry. Only after that, the button stopped re-appearing.

I want deCONZ to reset devices when they're removed (through the API or from the GUI), see #2377. Note however, that won't prevent this situation from occurring ever again. If the device's _Leave_ message won't reach one of its neighbours (e.g. because the neighbour is offline), it'll keep the device in the neighbour table entry. Also, it might take up to an hour for the _Leave Request_ to reach a "deep sleeper" battery-powered end device. If you reset or power down the device before that, it won't send the _Leave_ message. You might want to wake battery-powered devices when removing them.

Until I'll have made the changes discussed in #2377, best remove devices through the API, supplying a {"reset": true} body to the DELETE request.

[meremortals70]

Another request here. Need the ability to clean up devices when deleted.

[meremortals70]

The reason I opened a new issue was it would seem this was dead, is anyone working on this please?

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ebaauw]

Bump

[meremortals70]

Yep Deconz is no longer in my network

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ebaauw]

Bump

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[realwax]

bump

[stale[bot]]

As there hasn't been any response in 21 days, this issue has been automatically marked as stale. At OP: Please either close this issue or keep it active It will be closed in 7 days if no further activity occurs.

[ebaauw]

@Mimiix, please assign the right label to shut up the bloody bot.

[labaland]

bumb