Rules erratic

…for the last few days.

Person detection on v2 (legacy) registers person, uploads 12-sec clip and sends notification, but the related Rule (if person detected on v2, turn on bulb, turn on plug) only fires erratically - sometimes yes sometimes no.

The rule is time restricted, like 11:01p - 5:55a. I’m on the new rules engine. These rules have been pretty stable for nearly a year.

If this should be merged into a bigger existing topic please do. I looked but found only this:

Also, the category of this post might better be Services and Integrations? And I didn’t find ‘Rules’ tag under either Cam or Services categories, fwiw.

/edited

/edit - documented some specifics in post 5 below

/edit - documented some specifics in post 6 below

/edit - documented some specifics in post 7 below

/edit - documented some specifics in posts 8 & 9 below

/edit - documented some specifics in posts 11 & 12 below

/edit - Done logging. How do Rules work operationally? Post 13.

/edit - Moved Topic to ‘Beta’ category to encourage dev review (as suggested)

/edit - Some light regarding AWS+Wyze operationally. Post 15.

There is another thread here creates after the one I made about the same issue

https://forums.wyzecam.com/t/what-happened-to-the-rules/193827

1 Like

Thanks tina! :slight_smile:

Do rules have any dependency on Amazon Web Services (AWS)? Or do they operate exclusively on Wyze servers?

I know there was an AWS outage within the last week that Wyze noted.

The thing is, if the New Rules Engine implementation may be causing unpredictable behavior across the rules function, I’ll just chill and accept that it’s in transition - as opposed to fiddling/changing things in an attempt to fix, which I always fear may make things worse.

Is that an announcement Wyze could make?: There may be irregular Rules behavior for the next week or so. Chill (don’t troubleshoot.) We’ll notify you when we’re done.

Ok, last night (Sun/Mon), Cam 1, Event Recording in effect from 11p-6a, Notification on Person Detection, Rule Trigger on Person Detection in effect from 11:01p-5:55a.

11:28p
Event-Person-Notify-

Revise Rule by changing start time by 1 min: 11:02p

11:46p
Event-Person-Notify-Trigger

11:57p
Event-Person-Notify-Trigger

2:11a
Event-Person-Notify-Trigger

2:36a
Event-Person-Notify-

4:35a
Event-Person-Notify-

ERRATIC: 3 of 6 failed. I am considering the Rule Trigger failed by the absence of an entry in the Rules History. The Rule Effect (Plug turns on lights) is not in my living space so I’ve haven’t documented the failure by observation.

Last night (Mon/Tue), Cam 1, Event Recording in effect from 11p-6a, Notification on Person Detection, Rule Trigger on Person Detection in effect from 11:02p-5:55a.

11:12p
Event-Person-Notify-

Revise Rule by changing start time by 1 min: 11:03p

11:19p
Event-Person-Notify-

11:58p
Event-Person-Notify-

5:25a
Event-Person-Notify-

ALL Rule Triggers failed - no entry in the Rules History. The Rule Effect (Plug turns on lights) failure WAS documented by observation for the first two Events.

I thought Revising/Saving the failing Rule might ‘refresh’ its operation, but last night it had no effect.

Last night (Tue/Wed), Cam 1, Event Recording in effect from 11p-6a, Notification on Person Detection, Rule Trigger on Person Detection in effect from 11:03p-5:55a.

11:05p
Event-Person-Notify-

11:30p
Event-Person-Notify-

12:11a
Event-Person-Notify-Trigger (Failed: Device offline)

1:09a
Event-Person-Notify-Trigger (Failed: Device offline)

1:17a
Event-Person-Notify-

2:53a
Event-Person-Notify-

3:34a
Event-Person-Notify-Trigger

3:55a
Event-Person-Notify-Trigger (Failed: Device offline)

5:19a
Event-Person-Notify-

5:42a
Event-Person-Notify-Trigger

5:54a
Event-Person-Notify-

ERRATIC: 9 of 11 failed. 6 in the prior way: absence of an entry in Rules History.

And 3 in a NEW way: entry in Rules History but status of Failed: Device offline.

Early evening (Wed/Thu), rebooted the Plug that is the Target of the Rule

