setting z-wave switch to 'always_on' does not hide the toggle about core

[home-assistant]

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

Code owner commands

Code owners of zwave_js can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign zwave_js Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

zwave_js documentation
zwave_js source
_{^{(message by IssueLinks)}}

[AlCalzone]

Configuration parameters have no meaning to Z-Wave JS, especially such behavior that isn't standardized.
Encoding interactions between that and standard functionality is simply not feasible.

[Mariusthvdb]

thanks. that really is a pity.
ofc I see there are hundreds of options out there... I figured this one, being nr 1, might be less exceptional ;-)

I did see another PR merged the other day in a comparable situation on another integration, need to find that for reference.

So, you don't think there is any other (current or possible future) way of indicating the always_on status?

edit
found the other PR #122035
that gave me hope this would be feasible

[AlCalzone]

always_on is not a standard Z-Wave feature. Both implementing it and assigning it config parameter no 1 is the manufacturer's choice.

[Mariusthvdb]

ok thanks. in that case I fear there is no other option than closing ;-)

would have been nice to create attributes/stand alone entities for features, which are enumerated somehow, so not implementing as fixed params, but add them as they are presented.

Might be a huge undertaking though, if t all possible...

anyways, thank you!