Remove multiple devices

Hi,

I have a smoke detector which is connected via the RFXCom integration which created more than 250 devices, is it possible to delete multiple devices?

Edwn

3 Likes

hi,

Same problem since a few months

and still no solution

Same problem. I have 710 Devices to delete. A year ago there was a delete option., but not now

Same issue, i have +400 devices to remove

I have the same issue, tried to remove by removing all entities from core.device_registry and core.entity_registry and core.restore_state. but they get restored once home assistant starts again.

And i have over 1500 devices and 6700 entities, most are the smoke detektor my neighbour has.

I wish there was a way to remove these easily

2 Likes

Upping the message. Same here, any chance to delete in batch ?

I have a whopping 15989 Apple Continuity devices…

1 Like

same here… you have bluetooth on as well I assume?

Still no way to delete many devices easily?

1 Like

Welcome to device hell:

imagen

Have you solved that? My Mosquitto Brokers is flooded with thousands of Apple Continuity devices from TheengsGateway BLEtoMQTT. I don’t know how to get rid off them!

I’m also looking for a way to delete multiple devices…

Me to. 3524 devices and 13830 rfxcom entities.
I use only 20 I think.

There is a feature request you can vote on here: WTH Can’t I mass-delete (non-existent) devices?

@BHSPitMonkey I guess that FR is locked or something as I cannot reply.
Just wanted to add that my Fritzbox and Unifi integrations are also adding hundreds of devices. I’ve disabled their tracking of new devices, as I don’t really need network clients as devices/entities, but I suppose that option doesn’t remove ones that have already been added.

Of course, I’m not about to go and delete them one by one.

And also why can we bulk-add entities to a label or area, but not literally do anything else in bulk? I mean why specifically those two actions? It just seems oddly specific, what with HA as a product being setup in such a generic way.

I just re-upped the WTH 2020 and WTH 2022 entries regarding this huge problem, for WTH 2024.

Perhaps it gets some attention from our (volunteer! please be nice to them) developers this year - one can hope :wink: