Much appreciated. Nothing but patient here. 
BTW: 4:30 pm Rule ran as expected and on time. 
Edit: I added my light triggers to start at 10 pm ET. In the past, setting my rule to trigger at 10 caused issues. I will report if it actually worked this time. I also set the Color Bulbs to come on Red.
@QiS For the new rule using a V1 motion sensor connected to the new Sense hub V2, where if the sensor detects motion to turn lights on, then turn off after 20 minutes of the room being clear. I observed the following event
The Rule to trigger the lights on and off works as expected. However, The WYZE bubs, when on, turn themselves off every 4-5 minutes in the 20 minutes No Motion period, then turn back on after 20-30 seconds. Until the off rule turns them off.
Log ID: 208920
I’m sorry I didn’t understand the scene you described. Do you mean that you set the bulbs to be turned on for 4-5 minutes then off? But they will be turned on automatically after 20-30s off.
Sorry, not my clearest description above.
The rule is set to turn a bulb group on with motion detected by a V1 motion sensor
Then set to turn the same Bulb group off if the area is clear for 20 minutes.
In between that that time The Bulb Group is turning itself on and off every 4-5 minutes when they are just suppose to be on, until the area is clear for 20 minutes the rule will then turn the bulbs off and they will stay off until motion is detected again.
Is it possible to get the ticket number?
12255
12254 for 5 minute recording issue
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?
It will be done within about 1 month after we release the official version.
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.
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?
I have the issue with wrong times with cam plus events as well but they are off by only a couple of seconds only.
I saw the couple of seconds as well. But when it goes the full 5 minutes or multiple minutes the time difference is larger, in my case.
BTW: did you get added to the Test Group?