search

bropat / eufy-security-ws

Small server wrapper around eufy-security-client library to access it via a WebSocket.
MIT License
176 stars 26 forks source link

[Bug]: T8520 Lock not responding to commands, won't lock/unlock #209

Closed graymccord closed 9 months ago

graymccord commented 1 year ago

Version

1.4.1

Node version

?

Operating System type

Other

Operating system version

HAOS 10.1

Describe the bug

LAtest HAOS and environment installed, including update to eufy-security addon to 1.4.1 Problem is that the lock shows up in the integration, but issueing the lock and unlock commands do not cause the lock to activate. HA does show acurate lock status but can't change it.

To reproduce

  1. Install addon and integration
  2. go to lock card in HA and click lock or unlock
  3. nothing happens

Screenshots & Logfiles

2023-05-07 20:44:07.162 DEBUG [Station.lockDevice] Sending lock device command to station T8520Q20214416E1 for device T8520Q20214416E1 with value: false 2023-05-07 20:44:07.169 DEBUG [Station.lockDevice] Locking/unlocking device... { station: 'T8520Q20214416E1', device: 'T8520Q20214416E1', admin_user_id: '6fcd92863306f17998cd3ef910daadda537bc6bf', payload: { commandType: 1350, value: '{"key":"03fcd6368765df53533dd7e77e78244f78e8e7ac3ad7b11219f1c8b3ed54f14041d73f834b2b91ebe52c52cd633d5fe4ec58ea5fc298be91c3f62f29b4c92c23a14b1f4b0f9ea2a358e7719b20e9e4d913483769ae6324fa2b41e5140156eec9ba37bc3dd0ec181a13ea9c364ab74fe43664a6ed4d5eb1d9a832200d60ab5ec4cd","account_id":"6fcd92863306f17998cd3ef910daadda537bc6bf","cmd":1961,"mChannel":0,"mValue3":0,"payload":"mPckkeJMfQqwrM10jhdK/Ny/NKynkfe46oSVCeO0E1pxS4+cUcY2L4CDP9qztrMU+4v1KBPm7/tiN2lrwOFLxTXCLALyfMUCLi8hzUEw9U9zt+V8ppdpgTFobI75dFC3829TqUM8eP3hjtU6mR/Olt7ISUksxkF69NyYl2+30t8\u003d"}', channel: 0, aesKey: '2FE8CC8606D3920437A2047D06E691D5' }, nestedPayload: { shortUserId: '0004', slOperation: 0, userId: '6fcd92863306f17998cd3ef910daadda537bc6bf', userName: '', seq_num: 892 } } 2023-05-07 20:44:08.958 DEBUG [Station.lockDevice] Sending lock device command to station T8520Q20214416E1 for device T8520Q20214416E1 with value: false 2023-05-07 20:44:08.965 DEBUG [Station.lockDevice] Locking/unlocking device... { station: 'T8520Q20214416E1', device: 'T8520Q20214416E1', admin_user_id: '6fcd92863306f17998cd3ef910daadda537bc6bf', payload: { commandType: 1350, value: '{"key":"02a58c00c4da55c725b8e3dba56ddef9f1a7953beb3b2fb2f2ddd05ed213b21ed016e657a9b73a437943411b33644d0f62e23a770d47f061069c99fee96b913fa6e31ac9822031785b5b7c9d29372898f47d1cfa8f661038a1cddf0840e3e8772f2158bed4b9e4b6e847b703c4936ff75a3bf5154281c781314ece30dc11cdd07a","account_id":"6fcd92863306f17998cd3ef910daadda537bc6bf","cmd":1961,"mChannel":0,"mValue3":0,"payload":"a3PLHo5Dccm9B/DY+k4GrdVZjkLvV+K+8S6CYBMRILOM3x1vHdxek7swqD8RJTB1y7yqa/ohuN5vCLTA8q/XaT44cr4M3ofpyzgq/DRz+FW1uPigNgblgI1q4Npi78gpb0AJEN9CilC45exuBEsgHY9wIq2dIkNE2uebj0t0Kew\u003d"}', channel: 0, aesKey: 'CE43DC2C422A046BF04168C90AF222C8' }, nestedPayload: { shortUserId: '0004', slOperation: 0, userId: '6fcd92863306f17998cd3ef910daadda537bc6bf', userName: '', seq_num: 893 } } 2023-05-07 20:44:10.228 DEBUG [Station.lockDevice] Sending lock device command to station T8520Q20214416E1 for device T8520Q20214416E1 with value: true 2023-05-07 20:44:10.235 DEBUG [Station.lockDevice] Locking/unlocking device... { station: 'T8520Q20214416E1', device: 'T8520Q20214416E1', admin_user_id: '6fcd92863306f17998cd3ef910daadda537bc6bf', payload: { commandType: 1350, value: '{"key":"02f0616db2be9dc2a945d8d1eff888c59fae0fefa801916e9a93073e1bb45f33b41f5a20066f36c3e1d9c47ba5170d30f86fdfc00596eaaa0c928a3d23c8dfc91ee2b0dccc699267a74bf1b83d35c8189c6b717bf616da07de85940ec586377f68b7af1826e7a6b68f4712b82d591d06cdb6657894872d4103aaa7a40b1b693b8c","account_id":"6fcd92863306f17998cd3ef910daadda537bc6bf","cmd":1961,"mChannel":0,"mValue3":0,"payload":"2e8M1h3Ps6Y2iIPtLNo62/jCbXxqEEgJPOdI/ZwNSrBTTSOAi5yn+sXVgYgHwlGxwPkTIyNHW6cx1kUFUpah7z8nRsT8nDBcn2DqLHBEDvnBeiNTezx3dnCSFGXxRlsw/GrjpPhdu2M7KWR085K3O1rGeMkcb0DMGmVC4yVTqrM\u003d"}', channel: 0, aesKey: 'B90C766389CA0040A386AD5F92203772' }, nestedPayload: { shortUserId: '0004', slOperation: 1, userId: '6fcd92863306f17998cd3ef910daadda537bc6bf', userName: '', seq_num: 894 } } 2023-05-07 20:44:11.252 DEBUG [Station.lockDevice] Sending lock device command to station T8520Q20214416E1 for device T8520Q20214416E1 with value: true 2023-05-07 20:44:11.259 DEBUG [Station.lockDevice] Locking/unlocking device... { station: 'T8520Q20214416E1', device: 'T8520Q20214416E1', admin_user_id: '6fcd92863306f17998cd3ef910daadda537bc6bf', payload: { commandType: 1350, value: '{"key":"03e0e21e896fd1203650abe899a7a8b93fd0ed91304878c3c9babd552cf63d5480848bb2a28c169d1b7d278438f21fe1a2425d1f64327f7a08869893dbae82501873d37fe3a66eae2e3322c8ea90c1e7fd712d7d8689f2d0ebbb2799d37c10de3329fd783885695384d6d3994b3910fcba79f5604752424b9d4099c15213d43769","account_id":"6fcd92863306f17998cd3ef910daadda537bc6bf","cmd":1961,"mChannel":0,"mValue3":0,"payload":"uNq1pxBESCIcsMlFASID6Zvbrett1ygDKbioU+uHnSGAubAmkL4/MEyDqplxaHSdfKWgMEWQRRR7x6YdhCH1hiAw0hLWiXdydWl2eUo4zty4usi3/4xhhUqKE3c5cErwHzXgFhxo+18j7LjNZQ+8ewUuk+kcvkjojrv29hwqLZE\u003d"}', channel: 0, aesKey: '25076810A77DC71054728D5E4B67D1E9' }, nestedPayload: { shortUserId: '0004', slOperation: 1, userId: '6fcd92863306f17998cd3ef910daadda537bc6bf', userName: '', seq_num: 895 } }

