home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.59k stars 29.91k forks source link

Evohome script disabled #86713

Closed dmsims closed 1 year ago

dmsims commented 1 year ago

The problem

From logs (I have replaced sensitive info with x)

Logger: homeassistant.components.script
Source: components/script/config.py:212
Integration: Scripts ([documentation](https://www.home-assistant.io/integrations/script), [issues](https://github.com/home-assistant/home-assistant/issues?q=is%3Aissue+is%3Aopen+label%3A%22integration%3A+script%22))
First occurred: 12:35:25 (1 occurrences)
Last logged: 12:35:25

Script with object id 'evohome' could not be validated and has been disabled: extra keys not allowed @ data['password']. Got 'xxxxxxxx' extra keys not allowed @ data['username']. Got 'david@xxxxxxx.xx.xx' required key not provided @ data['sequence']. Got None

What version of Home Assistant Core has the issue?

2023.1.7

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Evohome

Link to integration documentation on our website

No response

Diagnostics information

No response

Example YAML snippet

Have replaced sensitive info with x

evohome:
  username: "david@xxxxxxx.xx.xx"
  password: "xxxxxxxx"

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 1 year ago

Hey there @home-assistant/core, mind taking a look at this issue as it has been labeled with an integration (script) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `script` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign script` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


script documentation script source (message by IssueLinks)

tdejneka commented 1 year ago

You appear to have entered the configuration for the evohome integration in the wrong place.

It belongs in configuration.yaml and, based on the error message (complaining about an invalid script), you appear to have put it where your scripts are located.

Screenshot_20230126-084728~2

Reference: Evohome

dmsims commented 1 year ago

Hmm I think it is in the right place ...... ha evohome yaml

tdejneka commented 1 year ago

Hmm, that's in the correct location.

It's unclear to me why the error message is reporting a problem with a script whose object_id is evohome. In other words, it's carping about an entity called script.evohome.

Just to be thorough, check the contents of your scripts.yaml file and ensure there's no "evohome" in there.

zxdavb commented 1 year ago

This does not appear to be an issue with evohome - it appears that your configuration.yaml is misconfigured.

I would like to close this issue, unless you can provide further information?

zxdavb commented 1 year ago

There has been no further information, and so I will close this issue.