I have a couple of Aeon Labs MultiSensor6 that operate on batteries; hence they should not be seen as routing nodes(neighbors) when optimizing other devices---right?
Well, I was optimizing a Z-wave A/C powered device and a MultiSensor6 node showed up as a neighbor of the device being optimized. Frightening!
Has anyone seen this? As suggested by Aeon Labs, when I set up the MultiSensors, I plugged in the USB power and hence they got added as "listening" devices(on the "node info" page). I subsequently removed the USB power and install batteries and all seemed well. The "node info" page still shows them to be listening devices. I wonder if a wakeup cycle occurred in the MultiSensor6 at the same instant I was optimizing the A/C device and the A/C device recognized the awake Multisensor and added it to it's routing table?
For those of you more fluent in Z-wave, is that possible? If so do we always have to check "neighbor lists" to make sure no battery devices get added?
BobSpen
Well, I was optimizing a Z-wave A/C powered device and a MultiSensor6 node showed up as a neighbor of the device being optimized. Frightening!
Has anyone seen this? As suggested by Aeon Labs, when I set up the MultiSensors, I plugged in the USB power and hence they got added as "listening" devices(on the "node info" page). I subsequently removed the USB power and install batteries and all seemed well. The "node info" page still shows them to be listening devices. I wonder if a wakeup cycle occurred in the MultiSensor6 at the same instant I was optimizing the A/C device and the A/C device recognized the awake Multisensor and added it to it's routing table?
For those of you more fluent in Z-wave, is that possible? If so do we always have to check "neighbor lists" to make sure no battery devices get added?
BobSpen