Additional context

At one point, this did work. I had HAOS 9.5 running and when I updated to HAoS10, by OdroidN2+ bricked and I had to perform a clean install of HA. Its never worked since.

bryan292 commented 1 year ago

having this issue as well

alexeiw123 commented 1 year ago

Same here.

If I use the eufy-security-ws add-on, then I can't use the lock/unlock function. If I use the older Eufy Security add-on (https://github.com/fuatakgun/eufy_security_addon) then the lock works fine, but the most recent version of this integration doesn't work (v6.3.0)

image

fuatakgun commented 1 year ago

@alexeiw123 , so it is broken after 1.3.0 version, to be precise

alexeiw123 commented 1 year ago

@alexeiw123 , so it is broken after 1.3.0 version, to be precise

Most likely yes. I didn't change to the bropat add-on until very recently, so not sure which specific version it broke on. Not sure if the fix is needed in the integration or add-on. Let me know if you want me to share my lock with you (and a dummy's guide of how)

alexeiw123 commented 1 year ago

@bropat I can share my T8520 lock with you if it would help in troubleshooting and fixing this issue.

alexeiw123 commented 1 year ago

OK I have found a workaround that gets the lock working again using the latest add-on by @bropat and latest integration by @fuatakgun. I noticed this issue and comment: https://github.com/bropat/hassio-eufy-security-ws/issues/16 and confirmed that this works for me.

