Would like to be able to create a shortcut with multiple automation triggers. Example presently I have two shortcuts for a bulb . One shortcut turn the bulb on and the second turns the bulb off. Would like to able to do this in one shortcut. I guess would say I would like to be able to use multiple event/time automations in one shortcut.
I believe I used the wrong wording in my request. I would like to have multiple triggering evetns/times in the shortcut (i.e. turn the light on at 7:30 am and turn the light off at 9:00 am and the ideally turn the light back on at 7:00 pm and turn the light off at 9:45 pm) Note : sunrise and sunset options in the time would be great.
For sunrise/sunset time triggers, hop over to and VOTE for this topic: Sunset, sunrise (dusk, dawn) trigger for shortcuts
I think it would be highly useful to have the ability to perform a task if sets of conditions are met. For example:
If the garage door is up + It’s after 9p, then send me a text.
If the jewelry safe is open + the garage door opens, then send me a text.
If all contact sensors are closed + there is motion in the hall, then turn on all my lights.
Here’s the situation I have and would like a set of rules under a single label (not 4+ separate actions):
if (Closet Sensor is Open) Turn On Closet Bulb if (Time is between 9pm-8am) Set Closet Bulb Brightness to 3% else Set Closet Bulb Brightness to 100% else (Closet Sensor is Closed) Turn Off Closet Bulb
Right now that relatively simple, and popular, action is 4 rules… per closet. A stackable if/else system within a single rule would be nice, similarly to how IFTT works… without the 8 second delay.
I moved your post over here to this more directly relevant topic. Note that it is “in development”.
I’m curious: are you implying that IFTTT already lets you do if-then-else type of rules? That would be a new one on me.
I was thinking on writing a new topic, but this idea is close to what I’m trying to achieve:
Creating a rule with multiple WHEN conditions (AND or OR) and/or multiple ACTIONS and/or JOIN schedule and triggers.
I will try to explain now with more details, I know others members can put their own examples:
Sometimes, a device single condition is not enough, and you need more than one device, with and OR or AND condition (coverage could be an example for the same device type, and complex conditions for different device types), to trigger an ACTION
Some Device trigger best fit at a specific time (Schedule)
For example, we want the light bulbs on the stairs to turn on WHEN someone passes BETWEEN sunset and sunrise (currently IFTTT but not available for multiple devices, just one per rule) or 6:00 p.m. At 7:00 am (available but as a schedule, not as a trigger). Something similar to this would be to enable this rule and disable it at that time or between sunset and until sunrise.
The Wyze app was developed to interface with their inexpensive yet powerful cameras. It’s evolution has focused on that camera core. With the addition of inexpensive Wyze sensors, the app evolved to provide ways to use sensors to queue the cameras. This limited use of sensors is great, but falls short of the potential for the sensors. Now the addition of smart lightbulbs and plugs introduces the opportunity for Wyze to create actions. Sadly, the actions that users can create using the current Wyze app will be largely restricted to turning on lights when the sensors (including cameras) detect things.
I think it’s time for Wyze to re-think the app and evolve it from a camera control app with glued on sensor and light control features into a first class Wyze IOT integration app. Such an app would make it easy for users to describe reasonably complex logic. Like “when motion is detected while I’m away within a minute of my door sensor opening, turn on the lights, put the relevant camera into an active search and track mode, alert me at high priority and send a trigger to IFTTT for other actions.”
Though I realize that this sort of control might some day be also done through IFTTT and Apilio.io that is not going to cut it. IFTTT can only handle single event/action pairs and Apilio can’t interact directly with systems like Wyze. This means that the relatively simple sounding use case above would require that the user create a separate IFTTT action/event pair to forward each individual sensor reading to Apilio, a complex logic system in Apilio to express the logic, then an additional set of separate action/event pairs to send each of things that the Wyze cam should do. This explosion of events simply becomes unmanageable for even simple use cases like this.
I don’t think that a first class Wyze IOT integration has to be a be-all, end-all IOT system app. I just think it needs to be sufficiently advanced to intelligently support basic use cases like the one described above. Then, once those use cases are in place, I would expect to see a lot of growth in demand for more Wyze system sales as people start automating things like checking on the water level in coffee machines.
I’d like to be able to set a device group as a trigger (a few motion sensors all having been clear for a set amount of time) to turn off some Wyze Bulbs and a Wyze Plug.
At this point, it only appears to be possible to have an individual motion having been clear to be a trigger.
Good idea. I think you could achieve this with ITTT in the mean time.
I have two garage doors.
I have a Wyze Cam in the garage
I have a Wyze contact sensor on each door
I’d like the ability in rules to trigger an event such as (disable motion detection) only if both garage doors are closed.
As noted in my earlier post, I use Apilio.io and IFTTT for automation right now. The application I use with Wyze is to turn on the cameras when I leave home and turn them off when I get home. I then use Wyze’s current features to trigger cameras when various sensors sense motion. That combo works fine with the current setup.
I also have Hue lighting and am building other home automation devices. I use Hue with Apilio and IFTTT to program some lights to turn on and off when I come and go and others to set various lighting scenes depending on the time of day and whether I’m home.
With the advent of cheap Wyze sensors and power switches, the first thing I would like to be able to be able to do things like monitor all my doors, including my garage door and monitor activity in various rooms. Then, depending on whether I’m home or not, adjust the lighting and turn on various powered things as I move about the home or send me alerts and setup recordings when I’m away.
As the sensors and switches become even less expensive, I would like to sense more and more trivial things, like closet doors to turn on lights and such.
Controlling lots of things requires lots of rules. It’s easy to get lost in all the rules. The rule engine needs to be clean and straightforward and it needs to be easy to debug. For example, you need to be able to watch when sensors fire, intermediate values change, and various devices get commanded to change. Without simplicity, the value of the sensors and switches is limited to users with a lot of patience.
Example: Motion Sensor#1 have rule#1 and rule#2 to turn on/off Wyze plugs.
Problem: Can’t add MotionSensor#2 on rule#1 and rule2.
Workaround: Create exact same rule for MotionSensor#2
- Doesn’t make sense.
- Not efficient. It adds clutter to the App.
- More of the same rules will become difficult to track.
This should be a simple upgrade and doesn’t look like to difficult,