Unsupported Integrations

Integrations That Cannot Currently Be Supported

Many lock integrations don't yet have Lock Code Manager providers, but could potentially be added in the future (see Adding a Provider). The integrations listed on this page are different - they cannot be supported due to fundamental limitations in their underlying libraries or protocols.

The Home Assistant lock platform only requires lock/unlock operations. User code management is optional, and these integrations don't expose it.

ESPHome

Status: Not possible

The ESPHome lock component only supports lock/unlock/open commands. There is no API for managing user codes on keypads.

What would need to change: ESPHome would need to implement user code management in its firmware and expose it through the ESPHome API. This would be a significant feature addition to the ESPHome project.

Yale / August

Status: Not possible

Four integrations exist for Yale/August locks:

Integration	Library	Notes
august	yalexs	Can READ PINs but cannot create/update/delete them
yale	yalexs	Same library as august - can READ PINs but cannot manage them
yalexs_ble	yalexs-ble	Only supports lock/unlock/securemode via Bluetooth
yale_smart_alarm	yalesmartalarmclient	Can use PIN to unlock, but cannot manage PINs

The yalexs library is the most promising - it has an async_get_pins() method that returns full PIN information including slot numbers, codes, user names, and access schedules. However, there are no methods to create, update, or delete PINs.

What would need to change: The yalexs library would need to add PIN management methods. This likely requires reverse-engineering August's undocumented API endpoints for PIN creation and deletion.

Want to Help?

If you're interested in adding support for one of these integrations, the blocker is typically the underlying Python library - not Lock Code Manager itself. Contributing user code management features to those upstream libraries would enable LCM support.

• ESPHome: esphome/esphome
• Yale/August: bdraco/yalexs