did you put your sensors like this?
[][]
the reed switch might have multiple on/off when the door opens.
what I did is as below, put it to the place it barely touch each other.
[]
..[]
1 Like
Yes, there are mounted like this. If this is the case (multiple on/off) the rule can't probably handle this, make sense....
1 Like
Not more than what I have written about in other threads, I do think I can enable the feature again on 2.2.3 bu just making sure to turn it off automatically if this issue happens again. That is, if try-catch can actually catch this issue.
Check the event log, that could definitely be a problem in terms of speed for the rule. In general it can be problematic when reed sensors slide in from the side, the magnetic field changes will make it think it opens and closes multiple times.
1 Like
Hi @markus, would it be possible to make the Recovery Mode a RO attribute?
It would be helpful in a dashboard so I can quickly see which devices I have forgotten to set back to normal recovery mode.
@markus thanks very much for the great Aqara D1 drivers 
Is it possible to add support to the Aqara D1 3 button wall switch? (QBKG26LM) the Aqara D1 1 button switch works great with your driver, but not the D1 3 button wall switch.
Many thanks
1 Like
I have the no-neutral version of that (QBKG25LM) but it's still in its box right now. If you've got one up and running then head to the device in HE and turn on debug logging. Then open your logs page and do the following on each switch, starting with the one on the left and working across to the right:
- Single press button
- Double press button
- Triple press button (may not be a thing on these, but to test)
- Press and hold button, then release
Once you've done that for all three, do the same but for buttons 1 and 2 together, buttons 2 and 3 together and buttons 1 and 3 together, then finally all of the buttons together. I think that's all the possible combinations.
Choose only that device in the logs from the devices listed at the top, then copy and paste everything into a post here between ' ``` ' tags to keep the formatting.
1 Like
Yes, but that would add even more attributes to a driver which already has a lot. Now with the limit on number of events kept per device being lower I guess it might not matter as much though. I'll think about it 
I'll get to it soonish, but yes, I'd need the information as asked for by @andydvsn
Btw everyone, the Aqara T1 T&H, Motion and Contact sensors (Zigbee 3.0) are FINALLY being released. I will get my first ones this week or next. I talked to a seller I know in an Aqara store and he'll send me a message as soon as they have received them. The T1 buttons/switches have also been released.
1 Like
It's not super important. Limited resources need to be used wisely. Just thought I'd ask being ignorant of how these things work.
Copy of Log below as requested. An interesting observation, is that the button presses are not registering at all (at least not from looking at the recorded log).
If there is anything else I can do, please let me know.
'dev:3152020-08-24 13:55:23.795 warnUnknown model (lumi.switch.n3acn3) - PLEASE REPORT THIS LOG TO THE DEV - description:read attr - raw: 03660200002E050042126C756D692E7377697463682E6E3361636E33, dni: 0366, endpoint: 02, cluster: 0000, size: 2E, attrId: 0005, encoding: 42, command: 01, value: 126C756D692E7377697463682E6E3361636E33 | parseMap:[raw:03660200002E050042126C756D692E7377697463682E6E3361636E33, dni:0366, endpoint:02, cluster:0000, size:2E, attrId:0005, encoding:42, command:01, value:lumi.switch.n3acn3, clusterInt:0, attrInt:5]
dev:3152020-08-24 13:55:23.773 debugdirty model = lumi.switch.n3acn3, clean model=lumi.switch.n3acn3
dev:3152020-08-24 13:55:23.770 debugModel Name Received - description:read attr - raw: 03660200002E050042126C756D692E7377697463682E6E3361636E33, dni: 0366, endpoint: 02, cluster: 0000, size: 2E, attrId: 0005, encoding: 42, command: 01, value: 126C756D692E7377697463682E6E3361636E33 | parseMap:[raw:03660200002E050042126C756D692E7377697463682E6E3361636E33, dni:0366, endpoint:02, cluster:0000, size:2E, attrId:0005, encoding:42, command:01, value:lumi.switch.n3acn3, clusterInt:0, attrInt:5]
dev:3152020-08-24 13:55:23.696 debugsendZigbeeCommands(cmd=[])
dev:3152020-08-24 13:55:23.689 debugsendZigbeeCommands(cmd=[he raw 0x0366 1 0x02 0x0000 {10 00 00 05 00}, delay 2000])
dev:3152020-08-24 13:55:23.685 debugrefresh cmd: [he raw 0x0366 1 0x02 0x0000 {10 00 00 05 00}, delay 2000]
dev:3152020-08-24 13:55:23.660 debugdirty model = lumi.switch.n3acn3, clean model=lumi.switch.n3acn3
dev:3152020-08-24 13:55:23.630 warnDisabling the Recovery feature due to Platform bug in 2.2.3!
dev:3152020-08-24 13:55:23.627 debugrecoveryMode: Slow
dev:3152020-08-24 13:55:23.612 infoRecovery feature ENABLED
dev:3152020-08-24 13:55:23.608 debugstartCheckEventInterval()
dev:3152020-08-24 13:55:23.569 infogetDriverVersion() = v0.8.1.0814
dev:3152020-08-24 13:55:23.566 debugrefresh() model='lumi.switch.n3acn3'
dev:3152020-08-24 13:55:23.542 infoinitialize()
--- Live Log Started, waiting for events --'
Hey @markus, I'm getting warning messages for all my devices that use your drivers:
Aqara Curtain below:
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 10:40:38.893 am [warn](http://192.168.1.222/device/edit/1892)Disabling the Recovery feature due to Platform bug in 2.2.3!
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 10:38:56.438 am [warn](http://192.168.1.222/device/edit/1892)Stopping Recovery feature due to Platform bug in 2.2.3!
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 10:38:44.337 am [warn](http://192.168.1.222/device/edit/1892)Unhandled Event - description:catchall: 0000 8032 00 00 0040 00 C3B0 00 00 0000 00 00 00000B010787E80408863C8B003C8BD347043C8B693B04693B706C403C8B25B504A0D0024604693B | msgMap:[raw:catchall: 0000 8032 00 00 0040 00 C3B0 00 00 0000 00 00 00000B010787E80408863C8B003C8BD347043C8B693B04693B706C403C8B25B504A0D0024604693B, profileId:0000, clusterId:8032, clusterInt:32818, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:C3B0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00, 0B, 01, 07, 87, E8, 04, 08, 86, 3C, 8B, 00, 3C, 8B, D3, 47, 04, 3C, 8B, 69, 3B, 04, 69, 3B, 70, 6C, 40, 3C, 8B, 25, B5, 04, A0, D0, 02, 46, 04, 69, 3B]]
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 09:48:33.107 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 09:48:33.104 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1224 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 08:48:33.093 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 08:48:33.090 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1164 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 07:48:33.096 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 07:48:33.092 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1104 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 06:48:33.086 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 06:48:33.082 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1044 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 05:48:33.145 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 05:48:33.142 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 984 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 04:48:33.122 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 04:48:33.118 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 924 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 03:48:33.089 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 03:48:33.085 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 864 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 03:32:28.282 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 03:32:28.266 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 848 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 03:32:27.586 am [warn](http://192.168.1.222/device/edit/1892)Unhandled Event - description:catchall: 0000 8032 00 00 0040 00 C3B0 00 00 0000 00 00 00000E0107D30604A0D03C8B403C8BD347043C8B693B04693B706C403C8BA0D004A0D0024604693B | msgMap:[raw:catchall: 0000 8032 00 00 0040 00 C3B0 00 00 0000 00 00 00000E0107D30604A0D03C8B403C8BD347043C8B693B04693B706C403C8BA0D004A0D0024604693B, profileId:0000, clusterId:8032, clusterInt:32818, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:C3B0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00, 0E, 01, 07, D3, 06, 04, A0, D0, 3C, 8B, 40, 3C, 8B, D3, 47, 04, 3C, 8B, 69, 3B, 04, 69, 3B, 70, 6C, 40, 3C, 8B, A0, D0, 04, A0, D0, 02, 46, 04, 69, 3B]]
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 02:44:32.103 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 02:44:32.100 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 800 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 01:44:32.099 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 01:44:32.095 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 740 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 12:44:32.091 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-24 12:44:32.088 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 680 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 11:44:32.085 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 11:44:32.081 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 620 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 10:44:32.116 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 10:44:32.112 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 560 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 09:44:32.133 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 09:44:32.130 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 500 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 08:44:32.098 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 08:44:32.094 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 440 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 07:44:32.111 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 07:44:32.107 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 380 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 06:44:32.091 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 06:44:32.087 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 320 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 05:49:12.740 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 05:49:12.680 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 265 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 05:48:21.446 pm [warn](http://192.168.1.222/device/edit/1892)Unhandled Event - description:catchall: 0000 8032 00 00 0040 00 C3B0 00 00 0000 00 00 0000070106D30680A0D03C8B043C8BD347043C8B693BC0693B706C00A0D0A0D004A0D0 | msgMap:[raw:catchall: 0000 8032 00 00 0040 00 C3B0 00 00 0000 00 00 0000070106D30680A0D03C8B043C8BD347043C8B693BC0693B706C00A0D0A0D004A0D0, profileId:0000, clusterId:8032, clusterInt:32818, sourceEndpoint:00, destinationEndpoint:00, options:0040, messageType:00, dni:C3B0, isClusterSpecific:false, isManufacturerSpecific:false, manufacturerId:0000, command:00, direction:00, data:[00, 00, 07, 01, 06, D3, 06, 80, A0, D0, 3C, 8B, 04, 3C, 8B, D3, 47, 04, 3C, 8B, 69, 3B, C0, 69, 3B, 70, 6C, 00, A0, D0, A0, D0, 04, A0, D0]]
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 04:53:12.085 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 04:53:12.081 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 209 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 03:53:12.093 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 03:53:12.089 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 149 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 01:25:35.102 pm [warn](http://192.168.1.222/device/edit/1892)Event interval normal, recovery mode DEACTIVATED!
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 12:53:12.093 pm [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 12:53:12.090 pm [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1410 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 11:53:12.091 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 11:53:12.087 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1350 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 10:53:12.092 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 10:53:12.089 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1290 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 09:53:12.110 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 09:53:12.107 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1230 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 08:53:12.088 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 08:53:12.085 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1170 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 07:53:12.106 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 07:53:12.103 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1110 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 06:53:12.130 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 06:53:12.126 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 1050 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 05:53:12.133 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 05:53:12.128 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 990 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 04:53:12.130 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 04:53:12.126 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 930 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 03:53:12.087 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 03:53:12.084 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 870 (maximum expected 90)
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 03:32:38.826 am [warn](http://192.168.1.222/device/edit/1892)Event interval INCORRECT, recovery mode (Normal) ACTIVE! If this is shown every hour for the same device and doesn't go away after three times, the device has probably fallen off and require a quick press of the reset button or possibly even re-pairing. It MAY also return within 24 hours, so patience MIGHT pay off.
[dev:1892](http://192.168.1.222/logs/past#dev1892)2020-08-23 03:32:38.819 am [warn](http://192.168.1.222/device/edit/1892)One or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 849 (maximum expected 90)
I can still control all these devices in Hubitat so they don't actually seem to have fallen off. 1 of my Aqara curtains has never properly checked in (never figured out the issue) and that's always giving log messages. However, this time, my tasmota devices (KMC 4 plug, shade motor and my light bulbs) and my 2 Aqara curtains all have warning messages.
The KMC 4 Plug and shade motor give warnings when the system restarts (I restart daily and just did a firmware update) so I'm less concerned about those. However, the 2 curtains are complaining a bit. The light bulbs are also claiming a bunch of restarts even though the system wasn't restarted at those times.
Light bulbs messages:
[dev:1205](http://192.168.1.222/logs/past#dev1205)2020-08-24 01:16:40.735 am [warn](http://192.168.1.222/device/edit/1205)RestartReason: External System
[dev:1205](http://192.168.1.222/logs/past#dev1205)2020-08-23 09:29:40.096 pm [warn](http://192.168.1.222/device/edit/1205)RestartReason: External System
[dev:1205](http://192.168.1.222/logs/past#dev1205)2020-08-23 03:59:54.430 pm [warn](http://192.168.1.222/device/edit/1205)RestartReason: External System
[dev:1205](http://192.168.1.222/logs/past#dev1205)2020-08-23 12:41:09.145 pm [warn](http://192.168.1.222/device/edit/1205)RestartReason: External System
[dev:1205](http://192.168.1.222/logs/past#dev1205)2020-08-23 10:16:49.872 am [warn](http://192.168.1.222/device/edit/1205)RestartReason: External SystemHmm. I'll fit mine to a convenient wall as soon as I can and check this out.
2 Likes
@markus, Is there an explanation for this?
The status of the device in HE was open but in reality the door was closed.
In the logs I see the door sensor is closing (07: 42: 22.363 infosendOpenCloseEvent (openClose = false) invertContact = false) but this is not visible in the events.
Or do I misinterpret the situation?
dev:257 2020-08-26 08:38:29.090 infobuttonDown(button=1)
dev:257 2020-08-26 08:38:29.082 infosendOpenCloseEvent(openClose=false) invertContact=false
dev:257 2020-08-26 08:38:29.076 infoKNOWN event (Xiaomi/Aqara specific data structure with battery data - 4C - hourly checkin) - description:read attr - raw: 51920100003002FF4C0600100021DB0B21A81324030000000021B100205E, dni: 5192, endpoint: 01, cluster: 0000, size: 30, attrId: FF02, encoding: 4C, command: 0A, value: 0600100021DB0B21A81324030000000021B100205E | parseMap:[raw:51920100003002FF4C0600100021DB0B21A81324030000000021B100205E, dni:5192, endpoint:01, cluster:0000, size:30, attrId:FF02, encoding:4C, command:0A, value:[false, 3035, 5032, 3, 177, 94], clusterInt:0, attrInt:65282]
dev:257 2020-08-26 07:42:22.368 infobuttonDown(button=1)
dev:257 2020-08-26 07:42:22.363 infosendOpenCloseEvent(openClose=false) invertContact=false
dev:257 2020-08-26 07:42:09.801 infobuttonPushed(button=1)
dev:257 2020-08-26 07:42:09.795 infosendOpenCloseEvent(openClose=true) invertContact=false
dev:257 2020-08-26 07:40:03.995 infobuttonDown(button=1)
dev:257 2020-08-26 07:40:03.969 infosendOpenCloseEvent(openClose=false) invertContact=false
dev:257 2020-08-26 07:40:03.957 infoKNOWN event (Xiaomi/Aqara specific data structure with battery data - 4C - hourly checkin) - description:read attr - raw: 51920100003002FF4C0600100021DB0B21A81324010000000021B100205F, dni: 5192, endpoint: 01, cluster: 0000, size: 30, attrId: FF02, encoding: 4C, command: 0A, value: 0600100021DB0B21A81324010000000021B100205F | parseMap:[raw:51920100003002FF4C0600100021DB0B21A81324010000000021B100205F, dni:5192, endpoint:01, cluster:0000, size:30, attrId:FF02, encoding:4C, command:0A, value:[false, 3035, 5032, 1, 177, 95], clusterInt:0, attrInt:65282]
I've updated the drivers to not permanently disable Recovery Mode in 2.2.3.x, I've not experienced this issue myself and can't be sure that the errors seen in the logs CAN be caught by a driver, if they can, I now have a try-catch surrounding the piece of code where this would happen due to the platform issue. If that is triggered the setting for Recovery Mode is changed to Disabled and to use it again after such an event as what has been reported earlier it needs to be enabled manually inside the device Preferences. If you do experience this and it works as expected, please report it in this thread
Don't worry about, but yes, let us not add more going into events right now
If @andydvsn doesn't sort it out it does sound like I might need to get one of those devices then.
I'm seeing this on 2.2.3.x, I will see what I can find to sort this out.
It looks like the event wasn't received, that must be due to some issue with the DB not committing it. Do you have other issues in the logs? Things like this can be DB corruption and downloading all backups, running SOFT reset (NOT EVER Full reset under any normal circumstances) and then restore could be enough to not have this issue.
1 Like
I’ll try to check it out today. Turned out where I wanted to put it has a shallow back box, so I need to drill out the hole. That’ll make me popular.
1 Like
Otherwise on the desk with exposed wires for kids to play with is also a very popular location I've heard 
2 Likes
You’ve seen my test thermostat setup then? 
(For the concerned, there’s no fuse in the plug. And it’s put away. All safe.)
1 Like
No, I must have missed that one. I do have devices loose on the desk, but no kids so that is ok. My wife knows that it is dangerous to touch anything on my desk, you never know what's connected to what...
1 Like
Not that I know, but this sensor is monitored using rule machine (if door is open to long) --> I am alarmed If the door is "open" but in reality not.
I understand If the status of a sensor is wrong it is corrected on the hourly check in, correct?
I will give the soft reset a try, thx for the suggestion
1 Like
Yes, that is correct. Though at times that hourly check in doesn't arrive. However, most of the time it does.
1 Like
Hi @markus
I've not seen any update through HPM.
Are these in beta and not formally released yet?
Just wondering as I wasn't seeing the issue either but updated automatically through HPM and have now lost that facility.
Thanks.
