Omnipro z-wave lock status not correct, help

I have recently replaced a z-wave lock that failed. I am unable to get the lock status to show correctly on the Omnipro. I have 2 Kwikset lever locks and one Kwikset deadbolt. None of the locks show the correct status. The one lever lock shows locked all the time. I can run the unlock command (via Haiku) and the lock will unlock but it still shows locked on the Haiku app and the web interface. I also tried PC access and it shows the same that the lock is always in the lock state. The deadbolt is the same way it always shows locked. I created a buttons to send the lock and unlock commands (regardless of the state of the lock) and I can both lock and unlock the deadbolt, But it still shows that it is locked. I have verified that the batteries are good, but the main status LED is flashing red.
 
Help, I have deleted the entire setup and re-included all the z-wave devices and associated them with the Vizia RF+ serial module and it still does not work. I have installed brand new batteries in the one lock with no effect. I do see the Red led (next to the include button) turn red when the lock changes state. I am using the Leviton RF+ installer tool V 1.1.2.0 to program the network.

Was it all working correctly before the lock failed?

It worked correctly when first installed. I was having issue with the lock that failed, but that does not surprise me.

Update. I just unlocked the one door and the status changed to unlocked, even after I locked it. I tried to cycle it a number of times and it still shows unlocked. I unlocked via the keypad and locked it via the Omnipro system (z-wave). Could this be caused by intermittent communication ?

Waht is your firmware version?

I am using Omnipro version 3.13. I just updated to 3.14A and still the locks do not show the correct status. My deadbolt shows locked, I can lock and unlock it using buttons and it works but the status always shows locked.

What version of VRC0P do you have? The modules without RF+ 3 designation do not support locks. Sometimes when deadbolt is not fully extended in the door hole, the status will be shown as unlocked. I cannot think of a reason for the always locked status unless you have the wrong VRC0P

I have the RF+3 module and when I first installed the locks the status worked correctly. 

More than likely the lock association (reverse association) with VRC0P+3 is not programmed correctly or the reverse routing table is not optimized. I posted in another thread what you need to do get lock working reliably. Even if you used the RFIT RS232 setup to program reverse association, the Kwikset locks only support one association. I have found that Kwikset locks are picky the single association begin reprogrammed. I would start with only one locks and get that working before trying all three. If you have access to Hyperterminal you can hookup the VRC0P+3 and watch all instant notifications. You will need to place the computer close the HA controller to emulate the distance.

I have a similar setup, OP2 version 3.14a, Kwikset Z-Wave deadbolt locks - however I haven't seen this particular issue.  I agree with d.dennerline, It sounds like the VRC0P isn't sending serial data to the OP2 controller.  I would direct connect the VRC0P to the serial port on a PC and test the lock; you should see serial data on the PC's terminal program.  And, if I recall correctly, this is how I first associated the lock to the VRC0P, direct PC command to the VRC0P.
 
In my case, I do have two odd issues:
 
1. The status of the lock doesn't update a Omnitouch 5.7e "status button".  However, if I make the lock status set a flag in the OP2, and then have the Omnitouch 5.7e status button monitor that flag, it works great.  So, and odd issue, but easily overcome.  (The lock status does correctly show in the OP2 and on Haiku, just not on the status button of the 5.7e)
 
2. My second issue is strange.  When I have the OP2 send "lock" or "unlock" commands to the lock, the lock does respond correctly - but you can clearly hear that the lock motor mechanism sound is different than a normal lock/unlock from the lock's direct-entry keypad.  That is, the noise the lock makes is significantly longer and different, like the internal motor is attempting to push the deadbolt out too far and then it resets (?) itself to a normal resting position.  The other odd thing I have noticed is that the indicator LED on the back of the lock stops flashing - like the lock can't figure out if it's locked (flashing orange) or unlocked (flashing green).  However, simply unlock/lock the lock from the inside thumb lever, and the flashing LED returns to normal.
 
In general, I'm thinking that this is some kind of mis-match between the OP2 firmware command for lock/unlock and the Kwikset lock command firmware.  
 
My next steps are to:
 
1. Directly connect the OP2-VRC0P serial port to my test laptop serial port and have it send the lock command.  Note the serial string it's sending out.
2. Compare that serial string to what the lock is expecting (from the Kwikset documentation (google: kwikset home connect application note pdf))
3. Directly connect the VRC0P to my test laptop serial port and send the OP2 "lock" command, monitor what the lock's response is (if it sends an "alarm" message back to the PC).
4. Send the Kwikset's "lock" command (if it's different than the OP2's command) and listen / see what the lock's response is.
 
And of course, while I'm typing this I just though to try the "lock" function with the door open - in case the door jamb isn't drilled out enough and the deadbolt is hitting the door frame is causing the issue.  I would think that it would be odd for the OP2 "lock" command to extend the dead bolt further than the lock's own direct-keypad push button, but it could be.
 
Has anyone else experienced this?  Odd / different motor sounds when the lock is commanded by the OP2?
 
Thanks!
Doug