Recently, I was wondering why IFTTT was no longer able to enable/disable motion events, per the related Wyze applets.
I looked into the settings for the two Wyze applets, that are related to enabling/disabling motion events, and discovered that the applet no longer knew about my 2 Wyze cameras!
I ended up having to remove the IFTTT-Wyze association, and then re-add the Wyze association, in order for my cameras to be detected again.
This is a bit annoying, as if I had gone away for a significant period of time, assuming that my Wyze cam had been properly enabled by the IFTTT applet, it would have notified me that the applet ran, but under the covers, it actually did NOT successfully activate the motion detection, due to it’s somehow having lost knowledge of what camera I had specified…
In other words, the IFTTT applets are flaky, and unreliable, at best. I actually don’t know if the bug is the fault of IFTTT, or the particular IFTTT Wyze applet that is being run.
This is why it’s probably a GOOD idea for Wyze to support geofencing enabling/disabling of motion events, per camera, natively within the Android/iOS Wyze app itself.
Additionally, add ability to reference count members of a household, via GPS tracking. Suppose two people live in a household. We should be able to configure it so that, if both people have left the house, enable motion events for camera A. When the number of people in the house > 0, automatically disable motion events for camera A.