@bcopeland, I tried the wake-up trigger on one of the Recessed Door Sensor 7 devices (Coat Closet Door sensor, see screenshot in my post above) after updating my C-7 to 2.2.4.141.
Bryan, simply to further complete your life, below is another, different, error message from the same Recessed Door Sensor 7, about which I posted above, that I did the wake-up trigger you indicated would be necessary. It’s the same C-7 running 2.2.4.141 as before. No additional wake-up trigger or Configure or Save Device or Save Parameters was done subsequent to the report yesterday that showed yesterday’s error message. Operation is still fine for this device.
As an additional piece of information, the error occurred the first time the door was opened after sitting closed overnight. Subsequent open/close today do not produce an error.
Same boat here. I have excluded and reset the sensor. Then included it without security just to make sure it wasn't the sensor and it worked perfectly. Since it is an exterior door, I'd prefer S2.
But I know @bcopeland is on it and it'll get resolved soon.
Bad news... Nothing I can do to fix this.. Aeotec has a firmware bug.. The SDK is blocking it because the session ID is not incrementing on the supervision get requests from the device..
Ok, fine, thanks for looking into this. I didn’t find any firmware updates on the Aeotec site. I looked before reporting issues for the device. My particular needs right now don’t require S2, but I would, eventually, like to put them on our front and back doors.
What about these other issues with this device that don’t involve S2? Note that these are just the things I have noted. Others have reported other issues.
Interesting note.. the button does not trigger wakeup.. so looks like there is no way to trigger wakeup from this device, you have to wait until the wakeup period..
Pressing the button just triggers a NIF, no wakeup