Pairing a Aqara Motion Sensor P1 using generic Zigbee

mnybon · January 6, 2023, 7:27pm

I have an openhab 3 instance running with the zigbee ember controller as my zigbee binding. I have a number of different things already connected and working, but lately I bought a few Aqara Motion Sensor P1’s because I needed some motion sensors with built in light in them.
https://www.aqara.com/en/product/motion-sensor-p1

The problem I am running into is that the sensor pairs (Under a wierd name LUMI lumi.motion.ac02) but the only channel it presents is the Battery Voltage channel, which is helpful, granted, but it is not exactly the most important one.

I have been keeping an eye on the event log, and even though the device is listed as online, and that is reflected in the log, I have seen no channel events from it at all.

Is there something I am missing? Does anyone have the sensor working using the zigbee binding? And if so, is there some way to just manually configure the damn thing so it will work?

anon71759204 · January 6, 2023, 8:21pm

Check whether zigbee_device_initialized is true:

If not

> Press and hold the reset button on the device for ± 5 seconds (until the blue light starts blinking). After this the device will automatically join. If this doesn’t work, try with a single short button press.

Read ZigBee - Bindings | openHAB.

mnybon · January 7, 2023, 9:39am

It is indeed initialized, and I can see that one channel. I have reset it multiple times as well.

JimT · January 7, 2023, 11:16am

I’ve been using that sensor with zigbee2mqtt for several years. It has lux sensor as well as motion.

anon71759204 · January 7, 2023, 11:43am

Please provide a Zigbee fingerprint from your sensor. Skimming over Aqara Motion Sensor P1 · Issue #5967 · dresden-elektronik/deconz-rest-plugin · GitHub I get the impression that your sensor is different from the Xiaomi MS-S02.

Then @chris might be able to add support for your device to the Zigbee Binding.

mnybon · January 7, 2023, 11:44am

So it would seem to be a problem with the generic zigbee controller then?

JimT · January 7, 2023, 12:07pm

Openhab’s zigbee binding might not have supported it yet. If you could provide the zigbee fingerprint as @anon71759204 mentioned above, it may be added into the binding in the future.

I don’t use the zigbee binding, but instead I’m using zigbee2mqtt to connect my zigbee stuff with openhab.

It depends whether you just want it to work right now, or you’d like to help the built in binding to expand its support.

mnybon · January 7, 2023, 12:17pm

I’ll get the fingerprint output as soon as possible. If you guys know where to look in the code I am probably not ready to do a PR at this point but I would love to have a look

dbeaudry92 · March 30, 2023, 11:39am

Here is the fingerprint output of my new Aqara Motion Sensor P1


openhab> zigbee fingerprint 54EF441000772XXX
|>| Node Descriptor
| |> Logical Type               END_DEVICE
| |> MAC Capabilities           [REDUCED_FUNCTION_DEVICE]
| |> Stack Compliance           22
| |> Server Capabilities        []
| |> Buffer Size                127
| |> Incoming Transfer Size     100
| |> Outgoing Transfer Size     100
|
|>| Power Descriptor
| |> Available Power Sources    [DISPOSABLE_BATTERY]
| |> Current Power Source       DISPOSABLE_BATTERY
| |> Current Power Mode         RECEIVER_ON_IDLE
| |> Power Level                FULL
|
|>| ZDO
| |> ManagementBindRequest      TIMEOUT
| |> IeeeAddressRequest         TIMEOUT
| |> ManagementLqiRequest       TIMEOUT
| |> ManagementRoutingRequest   TIMEOUT
|
|>| Basic Information
| |> Generic Device Class
| |> Generic Device Type
| |> Manufacturer Name
| |> Model Indentifier
| |> Product Code
| |> Product URL
| |> Date Code
| |> Application Version
| |> Software Build ID
| |> Hardware Version
| |> Zcl Version
| |> Stack Version
| |
| |>| Endpoint 1
| | |> Profile                  0104  ZIGBEE_HOME_AUTOMATION
| | |> Device Type              0107  OCCUPANCY_SENSOR
| | |> Device Version           1
| | |
| | |>| Input Clusters
| | | |
| | | |>| Cluster 0000 Basic
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> FAILURE
| | | | |
| | | | |>| Attribute Values
| | | | | |> FAILURE
| | | |
| | | |>| Cluster 0001 Power Configuration
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0003 Identify
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster FCC0
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | |
| | |>| Output Clusters
| | | |
| | | |>| Cluster 0003 Identify
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0019 Ota Upgrade
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> FAILURE
| | | | |
| | | | |>| Attribute Values
| | | | | |> FAILURE
| | | |
| | | |>| Cluster FCC0
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally

dbeaudry92 · April 1, 2023, 6:15pm

After adding the install code to enable Zigbee 3, I have better results. Before that, no battery voltage reading were available. Now I can read 3.
This is the new fingerpring with updated ZDO, Basic Information and Product code now available. Hope this can help.

