[Bug]: T-8520 WiFi Lock not acting on button presses

[graymccord]

Client version

2023.4.6

Node version

unknown

Operating System type

Other

Operating system version

HAOS 10.1

Describe the bug

HA shows and updates status of lock, but does not respond to lock / unlock commands. There is no info in the logs after I activate the lock.T-8520 lock with 1.4.2.8 firmware. Also, the entities related to the lock have apparently changed from prior versions. At one time, there were temperature and maybe other data, but all gone now. Just lock status and battery percentage remain.

To reproduce

1. check lock status, including battery, in dashboard
2. press lock or unlock button to chage state
3. nothing happens

Screenshots & Logfiles

No response

Additional context

No response

[graymccord]

Some log info. from debug mode.
{
deviceSN: 'T8520Q20214416E1',
properties: {
name: 'Front Door',
model: 'T8520',
serialNumber: 'T8520Q20214416E1',
type: 51,
hardwareVersion: 'P3',
softwareVersion: '1.4.2.8',
stationSerialNumber: 'T8520Q20214416E1',
autoLockTimer: 180,
autoLockScheduleStartTime: '21:00',
autoLockScheduleEndTime: '06:00',
wrongTryAttempts: 5,
wrongTryLockdownTime: 180,
sound: 1,
wrongTryProtection: true,
notification: true,
autoLock: false,
autoLockSchedule: false,
notificationUnlocked: true,
notificationLocked: true,
oneTouchLocking: true,
lockStatus: 3,
locked: false,
battery: 67,
scramblePasscode: false
}
}
2023-05-02 22:24:06.171 DEBUG [PushClient.sendHeartbeat] Sending heartbeat... 18
2023-05-02 22:24:06.173 DEBUG [PushClient.buildHeartbeatPingRequest] heartbeatPingRequest
{
last_stream_id_received: 18
}
2023-05-02 22:24:06.208 DEBUG [PushClient.handleHeartbeatAck] Heartbeat acknowledge
{
tag: 1,
object: {
lastStreamIdReceived: 11
}
}
2023-05-02 22:24:32.159 DEBUG [Station.lockDevice] Sending lock device command to station T8520Q20214416E1 for device T8520Q20214416E1 with value: true
2023-05-02 22:24:32.168 DEBUG [Station.lockDevice] Locking/unlocking device...
{
station: 'T8520Q20214416E1',
device: 'T8520Q20214416E1',
admin_user_id: '6fcd92863306f17998cd3ef910daadda537bc6bf',
payload: {
commandType: 1350,
value: '{"key":"031d19998a63abb5dc2c0c76f469ea2a42605e2388de4c5b10beedcdcb922abd5a2793592015db2934a2a97740469aaa6451be33c5f887cd0de6b869faf597d62cc146122f1772b955a1fdba2358c002b29abdbbc8ca1f5b7f7113298906d2f415687e338fc1da72f9a1e689803a7471687f913df98f6975f4487a74aef4ebcab3","account_id":"6fcd92863306f17998cd3ef910daadda537bc6bf","cmd":1961,"mChannel":0,"mValue3":0,"payload":"Ypr/gr1sdkvPKw05PPLu3JPVIrvuiioWeHRkGjZtVGxv1mbjWnJMla7SnYgCAHQAE01H2zEoriz0Iwysx5yBTOWkxacQXlar0Y1x97x0ix2hqMnboVCYeZ1P0w9nHuuDlCH7EbcVmDGGEC7EWeOU0gKHrF6k9NW0eCJ9fFu6L08\u003d"}',
channel: 0,
aesKey: 'E65287A336AD53582BB1CD6593441B7A'
},
nestedPayload: {
shortUserId: '0004',
slOperation: 1,
userId: '6fcd92863306f17998cd3ef910daadda537bc6bf',
userName: '',
seq_num: 176
}

[Dataninja126]

I'm having the same problem with the same lock

[chicknlil]

Also having the same issue with this device. I used to be able to lock and unlock this device from HA and no longer am able to do so, but like OP, the state does change.

[alexeiw123]

This is the same problem I'm seeing and listed here: bropat/eufy-security-ws#209
I'm really not sure which repo is the most appropriate to provide details on. As mentioned on the other, happy to share my device.

Have noticed that the lock works as intended if you use the deprecated https://github.com/fuatakgun/eufy_security_addon add-on (v1.3.0) but you also need to use v6.2.0 or earlier of the integration (available in HACS).

[alexeiw123]

workaround here: bropat/eufy-security-ws#209 (comment)

[bropat]

The cloud discovery of the devices does not work 100%. One part has not yet been reverse engineered correctly.
As a workaround, the static IP configuration addressed by @alexeiw123 was implemented.
So at the moment the proposed solution from @alexeiw123 is the best ;)

[bropat]

The cloud discovery part should now work reliably (from version 3.0.0).