Yale Security YRD210-ZW-619 - Device Status in UI
Posted: 10 Sep 2015 18:21
Hey guys! First, I'd like to say, great work on 2.1.1. I'm glad my dimmers now update continuously in the UI until their state stops changing.
I wanted to report on the behavior of a device that I had integrated into my Z-Wave network a few months ago - It is a Yale Security YRD210-ZW-619 http://www.yaleresidential.com/en/yale/ ... -deadbolt/.
The device interviews without a hitch and integrates just fine into the network. Responds perfectly to UI commands, locking and unlocking when requested.
The only hiccup I have with the device, is the state of the unit in the UI. Right now for instance, the unit is in the locked position and if I issue an unlock command, the UI will report that the unit is still in the locked position.
The next subsequent command, be it unlock or lock, will update the UI to the units CURRENT state. So, to clarify, if the unit is in the locked position, and the UI reports that the unit is locked, an unlock command will not change the state, BUT the next command will update the unit status to unlocked.
To simplify this a bit, the units reported state in the UI always seems to be the last state the unit was in before a command was received.
When I inspect the server queue, I see status reports are being sent from the unit when commands are issued from the web interface. In fact, I can even see status updates are sent from the unit when the deadbolt is manually turned on the unit. So I know it's reporting back to the server.
Any ideas? Sorry if my explanation is a bit long winded.
Thanks again for all your help!
I wanted to report on the behavior of a device that I had integrated into my Z-Wave network a few months ago - It is a Yale Security YRD210-ZW-619 http://www.yaleresidential.com/en/yale/ ... -deadbolt/.
The device interviews without a hitch and integrates just fine into the network. Responds perfectly to UI commands, locking and unlocking when requested.
The only hiccup I have with the device, is the state of the unit in the UI. Right now for instance, the unit is in the locked position and if I issue an unlock command, the UI will report that the unit is still in the locked position.
The next subsequent command, be it unlock or lock, will update the UI to the units CURRENT state. So, to clarify, if the unit is in the locked position, and the UI reports that the unit is locked, an unlock command will not change the state, BUT the next command will update the unit status to unlocked.
To simplify this a bit, the units reported state in the UI always seems to be the last state the unit was in before a command was received.
When I inspect the server queue, I see status reports are being sent from the unit when commands are issued from the web interface. In fact, I can even see status updates are sent from the unit when the deadbolt is manually turned on the unit. So I know it's reporting back to the server.
Any ideas? Sorry if my explanation is a bit long winded.
Thanks again for all your help!