Great. Simply FYI, the 2.2.4.139 update has been running now on my C-7 since moments after it was released (almost a full day now), and there has not been a single instance of “Not Responding” or “Failed” for any of these devices. That’s a dramatic change. They always worked, more or less, and I could get the status to go back to OK simply by opening and closing the appropriate door, but the “Not Responding” or “Failed” would always return in an hour or two. So, on that point, congratulations and thanks.
On a related point, the subject of my initial post, see the screenshot below. It may be of interest that the Bedroom Closet Door Sensor, the one that now lags several seconds turning on after a long time inactive (a few hours), but which becomes instantaneous after that initial open/close, is the only device that doesn’t report a RTT value. Perhaps that means something. Firmware values in screenshots above, etc.
it will eventually.. This is measured from packets sent from the hub from the driver. So sleepy notification based sensors won’t have this populated until a wakeup event.
Ok, but this recessed door sensor 7 is the most used of all. The others report an RTT but have only been opened/closed once or twice. Again, this may be related to the fact that this, and only this, recessed door sensor 7 has the initial several second response lag after not being opened/closed for a couple of hours, and then will be fine.
Right.. but the only time anything is sent to the device is during a wakeup event.. RTT is measured on packets sent to the device from the driver. So until a packet is sent from the driver to the device there is nothing to show here. You can't measure round trip time on incoming packets.
I have excluded and included a couple of times and I cannot get it to work correctly (Aeotec Door Recessed Sensor) Here is the log that I snip. It now shows the battery and closed but when I try to open and closed nothing happens? Is there anything else that I need to do? This is a C-7 hub and latest firmware.
@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..
