I use ZHA, after you set up the lock through the wyze gateway and calibrate it, you just start the joining process via HA and then hold the button on the lock down for like 3 seconds until it starts blinking green I think.
The only thing that will work is lock/unlock at this point wyze hasn’t been forthcoming who’s what all the manufacturer specific clusters are sending so it will take some time before it is all decoded and usable. Not sure how night of a priority it is for the zha devs. (Or z2m or deconz).
The more people who ask wyze for info the better. So far they have said they have no interest in implementing third party support. Despite the request just for information about the messages sent.
I don’t have Tradfri gateway, I use the ZHA integration in HA so no need for other zigbee hubs. The Tradfri gateway controls what can and can’t work with it.
Unfortunately I don’t know enough about the tradfri gateway to know if it would work or not. I kind of doubt it. The device is only working in sort of an alpha stage with HA and ZHA now. Wyze is not sharing details on how it communicates fully.
there is a quirk in development that works, however you have to customize the quirk per installation as the locks send data specific to each lock. Until there is a calibration step native in HA, the quirk will need to manually edited before it will work.
I honestly do not have it in use. I’ve tested the quirk that I linked above and it works but has to be manually updated. I run HA Supervised so I have to had that quirk back every update which I have not done. The lock does stay online in my zigbee mesh, and I can trigger a lock/unlock without the quirk and it works consistently, it just does not report the the states.
Thanks for the response. How do I manually install/update those ZHA quirks? I’m running HA container, didn’t find the instruction from the github page.
you have to get a command line inside the docker container. With HA Supervised, I use portainer, and am able to use that to get a command line. I put the quirk files in a directory in my config directory, then copy them over to the quirks folder.
in the HA docker container they are here: /usr/local/lib/python3.7/site-packages/zhaquirks/
For this quirk you have to turn on debug logging and and watch the logs then edit the quirk to match the responses your lock gives. It is far from straight forward, it has been a while since I worked with the dev and he helped me get it working.
I believe I understand what needs to be done to modify the quirk to get it working properly. What i’m confused about is how do you obtain the data that’s needed? Could you please shed some light on this for me? I’m guessing you need to use a sniffer or a logger of some sort but i have no clue how that works.
It’s been a long time since I did this, but you’ll want to install the quirk as is, then turn on debug logging for zigpy.
Trigger all the different states (manual lock/unlock, app lock/unlock, open/closed)
Do them all a few time the lock will send some long codes for each which should be in the logs. I believe the quirk will spit out some useful logging to help guide you to the values needed. I’ll try and double check later tonight.
Thanks, this was helpful but I must still be doing something wrong. Do i need to use zigbee2mqtt or something? Currently using ZHA and my logs are not spitting out anything that resembles the data above.
So i installed the quirk a while back using Portainer but i’m not getting the same kind of output in my logs when i use the lock. Not sure where I went wrong, here is what i’m seeing in my logs:
