[OBSOLETE] Xiaomi Sensors and Button (beta)

I see the same pattern for Xiaomi button:

Parsing ‘catchall: 0000 8021 00 00 0140 00 C101 00 00 0000 00 00 4584’

catchall is not complete and that is why it doesn’t resolve the batter level.

Then I have:
SmartShield(clusterId: 0x8021, command: 0x00, data: [0x45, 0x84], destinationEndpoint: 0x00, direction: 0x00, isClusterSpecific: false, isManufacturerSpecific: false, manufacturerId: 0x0000, messageType: 0x00, number: null, options: 0x0140, profileId: 0x0000, senderShortId: 0xc101, sourceEndpoint: 0x00, text: null)

whatever it means.

@a4refillpad could you advise how does it work, and maybe think what could be a reason of not complete catchall message ?

Do you think maybe handler needs some update ?

For the working button i have:

Parsing ‘catchall: 0104 0000 01 01 0100 00 BC42 00 01 1234 0A 01 02FF4C06001001210A0C21A813240100000000215E01205B’

so again it seems to be complete.

Interesting, Zigbee OTA is disabled on my hub.

Never made a difference before and I have switched the setting a few times. It actually updated my Samsung Multi Sensor a few times in the past week or so. I would leave it as it is. :grin:

I think it is simply down to the fact that it does not handshake correctly and doe not establish the chaeckin correctly, because of this it does not read the correct info or it does not get sensor to send the correct info and so it does not pick up the checking every hour.

No idea what ST are up to though as my existing ones dropped off the system earlier and have not come back. Although they are still connected somewhere as if the connection drops completely then the little led on the units lights up with a trigger whereas mine are still all off. Something is really messed up somewhere.

I added 3 of the new ones back again a short while ago and 2 f them came up with the battery straight away. This never happened before so I really think that the Software engineers are playing with the Cloud settings, cannot explain it any outer way tbh.

Today I tried paring Xiaomi magic cube and looks like it have same issue. Paired and worked fine but then lost connection.

Yeap might be. I have repaired my button and temp sensor after seeing your post, currently still works and I have battery showing for button, which is a progress. Now have to wait and see if it gonna work tomorrow after night.

Not sure if it made a difference but I turned off the hub and got the battery out for one hour as adviced to reset ZigBee mesh.

Does anybody have a solution for really inconsistent updates from the Xiaomi Temperature/Humidity Sensors? I’ve been logging every 15 minutes. and two sensors seem to regularly go 12+ hours without a temperature report. They’ve been doing this since I bought all 3… The “Baby Room” sensor is approximately 1.5m from the “Bedroom” sensor, with the “Den” much further away, so I don’t think its signal strength related.

Put all 3 together in one place and then compare. Maybe the temp in one room doesn’t change much and that is why you don’t see the change. Check also the “last events” on each of the sensors in developer idea in given device settings, to see if the updates were send or not.

Should have mentioned that the “last events” are sometimes updating with noting else showing in the history over the same flat-line periods. When they are not, I suspect it is similar to the connection problems discussed above. I’ve added some more logging to try and see how often this happens.

Baby Room and Bedroom should be pretty consistent profiles between the two. There is no way my bedroom is staying within 1 degree over the same period that the baby room is fluctuating 4-5…

A little update on mine is I found that if I pressed the small button just a press no hold it came straight back online

I paired mine a couple of months ago and it’s been solid ever since.

So maybe it is to do with this new firmware.

@ArstenA have you worked out what the aqara door sensor is trying to send here I dont think it will solve the problem just trying to understand zigbee.

Wonder if is is down to the Aqara sensors. I have never had any sensor come back online with a single button click in the past. May try to get hold of a single unit although that may still take 3 weeks to get to the UK lol.

What with all my other zigbee sensors going offline earlier today I am slowly losing my patience with this tbh. I was happy before as was trying to get things working with the new hub f/w but now that all my existing zigbee sensors have gone including Samsung’s own one and there has been zero info from the staff I just feel let down. After all how long does it take to write a message that they are still looking at the issues and will keep us updated…

Nick from Smartthings provided some insight in the new firmware thread. Not directly related to Xiaomi sensors but still…

I started to look into this and my aqara door/window sensor sends me this message:

SmartShield(clusterId: 0x0000, command: 0x0a, data: [0x01, 0xff, 0x42, 0x1d, 0x01, 0x21, 0xe5, 0x0b, 0x03, 0x28, 0x15, 0x04, 0x21, 0xa8, 0x13, 0x05, 0x21, 0x35, 0x00, 0x06, 0x24, 0x01, 0x00, 0x00, 0x00, 0x00, 0x0a, 0x21, 0x00, 0x00, 0x64, 0x10, 0x00], destinationEndpoint: 0x01, direction: 0x01, isClusterSpecific: false, isManufacturerSpecific: true, manufacturerId: 0x115f, messageType: 0x00, number: null, options: 0x0100, profileId: 0x0104, senderShortId: 0x3a1d, sourceEndpoint: 0x01, text: null)

I am starting to make sense of it…
command 0x0a = Report Attributes
0x01, 0xff, 0x42,
0x1d, = Message Length
0x01, (CMD) 0x21, (U16) 0xe5, 0x0b, (3045)
0x03, (CMD) 0x28, (S8) 0x15, (21)
0x04, (CMD) 0x21, (U16) 0xa8, 0x13, (5032)
0x05, (CMD) 0x21, (U16) 0x35, 0x00, (53)
0x06, (CMD) 0x24, (U40) 0x01, 0x00, 0x00, 0x00, 0x00, (1)
0x0a, (CMD) 0x21, (U16) 0x00, 0x00, (0)
0x64, (CMD) 0x10, (BOOL) 0x00 (FALSE)

I do not know what this data means…

Perhaps the 3045 is millivolts?

I’m is doesn’t have that much data

SmartShield(clusterId: 0x0000, command: 0x0a, data: [0x01, 0xff, 0x42, 0x09, 0x04, 0x21, 0xa8, 0x13, 0x0a, 0x21, 0x00, 0x00], destinationEndpoint: 0x01, direction: 0x01, isClusterSpecific: false, isManufacturerSpecific: true, manufacturerId: 0x115f, messageType: 0x00, number: null, options: 0x0100, profileId: 0x0104, senderShortId: 0x57f3, sourceEndpoint: 0x01, text: null)

yeah you only have commands 0x04 and 0x0A. Not sure why…
But that said, the byte I was using for the battery % is NOT correct. I am not sure which is…

Here is a comparison of the data from an aqara door switch and an original door switch.
The aqara seems to be more compliant than the original, but the data is manufacturer specific so it is difficult to know what the data means.

There is another individual that has posted his Aqara Door Sensor data in another thread. He has an addiitional attribute more than mine. So I am not sure how to get these devices to configure all the same, but we need to do some more investigation.