Aqara P1 motion sensors dropping offline

Mid morning after adding M1P-2 back. See it has a GroovyRuntimeException and two warning events after it. will see how long it stays on:

2025-03-11 10:43:25.402 AMinfoM1P-2 illuminance is 122 lx (delayed)

dev:2662025-03-11 10:43:24.442 AMinfoM1P-2 Motion is active 9s

dev:2662025-03-11 10:43:21.408 AMinfoM1P-2 Motion is active 6s

dev:2662025-03-11 10:43:20.317 AMinfoM1P-2 illuminance is 119 lx (delayed)

dev:2662025-03-11 10:43:18.348 AMinfoM1P-2 Motion is active 3s

dev:2662025-03-11 10:43:15.380 AMinfoM1P-2 Detected motion

dev:2662025-03-11 10:43:15.314 AMinfoM1P-2 illuminance is 121 lx

dev:2662025-03-11 10:43:08.136 AMinfoM1P-2 Motion reset to inactive after 30 s.

dev:2662025-03-11 10:42:38.145 AMinfoM1P-2 Detected motion

dev:2662025-03-11 10:42:38.118 AMinfoM1P-2 illuminance is 119 lx

dev:2662025-03-11 10:42:33.017 AMinfoM1P-2 LED is Enabled (1)

dev:2662025-03-11 10:42:33.004 AMinfoM1P-2 illuminance is 142 lx

dev:2662025-03-11 10:42:32.994 AMinfoM1P-2 Battery level is 99 %

dev:2662025-03-11 10:42:27.981 AMinfoM1P-2 (parse attr 5) device lumi.motion.ac02 button was pressed

dev:2662025-03-11 10:42:26.586 AMinfoM1P-2 Debug logging is false; Description text logging is true

dev:2662025-03-11 10:42:26.584 AMinfoM1P-2 Updating Aqara P1 Motion Sensor RTCGQ14LM model lumi.motion.ac02 manufacturer LUMI (driver version 1.7.3 2025/01/16 11:46 PM)

dev:1402025-03-11 10:42:21.015 AMwarnEvent 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:1402025-03-11 10:42:21.013 AMwarnOne or several EXPECTED checkin events have been missed! Something MIGHT be wrong with the mesh for this device. Minutes since last checkin: 521313 (maximum expected 140)

dev:2662025-03-11 10:42:08.129 AMerrorgroovy.lang.GroovyRuntimeException: Ambiguous method overloading for method java.lang.Integer#minus. Cannot resolve which method to invoke for [null] due to overlapping prototypes between: [class java.lang.Character] [class java.lang.Number] on line 1164 (method parse)

dev:2662025-03-11 10:42:02.600 AMinfoM1P-2 (parse attr 5) device lumi.motion.ac02 button was pressed

dev:2662025-03-11 10:42:02.598 AMinfoM1P-2 (parse) device model is LUMI

dev:2662025-03-11 10:42:02.374 AMinfoM1P-2 healthStatus changed to online

dev:2662025-03-11 10:42:02.255 AMinfoM1P-2 configure...fullInit = false (driver version 1.7.3 2025/01/16 11:46 PM)

sys:12025-03-11 10:42:01.250 AMinfoFound previously joined Zigbee device M1P-2

sys:12025-03-11 10:41:58.939 AMinfoZigbee Discovery Running

My hub is about 10ft away from the nearest access point. I could move it to an unused upper BR that would be the farthest away from any AP.

Closest repeater [Sonoff plug switch] would be about 15ft away and all communication would have to go thru it.

At this point, I'm wiling to try anything - even the Matter route, which is just another PIA / learning curve.

The problems are coming from the ‘Sonoff S31 Lite zb’ plugs being incompatible with Hubitat, I will write more later.

2 Likes

@user2428 please refer to this post by Hubitat support :

Ther are other complains in this forum, but also on Home Assistant / GitHub that SONOFF plugs model 'S31 Lite zb' are creating problems with the stability of the Zigbee networks.

The best approach would be to gracefully remove all S31 plugs from HE (use the red 'REMOVE' button on the device web page), or you can alternatively just remove the plugs from the wall sockets. Note, that simply disabling the devices from HE web interface will have no effect - the problematic devices will still be part of the HE Zigbe network and will continue to create instability. A ZIgbee router (repeater) instability creates problems also for all the battery-powered Zigbee devices that were routing through it!

My advice is to stay away from SONOFF plugs. Sonoff S26R2ZB plugs are also known to create very similar problems in Hubitat.

3 Likes

Based on what Krassimir found I would suggest using some Third Reality smart plugs. You can get them in energy monitoring and non energy monitoring depending on your needs. I use them with zero issues.

1 Like

Based on kkossev and you comments ordered 4x metering type (as I can get them overnight) and 4x to replace the others I have.

Will see if this fixes issue, do not want to think how many times I rejoined the motion sensors (would have just been simpler to turn on the lights manually)

I have 10 of them throughout my house and have had zero issues in anyway with them. They all have child devices off of them.