Same two sensors - different statuses

I am a Newb and I just got all of my devices set up. I can say that I have had a very good experience so far and this community has been incredible.

I ran across an issue with my new Aqara P1 Motion Sensor RTCGQ14LM. The device in the bathroom has worked perfect since minute one. The one at the back door has not. Here is the statuses on both:

Back Door Sensor

Current States

  • motion : inactive
  • powerSource : ?

Bathroom Sensor

Current States

  • battery : 100
  • batteryVoltage : 3.192
  • illuminance : 39
  • motion : inactive
  • powerSource : battery
  • temperature : 77

This is a zigbee device which is new for me as I have mostly always used Z-Wave.

Any idea of how I should proceed.

Most of the Aqara battery-powered sensors are difficult to pair.
Try pairing again several times, very close to the HE hub.

Is there a way to do that without removing it. The way the thing is made it uses double sided tape which is stuck to my wall and to the bottom of the device. If I take it down, I will need to remove the tape and put new on. Not too big of a deal but I am old and don't like to get on the ladder. The device is very close to the hub.

Just try several times then. Persist, until the Current states are populated with all attributes,
Keep pressing shortly the pair button on the device during the Zigbee discovery process.

Just to be clear, I have tried three times and still have the same issue. As I went back and carefully read your response, you said

Do you mean, put device in pairing mode and when the sensor starts blinking keep pressing the button while it is blinking?

Yes

1 Like

Slightly off-topic - I have begun using 3M Command Strips rather than the double sided tape when mounting devices such as this. It makes it easier to remove them for things like battery changing . . .

4 Likes

Ditto. I like the velcro command strips if it's something I think I'm going to be regularly taking on and off.

1 Like

I'm a huge fan of Gorilla Mounting Putty.

How close? Can you bring the hub to be within 2 feet? Thereโ€™s a lot of wireless traffic during pairing.

1 Like

Before, I was able to pair the Aqara P1 sensor far away from the hub while developing the driver.
Later, I added more Zigbee devices including two Tuya radars that send distance reports every second when activated - and as a result, I can't pair again P1 from a long distance anymore, must be 2-3 feets close to the hub.

1 Like

Great suggestion. Thanks

Yes, I actually set it about a foot away.

This is my second one of these that is not polling properly. This time it shows the following:

Current States

  • illuminance : 68
  • motion : inactive
  • powerSource : battery

Which is a little more than before but still not the same as my first one I connected which is still showing:

Current States

  • battery : 100
  • batteryVoltage : 3.192
  • illuminance : 39
  • motion : inactive
  • powerSource : battery
  • temperature : 77

Do you think that pushing the button continuously while it is pairing would help anything? You had suggested that earlier. Thoughts?

No continuously. But tapping it on/off should help. And, that suggestion was from @kkossev.

Have you tried simply clicking the CONFIGURE button on the Hubitat device details page for the one that has not yet reported in all of its attributes? Sometimes devices also have a REFRESH command that can cause them to send their latest status reports to the hub.

Or, simply wait, and those additional attributes may just fill in on their own over time. The Aqara devices are finicky, which is why Hubitat does not list them as being fully supported.

3 Likes

When clicking on the 'Configure' button, you must wake up the battery-powered device at the same time. Waking up can be done by a motion near the sensor or again by a short press of the physical pair button.

2 Likes

yes, I have tried that several times.

You were right, I left it alone and came back to look at it and lo and behold, the other attributes were there.

Thank you for responding.

2 Likes

Great to hear!

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.