T8520 Lock disabled after fresh installation

[skyler91]

Describe the bug

I performed a fresh install of the Integration. While my cameras, home base, and doorbell are working correctly, my T8520 lock is currently disabled. I see the device in HA, but the lock entity is only displayed under the "Diagnostic" section and is marked as disabled.

To reproduce

Steps to reproduce the behavior:

1. Fresh install Eufy integration
2. See that lock entity is disabled

Expected behavior

Lock entity should be enabled, report status, and able to be toggled.

Additional information

• Home Assistant Installation Type (OS - Supvervised - Core): Home Assistant Container
• Home Assistant Core Version: core-2024.12.0
• Eufy Security Add-on Version: latest (sha256:8794ee5090675e7fe3a62ff021e7bec67dce5fdb2f8b18e6d100df1979726614)
• Eufy Security Integration Version: Checked out from git repo master branch on 12/4/2024
• Using go2rtc Add-on or webrtc custom integration with integrated go2rtc: go2rtc

Hardware Information;
Eufy Lock T8520

• Debug Logs from Home Assistant:
  Only Eufy related message is:

2024-12-04 13:19:19.533 DEBUG (MainThread) [custom_components.eufy_security.eufy_security_api] _on_message - {'type': 'event', 'event': {'source': 'station', 'event': 'disconnected', 'serialNumber': 'T8520Q2021370C9D'}}

• Logs from Eufy Security Add-on (either from Add-ons page of Home Assistant or Docker output):

SECURITY WARNING: Reverting CVE-2023-46809: Marvin attack on PKCS#1 padding
2024-12-04 21:18:43.831 INFO    eufy-security-ws        Eufy Security server listening on host 0.0.0.0, port 3000
2024-12-04 21:18:47.143 INFO    eufy-security-ws:eufy-security-client   [http] [Station.onConnect] Connected to station T8424N1021280BC5 on host 192.168.68.57 and port 17227
2024-12-04 21:18:47.405 INFO    eufy-security-ws:eufy-security-client   [http] [Station.onConnect] Connected to station T8010P13202729E9 on host 192.168.68.50 and port 15783
2024-12-04 21:18:48.744 INFO    eufy-security-ws:eufy-security-client   [main] Push notification connection successfully established
2024-12-04 21:18:49.266 INFO    eufy-security-ws:eufy-security-client   [http] [Station.onConnect] Connected to station T8520Q2021370C9D on host 192.168.68.62 and port 25826
2024-12-04 21:18:52.084 INFO    eufy-security-ws:eufy-security-client   [main] MQTT connection successfully established
2024-12-04 21:18:52.176 ERROR   eufy-security-ws:eufy-security-client   [mqtt] Subscribe error for lock T8520Q2021370C9D {
  error: {
    cause: undefined,
    message: 'Error: Subscribe error: Unspecified error',
    context: undefined,
    stacktrace: 'Error: Subscribe error: Unspecified error\n' +
      '    at handleAck (/usr/src/app/node_modules/mqtt/build/lib/handlers/ack.js:101:27)\n' +
      '    at handle (/usr/src/app/node_modules/mqtt/build/lib/handlers/index.js:36:31)\n' +
      '    at work (/usr/src/app/node_modules/mqtt/build/lib/client.js:227:40)\n' +
      '    at writable._write (/usr/src/app/node_modules/mqtt/build/lib/client.js:252:13)\n' +
      '    at writeOrBuffer (/usr/src/app/node_modules/readable-stream/lib/internal/streams/writable.js:334:12)\n' +
      '    at _write (/usr/src/app/node_modules/readable-stream/lib/internal/streams/writable.js:283:10)\n' +
      '    at Writable.write (/usr/src/app/node_modules/readable-stream/lib/internal/streams/writable.js:286:10)\n' +
      '    at TLSSocket.ondata (node:internal/streams/readable:1007:22)\n' +
      '    at TLSSocket.emit (node:events:519:28)\n' +
      '    at TLSSocket.emit (node:domain:488:12)'
  },
  deviceSN: 'T8520Q2021370C9D'
}
2024-12-04 21:18:52.179 INFO    eufy-security-ws:eufy-security-client   [mqtt] Successfully registered to MQTT notifications for lock T8520Q2021370C9D
2024-12-04 21:19:19.530 INFO    eufy-security-ws:eufy-security-client   [p2p] [Timeout._onTimeout] Initiated closing of connection to station T8520Q2021370C9D for saving battery.
2024-12-04 21:19:19.531 INFO    eufy-security-ws:eufy-security-client   [http] [Station.onDisconnect] Disconnected from station T8520Q2021370C9D

• Would you share your device with me in case further debugging required? (Yes/No):
  Yes

Additional context

I have been using this integration for quite some time without issue, albeit with a much older version. I am in the process of moving my HA installation to a new server and wanted to reinstall the latest integration with it and ran into this issue.

[HartR]

same issue for me, except for the T8502

[asan2020]

Looks like I have the same issue with T8531 posted 1263
Does this integration need Home Base? I currently do not have a Home base