I am writing software using OpenZWave. I am sending/receiving ZWave commands on my own, so I am not using the HS3 software. The latest firmware seems to have greatly improved status reports when operating the device locally (w/ button press), but when operating the device remotely via ZWave I am not getting the final value when the dimmer finishes ramping up or down.
When operating the device locally, I get two status reports. The first report is typically 2-3% from the starting value. The final report is sent when the device finishes ramping up/down from an on or off state.
When operating the device remotely via zwave I get the same initial report that is 2-3% from the starting value, but the final report is not sent, so I do not get the final value.
A work around I have done is when I get the initial value I poll the device 1 second later, and continue to poll if the value changes. I stop polling once the value stops changing. This works, but I would rather the device work consistently if possible - when I get the report I have no way of knowing how the device was updated, so I have to poll regardless if the update happened local or remote.
I suspect when the firmware was updated to include instant status from locally controlling the device, that was the only part that changed. I have tested older firmware, and the remote control behavior is the same, while local control is different.
Ideally it would be nice if the device only sent 1 update when the device finished on both local and remote control. But having both sent on local and remote would be sufficient. I just want the behavior to match regardless of how the device is controlled.
When operating the device locally, I get two status reports. The first report is typically 2-3% from the starting value. The final report is sent when the device finishes ramping up/down from an on or off state.
When operating the device remotely via zwave I get the same initial report that is 2-3% from the starting value, but the final report is not sent, so I do not get the final value.
A work around I have done is when I get the initial value I poll the device 1 second later, and continue to poll if the value changes. I stop polling once the value stops changing. This works, but I would rather the device work consistently if possible - when I get the report I have no way of knowing how the device was updated, so I have to poll regardless if the update happened local or remote.
I suspect when the firmware was updated to include instant status from locally controlling the device, that was the only part that changed. I have tested older firmware, and the remote control behavior is the same, while local control is different.
Ideally it would be nice if the device only sent 1 update when the device finished on both local and remote control. But having both sent on local and remote would be sufficient. I just want the behavior to match regardless of how the device is controlled.
Comment