Replies: 3 comments 2 replies
-
In general, security locks don't provide simple remote lock/unlock functionality. There is maybe a way to remotely unlock using a passcode, but the way to do that is not well understood so not implemented by this integration. Adding new credentials is likewise not well understood, and not implemented. Other config options that the lock offers can generally be made available, and the status - what method and credential id was used to open the lock should be available. |
Beta Was this translation helpful? Give feedback.
-
So if configuration changes are impossible, is the only point so that you can base triggers off the sensor data? |
Beta Was this translation helpful? Give feedback.
-
I haven't seen this data anywhere on my stuff.
…-------- Original Message --------
On 1/15/25 5:42 PM, Jason Rumney wrote:
If available, it is in the changed_by attribute of the lock, which normally will show in the LogBook.
—
Reply to this email directly, [view it on GitHub](#2110 (reply in thread)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ADS37XALYX2CXUKFI2RTZO32K3P33AVCNFSM6AAAAABK2S7UH6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBUHA2DMNI).
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
I was just curious as to what features we should be seeing when integrating locks. I have some elcheapo fingerprint door handle lock, and I tried various devices that were listed, and really all I see is the status. There's no control/configuration other than lock/unlock, which doesn't work due to read-only error. Despite changing the lock to 'controllable' in the Tuya cloud item.
Are we supposed to be able to program codes/users/fingerprints, or anything else? IE, am I just using the wrong device type, or is that the full functionality to expect?
Thanks!
Beta Was this translation helpful? Give feedback.
All reactions