I recently added several more Z-Wave devices to my setup and ran across some interesting behaviors.

The two Aeotec Trisensors I added behaved differently from each other if the Admin UI is assumed to be accurate with respect to device state.

On motion detection, each sensor changes its motion state from off to on. Upon reaching the timeout period, only one sensor reverts back to an off state for its motion state. The other sensor remains in an On state with respect to motion detection. All of this was reported in the Admin UI.

I tried modifying the parameter of the motion sensor, but upon choosing (Write Changes), the Admin UI returned a communication error for the sensor. I assumed this was due to the proximity of the sensor from nearby Z-Wave devices.

For a completely different reason, I installed UD Mobile on my phone. I looked at the device state for the motion sensors and noticed that both motion sensing states were now off. I triggered each of the sensors and waited for the timeout period to be reached. In the mobile app, both sensors reverted back to an off state after the timeout period was reached. There were no communication errors.

What can account for the difference in reporting from the Admin UI and UD Mobile? Why am I getting communication errors in the Admin UI with these devices but not in the mobile app?

It could be due to marginal communication issue or a minor issue with the Admin console.

What version of the Zwave board do you have

What are your ISY firmware and UI versions

 

 

I have an ISY994i with version 5.3.4 firmware. I have the Z-Wave Plus board installed in the controller.

 

I was able to address the issue with odd behavior in the Admin UI with respect to the state reporting of Z-Wave devices recently added to my setup.

The Admin UI was not correctly displaying the state information from one of two Aeotec Trisensors I added. One of the sensors would toggle on a motion sensing flag then toggle the flag off after the timeout period was reached with no additional motion sensed. The other sensor would toggle on like the first one on motion detection but would fail to toggle off on timeout.

At the same time I was having this issue, one of my Z-Wave devices kept reporting communication errors. The option to repair links or update neighbors didn't do anything to resolve the communication errors. So I deleted and added the device back, then restored any links or references in programs that were broken when the device was deleted.

This cured the communication error, and also corrected the state information reported in the Admin UI. For whatever reason, UDI Mobile was reporting the correct state information from both Trisensors.

FWIW, this is what I found as a solution. If you have Z-Wave devices and get communication errors, don't ignore them - other devices in your Z-Wave network may be impacted if you leave the error(s) unresolved.