Assign Unique_ID to groups, but how?

Configuration
1

In the blog post announcing 2021.8.0, it says:
“You can now assign a unique ID to light, cover and media player groups, allowing you to manage them from the Home Assistant frontend and assign them to an area!”
But the docs don’t explain how, and simply adding one in YAML only angers the config-parser.
Will this be documented soon?

2

It is already documented:

FYI, when a release is issued, all documentation is updated instantly.

3

Thank you!
I had been looking at the page for ‘Groups’ only - not having ever noticed that the domain-specific groups existed separately.

4

I’m assigning a unique_id to the group but I don’t know what’s wrong.

 suite:
   name: Luzes da Suíte
   icon: mdi:lightbulb-on
   unique_id: 12456789
   entities:
     - switch.suite_tv
     - switch.suite
     - light.led_suite

The code above gives me the following error:

Invalid config for [group]: [unique_id] is an invalid option for [group]. Check: group->group->suite-unique_id. (See /config/configuration.yaml, line 34).’

A question, where are the groups created by the UI stored?

5

See the thread and docs above. You may be trying to do it the way I was, which wasn’t correct.

6

You can’t add unique_id’s to groups in the group domain.

3 Likes
7

Is there a reason why this is not possible for the group domain?

1 Like
8

I don’t know of any reason other than it predates the requirement for unqiue_ids.

2 Likes
10

any changes so far? I have group for binary sensors that must be updated dynamically I can only use old groups to use automation to change their members… but it does not allow to add unique id to the group.bla_bla, therefore it is not possible to mage it from gui

11

Use labels instead of groups. The Spook custom integration includes actions to manage labels.