Now that is ingenious. I saw where individuals have done this for leak sensors and such, but not for an actual light switch. Impressive.
I can’t take all the credit, someone else posted it & it was exactly what I needed. It’s an unfinished basement so all the lights just had a pull string. This solution makes it like a standard circuit.
This is the same as my Nephew… I am going to send these to him.
Thanks for the images and idea. Even if you got it from someone else.
@QiS I know you’ve heard similar things a million times on these forums, but when I haven’t heard is trigger>action (and a secondary trigger the only allows that action to stay active for a certain amount of time set by the user)
For instance, I currently have a rule that when someone pushes my doorbell I have certain lights that turn on and turn a certain color in addition to the wyze chime. I would love to be able to have a sub rule for that so those lights that come on for that rule and for that rule only only stay on for a set amount of time.
Currently I have to set up a rule that if lights are on for so long between time one and time two they automatically turn off. So I effectively have to turn off that rule in order to use those lights outside of the doorbell trigger.
It’s just a thought, I hope my spiel was fairly understandable here
If I understood correctly, I would agree with you. It would be nice to have something trigger a light, then within the same trigger action, set a delay and then kick off a second action.
So in your case:
- Doorbell is the Trigger
- Action 1 is turn on Lights and maybe other things happen
- Delay for x time (1 minute)
- Action 2 is to turn off the light
BTW: I like this, have not thought about triggering a light when the doorbell is pressed.
Thank you thank you thank you yours is far more clear than my run on
Sadly I can’t take full credit. When the doorbell was first out you couldn’t trigger things with it being pressed. Someone came up with the idea for the lights because it would help people with disabilities such as hard of hearing or fully deaf. I thought that was a great idea it just needs some refinement
That’s a good use case, we’ll think about it.
Thanks for the feedback on this. Glad you all are looking into it. But I must give credit to @Bam . I rephrased what he said.
Teamwork makes the dream Work.
Haha, welcome to work at Wyze.
Are you also looking at ways to tweak some of the rules or the actions they can do or just at the way we create the rules? As far as templates, I would like it on one screen so I can do each part in the order that works for me, as in if I want to set up my action before my trigger it would likely be doable if it was on screen.
nope was talking about creation.
Have every steeps on one page, I think it would allow for each part of a rule to be worked in the way that works for best for the user.
That’s a good suggestion, while there’re some limitations. We’re working on the improvement to make the flow simple.
BTW I know it’s a bit OT, but can we please get a blinky rule for the doorbell? It would be good for those of us with hearing issues.
I’m sorry to hear that. I’ll confirm with our doorbell PM whether the hardware supports this blinky feature. If yes, we may implement it in Rule Engine.
From a conversation we had back on May 17th
Wishlist Item for Rules Engine:
Copy and Edit ability
Rules are often repeated, turn off, turn on etc… with multiple end points in some cases. Rather than having to repeat from scratch it would be faster if the user could copy a rule and modify attributes.