We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi, It seems that this extension does not recognize this template schema (which is working fine in HA, no error in logs):
In configuration.yaml:
template: !include templates.yaml
in templates.yaml:
- binary_sensor: name: ... unique_id: ... ... - binary_sensor: name: ... unique_id: ... ... - sensor: name: ... unique_id: ... ... - sensor: name: ... unique_id: ... ...
Error is: Incorrect type. Expected "array".yaml-schema: http://schemas.home-assistant.io/integration-template
Incorrect type. Expected "array".yaml-schema: http://schemas.home-assistant.io/integration-template
Also note that URL http://schemas.home-assistant.io/integration-template is not working.
The text was updated successfully, but these errors were encountered:
I'm experiencing the same problem with the Visual Studio Addon (5.11.0) and Home Assistant 2023.9.3.
The configuration.yaml file is fine and runs with no errors in Home Assistant, but if I try and use the VS Code editor I get:
Incorrect type. Expected "object".yaml-schema: http://schemas.home-assistant.io/configuration
The schema url is also incorrect.
Sorry, something went wrong.
Same problem here. Schemas are not working for automation.yaml too.
No branches or pull requests
Hi,
It seems that this extension does not recognize this template schema (which is working fine in HA, no error in logs):
In configuration.yaml:
in templates.yaml:
Error is:
Incorrect type. Expected "array".yaml-schema: http://schemas.home-assistant.io/integration-template
Also note that URL http://schemas.home-assistant.io/integration-template is not working.
The text was updated successfully, but these errors were encountered: