Xiaomi Aqara motion sensor not working with Conbee II

Hardware
,
1

I have a number of Xiaomi Aqara motion sensors in my house set up using deconz Conbee II. I’ve had them for about a month, and they have all been working fine for the last month, until now.

For some strange reason, some of that stats that one of them is reporting back to Conbee doesn’t seem to be relaying to Home Assistant and therefore not activating automations.

I don’t think this is a problem with the sensor, as the stats are appearing in Conbee every few minutes (as you can see from the picture below). But that information doesn’t seem to be appearing in my Home Assistant logbook, like the other same make sensors that I have.

Has anybody else had this problem or have a solution? To be clear, it’s just happening with one sensor out of the eight that I have.

Xiaomi
Xiaomi1326×543 33.8 KB

2

I’ve only been using HA for a week now. I have a couple of Sengled bulbs, an Osram A19 and a Sonoff BASICZBR3 connected to a Conbee II working fine. I just received and tried pairing a Xiaomi motion sensor and, after eventually getting it paired, I have no triggers? (In HomeSeer-speak they are called “child” devices). I haven’t figured out yet who/where to report this…

unk_model by unk_manufacturer
unk_model by unk_manufacturer308×531 15.3 KB

{
  "node_descriptor": "<Optional byte1=2 byte2=64 mac_capability_flags=128 manufacturer_code=4151 maximum_buffer_size=127 maximum_incoming_transfer_size=100 server_mask=0 maximum_outgoing_transfer_size=100 descriptor_capability_field=0>",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0104",
      "in_clusters": [
        "0x0000",
        "0x0003",
        "0x0019",
        "0xffff"
      ],
      "out_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0008",
        "0x0019"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.sensor_motion",
  "class": "zigpy.device.Device"
}
3

Shouldn’t you start your own topic?

4

That is an odd issue. I can only imagine it would be an issue with the integration, but then you would also probably get an error in HA about it.

5

Yes I was planning to but was perusing for other issues that might be like mine and happened to see this one asking a question similar to mine so I was adding my experience.

7

Ok, so I removed the entity and re-paired it using a less frequent “keep-awake” cycle (4-5 seconds). I now have motion, occupancy and battery sensors.

{
  "node_descriptor": "<NodeDescriptor byte1=2 byte2=64 mac_capability_flags=128 manufacturer_code=4151 maximum_buffer_size=127 maximum_incoming_transfer_size=100 server_mask=0 maximum_outgoing_transfer_size=100 descriptor_capability_field=0>",
  "endpoints": {
    "1": {
      "profile_id": 260,
      "device_type": "0x0107",
      "in_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0406",
        "0x0500",
        "0xffff"
      ],
      "out_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0019"
      ]
    }
  },
  "manufacturer": "LUMI",
  "model": "lumi.sensor_motion",
  "class": "zhaquirks.xiaomi.mija.motion.Motion"
}

Xiaomi Motion