-
Notifications
You must be signed in to change notification settings - Fork 168
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 editor error with ESPHome secrets: "cannot merge mappings; the provided source object is unacceptable" #248
Comments
@danielperna84 |
Due to private commitments I'm not able to work on this project. Somebody else has to contribute a fix, which I could then merge into the code. |
@frenck |
Sorry, can't help with this. |
Describe the issue you are experiencing
The problem
Hello!
I enter in file
/homeassistant/esphome/secrets.yaml
the following (and only) line:<<: !include ../secrets.yaml
The File editor then complains with a red exclamation mark symbol and the following error:
Nevertheless, an ESPHome node correctly gets the secrets from one level above, i.e. from
/homeassistant/secrets.yaml
.Please note:
I've entered:
<<: !include ../secrets.yaml
FE complains:
<<: .include ../secrets.yaml
Is the File editor misinterpreting the trailing exclamation mark (!) as a period (.)?
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
File editor
What is the version of the add-on?
5.8.0
Steps to reproduce the issue
Enter in file
/homeassistant/secrets.yaml
the following line (example):wifi_password: "blablabla"
Enter in file
/homeassistant/esphome/secrets.yaml
the following (and only) line:<<: !include ../secrets.yaml
Observe the File editor error message:
System Health information
No response
Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: