I have a Aeotec Gen 5 Recessed contact switch (Z-Wave) that is acting strangely. If I move it to a certain location in the house (carrying it around by hand) it registers open/close actions. However once I install it in its proper place, the status remains "open". I can see the debug messages in the log for open/close activity when its installed (and not updating):
dev:2642021-12-09 09:59:18.528 pm debug parsed 'zw device: 27, command: 3003, payload: FF , isMulticast: true' to null
dev:2642021-12-09 09:59:14.551 pm debug parsed 'zw device: 27, command: 3003, payload: 00 , isMulticast: true' to null
This is what I see in the logs when it is in a "working" location in the house and is updating status properly:
dev:2642021-12-09 10:01:04.789 pm debugparsed 'zw device: 27, command: 3003, payload: FF , isMulticast: false' to [name:contact, value:open, descriptionText:Front Door Contact was opened]
dev:2642021-12-09 10:01:04.785 pm infoFront Door Contact was opened
dev:2642021-12-09 10:01:04.780 pm debugSensorBinaryReport cmd:SensorBinaryReport(sensorValue:255)
dev:2642021-12-09 10:00:59.700 pm debugparsed 'zw device: 27, command: 3003, payload: 00 , isMulticast: false' to [name:contact, value:closed, descriptionText:Front Door Contact was closed]
dev:2642021-12-09 10:00:59.697 pm infoFront Door Contact was closed
dev:2642021-12-09 10:00:59.691 pm debugSensorBinaryReport cmd:SensorBinaryReport(sensorValue:0)
My question is, why is the debug payload mostly the same (with the exception of the 'isMulticast' bool), yet the hub doesn't seem to recognize it as a contact state update when it is in the location that "does not work"?
I've repair the Z-Wave network several times and let it sit for 24 hours untouched. I even went so far as to put a repeater about 6 feet from the door frame where it is installed, even though the hub is only 12 feet from the doorframe as it is.
