Help with secrets.yaml esphome

ESPHome
1

Just realize that I should add secrets.YAML and base on information the way to do it is adding esphome/secrets.YAML with this <<: !include ../secrets.yaml

I reboot my HA and the ESPHome Addon, on my ESPHome I already see secrets editor,
however, when I add !secret on my ESPHome device I got a red X on the first line saying it did not find secrets.YAML or error.

So I did not dare to go through worrying my device will become disabled.

Does anyone know what I did wrong?

Running HA 2021.7.4 with supervised + ESPHome AddOn. The ESPHome Directory is inside the config directory.

3

That’s not the issue. He was referring to this:

https://esphome.io/guides/faq.html#how-do-i-use-my-home-assistant-secrets-yaml

Others have problems with this too. See https://community.home-assistant.io/t/accessing-home-assistant-copy-of-secrets-yaml-from-esphome/179053

Basically the advice in the ESPHome documents on using the Home Assistant secrets file don’t seem to work.

4

Ah yes, misunderstood the question. Deleting my post.

5

I got that problem and I know how to used !secret

@tom_l spot on any advice on how to solve the issue?

6

no… I’m just saying that I already create secrets.yaml inside the yaml on esphome directory which confirms on that file appears on esphome apps.

7

any solutions? Its say he need to modified the ESPHome code? Which files?

8

No idea I use two secret files.

9

put a “secrets.yaml” file in /<ha_config_dir>/esphome
I’ve added a single line to that file like as follows:

wifi_pw: Password123

Then in your esphome yaml for the device
it refers to the above like this:

wifi:
  ssid: "MySSID"
  password: !secret wifi_pw
  manual_ip:
    static_ip: 192.168.86.101
    gateway: 192.168.86.1
    subnet: 255.255.255.0
10

Sorry for necroposting, but I faced some problems with this issue too. But it seems to only be a problem with the add-on “File editor” for me, not an actual problem. I run a supervised instance.

As soon as I enter the required <<: !include ../secrets.yaml in the /config/esphome/secrets.yaml file through File editor, a red exclamation pops up in File editor with a weird message:

cannot merge mappings; the provided source object is unacceptable (1:29)

 1 | <<: .include ../secrets.yaml "
---------------------------------^

Initially I thought I had the same problem with the others and tried to debug. But I gave up and just thought to try to compile and upload to a node. YAML was validated, compilation completed without any errors and as soon as the firmware was uploaded, the node connected to wifi just fine. I had initially replaced the wifi_ssid name only, and went on and tried with wifi_passw after that. It worked too. So in my case it’s just a false positive on the File editor’s GUI, nothing more than that.
If someone has figured out what that message means, please let us know.

1 Like
11

Hello!

I have the same problem posted by @Tryfos. Is there a solution that the HA File Editor does not complain as described? Even knowing that it works nevertheless, it is a bit “disturbing”. :wink:

Home Assistant 2023.4.6
Supervisor 2023.04.1
Operating System 9.5
Frontend 20230411.1 - latest

PS/EDIT: Unfortunately, with this …

<<: .include ../secrets.yaml

… in /config/esphome/secrets.yaml

… I cannot update, because the update quits with this error message:

Updating /config/esphome/esp32-ha1.yaml
------------------------------------------------------------

INFO Reading configuration /config/esphome/esp32-ha1.yaml...
ERROR Error while reading config: Invalid YAML syntax:

While constructing a mapping
  in "/config/esphome/secrets.yaml", line 1, column 1:
    <<: .include ../secrets.yaml
    ^
Expected a mapping or list of mappings for merging, but found <class 'esphome.helpers.EStr'>
  in "/config/esphome/secrets.yaml", line 1, column 5:
    <<: .include ../secrets.yaml
        ^
========== [ERROR] /config/esphome/esp32-ha1.yaml ==========

Thanks for sharing your thoughts! :slight_smile:

12

! not .

<<: !include …/secrets.yaml

You should see the syntax highlighting change the color of the include statement when you get it right.

13

That’s all inspiring, but I just kept 1 secrets.yaml file and put a symbolic link from my extended folders back to the original in config/esphome.
Then the secrets thing works in the addon, the fussy include thing can be ignored, and all is well in Mudville.

cd {to the folder trying to reference the secrets.yaml}
ln -s {Path to your esphome folder}/secrets.yaml secrets.yaml
14

Sorry for my very late reply.

I have entered: <<: !include ../secrets.yaml
FE complains: <<: .include ../secrets.yaml

Is the File editor misinterpreting the trailing exclamation mark (!) as a period (.)?

I have opened an issue there:

15

You’re using the wrong syntax. It should be !include groups.yaml with no arrows as per the ESP home docs

16

In named docs I read:

If you want to keep all your secrets in one place, make a secrets.yaml file in the esphome directory with these contents (so it pulls in the contents of your main Home Assistant secrets.yaml file from one directory higher):

<<: !include ../secrets.yaml

17

As issue File editor error with ESPHome secrets: "cannot merge mappings; the provided source object is unacceptable" · Issue #248 · danielperna84/hass-configurator · GitHub is still open, I assume that the as per documentation recommended <<: !include ../secrets.yaml is not correctly interpreted by the file editor/hass-configurator.

@ShadowFist
How come that you refer to the documentation and see that chevrons should not be used, whereas the docu you linked yourself does include them (and the colon)? See screenshot below:

grafik

What am I missing?

18

The answer is pretty simple - my brain was mush after a long day of work and I thought you were referring to the separate ESPHome secrets yaml, instead of using the HA secrets yaml.

Apologies for misleading you - I really should learn to read properly before posting when I’m exhausted (or before the coffee kicks in)

1 Like
19

Well, maybe I misunderstood something. Just to be clear: I have the real secrets in secrets.yaml in the same folder as the configuration.yaml, and the secrets.yaml in folder esphome should refer to it.

20

The bottom line for users that might stumble over this, is as follows:

  • Put your stuff into homeassistant/secrets.yaml
  • Put the following into homeassistant/esphome/secrets.yaml:
    <<: !include ../secrets.yaml
    (the File editor will show an error message that you can obviously ignore)

Devs/people with coding skills might wish to contribute to a resolution of the (unwanted) error message from the File editor:

1 Like