-
Notifications
You must be signed in to change notification settings - Fork 0
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
Keep getting error: "Message malformed: extra keys not allowed @ data['automation']" when trying to save automation #25
Comments
Hi. What version of the United Consumers integration are you using? To be able to help you troubleshoot, you should edit your issue and put 3 backticks ( Are there any errors when you check you configuration? |
I'm using v0.4 of United Consumers. I think I now put the backticks in the wright way ;-) |
From the error message it looks like you added the line "automation:" where you shouldn't. If you paste the automation in the automation editor you should leave that line out. You can have it only once in the file at the top. |
Please try to replace the hyphen before "alias" with a space. The automation should be left aligned without any leading hyphens. Open one of your other automations as yaml to see what I mean. |
I think it now works. I did change the automation text in:
Now hoping for lower prices here in the Netherlands ;-) |
I was getting United Consumers working within HACS. This is working oke. Than I added in configuration.yaml the sensor:
Did try the extensive sensor too.
Didn't work either.
Restarted HA after adjustment. After this I wanted to add the automation (changed automation screen to yaml) and paste the text:
When wanted to save the automation I'll keep getting the message:
In log files there are no clues
The HA is running on a RPI4 from an SSD stick
Editing in Chrome browser on a Windows 11 machine
Strange thing is happening for the other fuel addon: dutch gas prices too. I don't get it. Is it because of the new version of HA that the functionality data doesn't work anymore?
The text was updated successfully, but these errors were encountered: