Curious, if others are noticing delays with their automations?
I have a few shortcuts that I use to adjust the brightness of color bulbs in my living room. These shortcuts used to work nearly instantaneously. For the past week or more, when I click on one of these shortcuts I have to wait close to 30-seconds for the brightness to adjust. Yet if I go directly to the bulb in the app, my brightness changes are instantaneous.
Last night, I setup a new automation. When my office camera detects a person, the automation should turn on a WYZE color bulb for 5-minutes. I was really hoping this would be close to instant. Instead, once again, it is taking about 30-seconds to turn the bulb on. When I check my camera events, it detected a person long before the bulb is turned on. If I go to manually turn the bulb on in the app, once again it is instant.
I have tried powering off the WYZE equipment for at least 30-seconds then powering it on again. When it comes to the response of these automations, the power cycles have had no impact. Over this past weekend I read a post from @carverofchoice who mentioned WYZE was having issues with automations as of late. In that post, it sounded like the issues were resolved. Again, just wondering if others are having issues and if anyone knows more about the automation problems that WYZE reportedly resolved?
I first saw @Bam report this about a week ago as the volunteers were trying to make Wyze aware of the issue, and apparently it was also discussed on Facebook (which I don’t use) and Reddit (which I rarely use). At the time, I created a couple of Shortcuts to test for Plugs and Bulbs, and I was seeing them execute ~2½ minutes after tapping in the app. For a few days now, though, execution has been nearly instantaneous, so I also thought the issue was resolved.
If you’re still experiencing issues, then you may want to log it and follow up by reporting it to Support to keep it on their radar. I’m not sure what else to suggest, as I suspect it’s an ongoing server-side glitch.
I did make a post on Facebook 5 days ago about this issue. I thought at the time that there may have been an AWS issue. Someone had opened a ticket and the response from Wyze that they had “a short term connectivity issue with Wyze Automations.” About a day later, my issues resolved and all my shortcuts are working as expected. And I just tested a couple to confirm proper operation.
As @Crease suggested, if you are still having issues, open a ticket with Wyze.
Quick update and additional info:
The automations to adjust the brightness of my living room bulbs is working properly again. However, the automation I created for my office cam to turn on a bulb for 5-minutes when a person is detected is still an issue.
It dawned on me, the cam and bulb are on two separate SSIDs that run from the same access point. Do you think this could potentially be causing the delay? I can turn the bulb on and off in a second using the app. I can livestream the cam without an issue using the app. Its just this automation that has delay.
I should also mention that this particular cam is using the cam plus lite service. For the record, I’ve been waiting at least 5-minutes between attempts to trigger the automation. I also just tried flashing the firmware on the v3 (to the same latest greatest version), but it had no impact.
My initial impulse is to say it’s doubtful, but then I remember when I connected my Wyze account to home assistant, it included support for my bulbs to function locally so everything was fast! All my lighting automations were way faster in home assistant than using Wyze directly for automations. So it’s possible that devices can do some local inter device communication in certain circumstances, but my impulse is to think that generally the automations run through the cloud server anyway, so a separate SSID shouldn’t change that. But maybe I’m wrong. Maybe lights can use rules locally… But be slower if they are on separate networks from the trigger.
Thanks for your thoughts Carverofchoice. Something else I noticed last night and again this morning regarding the camera person detection automation that turns a bulb on for 5 minutes. If I put my phone in airplane mode, meaning it has no internet connectivity, the camera person detection automation does not function at all. I find that VERY odd and surprising! Like you, I thought ALL automations were stored in the cloud and did not require your device to function. Apparently that is not the case with camera motion that triggers bulbs.
I have pondered that possibility before, but if that is true, then I remember that I have at least 9 devices running the Wyze app with my account logged in… How does it decide which one of those to actually ruin the automation, or why didn’t some of them trigger 9 times?
I would guess that it submits it to some sort of job queue and whichever device ID grabs it first it puts a lock on the job such that nothing else attempts to process it. A total guess on my part of course.
I still find it amazing that the camera motion to turn on bulb automation requires my device to have internet connectivity. There is no doubt about this as I can do jumping jacks in front of the camera and the light never turns on when my device is in airplane mode.
That should be relatively easy to test. In your situation, if an automation is not running when you put your phone into airplane mode or turn it off, all you would have to do to test that is to log into the Wyze app with the same account on a second device, and then put one of them into airplane mode or turn them off and see if the automation still runs. If it does, put the other device into airplane mode or turn it off as well and then test again and see if it doesn’t run if both devices are off.
That would be an interesting test anyway. Understandable if you don’t bother to do it though.
I think testing with one devices is enough to prove it out. No need to add a second device. It is clear to me that the automation in question will only run (with horrible delay) if a device running the WYZE smart app has internet connectivity.
Oddly enough, when I put my phone in airplane mode last night the automation did work. Still with crazy delay, but it worked. Then again this morning prior to taking my phone out of airplane mode, the automation worked…with crazy delay.
This weekend I plan to move the cam to the same SSID as the bulb to see what that does for me when it comes to the delay. I might put one of my cam plus licenses on the camera first to see what that does for me.
The troubleshooting of WYZE issues has been consistent since my first purchase back in 2018.
Moving the cam to the same SSID as the bulb had no impact when it comes to the delay. This holds true with the latest v3 firmware that was released today. I decided to swap out the cam and try a different v3. This also had no impact on the significant delay.
I give up, this automation is simply not going to work out. So much delay that I am out of the room before the light even turns on…if it turns on at all.
I have the automation working again with person detection from a v3 that has remained on my account for years. However, I have a 12-16 second delay between standing in front of the camera and my bulb turning on.
I modified this wireless SSID and disabled client isolation. I thought that maybe having this enabled was causing the delay. From what I can, this change has not made a difference.
I have had the same problems you mentioned 3 years back and on cp-lite no subscription.
The only way I found to resolve the matter was to use “Motion Detection” and it activates within 1-2 seconds. so it seems to be “Person Detection” only glitch for cp-lite devices.
Tested on my V3 Wyze Cams , V2 Outdoor Cams, Pan Cams V2 , Wyze OG V1 Cams, and Pan Cams V3 which 2 of 3 also have the dreaded “No video available at this time” which has been going on for nearly a year and half
Have been purchasing Tapo’s starting last year and very satisfied with their products.
I did try for a bit. It did seem to work better. Only issue is I am turning a bulb on for X amount of time. When the time was up and the bulb turned off, the cam detected it as motion and turned the bulb on again. I tried adjusting the detection zone and sensitivity as well. This had no impact. As soon as the bulb would turn off, motion was detected and the bulb would turn on again.
So I am stuck having to use person detection. Sad thing is, if in a cam plus cool down period, you can do jumping jacks in front of the camera and the automation will not be triggered. Once the cooldown lapses, then it will detect a person and turn on the bulb with what is averaging out to be a 20-second delay.
I have another thread going where an old v3 was pulled from storage. I updated the firmware as far as I could by flashing with an SD card. Then I had to update to the latest over the air. That cam is on cam plus, has no cool down period, has no person/AI detection, and will record motion for far more than 12 second clips. WYZE gear is not very consistent. I do not blame anyone for moving away from the brand.
