-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
!File causes errors in 107.0 #12
Comments
I think this is duplicate of #11 . But I have the same issue. Only workaround so far is:
|
One of the workarounds I found is to include in the configuration.yaml all the Lovelace resources eg:
and lovelace/resources.yaml
|
As mentioned in the readme, operation in the backed configuration cannot be guaranteed. |
Thanks for the tip, it worked for me too! |
Moved resources from ui-lovelace.yaml to configure.yaml (via !include_dir_merge_list) for 107. !file entries then causes parsing errors and Safe Mode. When !file entries removed Lovelace seems to work properly. I've put "# lovelace_gen" as first line in both the included yaml for resources and configuration.yaml.
Here's the log:
2020-03-19 08:44:48 ERROR (SyncWorker_0) [homeassistant.util.yaml.loader] could not determine a constructor for the tag '!file'
in "/config/ui-lovelace_resources/ui-lovelace_resources.yaml", line 4, column 8
2020-03-19 08:44:48 ERROR (MainThread) [homeassistant.bootstrap] Failed to parse configuration.yaml: could not determine a constructor for the tag '!file'
in "/config/ui-lovelace_resources/ui-lovelace_resources.yaml", line 4, column 8. Activating safe mode.
Want anything else?
Thank you Thomas.
The text was updated successfully, but these errors were encountered: