Assign Area to multiple entities in bulk

[michaelklanner]

Describe the enhancement

It would be nice if we could assign an area to multiple entities at once. Currently, this can only be done for devices. And we can already assign a label to multiple entities at once.

Use cases

If I add several entities via a YAML configuration that does not allow defining an area, it would be very handy to select all entities in the UI and assign a specific area. Currently, I have to click each entity and assign the area.

Visual examples

No response

Anything else?

No response

[teskanoo]

Just spent over an hour assigning another few hundred entities to areas that I have recently created or have been created by others' packages - still got another 400+ to go - need to take a break.

Please just let us do this like we can with labels - not all of our entities have devices or are created by MQTT - single assignment from ungrouped area is such a pain

[karwosts]

I think this was resisted at some point by developers as they primarily want to push users to assigning device areas instead, and were afraid that this would mess people up.

You can use a little code in your browser console to bulk assign in the meantime. Just check the checkboxes for the desired entities on the config/entities page and run the following in the browser console (fill in your own area_id):

(try at your own risk 🙃 )

area_id = "bedroom";

hass = document.getElementsByTagName("home-assistant")[0].hass;
table = document.querySelector("body > home-assistant").shadowRoot.querySelector("home-assistant-main").shadowRoot.querySelector("ha-drawer > partial-panel-resolver > ha-panel-config > ha-config-entities").shadowRoot.querySelector("#entity_id").shadowRoot.querySelector("hass-tabs-subpage > ha-data-table");
table._checkedRows.forEach((entity_id) => hass.callWS({type: "config/entity_registry/update", entity_id, area_id}))

[teskanoo]

Thank you so much karwosts, That is really very helpful - I will backup first
I recall the developers pushing back on this and I could see the reasoning to an extent, however, this option could possibly be enabled if it could be detected that the current checkbox selection pertained only to entities not having an associated device - and of course, there's always Spook ;)