Motion Sensor V2 with Home Monitoring Useless

Sure you can do that, but don’t expect a response. Lol

1 Like

Not a single one in 2 years and hundreds of logs.

1 Like

Did you try removing and reinstalling batteries?

Yup… no luck.

Except for putting it in the driveway and running over it, I’ve done everything I know to do to try to get it to work right, instead of the plastic piece of crap it is.

I love Wyze and have pushed it on several of my friends and family. But I’m afraid if they don’t stop putting out POS stuff, people will sour on them, even big fans like me. I’m not bashing them, like I said I’m a big fan, just don’t want to see them crash and burn.

1 Like

Sure hope your sensor is a one-off. I just ordered three motion sensors for my system. Guess I’ll see if they’re all lemons.

Quick update…

After speaking with support, who I will add was fantastic, I finally figured out what was causing the issue with the Wyze Sense v2 motion sensor giving false alerts.

I deleted and re-added the sensor, which I had done 2 or 3 times before, but this time, I added it within the Home Monitoring tab, in the Home/Away section, instead of from the main “Home page” of the app. The sensor now seems to be working as it should.

Hope this helps others having the same issue.

3 Likes

Interesting. What this something support specifically recommended?

I had a similar issue recently where one of my V2 Motion sensors started give false alerts. I stuck it inside a drawer for a couple days and it stopped giving false reports. I then removed it and added it back and it has been fine since. I don’t recall if I added it from the main app screen or from withing the HMS section.

Yes support recommended it.

I had been experiencing the same issue. Motion sensor was setup and would report movement when I was in the basement office, no one upstairs or while away it would still report movement. I could not reliably use the Away alarm at all.

I removed and re-added but from within the Monitoring part as @mbrindle suggested. I left he house yesterday, didn’t set the alarm but I had the default setup for the app to notify on every movement detected. While away for a few hours I didn’t get any notifications.

I’ll continue to test and monitor but I believe my issue is resolved.

1 Like

I have this exact same problem. I’ll try deleting it and re-adding it within the home monitoring service tab. But I don’t understand why it should make a difference. For example, I have the V2 door sensors connected to the hub, but outside of the home monitoring service tab, and they seem to be working fine. Can somebody please explain the difference between adding a V2 sensor on the homepage versus the home monitoring service tab? I just recently set everything up, and added it to the homepage, with the intention of eventually looking into the home monitoring service. But I wasn’t ready to do that yet. Thanks.

I should note that my issues with one of the sensors resumed after a while. Repeated all the steps again to “reset” it and it again started false positives. Eventually, support sent a replacement, which I have yet to install.

This is EXACTLY what’s happening to 2 of my sensors and Noonlight has called me now twice. I first thought it was my curtains in my front office moving from the heat vent but I looked and it’s every 13 minutes my motion sensor goes off.

I will delete the 2 sensors and add them through HMS system and check to see if it fixes it. I’ve only had HMS since early December and these sort of glitches scare me.

I’m it fixes it for these 2 sensors but I have 5 others in my house that I feel like is only a matter of time now.

I also feel like I need to keep my phone with me at all times due to this glitch to ensure I don’t miss a call from Noonlight and the cops show up at my house. That’s a lot of stress I don’t need from a system that’s suppose to keep your mind at ease. Maybe this wasn’t the best replacement to Nest Secure, maybe I’ll look at Ring or Simplisafe if this happens again, cut my losses and toss this out.

If your motion sensor is near a door sensor it can create this situation. Try moving the motion sensor further away from any door sensors you may have.

1 Like

Thanks for the reply, none of them are within at least 6 ft of an Entry sensor. I did delete both Motion sensors and readded them via the HMS processes vs the general + icon on the main screen and so far that has reset them without having the 13 min motion sensor alert.

Thankfully renaming the motion sensors the same name, I didn’t lose any Rules and thus didn’t have to reset any of those up. I did have to readd those Motion sensors to my Away mode, which was expected.

Hopefully this fixes them in the short term, I have a year with Noonlight, depending on how the next 10 months go, maybe I’ll stay or maybe I’ll switch, again. :person_shrugging:

The app doesn’t seem to care about names. It uses some other identifier (mac?) for the sensors.

1 Like

I am confused. How do you add the sensors from the HMS menu? The only place I see in the app where you can add a device is from the Home/Main page.

Never mind… I found it :slight_smile:

Mine too was going off exactly every 13 mins. I did what @Mynus64 mentioned (remove and then re-install through the HMS section) and the problem has been resolved for the last couple of days. I may wait another day or two before actually enabling for Moonlight monitoring, just to make absolutely sure it’s working properly.

1 Like

Went through the remove the batteries, delete and re-enroll routine a few months ago, and now the dreaded false motion event every 13 minutes is back again. Always less than 1 min events. Support seemed like they had never heard of the issue before … Clearly Wyze has a problem with these devices based on all the reports, wish they would post the cause and how they plan to fix it permanently.

[Mod Note]: Your topic and replies were merged for consistency in grouping posts in identical topics.

Mine are all over a year old. Many with the original batteries. All are still operational. I had 3 that gave me the same problem, but I fixed it: