Shared users can now independently manage their notification settings and use the Snooze button. Rollout covers Cam v3/v3 Pro, Cam v4, Pan v3, Doorbell v2, BVD, Apollo, Bulb Cam, and Floodlight v2
Bug fixes
Important Note for Android Beta Testers:
If you have a Wyze Scale connected to your account, please do not upgrade its firmware while using this 3.15 Android beta app. Doing so may block future firmware upgrades, though it will not impact your daily usage of the scale. We apologize for the inconvenience and will have this resolved in an upcoming update.
The roll back fix the issue on the floodlight pro on the release version today also On firmware works on cellular wait on the beta release to to test haven’t received yet
This is going to be really exciting for some people. Maybe my wife will even go back to using her own account instead of mine so she doesn’t have to get bombarded by all my notifications. lol
This will also be useful for me, personally. Right now I have some notifications that I don’t actually want to see on my primary phone, but I need the notification to pop-up so my secondary phone will see it and send a webhook to Home Assistant to inform Home Assistant that a “Person Detection” or “Pet Detection” event (or other kind of event) occurred on that camera so I can run automations. But it crowds up my primary phone notifications, so I have to use another notification parsing app to intercept and block those notifications on my primary phone. Now I can just tell my primary phone to ignore those notification and let the secondary phone use a secondary account to only get the notifications it needs/wants for my automations.
Thanks Wyze. This will be useful (when I actually take the time to implement it).
b813 is causing my Wyze Cam OG to send unwanted notifications that say, “Complete Motion Detected”. First, my settings should not allow motion notifications. Second, this type of notification does not exist in the app.
Not sure if you are still experiencing this, but try “reset services” in the camera settings and then restart the camera. This experience was reported by @carverofchoice and these actions resolved this issue for him.