No entities found in new group config panel

Configuration
1

I’ve got an empty groups.yaml, configuration panel added fine. I’ve cleared out any previous reference to groups (unless there’s some cache to clear?). Every time I go to the new group config panel I get a spinning circle which eventually ends and gives me “no entities found” as a result.

Where do I look for problems? Did I miss something?

2

I’ve got exactly the same issue. I’ve got my “group: !include groups.yaml setup” (with a still empty groups.yaml file) and I get exactly the same error message. My entities DO exist as all other features of HA are working fine. I have an SSL enabled config.

3

Looks like a documentation error, try with groups: instead of group: and it should work (at least, it does here)

4

I get an error when changing to groups: unable to load
Component groups.

5

I should have added, I did make the “group:” correction. Still no entities found, though all entities are accessible through the states panel and working normally.

6

groups: is incorrect. It should be group:

If you make that change you should lose that particular error.

7

Same here. Even in a new installation.

8

So I just got the group config panel working.

I previously had this in my configuration yaml:
group: !inlcude_dir_merge_named includes/groups

I commented this out before trying the new config: option and created the new empty group.yaml file, because that’s how I understood the instructions. In addition I commented out my above include and created a new group: !include groups.yaml

I would restart, get the config panel, and the new group panel would find nothing.

I reverted back to my old include directory and commented out the new one pointing to the empty file, but left config: in, restarted HA, and now I see my entities in the new group panel.

I’m losing my ability to follow instructions, or I’m being gas-lighted.

correction: entities and existing groups populate, but saving changes doesn’t seem to work. I think I’m giving up.

2 Likes
9

It seems if you already had a groups.yaml file you do not need to have an empty file. In other words it is a documentation fail. Restoring my original groups.yaml made everything work.

10

Isn’t that just a permissions issue, that your config files are created and owned by the PI user and user that is running the Home Assistant service doesn’t have write access to these files?