Make sure your groups only contain these options (they have changed):
Exact same problem here. Same error, same behavior from 0.107.b00 til 0.107.1
are you using ui-lovelace.yaml or editing lovelace from the frontend as only the latter will migrate the resources automatically
Also i think the new way to add resources it aimed at mistakes not happening when using the raw lovelace editor to add resources, which makes sense for average user
It is very subtle - and an error in the example in the documentation.
The “id” of the dashboard needs to have a “-” in it.
So
dashboards:
yaml:
(...)
Is incorrect and needs to be cahnged to something like
dashboards:
yaml-dashboard:
(...)
(or whatever, as long as it contains at least one “-”)
1 Like
Check you don’t have any groups defined somewhere else, such as in a package.
I found that even though I commented out everything in my groups.yaml file the config validation still referenced the line
group: !include groups.yaml
I had multiple package files with groups that had various combinations of
view: false
and / or
control: hidden
1 Like
Always edit lovelace from the front end … wish you could add comments via the interface as my resources looked like this before:
- type: js
url: /local/resources/html-template-card.js?v=1.0.2
web: >-
https://github.com/PiotrMachowski/Home-Assistant-Lovelace-HTML-Jinja2-Template-card
- type: module
url: /local/resources/decluttering-card.js?v=0.3.0
web: 'https://github.com/custom-cards/decluttering-card'
I just upgraded to 0.107.1 and upgraded canary-card through HACS and the problem is gone, did not have to do anything with custom header.
Don’t know which of those solved the problem though.
I haven’t updated to 0.107 yet so i can’t help to say if it’s reproductable but have you checked that Safari’s privacy mode is not enabled ?
Edit: Forget about it, i have missed that #5264 issue
It looks from what I can tell like the homeassistant/home-assistant Docker image is now built on s6-overlay and therefore now needs to be run as root. This would probably be worth mentioning in the “breaking changes” section of the release notes.
1 Like
Absolutely no big deal but surely a prefix such as dashboard would have been better than an ‘arbitrary-random-and not-intuitively-knowable’ embedded dash?
No I wasn’t part of the discussions on Discord and as I said, it’s no big deal. I’m just passing the time in these socially isolated times…
EDIT: and hey, be nice, it’s my special day… 
Congrats 
1 Like
Did you find a solution for the Custom element doesn’t exist: hui-conditional-card error?
Yes , you need to use the preloader, then add the conditional card
I have the same issue here. have removed all groups.yaml entried (no longer needed) and still no joy either
Did you check for discontinued group services in your automations and scripts?
I have enabled zone: but the zones are not loading (just the Home zone) Worked in 106
Update:
I use
zone: !include_dir_named …/entities/zones
in 106
in 107 something has changed (has become a dict?)
When I use: include_dir_merge_named I get 1 zone, but the rest doesn’t load
(every zone is a differnt yaml file)
Just signed in to thank all the Home Assistant contributers! 
Updated from the latest 0.106 to 0.107 and then to 0.107.1 without a single problem.
Thanks again for the great work!
2 Likes
Just updated from 0.106.6 to 0.107.1 and everything working, even hacs with custom cards:
- Custom Header
- Mini Graph Card
- Mini Media Player
- Upcoming Media Card
- Plex Recently Added
- Samsungtv Custom
Thank you, the new improvements are amazing.
1 Like
Could you tell show me how your configuration looks like? I’m experiencing the same issue and adding ‘decluttering’ doesn’t seem to work…
ui-lovelace.yaml:
preload:
- picture-entity
- decluttering
I love version 0.107, so far all seems to work okay. Thanks