LordNex
commented
2 years ago Don’t know if you knew this but you can use the lock without this integration. You can use Zigbee Home Automation(ZHA), just hit the pair button on the lock again while your searching for Zigbee devices. Of course you need a Zigbee hub or multis stick. I have the Nortek HUBZ1 I think it’s the model. But it’ll do both ZHA and ZWave. Just make sure you use a usb extender cable to get the dongle as far away from any other radio interference.
I originally chipped in to have Josh integrate the lock. But with my crappy sat internet it’s just not responsive enough. So I went with Zigbee. I’m supposed to be getting Starlink in a few months though so I’ll reevaluate it then.
On Jan 1, 2022, at 11:27 AM, dave-dube @.***> wrote:
When clicking LOCK or UNLOCK button, the lock status is updated pretty close to the right status, but few seconds later, the status is back to the previous state, and again +-5-6 seconds later the state is back to the correct status...
Here is an example: 1- the lock state = LOCKED 2- i click UNLOCK button 3- the state change to UNLOCKED (perfect) 4- and 2-3 seconds later, the state change back to LOCKED (hum.. wrong) 5- and 5-6 second later again, the state change to UNLOCKED (good now)
So its like the Integration is reading state from Wyze server too rapidly... and getting the old state just before the new state reach the Wyze server. Maybe the integration should wait maybe few second before calling the API, to make sure the server has the new state ? just basic idea...
I'm actually running the latest HA and WyzeAPI Integration. And my lock is configured to use the standard Wyze gateway. So i can use HA and Wyze App together.
** Sometime, (maybe 1/10) the state behave properly. meaning i dont have the "step 4"... Probably come from the fact that the state on the server is update between 2 API call event. i don't know what is the API polling frequency
— Reply to this email directly, view it on GitHubhttps://github.com/JoshuaMulliken/ha-wyzeapi/issues/322, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACGXNJAUDY7QMW2WTNBE2Q3UT42P7ANCNFSM5LCVYUKA. You are receiving this because you are subscribed to this thread.Message ID: @.***>
dave-dube
SecKatie
When clicking LOCK or UNLOCK button, the lock status is updated pretty close to the right status, but few seconds later, the status is back to the previous state, and again +-5-6 seconds later the state is back to the correct status...
Here is an example: 1- the lock state = LOCKED 2- i click UNLOCK button 3- the state change to UNLOCKED (perfect) 4- and 2-3 seconds later, the state change back to LOCKED (hum.. wrong) 5- and 5-6 second later again, the state change to UNLOCKED (good now)
So its like the Integration is reading state from Wyze server too rapidly... and getting the old state just before the new state reach the Wyze server. Maybe the integration should wait maybe few second before calling the API, to make sure the server has the new state ? just basic idea...
I'm actually running the latest HA and WyzeAPI Integration. And my lock is configured to use the standard Wyze gateway. So i can use HA and Wyze App together.
** Sometime, (maybe 1/10) the state behave properly. meaning i dont have the "step 4"... Probably come from the fact that the state on the server is update between 2 API call event. i don't know what is the API polling frequency