I only have experience with Zooz Z-wave devices, but this may apply to other Z-wave devices as well.

I have a combination of hard wired and battery Z-wave devices, with the majority being battery operated. In particular, I have four ZSE42 and one ZSE42 800LR leak detectors.

Here are some of my roadmap desires for Z-wave:

• Improve the inclusion process, such that all identical devices receive the same node groups and icons. Currently, I may see 4 nodes for some and 5 nodes for others.

• When a faulty device needs to be replaced, or more commonly, when it has to be reset for troubleshooting, can a mapping table be created such that when I remove, e.g., ZY_003 and add it again as the next sequential device e.g., ZY_044, I can then map the two and let eisy correct my programs automatically.

• Currently, when eisy has to be rebooted for any reason at all, I find that it can take days, or maybe never, for a battery operated leak detector to show up with a value for battery and/or wet/dry status. Even with a programmatic query after a wakeup event, this is often the case. There is something wrong with that process in my experience.

• OTA updates for battery devices is horrible, where I must hold the device, continuously pressing the button 4 times to ensure it stays awake. Even if I have to manually wake up the device to initiate the OTA, I would like eisy to tell the device to stay awake until the OTA is complete.

Rob

The number of device nodes can vary with the specific models and firmware versions of the device. I have several Weiser Smartcode locks. Some are Smartcode 10 (500 chip set) and Smartcode 620 (700 chip set), there are more nodes for the Smartcode 620.

2 minutes ago, Guy Lavoie said:

The number of device nodes can vary with the specific models and firmware versions of the device. I have several Weiser Smartcode locks. Some are Smartcode 10 (500 chip set) and Smartcode 620 (700 chip set), there are more nodes for the Smartcode 620.

Hi Guy,

I do understand that nuance, but I am talking about for the same model and firmware versions. Here is an example of 2 ZSE42 Leak Detectors. Same H/W version and same firmware.

You could try redoing the interview on the one with less nodes and see if anything gets added.

Right click on the device and do Z-wave -> Synchronize -> Update with Interview

I have done that on devices in the past after a recommendation from support. Things may or may not change when I do. It should not be so hit or miss IMO.

I am not trying to solve my current device situation as I can use them effectively as is. I just want UD to do better if at all possible.😁

Edited September 17Sep 17 by RRalston
correct typos

In my original post, I indicated z-Wave battery devices can take a very long time, if ever, to update information after a reboot. That seems to be improving. But in addition, I have found my Zooz Water Valve control, which is AC powered all the time, never updates its status of Open/Close or Off/On until I force a query, after a reboot. It is always awake. I have query all devices set after reboot. So why doesn't this get updated by that after a reboot?

And again, I am not trying to solve this here. I am just reporting this here as part of my desire for UD to handle all Z-wave devices better. It is so hit or miss in my experience.

Before I force a query. No Status.

Immediately after when I query, Status shows up. Note, I do not have a battery back attached, so Battery Level is always 0%