[Feature Request] Make use of unified API to manage credentials added in Z-Wave JS 15.23.x

[Hedda]

Problem Description

Z-Wave JS 15.23.0 to 15.23.5 added a new unified API to manage credentials across a range of legacy and modern devices

https://github.com/zwave-js/zwave-js/blob/master/CHANGELOG.md

• Add unified API to manage users and credentials across User Code CC and User Credential CC
• Support User Credential CC V1/V2

15.23.1 (2026-04-14) The unified API for credential management introduced in v15.23.0 is now accessible through endpoint.accessControl instead of living directly on the endpoint. This change paves the way for similar high-level feature APIs to be added in the future without polluting the Endpoint class signature.

This is technically a breaking change, but Z-Wave JS developer expect that this API is not being used yet, so we're going to do some emotional versioning for this release and call it a patch.

15.23.2 (2026-04-15) This release iterates on the new endpoint.accessControl again, making that property undefined when none of the required command classes are supported.

15.23.3 (2026-04-22) This release continues to iterate on the new endpoint.accessControl API:

• Credential slots are considered global per device, not user specific.
• Set-type credential management methods return specific error types that give more information about what failed.

Feature Description

Make use of unified API to manage credentials added in Z-Wave JS 15.23.X

Anything else?

This is technically a breaking change, but Z-Wave JS developer expect that this API is not being used yet, so we're going to do some emotional versioning for this release and call it a patch.

[raman325]

you are ahead of the game 🙂 there's a lot of support that still needs to be added before it's available in HA. As far as I can tell, this doesn't actually give us any benefit aside from being futureproofed for future changes, but we want to be on the latest and greatest anyway and if there's a standardized model even better.