Tuya integration Smart Lock - T12-Wifi-II / Card+PIN - remote unlock

[macxq]

The problem

There is not possibility remote unlock via HA only status is reported

What version of Home Assistant Core has the issue?

core-2023.5.0

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Tuya

Link to integration documentation on our website

https://www.home-assistant.io/integrations/tuya/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

• https://community.home-assistant.io/t/tuya-smart-life-door-locks/411396/17
• https://github.com/home-assistant/core/issues/68100

[home-assistant[bot]]

Hey there @tuya, @zlinoliver, @frenck, mind taking a look at this issue as it has been labeled with an integration (tuya) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of tuya can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign tuya Removes the current integration label and assignees on the issue, add the integration domain after the command.

_{^{(message by CodeOwnersMention)}}

---

tuya documentation tuya source _{^{(message by IssueLinks)}}

[macxq]

Any chance that this could be implemented ?

[hniehorster]

+1

[carsten12]

+1

[carsten12]

+1

[carsten12]

+1

[migrivas]

+1, It would be great to implement this feature, @tuya, @zlinoliver, @frenck 🙏🥺

[contact411]

+1 - Would definitely love to see this added

[macxq]

Any updates around that ;) is this even possible ?

[GigiGat]

+1

[Niek]

Remote unlock would be awesome. But also the status is not updating for me if manually unlocked. Is this a known issue?

[romanad]

+1

[Drac0fly]

+100000 up!

[Adavidebaba]

+100

[bgeza]

+1

[moryoav]

+1

[MOHAMMAD-QATANANI]

+1

[msazanov]

+1

[kennedyoliveira]

+1

[MikeTechnical]

+100

[macxq]

+1

[davidedipeppe]

+100

[LeGoFiN]

+1

[carsten12]

Some comments from my side, after I have checked different integrations:

• the code is most probably not buggy, the lock will open for a very short time only and you might not see it in the status tile
• the device is special in that sense that it does not have a status. It can only be polled
• when polled, it will send close_open_kit messages and then, on another dp, let's say unlock_password_kit, send the number of the password used to unlock base64 (and something like 000000010000 or 000000020000.
• when opening it with remote, it will send a code on unlock_remote_phone_kit
• the problem is that one would have to check the timecode of the messages to understand what exactly opened the lock, as there is more than password and phone remote opening possible. So you have to find the unlock_*_kit that fits to the timecode where open_close_kit is received to link them. HA is also not really prepared to get this information back. Maybe a sensor with enumerated state ca do the job, but I am not an expert.

As a workaround, I added (in the code, for this you need to copy the core code into custom_components and change it, means: add some code in binary_sensor.py and const.py) another binary_sensor and declared it as window. I defined to get "on" when password 1 code is set, so that it will report to a second sensor in HA whether the "window" is open or close. That fits perfectly to my use case, where one password is used to open and one to close a shutter for emergency/lazyness reasons with the lock placed directly next to the shutter.

If someone ever wants to update tuya core integration, please ask me for details. Other integrations should work as well, e.g. tuya-local but the device will not be created. I was not able to explain good enough to the code owner that the device only needs to be created as device22 in tinytuya (which is under the hood) and polled.

Hope this helps some people to continue to work on the integration of this device.

BR, Carsten.

[MarekPro1]

+1

[alsalvad]

+1

[macxq]

+1

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[limacohen]

+1 Still hoping for a better implementation of smart locks.

[Rezyyn]

+1 just hoping....