Quite simply, in the add-on, add the yaml:

stations:
  - serial_number: T8520Q##########
    ip_address: 192.168.1.##

I assigned a static lease on that ip to make sure it doesn't change. I have no idea why but the lock/unlock service doesn't work unless you assign the station manually.

bropat commented 1 year ago

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 ;)

alexeiw123 commented 1 year ago

Hi @bropat - this behaviour has returned for me, despite having station added in configuration.

All I'm seeing in add-on logs is this (I tried twice):

2023-08-27 22:34:26.524  INFO  Connected to station T8520Q# on host 192.168.1.33 and port 24727 
2023-08-27 22:34:56.822  INFO  Initiated closing of connection to station T8520Q#for saving battery. 
2023-08-27 22:34:56.826  INFO  Disconnected from station T8520Q#
2023-08-27 22:34:58.423  INFO  Connected to station T8520Q2# on host 192.168.1.33 and port 17159
2023-08-27 22:35:28.694  INFO  Initiated closing of connection to station T8520Q# for saving battery. 
2023-08-27 22:35:28.698  INFO  Disconnected from station T8520Q#

If there's a way to get more detailed logs from the add-on, I'm happy to help.

roozbehv commented 1 year ago

Same here, I reverted back to 1.6.2

alexeiw123 commented 1 year ago

Same here, I reverted back to 1.6.2

good pick-up that worked for me too. Luckily I still had the partial back-up, I'm not sure how to downgrade an add-on any other way. I had to reboot my home assistant hardware to get it working. Oddly, add-on and integration reload wasn't enough.

tismofied commented 1 year ago

I am having this exact same issue as OP. I did the stations modifications as @alexeiw123 suggested but didn't work for me. The unlock/lock buttons are unresponsive and I get the following errors in the log

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2023-08-28 13:37:24.012  INFO  Eufy Security server listening on host 0.0.0.0, port 3000 
2023-08-28 13:37:25.702  INFO  MQTT connection successfully established 
2023-08-28 13:37:25.750  INFO  Successfully registered to MQTT notifications for lock T8520**********
2023-08-28 13:37:27.057  INFO  Push notification connection closed 
2023-08-28 13:37:27.250  INFO  Push notification connection successfully established 
2023-08-28 13:37:32.445  INFO  Push notification connection successfully established 
2023-08-28 13:37:45.686  WARN Station T8520******** - Tried all hosts, no connection could be established 
2023-08-28 13:37:45.688  INFO  Timeout connecting to station T8520*******
9dnsb commented 9 months ago

Not working for me either

2023-11-24 20:27:57.529 INFO Eufy Security server listening on host 0.0.0.0, port 3000 2023-11-24 20:28:01.110 INFO MQTT connection successfully established 2023-11-24 20:28:01.160 INFO Successfully registered to MQTT notifications for lock 2023-11-24 20:28:01.163 INFO Successfully registered to MQTT notifications for lock 2023-11-24 20:28:04.318 INFO Connected to station on host 192.168.2.18 and port 23900 2023-11-24 20:28:04.326 INFO Connected to station on host 192.168.2.19 and port 23900 2023-11-24 20:28:12.634 INFO Push notification connection successfully established 2023-11-24 20:28:34.542 INFO Initiated closing of connection to station for saving battery. 2023-11-24 20:28:34.547 INFO Disconnected from station 2023-11-24 20:28:35.020 INFO Initiated closing of connection to station for saving battery. 2023-11-24 20:28:35.024 INFO Disconnected from station

kebel87 commented 9 months ago

Same problem here, unfortunately. My device is available to help!

nickmarko commented 9 months ago

Same here. I added an issue. However, I also saw elsewhere in a related issue that someone mentioned going to disabled entities and enabling the lock entity manually. Did that and it seems to be working now.

9dnsb commented 9 months ago

Same here. I added an issue. However, I also saw elsewhere in a related issue that someone mentioned going to disabled entities and enabling the lock entity manually. Did that and it seems to be working now.

Doing this has worked for me and fixed the issue

bropat commented 9 months ago

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 ;)

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