This is in relation to zwave locks. I’ve been working with HA for a few months now and love whats been done so far and the flexibility.
My problem is that when building a custom interface to add and remove lock codes from locks there are a few things missing.
- The getlockcode service is not useful because you cannot actually get the code that is added to the lock as it comes back encrypted etc…
- You cannot verify a code has been added to the lock even though Zwave does respond with a success HA does not seem to capture that event.
- Locks like Schlage have to follow a regex type pattern i.e. first 4 - 6 digits cannot be the same as an existing code on the lock. If we cant get the lock code no method to compare or match against regex.
- If we could store secrets via node-red or templating or if we could hash input_number variables I could simply store lock codes within HA as a secret and grab those values to perform compares on and store the value in HA after being added to the lock. I’m not comfortable storing a door lock code in HA as a input_number as it stands.