Recently I had occasion to exclude a device. I went to the device control panel, hit the trash can icon, and chose unpair. Vera dutifully put itself into exclusion mode, and the next thing I know, it reports that it’s excluding a node, before I even touched the switch I intended to exclude. On my server I’ve got a daily report generated of installed devices and health, so it was quick work to figure out what got dropped–the motion sensor in my son’s bedroom. I guess he moved right about the same time.
Given that I started the process by intending to remove a specific device, and launched the process from that device, I’m wondering why/how another device ended up being the victim.
- Is this a Vera defect in that it accepts an exclusion from a device other than the one from which one starts the exclusion process? That is, does the Z-Wave chip tell Vera that a particular device signaled while in exclusion mode, but Vera doesn’t compare the node number of the reported device to that of the intended device and tells the chip to go ahead and exclude the reported device anyway?
- Is this a Z-Wave defect/limitation in which exclusion is an autonomous mode of the chip and there’s no opportunity for Vera to filter out unintended devices that may become active at the wrong moment? That is, in exclusion mode the chip simply excludes the first (or every) device to talk to it and tells Vera what it did after the fact? I know exclusion mode works on any device, even devices that aren’t registered in the network, but is there a handshake that could be used to restrict which node gets excluded?
- Is there a “best practice” (other than extreme caution–nobody move!) to focusing exclusion on a single device and ensuring nothing else is unintentionally caught in the net?