In my case logic is trumped by the impatience. In my defense this has happened twice before with the 3.x app and both times was after an update and needed a reset on my end.
Maybe if I had seen the trick of toggling them off and on before reinstalling the app it would have worked, but again, impatience.
I doubt that would’ve worked. As far as I know notifications are cloud based, so we’re on Wyze’s mercy when it comes to notifications.
In another thread apparently it fixed it for some so it may have been some glitch with the setting on the server or something. Reminds me of when the OGs were losing the detection zone, toggling it off and back on would fix it for a while. Who knows. Working now so it is what it is, next time it will be totally difference so no sense in trying to figure out this instance.
As I said, when it comes to notifications, we’re at Wyze’s mercy, They are all server based
Yeah but I’ve had two previous instances where it was the app for some reason modifying Android’s settings and partially or completely disabling them during an update. So I ASSumed it was similar this time.
Are you sure it was App based? From what I understand all notifications are server based, so you might have had one to many the night before 
Just kidding of course 
No such thing 
I know they come from the cloud, but they go Cloud → App → OS. The App → OS linkage has gotten broken/disabled with a couple updates in the last few months.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.