TTLock Integration

[samuellazea]

Hello,

First of all I want to say really nice work on the integration. It's appreciated.
I am wondering, is there any thinking of extending the keymaster a bit more?
Like with ttlock https://github.com/jbergler/hass-ttlock.
This would broader the use of the integration and will help people have more flexibility

For me I am using the ttlock integration standalone and I also use the https://github.com/tykeal/homeassistant-rental-control that makes use of keymaster also.

Thank you in advance and it would be greatly appreciated

[tykeal]

v0.1.3 now supports the ability to create new lock providers and not just ZWave based locks. For instance: #578 is the first proposed non-zwave lock we've got coming. I do not have a TTLock to do testing or development against. So I'm not willing to write such a provider when I can't fully test it. You're welcome to raise a PR based on the work from #578 to get TTLocks working as well.

There will also be a new provider for Schlage WiFi locks coming after HA 2026.4.0 releases as that version of HA will have support for code management in the schlage integration that does not exist yet. I already have the feature prepped, but without the new HA available, there's no reason to raise the PR.

Things to think about:

• Does the lock / integration use "slots" like Zwave does? Keymaster is designed around this slot concept
• If it does not use slots, then can the named PINs have spaces and other characters such as [, ], or : in the name? If so, then the virtual slot setup that the Akuvox and Schlage providers will both use can be similarly done
• Do the "slots" allow for easy renaming via the management integration? Yes? Look at the Akuvox provider. No? Look at the Schlage provider when it is available (implements delete/add for modify operations as the schlage integration does not have a modify action)