openhab> zigbee fingerprint 54EF441000772xxx
|>| Node Descriptor
| |> Logical Type               END_DEVICE
| |> MAC Capabilities           [REDUCED_FUNCTION_DEVICE]
| |> Stack Compliance           22
| |> Server Capabilities        []
| |> Buffer Size                127
| |> Incoming Transfer Size     100
| |> Outgoing Transfer Size     100
|
|>| Power Descriptor
| |> Available Power Sources    [DISPOSABLE_BATTERY]
| |> Current Power Source       DISPOSABLE_BATTERY
| |> Current Power Mode         RECEIVER_ON_IDLE
| |> Power Level                FULL
|
|>| ZDO
| |> ManagementBindRequest      SUCCESS
| |> IeeeAddressRequest         SUCCESS
| |> ManagementLqiRequest       SUCCESS
| |> ManagementRoutingRequest   NOT_SUPPORTED
|
|>| Basic Information
| |> Generic Device Class       0
| |> Generic Device Type        227
| |> Manufacturer Name          LUMI
| |> Model Indentifier          lumi.motion.ac02
| |> Product Code
| |> Product URL                www.aqara.com
| |> Date Code                  Jun  9 2022
| |> Application Version        6
| |> Software Build ID          0.0.0_0006
| |> Hardware Version           1
| |> Zcl Version                3
| |> Stack Version
| |
| |>| Endpoint 1
| | |> Profile                  0104  ZIGBEE_HOME_AUTOMATION
| | |> Device Type              0107  OCCUPANCY_SENSOR
| | |> Device Version           1
| | |
| | |>| Input Clusters
| | | |
| | | |>| Cluster 0000 Basic
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> FAILURE
| | | | |
| | | | |>| Attribute Values
| | | | | |> FAILURE
| | | |
| | | |>| Cluster 0001 Power Configuration
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0003 Identify
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster FCC0
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | |
| | |>| Output Clusters
| | | |
| | | |>| Cluster 0003 Identify
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0019 Ota Upgrade
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> FAILURE
| | | | |
| | | | |>| Attribute Values
| | | | | |> FAILURE
| | | |
| | | |>| Cluster FCC0
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally

twemperor · September 3, 2023, 11:47pm

Hi! I’m running OpenHAB 4.0.2 and I just purchased an Aqara Motion Sensor P1, and I also only see the battery voltage channel (reading 3.1, currently). Has there been work to add the other channels to the binding, or is there information I can provide?

Zigbee Fingerprint (lots of failures…):

|>| Node Descriptor
| |> Logical Type               END_DEVICE
| |> MAC Capabilities           [REDUCED_FUNCTION_DEVICE]
| |> Stack Compliance           22
| |> Server Capabilities        []
| |> Buffer Size                127
| |> Incoming Transfer Size     100
| |> Outgoing Transfer Size     100
|
|>| Power Descriptor
| |> Available Power Sources    [DISPOSABLE_BATTERY]
| |> Current Power Source       DISPOSABLE_BATTERY
| |> Current Power Mode         RECEIVER_ON_IDLE
| |> Power Level                FULL
|
|>| ZDO
| |> ManagementBindRequest      TIMEOUT
| |> IeeeAddressRequest         TIMEOUT
| |> ManagementLqiRequest       TIMEOUT
| |> ManagementRoutingRequest   TIMEOUT
|
|>| Basic Information
| |> Generic Device Class       
| |> Generic Device Type        
| |> Manufacturer Name          
| |> Model Indentifier          
| |> Product Code               
| |> Product URL                
| |> Date Code                  
| |> Application Version        
| |> Software Build ID          
| |> Hardware Version           
| |> Zcl Version                
| |> Stack Version              
| |
| |>| Endpoint 1
| | |> Profile                  0104  ZIGBEE_HOME_AUTOMATION
| | |> Device Type              0107  OCCUPANCY_SENSOR
| | |> Device Version           1
| | |
| | |>| Input Clusters
| | | |
| | | |>| Cluster 0000 Basic
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> FAILURE
| | | | |
| | | | |>| Attribute Values
| | | | | |> FAILURE
| | | |
| | | |>| Cluster 0001 Power Configuration
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0003 Identify
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster FCC0 
| | | | |> Type                 Server [Input]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | |
| | |>| Output Clusters
| | | |
| | | |>| Cluster 0003 Identify
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally
| | | |
| | | |>| Cluster 0019 Ota Upgrade
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |
| | | | |>| Commands Generated
| | | | | |> FAILURE
| | | | |
| | | | |>| Commands Received
| | | | | |> FAILURE
| | | | |
| | | | |>| Attributes Supported
| | | | | |> FAILURE
| | | | |
| | | | |>| Attribute Values
| | | | | |> FAILURE
| | | |
| | | |>| Cluster FCC0 
| | | | |> Type                 Client [Output]
| | | | |> Manufacturer Spec.   No
| | | | |> Unsupported locally

alexkarageorgis · January 24, 2024, 9:55am

hi @twemperor did you manage to find a way to correct this - same situation

alexkarageorgis · January 24, 2024, 9:56am

hi @dbeaudry92 could you explain (as if to a child ) the install code thing? is it a code you find somewhere/create yourself? (i have a sonoff coordinator usb dongle - E) and my install code is currently blank.

so if you can help me understand where to find it
how to use it correclty?

alexkarageorgis · January 31, 2024, 7:40pm

Hey @twemperor any chance u saw my message;

twemperor · March 21, 2024, 6:22pm

Sorry for not seeing this message and replying sooner. I gave up on the Aqara motion sensor and bought a Sonoff Motion Sensor (MS01).

The Aqara is supported by Zigbee2MQTT, which can be hooked into OpenHAB. I wanted to stay with the Zigbee setup I already had.

alexkarageorgis · March 22, 2024, 3:23pm

yes I am aware - I actually use the MS01s - 3d printed an external case + added a big battery and they are super.

I just wanted the inteligence of the aqara sensor in terms of light sensor.

I think i will try the new sonoff sensors that are more of a presense sensor soon.