VERSION: iOS: 2.20.151(2) Android: 2.20.50 *** The iOS test app may available later in Test Flight due to waiting for review.*** WHAT’S NEW: Rule Engine migration This is a gradual release. The new Rule Engine may available at a later time for you. SUGGESTED TEST AREAS: Creating new Rules Rule execution latency Rule history accuracy KNOWN ISSUES: Rule execution may be delayed FAQ for Rule Engine Migration Q: WHAT IS A RULE ENGINE? A “smart home” is a residence equipped with a number of devices that automate tasks normally handled by humans. A Rule Engine is a system that applies a series of decisions to determine how to react to a certain situation or what to do (e.g. turn off all the bulbs when you leave your home). The objective of the Rule Engine is to provide automatic control of various devices in the home based on events and conditions. Q: WHAT IS THE RULE ENGINE MIGRATION? We created a new Rule Engine to replace the existing Rule Engine. During the migration progress, your Rules data such as your Rules and Rules history will be migrated to a new database. Q: WHY DID YOU DECIDE TO LAUNCH A NEW RULE ENGINE? First, as we have more and more users, the old Rule Engine won’t be able to meet our users’ requirements. This could lead to a bad experience such as a long delay before a Rule is executed. The second reason is that the old Rule Engine did not support flexible expansion. The new features, such as sunset, sunrise, and location triggers, and dynamic action are hard to develop in the old Rule Engine. In summary, we created this new Rule Engine for improved user experience and performance. Q: WHAT HAPPENS DURING THE RULE ENGINE MIGRATION? Generally, the migration will happen automatically in the background. It will last less than 1 minute and you shouldn’t notice it. If you happen to enter your Rules page during the migration, a pop-up will notify you that the migration is occurring and to try again later. At the end of the process, a successful migration will have your account running the new Rule Engine. If the migration failed, you’ll still use the previous Rule Engine. Q: HOW DO I KNOW WHETHER THE MIGRATION WAS SUCCESSFUL? You can test this! To do that, create a new schedule. If you see the new design with the day abbreviations in circles instead of written out, you’re using the new Rule Engine! Q: WHAT HAPPENS IF RULE ENGINE MIGRATION FAILED? If the migration fails, we’ll just use the old Rule Engine until we’re ready to try it again. Your data will still be stored in the old Rule Engine and you’ll be able to use your Rules as usual. Q: WHAT IF THERE’S A BUG AFTER THE MIGRATION? If you run into any issues with your Rules after the migration, please submit a log through Account > Wyze Support > Submit a log > Wyze App & Services > Rules and let us know the log number and a description of the issue as a reply to this post. We’ll fix it as soon as possible! :camera: PLEASE INCLUDE THE FOLLOWING INFORMATION IN YOUR POST: A detailed description of the issue Your app version number (found under Account > About) If you are using iOS or Android Log number [image] [image]

Thanks - do you have the one for the Live Streaming Issue? Edit: Oops… sorry - saw you provided it.

Got it, We’ll look into it tonight.

@QiS just finished setting up my Rules as described above. However, this is not an issue but not sure if it was intended. When I set the Rules, I named them Similarly to what was there originally and only disabled the original Trigger Rule. When I set the Time Constraint on the new Rule, It defaulted to the time constraint of the original rule. It did this for all the 10 Trigger Rules I setup. Is this the intended way it is supposed to work?

Over what sort of time period can we expect this rule engine migration to happen? Not trying to rush anything. Just curious because I’ve had the new beta installed on iOS for 3 days and I’m definitely still on the old engine.

Do you mean you have multiple rules and only set the time constraint for one of them, but the other rules were affected by the time constraint, event the time constraint was not applied to them?

Here is an example of what I did: I have an old Trigger Rule named: Night - FR Motion Started It is setup as follows: when motion detected on my Family Room motion sensor, turn on my Family Room Lights and my Color Bulb Notification Light (which is set Blue and cannot be changed with the previous rule engine) Between the hours of 10:01 pm to 3:25 am. I have an old Trigger Rule named: Night - FR Motion Ended It is setup as follows: when motion clears on my Family Room motion sensor, turn off my Family Room Lights and my Color Bulb Notification Light between the hours of 10:01 pm to 3:25 am. I disabled this rule and created 2 new rules as follows - Changed the name of the rules slightly: I setup a new Trigger Rule named: Night Mode - FR Motion Started It is setup as follows: when motion detected on my Family Room motion sensor, turn on my Family Room Lights and my Color Bulb Notification and set the color to Red. When I went to set the Time constraint, it was already set to the hours of 10:01 pm to 3:25 am. I did not enter this as it was a new Rule. I setup a new Trigger Rule named: Night Mode - FR Motion Ended It is setup as follows: when motion clears on my Family Room motion sensor, turn off my Family Room Lights and my Color Bulb Notification Light between the hours of 10:01 pm to 3:25 am. Again, this was a new rule and when I was going to enter the Time Constraint, it was automatically populated to the time the old Rule was set at. This was the same for all of the Trigger Rules I was creating. They mirrored the Times that were on the old Rules. Some were set for 10:01 pm - 3:25 am Some were set for 10:05 pm - 3:25 am some were set for 5:01 am - 9:55 pm Note, I ended up changing my start time on the 10:01 Rules to 10:00 pm as I had an issue when I set the Rules to start at the top of the hour. Make sense? If you want me to send you a log or record what I did, please ask. The recording may be large, but I can possibly compress it with my editing tools.

Hi @spamoni Thanks for such a detailed explanation. Could you submit a log? We need this to dig deep.

Just did 209195 is the log number. I want to also let you know that the issue I was experiencing which precluded me from setting rules to start at 10pm, may have been corrected or at least, the problem does not exist now. The Rule to turn the lights on fired at 10pm when I moved around my family room. In addition the Color bulb was set to the Red as I wanted. So far everything is looking good. Great job, Will continue to test and provide feedback.

@QiS , I figured out what is happening. When you start a new rule from scratch and don’t open a previous rule the Time Constraint will default to the current time for start and end. However, if you open an existing rule with a time constraint and then close that rule and start to create a new rule, the default time constraint when you toggle the slider is set to the start and end time of the last rule you opened. It does not reset the time fields. Not sure if this is a bug or intended. Does this make sense?

2.20+ app Beta test 5/14/2021

Beta

QiS May 19, 2021, 12:02am 113

It will be done within about 1 month after we release the official version.

2.21 Beta App for New Rule Engine

Topic		Replies	Views
2.32 app RC test 6/9/2022 Beta	70	2913	June 21, 2022
Bulbs not turning on/off with rules Power & Lighting troubleshooting , bulb-color	76	8485	March 11, 2022
2.21 Beta App for New Rule Engine Beta	56	3881	June 21, 2021
Rules erratic Cameras troubleshooting , bug , automations	25	2849	December 19, 2021
Rules failing 5-21-20 Cameras	96	7037	June 16, 2020

2.20+ app Beta test 5/14/2021

Related topics