I just got a phone call from two of my friends who have V3 cameras like myself, they asked if I was receiving motion notifications, I am not. That’s three people at three different locations not receiving notifications, Is there a reported issue? Updated iPhone app and firmware up to date. All settings checked
I believe they just released an app update. You may want to see if that is available on iOS and test it out.
Still not available on App Store.
Sometimes the Wyze servers get overwhelmed and fail to send notifications. It gets self corrected eventually. Not much you can do about it.
I already updated the app earlier, didn’t work for any of us.
That’s what I was thinking, Thanks
I see many reporting notifications being in the wrong time zone, or being off by many hours today. For me, they’ve stopped completely on both the 2.5 and 3.5 app on two different android phones.
The app is not attempting to even send a notification to the OS.
Uninstall/reinstall, reboot cameras, reset services, clear cache, etc has no effect. This looks to be server side.
Anyone else seeing none at all or just the time zone issues?
I’m reporting it to chat support right now but that’s probably going to be fruitless.
Apparently a known issue (or maybe they’re just blowing me off)
We completely understand how frustrating this must be, especially since it’s happening across multiple devices. The Wyze team is aware of this issue and is actively investigating to resolve it as quickly as possible.
We truly apologize for any inconvenience or confusion this has caused.
Please know we’re working hard to get things back on track, and you can stay updated on our progress by checking the Service Status & Known Issues page (https://support.wyze.com/hc/en-us/articles/360015979872-Service-Status-Known-Issues).
Thank you for your patience and understanding while we address this concern.
Of course, it is not mentioned anywhere on that known issues page to which they replied
“It is not yet mentioned as the fix is still on the works.”
I just walked in front off six of my cameras and got notifications instantly at the correct time. Using iOS 17.7.2 and WYZE app iOS 3.2.5
Thanks, did not realize that
Yeah I suspect if it was a total outage there’d be more people mentioning it. Wonder if it is related to specific cam models, accounts etc.
For me it is doing it on OG and Panv3 and on two different versions of android and the android app, so I’m pretty confident it isn’t something on my end. But I did uninstall/reinstall, reset services, reboot everything, etc just in case. No difference.
I suspect it is somehow related to the people who are reporting that their notifications have the wrong time/time zone on them.
So it appears we have two issues
Notifications being off by several hours/wrong time zone for several users
Notifications not working at all on v3, OG, Panv3 for several users.
[MOD EDIT] Removed item related to merging of two similar threads
Are you on Cam Plus/Unlimited? Looks like the people who have notifications that are off by several hours are subscribers. Wonder if people with a subscription are getting notifications (some with the wrong time) and non-subscribers aren’t…
I don’t think this issue is isolated to the V3. I’m no longer receiving notifications on my Doorbell Pro. Reset, deleted and reinstalled, toggled all options, etc. No luck. Started first week of November. It’s recording events perfectly but no notifications reach mine or my wife’s phones suddenly.
I am on Cam Unlimited, in California, four WCO v1, two V4 cams and one V3 Pro and six V3 cams all on iOS.
It is impacting my OG and Panv3 but only started today or maybe late yesterday.
Looks like the time offset issue was fixed for others, unfortunately still no notifications at all for my cams (never had the time issue, notifications just totally stopped working).
Issue resolved itself today.
In my two plus years with Wyze I learned that cloud related issues crop up once in a while and resolve on their own.
I’m not the patient type
In reality having lost notifications with two app updates which resolved by resetting or reinstalling, I just assumed this was the same and jumped right into it. But then I realized they weren’t working on my old 2.5 phone either (usually they are silenced on that but could see there was nothing in history).
Me neither, but this one is one of those tried-tested and true