eufy-security-client
eufy-security-client copied to clipboard
bropat
[Question]: T8520 Firmware 1.3.8 Support in the near future?
Ask your question
My eufy T8520 smart lock was recently upgraded to he 1.3.8.0 firmware (unwillingly). I'm using the homeassistant integration, but noticed ever since the firmware upgrade the lock is unresponsive and continually logging an error: Tried all hosts, no connection could be established.
I also accidentally updated my T8520 to the latest firmware.. Surprisingly, I couldnt find a way to downgrade the firmware. Hi @bropat , let me know if you need access to my door lock. I can try my best to help you get the access. Thanks.
To debug the cause i need access to the device. Could you please share your device with me (i need admin rights):
- [email protected] (for EU)
- [email protected] (for US)
Thanks!
To debug the cause i need access to the device. Could you please share your device with me (i need admin rights):
- [email protected] (for EU)
- [email protected] (for US)
Thanks!
My account is in "Australia" region. Am I still be able to share it?
I also have this issue, below is my log with some text replaced with xxxxxx
2022-08-08 13:44:36.311 INFO Eufy Security server listening on host 0.0.0.0, port 3000
2022-08-08 13:44:41.600 INFO MQTT connection successfully established
2022-08-08 13:44:41.836 INFO Successfully registered to MQTT notifications for lock T8520xxxxxxx
2022-08-08 13:44:43.836 INFO Connected to station T8520xxxxxxxx on host xxxxxxxx and port xxxx
/usr/src/app/node_modules/eufy-security-client/build/http/station.js:315
return ((_a = this.rawStation.devices[0]) === null || _a === void 0 ? void 0 : _a.device_sn) === this.rawStation.station_sn;
^
TypeError: Cannot read properties of null (reading '0')
at Station.isIntegratedDevice (/usr/src/app/node_modules/eufy-security-client/build/http/station.js:315:50)
at EufySecurity.onStationCommandResult (/usr/src/app/node_modules/eufy-security-client/build/eufysecurity.js:1351:25)
at Station.
To debug the cause i need access to the device. Could you please share your device with me (i need admin rights):
- [email protected] (for EU)
- [email protected] (for US)
Thanks!
My account is in "Australia" region. Am I still be able to share it?
Yeah.
@zuohaot
What is not working for you or what error are you getting?
I'm sorry Bropat. I think I was just dumb.. I thought 1.3.8.0 was not supported according the wiki page of known-working-device list. Now, I realised that my error was simply caused by low acoount permission rights..
Maybe we can update the list as 1.3.8.0 is supported now?
Anyhow, it is working now. Thanks for your excellent project!!
I can only get the baterry level... I'm not seeing the lock status. Are you seeing your lock status @zuohaot
I can only get the baterry level... I'm not seeing the lock status. Are you seeing your lock status @zuohaot
Yes, I can see the lock status, battery level as well as control the lock. I use Home Assistant with it btw. I also tried on Homebridge. It also worked.
Ahhh mine is working too now... Had to update to the latest version of the integration 🙂
@zuohaot
I have found an error in the emitting of the locked event. I will try to fix it tonight. Can you keep the sharing going until tonight so I can test it?
@zuohaot
I fixed the locked event in the develop branch (will be released in the next version). You can remove the device sharing.
Thanks!
@zuohaot
Maybe we can update the list as 1.3.8.0 is supported now?
I have also added the firmware version 1.3.8.0 as tested in the documentation.
Note: The column Tested version means what firmware version was tested by me and certified as working. It does not necessarily mean not supported. ;) Not supported is when you find a red cross under the column Support status.