New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please check that doorlock vDev is updated on lock manual operation #426

PoltoS opened this Issue Mar 6, 2017 · 4 comments


None yet
4 participants

This comment has been minimized.

kvolden commented Mar 7, 2017

I'm the one who started the thread, and would like to add that the vDev doesn't update it's status to open even when I use the web interface or api to open the lock. The actual physical lock turns and opens like expected, but the vDev status remains at "close".

Logs for both use cases are in the thread.


This comment has been minimized.


PoltoS commented Mar 28, 2017

Looks fixed (in v2.3.1). Please confirm:


This comment has been minimized.

kvolden commented Mar 29, 2017

It works again in version 2.3.1.

@PoltoS PoltoS closed this Mar 29, 2017


This comment has been minimized.

ToddGreenfield commented Apr 2, 2017

Hi. This is not working for me. I just updated to 2.3.1 and while this update solved the problem of not showing a status in the smarthome UI (which it does now) SphtKr/homebridge-zway#103, the new problem is when the lock auto-locks or I manually change lock states it does not update the smarthome UI. Additionally, in the expert UI I no longer see the lock in the Control/Locks section. It just disappeared from that screen, but the lock still shows on the others as well as the smarthome UI.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment