Am I using Rules/Shortcuts wrong?

Hi. When I first got Wyze cams I was amazed at how easy the app was to control things I wanted to control. I set up two simple shortcuts that looked like this:

“On” - turn everything on - notifications, cameras, motion detection, motion sensors, sensors.
“Off” - turn everything off.

Simple. Then I realized I could set those shortcuts to come on at a schedule. Brilliant. So I set “On” to activate at 11pm, roughly bed time. And “Off” to activate at 7am, roughly when I get up.

I did a bit more than just that but that illustrates a pretty simple (yet really cool) use case which illustrates my point. I would never have to think about turning Wyze on at night, it just happens! And I could still manually trigger those shortcuts any time if I wanted.

But then a few months ago the app was updated and I could no longer do this. Instead, to my understanding, to achieve the same thing I would need to add an additional 5 rules - to turn each of those things on and off. This is in addition to the 2 shortucts “On” and “Off” which I still want to be able to manually trigger.

What a pain. And to make it worse, those 5 rules are hardly distinguishable from each other so its super hard to maintain that list.

Then we were told improvements were coming to Rules. Then that they had arrived in version 2.6. Except I don’t see any difference.

You can add a name to a Rule, But that’s of no use because when you do that it doesn’t show you the time. So you would have to type out both the action and the time for it to be useful. Why should I have to type that? Why not just put the action with the time on the rule (you can only have one action anyway).

But still, that doesn’t solve the fundamental problem that its now way harder to do the simple scenario I described at the top. The problems only gets worse the more things you want to schedule.

Am I using it wrong?


Why not just allow an activate schedule back on the Shortcut (multi-action)? It doesn’t need an end time, Problem solved.

It seems the current approach has inverted that logic, Even if that’s how it works under the covers it doesn’t mean the UI should work that way.

Why not configure all your cameras individually with notifications settings etc, then add all your cameras in a group (including the camera with the bridge). Create a scheduled rule that turns on that group at whatever time, and another rule that turns them off at a certain time. If a camera is " off " in app, by default there will be no notifications, motion detection, live view, etc. Also if the camera with the bridge is “off”, then your motion or contact sensors will also be “off” so no need to disable their notifications. Turning a camera off and then disabling the settings in rules and the opposite, turning a camera on and enabling the settings is “redundant redundancy”. Simplify it.

1 Like