How to have notification of sound being detected. Third cam pan v3 i try and I tried to talk to 6 people from wyze ...so i turn to the community

Cameras
,
15

Since @fmills1d pinged me, I’ll chime in and say that I agree there may be a misunderstanding, as my impression from the beginning of this topic is that @samsam wants to get notifications of any/all sounds detected by the Cam Pan v3, regardless of what those sounds are, but is specifically interested in dog barking/whining and expecting only generic sound and not Smart Detection to be the determinant of what initiates a detection and notification. When I read @dave27’s question about  Settings ➜ Event Recording ➜ Sound  yesterday, I thought that was the right question. :+1:

Because I’m using Cam Unlimited, all my Cams are automatically added to that subscription, and I’m not aware of an easy way to unsubscribe and test the generic sound detection in a way that would avoid subscription interference without creating a secondary Wyze account and re-initiating setup on the Cam Pan v3. Short of doing that, I’ll say that I agree with @dave27 and don’t believe a subscription is necessary for nonspecific sound detection, which should include the dog barking but wouldn’t be tagged/labeled as such.

My one other thought for @samsam was to be sure  Settings ➜ Advanced Settings ➜ Record Sound is toggled on (), but in the testing I did just now I don’t think this is actually necessary. I set my (subscribed) Cam Pan v3 like this:

  •  Settings ➜ Detection Settings ➜ Sound Detection Sensitivity ➜ 100
  •  Settings ➜ Event Recording ➜ Sound 
  •  Settings ➜ Event Recording ➜ All Events 
  •  Settings ➜ Event Recording ➜ Customize Detections ➜ Other Sounds ➜ NOTIFY 
  •  Settings ➜ Advanced Settings ➜ Record Sound 

Then I started making sound near the Cam with a handheld clicker. Even with Record Sound disabled, I was still able to generate “Sound detected” notifications, but only once every five minutes. I guess I didn’t realize (or maybe I’d read somewhere and forgotten) that even with a subscription there’s apparently an enforced cooldown for nonspecific sound detections. Weird.

I don’t know if this helps the situation at all, but I’m interested in seeing an update from @samsam.