Add More Actions for Wyze Rules

A post was split to a new topic: Remove the annoying “rules suggestions “

A post was merged into an existing topic: Allow cams to automatically connect to multiple networks (multiple WiFi & mobile/cellular networks, etc.)

IR LEDs “when motion is detected”

I voted on the “rules” thread for having a rule to turn night mode on, but wanted to propose a potentially more elegant solution here too.

When the IR LEDs are on, they attract bugs, and reflect off rain drops and even a light mist. This causes a lot of false events and in the case of a pan camera with motion tracking, it is constantly tracking all over.

There are many scenarios where there is sufficient ambient light to detect motion, but not enough to have a good clear image. So adding an option to the IR LED control for “when motion is detected” in addition to “on” and “off” would be a great solution for this. Reducing wear and tear on the motors and false events. As far as shutting them back off after I’m assuming it would just shut them off either x minutes after the motion originally started, or maybe x minutes after motion is no longer detected. Of course those pesky bugs and rain may cause it to stay on in the second scenario, but hopefully within a reasonable amount of time it would have 30 seconds or a minute of nothing to be able to shut off.

The trigger to detect motion and AI types already exists including implied motion no longer detected. All we need is the action to turn on/off IR. The needed action is currently listed in the table above, 1st post:

Without this IR on/off action, the only workarounds are to turn IR off on your cam and either install a 3rd party IR illuminator or repurpose a 2nd cam for sole purpose of IR illumination.

That is what I have done and switched off the camera LEDs permanently. Positioning the illuminator away from the camera stops any reflections from the illuminator to the camera. I used 940nm LEDs and have not noticed them attracting any insects.

I obviously have to switch the cameras to night vision at night and switch off night vision during the day - hence why I would like a rule to do the switching automatically at set times. I have eight cameras, all if which have to be switched manually (and individually) every day.

1 Like

Thanks, didn’t notice that action was just focusing on the ones with voting attached to them, so looks like it is already covered. Fingers crossed.

I also noticed that when the pan v3 aims downward, even if it can’t “see” the base, the lights reflect and wash out the image. I’m planning to either paint or waterproof tape the top of the base matte black (did a test with black paper and it solved the issue).

The area where I have it, it was originally upside down and that was a better setup, keeping the base totally out of the way, but I found that even having taken measures to protect it from water, it finds a way in, so had to swap to right side up.

1 Like

Can’t you just leave night vision on auto with the LEDs off? Or does the illuminator confuse it?

There is a street light nearby that forces the camera into day vision but there are dark shadows cast by the light that day vision cannot see into. Switching on night vision and using an IR illuminator allows me to see details in the shadows.

1 Like

Ah gotcha. I have one (an OG) in a similar situation but I have a rule to turn on the spotlight when motion is detected which works well for me (it never goes into night mode and there is plenty of light to see most stuff, and the spotlight makes sure a face etc is visible). So yeah I can see how a rule to turn on/off night vision on a schedule would be useful in cases like yours.

One thing I’ve noticed about rules, they do seem to always do the initial action properly (though I may have just not noticed when they don’t), but sometimes they don’t do the opposite action - like turning the spotlight back off after 1 minute. Sometimes it will be on all night after the rule fires. Fairly rare but does happen sometimes. Odd, I guess maybe the second command doesn’t always make it to the camera or something. Some of my cameras are “moderate” wifi signal so I’m guessing that is the reason.

I use the 940nm infra red lamps because they can illuminate an area without annoying my neighbours as 940nm cannot be seen by humans but the cameras can.

Also helpful if there is very little light due to no moonlight. All the illumination is from IR illuminators -so anyone looking will not see the light - it looks pitch black and they would need a flashlight to see anything

The streetlight can be seen above the roofline and the illuminators allow the camera to see in the shadows caused by the streetlight

With illuminator switched off the street light stops the camera seeing the cars


Opening and closing garage door trigger rule for the garage door opener, based on location?

Location rules for opening a garage door does get risky though. Phone Location is a tricky subject. Sometimes, even at home, people’s location accuracy can vary dramatically. If your phone is in suspended status (screen off, in your pocket, in your basement, etc) your location can be off by several hundred feet or more and bounce back and forth in and out of your home, which would then cause the garage to open and shut repeatedly. There are ways to ensure the location stays more accurate, but then your phone battery drains really fast.

All of the following red dots are location pings of a phone logged between 3:22pm until 3:45pm. and the phone was 100% of the time at that house with the pin and orange circle around it. Yet, sometimes the estimated location bounced way outside of the zone it is configured to detect. Look how many houses away it thought she traveled, sometimes in less than 10 seconds. It sometimes estimated that she traveled all the way out and back in 10 seconds, which is impossible on foot (55mph in a straight line through houses walls, fences, etc,):

