hassfest: Collapsible sections giving extra keys not allowed errors

[Snuffy2]

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: https://github.com/travisghansen/hass-opnsense/pull/204

Integration opnsense - /github/workspace/custom_components/opnsense:
[64](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:67)
Error: R] [SERVICES] Invalid services.yaml: extra keys not allowed @ data['close_notice']['fields']['multiple_opnsense']['collapsed']. Got True
[65](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:68)
extra keys not allowed @ data['close_notice']['fields']['multiple_opnsense']['fields']. Got {'device_id': {'name': 'OPNsense Device', 'description': 'Select the OPNsense Router to call the command on. If not specified, the command will be sent to all OPNsense Routers.', 'required': False, 'selector': {'device': {'multiple': False, 'filter': [{'integration': 'opnsense'}], 'entity': [{'domain': 'sensor'}]}}}, 'entity_id': {'name': 'OPNsense Entity', 'description': 'Pick any sensor in the OPNsense Router you want to call the command on. If not specified, the command will be sent to all...
[66](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:69)
extra keys not allowed @ data['restart_service']['fields']['multiple_opnsense']['collapsed']. Got True
[67](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:70)
extra keys not allowed @ data['restart_service']['fields']['multiple_opnsense']['fields']. Got {'device_id': {'name': 'OPNsense Device', 'description': 'Select the OPNsense Router to call the command on. If not specified, the command will be sent to all OPNsense Routers.', 'required': False, 'selector': {'device': {'multiple': False, 'filter': [{'integration': 'opnsense'}], 'entity': [{'domain': 'sensor'}]}}}, 'entity_id': {'name': 'OPNsense Entity', 'description': 'Pick any sensor in the OPNsense Router you want to call the command on. If not specified, the command will be sent to all...
[68](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:71)
extra keys not allowed @ data['send_wol']['fields']['multiple_opnsense']['collapsed']. Got True
[69](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:72)
extra keys not allowed @ data['send_wol']['fields']['multiple_opnsense']['fields']. Got {'device_id': {'name': 'OPNsense Device', 'description': 'Select the OPNsense Router to call the command on. If not specified, the command will be sent to all OPNsense Routers.', 'required': False, 'selector': {'device': {'multiple': False, 'filter': [{'integration': 'opnsense'}], 'entity': [{'domain': 'sensor'}]}}}, 'entity_id': {'name': 'OPNsense Entity', 'description': 'Pick any sensor in the OPNsense Router you want to call the command on. If not specified, the command will be sent to all...
[70](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:73)
extra keys not allowed @ data['start_service']['fields']['multiple_opnsense']['collapsed']. Got True
[71](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:74)
extra keys not allowed @ data['start_service']['fields']['multiple_opnsense']['fields']. Got {'device_id': {'name': 'OPNsense Device', 'description': 'Select the OPNsense Router to call the command on. If not specified, the command will be sent to all OPNsense Routers.', 'required': False, 'selector': {'device': {'multiple': False, 'filter': [{'integration': 'opnsense'}], 'entity': [{'domain': 'sensor'}]}}}, 'entity_id': {'name': 'OPNsense Entity', 'description': 'Pick any sensor in the OPNsense Router you want to call the command on. If not specified, the command will be sent to all...
[72](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:75)
extra keys not allowed @ data['stop_service']['fields']['multiple_opnsense']['collapsed']. Got True
[73](https://github.com/travisghansen/hass-opnsense/pull/193/checks#step:4:76)
extra keys not allowed @ data['stop_service']['fields']['multiple_opnsense']['fields']. Got {'device_id': {'name': 'OPNsense Device', 'description': 'Select the OPNsense Router to call the command on. If not specified, the command will be sent to all OPNsense Routers.', 'required': False, 'selector': {'device': {'multiple': False, 'filter': [{'integration': 'opnsense'}], 'entity': [{'domain': 'sensor'}]}}}, 'entity_id': {'name': 'OPNsense Entity', 'description': 'Pick any sensor in the OPNsense Router you want to call the command on. If not specified, the command will be sent to all...

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

[mib1185]

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. The developer channel in particular could be of interest to you 😉

Thanks! 👍

[Snuffy2]

Yep, I don't think it's a support issue, I think it's an issue with hassfest.

[mib1185]

but even this hassfest github action, is not part of HA core, so you should report your issue to the actions repository 😉 Anyway, I think the most reliable way to get support in this, might be our Discord chat server, especial the developer or supüport channel in there.

[Snuffy2]

I asked where to post this on the Discord Dev and they said Core. It is also posted to actions though: https://github.com/home-assistant/actions/issues/114

[mib1185]

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 :+1: In this case, as it get confirmed as a core issue, it is safe to close the issue report in the actions repo on behalf of this one here :+1: I'll re-tag this issue report here accordingly