#New automation will not save.

1 messages · Page 1 of 1 (latest)

raw canyon
#

I am a new user of HA, and i am trying to setup a Hue dial to turn on or off a Hue light (hopefully with dimming control),
I've tested the light using the UI from HA (everything ok)
I can see the reaction from button presses and such from the dial, no problem

but for some reason i cannot make an automation to use this dial with the light.
the HA browser tries to save the automation but just has a spinning wheel for ages, no change.
I asked chat gpt and i looked into the file via terminal and I could see there where lines of code, but it couldn't help diagnose the issue.

cedar pulsar
#

what's in your configuration.yaml for automation: ?

raw canyon
#

does this look right?

red junco
#

No that's not the configuration.yaml

raw canyon
#

empty
plz forgive me does each plugin need a different configuration file or do they append them together?

red junco
#

The configuration.yaml is joining the other yaml files together. It is the "root yaml file". If it doesn't have any content the automations.yaml won't be read. Why are you editing those files in the first place? Especially when you're a new user you should use the graphical automation editor. You can still edit the automation by putting the editor in yaml mode

raw canyon
#

yeah, sorry the syntax in editor mode got me confused,
as per the og post, the UI didnt work, and froze.
sooo i looked into the code

#

...
so this is my 1st automation as well

red junco
#

All you're experiencing is because the configuration.yaml is empty. Now the question is "why is it empty"

raw canyon
#

ah right,
i knew it was simple,

so that file, where can i find it ?
can i type nano config/configuration.yaml
to edit it and maybe paste in a sample off github?

#

or just right the 1st couple of lines

red junco
#

I'd suggest to install the file editor or studio code server addon for editing the files. Both have yaml syntax highlighting/checks.
Then adding the default configuration.yaml should fix your issue. After that check if your system is in a "clean" state by using the "check configuration" button in the developer tools. If that's reporting that nothing is preventing homeassistant from restarting you should do a full reboot of the entire machine.

raw canyon
#

yeah ok thats a great start, thank you!

raw canyon
#

@red junco
so im in the file editor
the error said line 2 column 9 which is the Frontend:
can you help me understand what the syntax is?

#

(sorry im coming from a background in html and css (and a little of flash programming)

red junco
#

Where does line 1 come from? It's only a partial version of what I have. The line should be a comment and in your case it's not

raw canyon
#

sorry i reloaded and tried to check it and
the plot thickens

#

probly something ive done

red junco
#

What are the repairs suggesting? But overall it at least shows that the automations.yaml is being read now

raw canyon
#

yeah,
...

#

The automation "automation 2" (automation.automation_2) is not active because the configuration has errors.

Error:extra keys not allowed @ data['name']. Got 'Hue Dial Light Control Off'.

To fix this error, edit the automation to correct it, then save and reload the automation configuration.

#

automation.automation_1 has the same error

red junco
#

But you can see the automations in the UI in the automation editor now? Then you either need to fix the automations or if they never worked and you didn't put too much effort on creating them you might as well delete and recreate them in the UI

#

Your initial problem is solved

raw canyon
#

Yay it works after deleting the broken 1's and starting again.

THANKS alot man, that realy helped.