For scale, those dots are ranging over 500ft in the above screenshot, but sometimes they happen even farther away for some people depending on the conditions. I have seen location pings off by 800ft+.

So it would be really risky for Wyze to allow a garage door to open based on a location rule unless the location was based on more accurate data than the phone’s passive location. On the other hand they could force location High Accuracy mode like Google Maps and some other apps do when they are actively using high accuracy location tracking, but then it would be doing so 24/7 in the background and totally kill your battery fast. That would make a lot of people really mad.

It’s a tough thing to balance. I’m not saying there are no solutions, just want to help some people understand why it is not as simple as it might appear.

(The above location pings and map are using Home Assistant Companion app and telling the app to just pull the location sensor data when the phone normally pulls it and use default accuracy limits and estimates and just use that same data that it’s pulling anyway, rather than telling it to pull special data on an extra interval or force the phone to always pull high accuracy mode at a faster interval which would kill the battery…Home Assistant Companion app has lots of customizable location options, and the above is basically using the phone defaults…this is with a Google Pixel 8 Pro, but I see the same thing on basically every other model that pulls phone default location settings unless you force high accuracy mode constantly to drain the battery fast…also, it should be mentioned that the phone itself does list what the +/- accuracy estimate is for the location, so it might know a person is somewhere within an 800 ft radius, and estimate they MIGHT still be at home…so Wyze could technically compensate for large location ranges, and even increase the home zone range…I’m not saying it can’t be done, but there are pros/cons for each solution and they will have to debate how much risk to allow for something like this).

Personally, I wish Wyze would let us choose our own location preferences like Home Assistant does so each person could decide for themselves what is adequate location accuracy for our preferences/tolerance and require multiple pings within a certain radius before it triggers. There are potential solutions, I’m just saying it is complicated and risky, and that’s why it may not be a simple immediate addition.

Still, I would love this too! I actually do this in Home Assistant right now using a ratGDO device and location considerations where I am able to set my own thorough conditions so there aren’t false triggers based on location like I was talking about above. It would be cool if Wyze figures out a more simple solution to do this too. :slight_smile: Just thought I’d share my knowledge on the complications involved since I recently learned about it all so I could set this up for myself in Home Assistant. :+1:

I tried location once, it drained my phone battery in like 6 hours, so useless feature as far as I’m concerned.

I LOVE location depending on how it is implemented. The difficulty for an app developer is determining which kind of location to use, including whether to force high accuracy, what interval and all sort of things like that. Hard to suit everyone’s needs/preferences. I don’t use it with Wyze now because I don’t know what kind of location settings they use.

I would prefer we are given options like the Home Assistant companion app allows. If that was resolved so people could set their own location preferences for accuracy, frequency, or just updating every 15 min or so when the phone OS sensors update anyway, that would make it a great option, but I think all of that needs to be considered in order to make it a great rule feature.

I don’t think they will do that though, because 1) Almost no apps give you those options either 2) lots of people would just be more confused and not understand any of the options. So it’s easier to just do it the way they did like everyone else does.

Yeah I mean only with the Wyze app, it drains the battery, runs the GPS non stop even when the screen is off. Phone is hot in your pocket. I use it with other stuff fine.

1 Like

Would like to be able to set rule to turn Infrared (IR) emitters on/off at sunset and sunrise, to avoid glare cause by nearby streetlight. Also would like to establish rule to turn notification on/off when at home or away.

1 Like

Action for any doorbell but selfishly the Wyze doorbell v2: do not disturb mode.

Related to being able to disable the chime on the actual doorbell but not exactly the same.

Use case: every parent that wants to automatically put the doorbell in dnd mode at specific times of day/exit dnd mode at specific times of day so the doorbell chime (either on the video doorbell or wired into the house) don’t ring when they are sleeping/napping.

1 Like

Currently, the garage door will open/close as an Action but not as a Device and Service Trigger. Example, when garage door is open, stop x camera notifications.

When I am working in the garage, my garage camera, driveway camera, and doorbell camera go crazy with notifications because I’m working in the garage. if the garage door is open, it’d be nice to be able to trigger turning off other notifications (I already receive a notification when the garage door is open so I would know when it is being opened unexpectedly).

I like the intruder alarm on the doorbell but I don’t want it for a chime all the time. Would be nice to be able to select that to alarm if one of my outside cam sirens goes off.

This would be great for cams in kid rooms. My son gets woken up by the sound of the click from the IR auto-switching on and off as lighting changes (cars driving by, etc.), so if I could schedule it instead of having it on auto, that would be perfect. As an interim solution, I just have his set to IR on all the time, which isn’t great during the day, but it gets the job done.