Has anyone managed to get full function of the smart lock on smartthings app?
Bump Bump Bump
This one, right? The retailer says âWi-Fiâ but itâs using zigbee.
https://www.gearbest.com/access-control/pp_1142172.html
Tagging @RBoy
1 Like
I believe this is a WiFi lock with an additional ZigBee module. Did you try using using the ZigBee Lock DTH for it after pairing it? (you will likely need to assign the DTH manually after pairing it)
1 Like
2018 Xiaomi Mijia Aqara S2 Smart Fingerprint Door Lock Digital Touch Screen Keyless Lock Smart Home App Control With Screw Kit
https://s.click.aliexpress.com/e/FPjGlDW
Talking about this lock, no wifi. Just zigbee
1 Like
Whatâs the issue youâre facing?
theres no device handler, ive paired it as a thing and all it shows is âplease waitâ
That means it didnât detect which handler to use (which is normal). Go to your IDE, open My Devices -> Locate âThingâ, click on it, edit the the Device type, select Z-Wave Lock and then scroll down and click update. Now see if it works.
Its a Zigbee lock. and it eventually detected it as samsung 2015 TV, i manualy changed it to zigbee lock but theres no info shown for battery level or if its locked / unlocked
Probably doesnât use a standard zigbee profile like all the other Lumi/Aqara products.
What should i do in that case? Also smartthing shows * model: lumi.lock.acn02
Gotta write your own device handler or wait for someone else to write one.
Under My devices -> click on the device, copy and paste the Raw Description
Raw Description 01 0104 000A 02 0A 0000 0003 0001 0002 0005 0004 000A 0020 0101 0019 02 0019 000A
unlock/lock function does not work, and battery level sits at 0%
Okay so it looks like it may work based on the clusters.
Try this:
- Pair your lock
- Set your device handler to
ZigBee Lockin the ST IDE - Open the ST Classic app, open the device, click on the Gear Icon on the top right corner, then click on Save
Before doing step 3, open the IDE Live Logging and capture the output and copy paste the logs you see coming from the lock device (filter it from the top row).
This should force a reinitialization of the lock and subscribing to the necessary clusters and hopefully that should be enough to get it to work.
Still doesnt work and this is the live logging output
DeviceUpdated c107fa26-5bd8-4fb8-960d-b12a9621cf4f
a8ace6b1-2fe8-4cdb-9edd-ec795b990843 16:10:18: warn No connection!
a8ace6b1-2fe8-4cdb-9edd-ec795b990843 16:09:18: warn No connection!
eb02e431-07f0-429c-979b-7d6e54e80e07 16:07:37: trace ZigBee DTH - parseAttributeResponse() - ignoring attribute response
eb02e431-07f0-429c-979b-7d6e54e80e07 16:07:37: trace ZigBee DTH - Executing parseAttributeResponse() for device Door lock with description map:- [raw:6BDE01010128F6FF42104D4C2102150B0B0B0B0B0B0B0B0B0B0B, dni:6BDE, endpoint:01, cluster:0101, size:28, attrId:fff6, encoding:42, value:4D4C2102150B0B0B0B0B0B0B0B0B0B0B, isValidForDataType:true, clusterInt:257, attrInt:65526]
eb02e431-07f0-429c-979b-7d6e54e80e07 16:07:37: trace ZigBee DTH - Executing parse() for device Door lock
a8ace6b1-2fe8-4cdb-9edd-ec795b990843 16:07:18: warn No connection!
eb02e431-07f0-429c-979b-7d6e54e80e07 16:07:14: trace ZigBee DTH - parseAttributeResponse() - ignoring attribute response
eb02e431-07f0-429c-979b-7d6e54e80e07 16:07:14: trace ZigBee DTH - Executing parseAttributeResponse() for device Door lock with description map:- [raw:6BDE01010128F6FF42104D4C2101110B0B0B0B0B0B0B0B0B0B0B, dni:6BDE, endpoint:01, cluster:0101, size:28, attrId:fff6, encoding:42, value:4D4C2101110B0B0B0B0B0B0B0B0B0B0B, isValidForDataType:true, clusterInt:257, attrInt:65526]
eb02e431-07f0-429c-979b-7d6e54e80e07 16:07:14: trace ZigBee DTH - Executing parse() for device Door lock
eb02e431-07f0-429c-979b-7d6e54e80e07 16:06:43: trace ZigBee DTH - parseAttributeResponse() - ignoring attribute response
eb02e431-07f0-429c-979b-7d6e54e80e07 16:06:43: trace ZigBee DTH - Executing parseAttributeResponse() for device Door lock with description map:- [raw:6BDE01010128F6FF42104D4C210C000B0B0B0B0B0B0B0B0B0B0B, dni:6BDE, endpoint:01, cluster:0101, size:28, attrId:fff6, encoding:42, value:4D4C210C000B0B0B0B0B0B0B0B0B0B0B, isValidForDataType:true, clusterInt:257, attrInt:65526]
eb02e431-07f0-429c-979b-7d6e54e80e07 16:06:43: trace ZigBee DTH - Executing parse() for device Door lock
I Understand that i cant remote lock and unlock, just view status and it should be enough for my needs
So Iâm reading your chart correctly you had triggered three events on your lock and the logs are showing the corresponding entries for those events.
If so then the lock is reporting attribute id fff6 for your lock control cluster.That would be a custom attribute. Your lock doesnât seem to be using the standard attributes as defined by the zigbee specs.
Are you seeing anything else or is this all youâre seeing?
Also the no connection message doesnât seem to be coming from the lock DTH but a different app. Can you isolate which one from the log top bar?
Setting the Type to lock capability has started showing things i do with the lock in the app ârecentlyâ tab
but wont show anything in live logging
Thatâs weird, could be temp live logging issue. Hard to decode this from the recently tab, see if you can catch in live logging. Are you getting status updates now?
What do you mean setting the âtypeâ to lock capability?