Oh NOT good to hear, I just ordered a bunch more Aqara contacts too!
I wonder if there may be a way to turn off the repeating function?
Oh NOT good to hear, I just ordered a bunch more Aqara contacts too!
I wonder if there may be a way to turn off the repeating function?
No. It’s in the firmware.
I don't think that it affects everyone, and my C8 had issues for months w/Zigbee devices that myself, other experts/ambassadors here, and HE staff were never able to completely sort. So could very likely be mostly a "just me" issue, YMMV occurs a lot w/this stuff.
FWIW I haven't had any issues w/them causing problems w/Aqara contacts on my C7, just the C8.
They seem to be repeating nicely for my Sylvania lights
If mine ever get here I'll let you know
As Tom Petty wisely noted, the waiting is the hardest part.
Anyone tried/successfully got theirs behind their tv? I just tried to temporarily stick mine on the wall and adjusted some of the sensitivity… but I think it’s just picking up noise from the tv?
Just trying it in my bedroom and… it’s not working as ideal as I had hoped?
It seems to fail to reliably+consistently detect static motion while me (and my dog) are laying in bed.
I turned on ignore distance reports
I bumped fade time to 120. Detect sensitivity default 5. Distance default 6
I did change static sensitivity to 10.
Though not sure why seeing stuff like this in the log:
Motion reset to inactive after 37s
Was it @bptworld?
Nope, mine is behind a mirror in the bathroom.
I tried and it didn’t work. It wouldn’t go inactive.
I have mine mounted high up on the wall and it is tilted slightly down. USB cable is oriented to the side.
Looking at my main floor (using an old+modified robot vac map!) I’m sort of struggling or wondering about advice for how many and where to play my sensors for adequate presence detection.
It’s a large rectangular room but with a bit more of a jut-out space in the top left. That’s my “office”. To the right of that is the couch which faces the right wall, and you can see the grey area representing my tv stand.
Below all that towards the bottom right is my kitchen and the grey area is all the cabinets.
One definitely doesn’t cover the large space. Putting one on top and bottom facing inwards would cover a lot but likely miss me entirely any time I’m at my desk. But then… 3? Is that not crazy to cover one open area… even if it is large?
Well, another "problem" I am encountering. I moved the sensor in my bedroom to just beside my window but moreso facing my bed. This was the results overnight (I just have an automation to log to the motion change for my own usage)
app:852024-01-13 08:29:33.231 AMinfoBEDROOM MOTION ACTIVE
app:852024-01-13 08:22:39.159 AMinfobedroom motion inactive
app:852024-01-13 06:11:29.579 AMinfoBEDROOM MOTION ACTIVE
app:852024-01-13 06:03:08.134 AMinfobedroom motion inactive
app:852024-01-13 05:56:55.445 AMinfoBEDROOM MOTION ACTIVE
app:852024-01-13 05:55:52.586 AMinfobedroom motion inactive
app:852024-01-13 04:57:37.279 AMinfoBEDROOM MOTION ACTIVE
app:852024-01-13 04:51:08.966 AMinfobedroom motion inactive
app:852024-01-13 03:37:02.269 AMinfoBEDROOM MOTION ACTIVE
app:852024-01-13 03:28:00.056 AMinfobedroom motion inactive
I went to bed maybe around 10-11pm, so it knew I was there until 3:28am. Butttt then it kept losing my presence there. But perhaps the biggest issue: since waking up around 8am and leaving the room and going downstairs - now 3+hrs later, the device is STILL showing as motion active.
Yep, mine (just have one) goes through periods where it just stays stuck on active. Then it snaps out of it and is fine for a while until next time. It's not great.
I'm anxious to see how Inovelli's mmWve switch goes (I have one on pre-order to replace this Linptech) -- hopefully, it's more reliable.
I really wonder why a "reputable" vendor hasn't made one of these mmWave sensors yet -- is that because there's something inherently immature with this overall technology or what... I'd pay top-dollar for a Hue-quality version of this thing (and I'm sure Hue would charge exactly that )
There's just been so much talk and praise about these, and seemingly lots of love for the linptech one. Yetttt it's proven so unreliable and wonky, I don't see how people can actually be using them.
Ours works good enough most of the time -- not quite so terrible that I'll tear it out now. I really just got it as an experiment to learn more about mmWave knowing the Inovelli switch would eventually replace it.
Just like any other AliExpress stuff, I knew reliability & quality would be a wildcard, so in that respect, it's neither exceeding or failing any expectations I had.
I knew this Linptech would always just be a placeholder -- its quality issues mean it'll never have a permanent place in my setup. If Inovelli's sensor is equally flaky, then I'll dump both and wait until someone like Hue gets into mmWave.
I had one that would not send changes. As I stood in front of it, the Blue Led would blink... but I had no way of knowing if it had been that way for the past hour, for example. With roughly 5 seconds between me seeing it blink after I stood in front, doesn't tell much.
A power cycle would revert it to normal functionality. This was my 2nd device and I returned it for a replacement. I have since gotten a 3rd one. All 3 exhibit the same 'freezing' but work for weeks. As @hydro311 suggests, these will get replaced by something someday that is more reliable.
All of mine are 'coupled' with PIR motion sensors. Originally I thought they'd replace them, but for now, no. One of mine are aimed at my bed and it is in an evening light automation. If, when the PIR senses motion AND the mmwave does not, the lights come on. In other words, no human on or near the bed, but PIR motion detects new motion, then that must mean someone is entering the room 'for the first time this evening.' In logic terms, the mmwave 'gates' the PIR activating lights. What I don't want to happen is PIR motion turning on the lights when some one is asleep. A failed mmwave would cause exactly that. So far, in 6 weeks, that hasn't happened, although I did have to power cycle it about 4 weeks ago.
All of my light automation everywhere else in the house is primarily to turn lights off. Yes, the light On aspect is welcome, but more important to me is that they always go Off. This bedroom automation is the only lighting automation that has no Off aspect.
I'm suggesting you try the power cycle, verify that it is indeed 'frozen/stuck' and then if that is needed again in less than a month, return it for a replacement, unless your exchange window is about to close, in which case I'd replace it immediately.
I have 12 of these in my house. They are working great for me. I have not had any issues with them. Anytime one remains active for me it's for a reason...like a plastic bag left on the table that is getting sightly moved by a ceiling fan or a plant or curtain etc...
I have one device that was wonky, others have been fine. So three of four good, one stopped communicating w/hub even though was registering motion itself (blue blinky when motion, none w/no motion). Reset/re-join resolved. I have had general Zigbee problems so it's hard to separate those issues from something that is device specific, as it behaved the same as other Zigbee devices that I was having trouble with. After re-joining it I have had it sitting next to me for weeks and it's behaved normally.
I'd buy another if I needed more, but at this point mmWave is really only necessary for me in three locations, the office and the two bathrooms, and I have a bunch of Iris v2/v3 motion sensors that work fine for my other locations/use-cases.