Xiaomi vs Aqara door/window sensors

Devices & Integrations
22

Mine is just progressed a little more.

23

And I believe yours has the correct fingerprints for Aqara?

1 Like
24

I only have the temp/humid aqara sensors and have no problem having it show up as a ā€œthingā€. Not sure the reset procedure is the same but for me. Hold down the button until the light blinks 3 times. Turn on ST discovery and press the button on the sensor a couple of times.

25

Just went through pairing 18 of these and they were all working beautifully using @ArstenA device handlerā€¦ But like clockwork after each sensor is online for about 2 hours they stop communicating and go unavailable. Battery state shows 100% for all. One thing I noticed is my hub has insecure rejoin disabled and I am unable to toggle it on. Not sure if this is a bug or if Samsung is forcing it that way for security.

I have tried power cycling the sensors while in learn mode, resetting my hub (removing the location) to no luckā€¦ Anyone run into this? Am I being punished for being a cheap bastard? :slightly_smiling_face:

26

I am on Android and have no issue toggling insecure on or off. Maybe try it in IDE.

Screenshot_20170924-081434
Screenshot_20170924-0814341080Ɨ1920 179 KB

27

I donā€™t even have the option for managing Zigbee in the ide. Are you using a v1 or v2 hub ?

28

I have both V1 and V2 hubs. There is no zigbee utilities in V1 Hub and I donā€™t think the sensors stay connected with V1 hub.

29

Thanksā€¦ I just picked up a V2 and I have the Zigbee utilities now. Did you need to enable insecure rejoin to get these to work ?

UPDATE: Everything is working great with V2 and Insecure rejoin disabledā€¦ So V1 will definitely not work with these.

30

I have a V1 and Iā€™m coming to the conclusion these are not going to work for me (Aqara door sensor). Bummer. Iā€™ve tried a number of device handlers and they pair easily but drop out after about an hour. I have other Zigbee items, is that not enough of a mesh to keep it online?

1 Like
31

Some believe it is the other zigbee mesh devices that cause the Xiaomi devices to drop.

32

my other devices are lights so not really negotiable. I can live without the extra cheap window sensors, but it is a shame. Is there any way to fix the ā€˜interferenceā€™ or whatever is happening?

33

Donā€™t think you can fix this. I have no clue why this is happening.
For this reason i went for a Xiaomi-only zigbee setup (and zwave) awhile ago, zigbee sensors and plugs for the mesh, this seems to work very well, no dropouts in months. (had one dropout in 6 months)
I now also added the Ikea Tradfri light bulbs (which also have a repeater), these seem to work very well together with the Xiaomiā€™s.

34

KI might have found the actual battery info for the Aqara.
This has taken quite some time because the catchall with battery info is only updated every 50 minutesā€¦
Iā€™m not sure about this. The battery-info i am comparing this to is not reliable: The other Xiaomi sensorā€¦

If i am correct then i have to figure out a factor, and the battery info go in steps.
Iā€™ll let you know if i have more info, i have to wait for one more catchall for some confidence.

On the other hand, i might be completely wrongā€¦

2 Likes
35

Let me know if I can help!
I searched for quite some time and did not find the battery report. It also seemed like my sensors were sending different data from other ppls.

36

If the battery reporting issues only happen with the newer Agara sensors and the originals seem nearly identical, does this mean itā€™s better to get the old models? Looking to place an order with Gearbest.

37

The issue with these sensors is the fact that they donā€™t report in quite often. The ā€œoldā€ xiaomi reports every hour and the Aqara reports every 50 minutes. It doesnā€™t matter that much, but 10 minutes closer to Zigbee specs.

38

I posted that i might have found the battery for the Aqaraā€™s
Still not sure yet, itā€™s quite difficult to get this. You cannot just compare the catchallā€™s from the Xiaomi to the Aqaraā€™s. First of all is that the position is different, and next is that the Aqaraā€™s battery indicator is not 0-100% like the regular Xiaomi.

What i did it compare this value over a longer period of time, swapped batteries and used a drained battery (used a light) to see if the value drops.
The weird part is that when i used this drained battery, it started out with a very low value, but then the value slowly increased. to about 50%. Not sure how far i drained the battery since i donā€™t have a tester and the regular Xiaomi battery indicator is not reliable.
The persentage raised in the following matter:

(used depleted battery, drained with light)
20:33 9 = 4%
21:24 39 = 17%
22:14 59 = 26%
23:04 59 = 26%
23:54 79 = 35%
00:45 89 = 39%
03:15 99 =
05:46 109 =
09:57 119 = 52%
11:38 119 = 52%

Now (12:04) still at 119.

I now have a lot of (catchall) data which i used and came to the following:
I think the battery indicator is at value 6. I saw the following values:

