-
Notifications
You must be signed in to change notification settings - Fork 116
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
Schlage Connect Door Lock - Manual operations do not update state in UI #433
Comments
What happens if you lock the door lock in the UI, then wait 10 seconds and click the button to lock again? Does the icon/state then update? |
Locking/unlocking the door in the UI (smarthome only - the lock doesn't show up in the expert UI due to some issue with that UI) works fine. If I click the lock or unlock icons the lock operates and the state is reflected correctly. It is the manual operation by hand (and subsequent auto-lock) of the lock which does not update state in the UI. I see the zwave "event" in the z-way-server.log (manual unlock pasted below), but am guessing the z-way-server is not listening? I also want to say this used to work in 2.2, but can't be 100% sure. [2017-04-16 09:53:59.959] [D] [zway] RECEIVED: ( 01 08 00 04 00 3A 02 98 40 13 ) |
Sounds like it's the opposite of the problem I was having. Your lock is reporting state changes correctly for z-wave operations, but manual operations are not updating in the z-way server. From your log output of the manual operation, it looks like the lock is sending out an alarm event only (command class 113). You could try using the Niffler app which should see this and then will request / Get() a status update from the lock. |
You should try to add in ZWave/index.js in Alarm section a binding to type 6, event 2 and do DoorLock.Get() from that place. It is quite hard to write this in blind. We can try it, but you will need to test it anyway on your side. We do not have such a lock to perform tests |
@PoltoS Just to make sure I am in the correct location, this would be /opt/z-way-server/automation/modules/ZWave/index.js. Correct? About what line# are you talking about? Looks like around 4400. If you can suggest specific code to add to what line(s), I would be grateful... thanks. |
@PoltoS would you suggest specific code to try? I am happy to test. Thank you |
Reading the thread, and the suggestions to use Niffler. Niffler stopped working for me after upgrading from 2.2.5 to 2.3.0. |
I think I had a problem with niffler as well after that. I stopped using it and use the periodic switch poller in the homeautomation app section of Z-Way now and it works fine, but only for switches - not for locks though. I would be happy to try adding code but am not sure what/where to add it... |
Hi,
Problem device is Schlage Connect model BE469NX with FW Ver MAIN_7.1 - running Razberry z-way (ZW0500) with FW Ver 2.3.1 (UI 1.7.0/Expert 1.3.0), on an RPI3 running Jessie-lite.
Issue is manual and auto-relock operations do not seem to communicate status back to z-way-server. Log files shows reports received and does not show errors for these operations, they just dont send status updates so UI doesn't reflect state change.
z-way-server log attached. First operation is unlocking via z-way smarthome, then locking with z-way, then a manual unlock and finally manual (auto-relock).
Thank you.
z-way-server.log.txt
The text was updated successfully, but these errors were encountered: