-
-
Notifications
You must be signed in to change notification settings - Fork 30.8k
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
hassfest: Collapsible sections giving extra keys not allowed errors #126467
Comments
We use GitHub for tracking issues with Home Assistant Core itself, not for providing support, so you should try our Community Forum or join our Discord chat server. Thanks! 👍 |
Yep, I don't think it's a support issue, I think it's an issue with hassfest. |
but even this hassfest github action, is not part of HA core, so you should report your issue to the actions repository 😉 |
I asked where to post this on the Discord Dev and they said Core. It is also posted to actions though: home-assistant/actions#114 |
please avoid cross posting the same issue in different repositories, without mention them to each other. This avoids duplicated efforts and keeps things in one place, thx 👍 |
The problem
Following the instructions here: https://developers.home-assistant.io/docs/dev_101_services/#service-action-description-example
I added a collapsible section to my services. Now hassfest is giving an error saying extra keys are not allowed. However, these are the keys that are listed on the HA site and appear to be working.
PR with error: travisghansen/hass-opnsense#204
What version of Home Assistant Core has the issue?
core-2024.9.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Supervised
Integration causing the issue
hassfest
Link to integration documentation on our website
https://github.com/home-assistant/actions
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: