Well more likely I'll return them, but I liked the dramatic headline.
I have two of these that I got for an application where I wanted a small contact sensor. I didn't notice at the time that they weren't the newer T1 Zigbee 3.0 version (MCCGQ12LM).
They are small, but they are also undependable. I paired them about three weeks ago, using Marcus' drivers, and they've been sitting in my spare parts box waiting for me to get around to my project. I pulled them out today and both are disconnected.
I'm going to be putting them in a spot that will be very tedious to have to get to if they fall off again. I'd rather return them if these just aren't going to play well. From other older posts it appears they are not fully Zigbee compliant.
Postage is way higher to Singapore! I'm in Toronto and have a Mijia Multimode Gateway I want to try them with. I heard it doesn't work, but I don't believe them. Will test for the good of the community
I have 2 contact sensors on my network and they work just fine, however I added another 2 a while back which then started to mess things up. Personally, If I could return them I would and buy something that's more stable rather than messing around trying to get it to work for the sake of a small saving.
I’m returning mine. They connect once and that’s it until you press the button again. It kind of defeats the purpose, unless the goal is for you to watch for a leak. In that case, they work great.
Yes I'm also using the drivers that Marcus created, and have a strong mesh that works very well, never had any zigbee device fall off it or misbehave - these contact sensors are the first, and I was so surprised that it took me about 5 minutes to really believe they were no longer connected.
All the repeaters were Xiaomi-compatible (5 Tradfri outlets, 6 Tradfri repeaters, 4 of @iharyadi's environmental sensors). So that's 15 repeaters for ~60 Xiaomi devices + 2 yale locks + 6 Sengled bulbs.
Everything was relatively stable with @markus' drivers. Two issues began with changes in @markus' drivers around June/July of last year.
There were missing events for the contact sensors and Aqara vibration sensors with @markus' drivers, but not @veeceeoh's drivers.
Once in a while there were missing events for my locks.
Moving everything to @veeceeoh's drivers resolved both issues, but the devices were more prone to fall off-line.
A few weeks ago, I moved all the Xiaomi devices to Mijia smart hubs and bring them into Hubitat via Node-RED. Everything has been rock stable and there are no missing events for my Yale locks either.
So my general feeling is that while @markus's drivers do a great job at keeping Xiaomi devices paired/online (when there are Xiaomi-compatible repeaters), it does come at a cost - especially when there's a large number of such devices.
I lost almost two years worth of battling with these devices (I'd had them over 5 years, initially on ST).
I have 5 wireless double boutons left, connected to deCONZ. The rest (8 contacts, 10 motion, 10 no neutral double switches, two Xiaomi hubs, 5 buttons) all went on ebay. Funnily enough selling them pretty much what I paid for them and in some cases more. I guess because they didnt have to come all the way from China
I replaced all the device with Iris motion and contacts, and Zemismart switches (non neutral).
My Zigbee has been the healthiest its been in a long time, and I really don't miss fighting with those damned devices any more
I do love the tiny form-factor of these contact sensors, but not going to add another hub, and not going to use them if they aren't 100% reliable in my house.
I should be "once bitten, twice shy" but am wondering if the newer Zigbee 3.0 version ( MCCGQ12LM) is any better (on it's own, no Aqara/Xiaomi hub)? Main reason I'm even thinking about it is that these are so small they are very easy to "hide in plain site" and my wife HATES seeing smart gear stuck to things around the house.
