[question] Deleted components re-appear?

[docbobo]

In order to keep my HA install as clean as possible, I delete a few of the components that were created on the Z2M side. But when I restarted Z2M, they all reappeared. Is there a way to peristently get rid of those?

[robertsLando]

You should click on store button to make changes persistent between reboots

Daniel

On 23 Dec 2019, at 23:27, Boris Prüßmann [email protected] wrote:

 In order to keep my HA install as clean as possible, I delete a few of the components that were created on the Z2M side. But when I restarted Z2M, they all reappeared. Is there a way to peristently get rid of those?

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or unsubscribe.

[docbobo]

That's what I did. But the deleted components re-appear after restarting Z2M. The view for the device then shows some components as stored, and the recreated ones as not stored. I am on 2.0.6-dev if that matters.

[robertsLando]

Are you deleting all components of a device or just some?

Anyway the other solution for now would be to delete the entire discovery payload from the hass json discovery (set discoveryPayload to {}) in this way when z2m tries to discover it will send an empty payload that will result in no device created

Daniel

On 24 Dec 2019, at 00:59, Boris Prüßmann [email protected] wrote:

 That's what I did. But the deleted components re-appear after restarting Z2M. The view for the device then shows some components as stored, and the recreated ones as not stored. I am on 2.0.6-dev if that matters.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or unsubscribe.

[docbobo]

Just some of the components of each device. Most of the time, all the alarm_* components. I'll give {} a try, so it would definitely be nicer, if the Z2M would also not contain all those uninteresting items ;)

[github-actions[bot]]

This issue is stale because it has been open 90 days with no activity. Remove the stale label or comment or this will be closed in 5 days. To ignore this issue entirely you can add the no-stale label