Pos 6 values:

  • 233 = 100%
  • 229 =
  • 213 =
  • 219 =
  • 209 =
  • 199 = 92% according to the other Xiaomi
  • 133 =
  • 123 =
  • 119 =
  • 109 =
  • 99 =
  • 89 =
  • 79 =
  • 59 =
  • 39 =
  • 9 =

I used a factor of 2,25 to calculate to percentage, 2,33 might be more accurate but didnā€™t convert to the old Xiaomi battery value.

I might be completely wrong here, again. So please feel free to try this and report back to see if this seems right. (No is also an answer :wink: )

39

Can you post the raw message fro. The catchall?

I have seen multiple messages fall into the catchall before.

40

I only have the cluster data, not the catchall itself.
Only from the last few:

Cluster.data: [1, 255, 66, 29, 1, 33, 119, 11, 3, 40, 27, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 1]

catchall: 0104 0000 01 01 0100 00 283F 00 04 115F 0A 01 01FF421D0121770B03281B0421A81305217200062401000000000A21F7C0641001

I was only interested in cluster data, i can post it if you want

41

And the clusterdata:
\ 6-10-2017 22:29:50: Cluster.data: [1, 255, 66, 29, 1, 33, 199, 11, 3, 40, 23, 4, 33, 168, 19, 5, 33, 110, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
6-10-2017 23:20:00: Cluster.data: [1, 255, 66, 29, 1, 33, 199, 11, 3, 40, 23, 4, 33, 168, 19, 5, 33, 110, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
6-10-2017 00:10:10: Cluster.data: [1, 255, 66, 29, 1, 33, 199, 11, 3, 40, 23, 4, 33, 168, 19, 5, 33, 110, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
91% 7-10-2017 19:24:30: Cluster.data: [1, 255, 66, 29, 1, 33, 199, 11, 3, 40, 23, 4, 33, 168, 19, 5, 33, 110, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
NEW 7-10-2017 20:41:20: Cluster.data: [1, 255, 66, 29, 1, 33, 213, 12, 3, 40, 23, 4, 33, 168, 19, 5, 33, 112, 0, 6, 36, 2, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
92% 7-10-2017 22:52:17: Cluster.data: [1, 255, 66, 29, 1, 33, 199, 11, 3, 40, 23, 4, 33, 168, 19, 5, 33, 113, 0, 6, 36, 8, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
92% 7-10-2017 23:42:27: Cluster.data: [1, 255, 66, 29, 1, 33, 199, 11, 3, 40, 24, 4, 33, 168, 19, 5, 33, 113, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]

First report (19:43) is wrong: 225, should be very low (batt depleted using lamp)
15-10-2017 19:43:36: Cluster.data: [1, 255, 66, 29, 1, 33, 225, 10, 3, 40, 27, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 3, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
low 15-10-2017 20:33:51: Cluster.data: [1, 255, 66, 29, 1, 33, 9, 11, 3, 40, 26, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
15-10-2017 21:24:06: Cluster.data: [1, 255, 66, 29, 1, 33, 39, 11, 3, 40, 26, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
15-10-2017 22:14:21: Cluster.data: [1, 255, 66, 29, 1, 33, 59, 11, 3, 40, 26, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
15-10-2017 23:04:36: Cluster.data: [1, 255, 66, 29, 1, 33, 59, 11, 3, 40, 25, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
15-10-2017 23:54:52: Cluster.data: [1, 255, 66, 29, 1, 33, 79, 11, 3, 40, 25, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 00:45:08: Cluster.data: [1, 255, 66, 29, 1, 33, 89, 11, 3, 40, 25, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 01:35:21: Cluster.data: [1, 255, 66, 29, 1, 33, 89, 11, 3, 40, 25, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 02:25:39: Cluster.data: [1, 255, 66, 29, 1, 33, 89, 11, 3, 40, 25, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 03:15:53: Cluster.data: [1, 255, 66, 29, 1, 33, 99, 11, 3, 40, 24, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 04:06:07: Cluster.data: [1, 255, 66, 29, 1, 33, 99, 11, 3, 40, 24, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 04:56:22: Cluster.data: [1, 255, 66, 29, 1, 33, 99, 11, 3, 40, 24, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 05:46:37: Cluster.data: [1, 255, 66, 29, 1, 33, 109, 11, 3, 40, 24, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 06:36:52: Cluster.data: [1, 255, 66, 29, 1, 33, 109, 11, 3, 40, 24, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 07:27:04: Cluster.data: [1, 255, 66, 29, 1, 33, 109, 11, 3, 40, 23, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]
16-10-2017 09:57:47: Cluster.data: [1, 255, 66, 29, 1, 33, 119, 11, 3, 40, 24, 4, 33, 168, 19, 5, 33, 114, 0, 6, 36, 1, 0, 0, 0, 0, 10, 33, 247, 192, 100, 16, 0]