Last night (Wed/Thu), Cam 1, Event Recording in effect from 11p-6a, Notification on Person Detection, Rule Trigger on Person Detection in effect from 11:03p-5:55a.

11:08p
Event-Person-Notify-Trigger

11:27p
Event-Person-Notify-Trigger

12:21a
Event-Person-Notify-

1:34a
Event-Person-Notify-Trigger

3:14a
Event-Person-Notify-Trigger

ERRATIC : 1 of 5 failed. But BETTER

Rebooting the target Plug may have helped (it didn’t hurt :slight_smile: )

Cam 2, a different Cam, a similar but separate Rule

Event Recording in effect from 11p-6a, Notification on Person Detection, Rule Trigger on Person Detection in effect from 11:01p-5:59a, Target is two Bulbs (not in a group)

Summary

Mon/Tue:   1 of 4 Failed
Tue/Wed   1 of 6 Failed
Wed/Thu   0 of 5 Failed

ERRATIC (but improving?)

Sent logs to support and they’re currently looking into it.

Last night (Thu/Fri), Cam 1 , Event Recording in effect from 11p-6a, Notification on Person Detection, Rule Trigger on Person Detection in effect from 11:03p-5:55a.

11:07p
Event-Person-Notify-Trigger

11:33p
Event-Person-Notify-Trigger

11:45a
Event-Person-Notify-Trigger

12:26a
Event-Person-Notify-Trigger

12:45a
Event-Person-Notify-Trigger

1:21a
Event-Person-Notify-

2:53a
Event-Person-Notify-

3:10a
Event-Person-Notify-

5:36a
Event-Person-Notify-Trigger

ERRATIC : 3 of 9 failed.

Cam 2 , a different Cam, a similar but separate Rule

Event Recording in effect from 11p-6a, Notification on Person Detection, Rule Trigger on Person Detection in effect from 11:01p-5:59a, Target is two Bulbs (not in a group)

Summary

Mon/Tue: 1 of 4 Failed
Tue/Wed 1 of 6 Failed
Wed/Thu 0 of 5 Failed
Thu/Fri:   1 of 7 Failed

ERRATIC   Does this need to be perfect? Not for my purposes, but it’s interesting to know.

Ok, I’m done with the logging. It’s been mildly tedious but helpful to Wyze and the community, I suppose.

Currently I run an Android 6 device that is still powerful enough but which has been OS-excluded from present and future Wyze app versions.

I also run Android 7 emulator Bluestacks on a PC which will be able to use the latest Wyze app into the future.

Regarding firmware, all my v2 cams are (as of today) two versions removed from the latest release. I routinely monitor the success of firmware releases (add features/fixes without introducing new issues to troubleshoot) before accepting the upgrade.

I prize stability quite highly.

I don’t like to physically futz with the cams which are perfectly mounted and aimed with precise motion detection zones established. Remounting multiple cams (for me) is more than tedious, it’s painful.

Operational perfection is nice but I am tolerant of, I donno, 90% plus? I don’t use the cams/plugs/bulbs for anything crucial.

Does any of the foregoing bear upon the ERRATIC Rules performance I am demonstrating?

I don’t know enough (anything, really) about how Rules operate on the backend to say. I mean do they reside primarily in the App software, the Firmware, the backend Server, AWS? Are they not primarily anywhere, but more evenly distributed among components? Heck if I know.

Maybe it makes a difference that I’m running two versions back in both the app and firmware. Maybe it doesn’t.

Maybe the backend is where all the action is. :cloud:

Maybe someone who knows can give me a clue. Please? :slight_smile:

Upon reflection, changed this from 95% (1 fail in 20) to 90% (1 fail in 10). I wonder how demanding of perfection the average user is…

FWIW, found some light re AWS:

8/31/21 12:00 PM PT- We use a service called Amazon Web Services (AWS) for tasks such as sending notifications. Currently, this service is experiencing difficulty and this is impacting some of our products. Amazon is working on it now but you may experience difficulty with making in-app purchases, IFTTT, Alexa, or Google integrations, notification delays, trouble with Cam Plus Events not playing smoothly or experiencing errors, or a delay when using Wyze Home Monitoring alarms or disarming your system. We apologize and appreciate your patience.

Here: