Don't want to hijack the thread but adding a +1 as someone else having issues with incorrect lock status reported by InControl. Thread reporting the behavior I am seeing (which admittedly is slightly different to that in this thread):
http://store.incontrolzwave.com/boards/topic/808/yale-real-living-lock-yrd220-zw-initial-state-on-server-startup
App shows wrong door lock status
- 109 Views
- Last Post 27 August 2015
Axial-User
posted this
26 August 2015
rscott
posted this
26 August 2015
Trying out 30 day trial pro version, have kwikset smartcode 914 set up and the free app for iphone, when I leave the house and come home the status always indicates unlocked, yet the door is locked, even if I close the app, re open, log into cloud on network or not, hit update, it will still show unlocked, i test the door so i know it really is locked, I have to hit LOCK then UNLOCK which sends the lock in to trying to lock first then it will unlock, that is a issue because I can never truly know if my door is locked or not while I am away.
Then I would like to have the log updated everytime the door is locked or unlocked, on unlocks I want the log file to tell me if a key was used, or what passcode was used. I figure this should be doable, another option would be to email me if someone tried to unlock the door with codes and failed.
Does the InControl server program on your PC show that it's unlocked as well? Can you perform an auto-configure on the lock (right click it from InControl) and report back the results with a screen shot of the window?
Axial-User
posted this
26 August 2015
Not sure if the PC shows locked or not, as I am outside when attempting to come in, I can come in another door I guess and check.
Axial-User
posted this
26 August 2015
Ok, so right now i see PC software shows unlocked, yet the door is locked.. not sure about the app, but certainly the status on PC is not showing correctly.. yet i can use it to lock and unlock.
rscott
posted this
26 August 2015
From what it seems, your lock isn't sending lock/unlock events to InControl like it should. Could you get it so the lock state is wrong (i.e, when InControl says it's unlocked but the lock is actually locked), then right click it and choose "Force poll" - wait about 30 seconds and let me know if it changes.
Also, In the screen shot you posted I see it shows a user code of "0" - If you set some user codes (right click the lock), are you able to see that user code number change when you type it into the lock?
f0ggy987
posted this
27 August 2015
Don't want to hijack the thread but adding a +1 as someone else having issues with incorrect lock status reported by InControl. Thread reporting the behavior I am seeing (which admittedly is slightly different to that in this thread):
http://store.incontrolzwave.com/boards/topic/808/yale-real-living-lock-yrd220-zw-initial-state-on-server-startup
