Yep, that did it.
Thank-you !
1 Like
Hi! First @bptworld thanks a ton for all the apps and the work you do. Just saw a comment on the old Wake Me Up thread that you do all this post-stroke and it makes me even more impressed. I think I have 2/3 of your apps running on my C7 but it leads me to always think about how different peoples brains think differently and what makes sense to others doesn’t make sense to me 
So I’m trying to move my son’s wake up routine for school days over to EE from WMU.
I set up the GCal Search and have it set to turn OFF a virtual switch on days there is “No School” otherwise it stays ON by default.
So I want to make sure the following EE will fire on M-F at 6am and sun up his light group and the clip lamp along with turning off his white noise machine. I included a screen shot of the virtual switch to Enable/Disable…so here’s the brain difference question….
If that switch is ON the cog will run and if it is OFF it won’t correct? It doesn’t have to be “turned on” to run right? It’s more an added condition like “if this switch is on then run cog” correct? Just making sure because the WMU version of this runs rock solid but since I added the V switch it hasn’t run even with the switch on.
If I’m misunderstanding it then I suppose I can just add the switch as a condition up at the start of the cog.
Thanks!
Event Engine Cog (2.8.8) - Event Engine Cog
Conditions
***** Cog will fire when ALL Condition are true (Using AND)
- By Days - [Monday, Tuesday, Wednesday, Thursday, Friday] - as Restriction: true
- Certain Time - Wed Apr 20 06:00:00 EDT 2022 - Repeat: false - Schedule: NA
Actions
- Switches to turn Off: [Sam’s Noise Machine]
- Select dimmer devices to slowly rise: [LG - Sam’s Room, Clip Lamp] - Minutes: 5 - Starting Level: 5 - Target Level: 99 - Color: Soft White
- Delay Between Actions: 100
Thanks
Correct, as long as that switch is 'on'. The cog will work.
Exactly
Hi,
I have a question regarding restrictions:
I have a cog that is triggered by a motion sensor being active. It turns on a light to a random color. Then once motion is inactive, it turns off the light. If the light is already on when motion is detected, I'd like the cog to do nothing.
I've tried using the light being on as a restriction. This works fine for preventing the cog from firing. But when the light is off and the cog fires, the cog ends up restricting itself after turning the light on (it no longer turns off when motion is inactive).
I know how to build these conditions in RM but I was hoping to use EE for the simple random color change functions.
Thank you!
Thanks
Was there a change to how the restrictions work though? Or is there a different way to program what I wanted? It still seems to work the same way after update.
Did you update your cog to match the one I posted? If you did and it still doesn't work, post a debug log and another cog description.
But your cog doesn't have an restrictions? That's what I'm trying to get working properly..
Sorry if I'm misunderstanding
You asked for a cog that can do this...
Which I read as:
On motion turn light on with random colors
When motion stops
- if light was off, turn light back off
- if light was already on, leave light on - returning to original settings
Here's where my mind works differently. Rereading your post just now, I think you want...
if motion and light is off
- turn light on with random colors
- when motion ends, turn light off
if motion and light in on
- do nothing
Let me try this scenario and get back to you.
Oh ya haha the latter is what I meant. Thank you so much!
Wasn't sure if EE already had this capability and I was just using restrictions wrong.
It didn't have this capability but it should now. 
Try this...
3.6.2 - 04/22/22 - Added another Reverse option
2 Likes
Perfect! Thank you so much!
1 Like
Minor feature request, if possible - for door code notifications, today, you need to specify each user. I'd love if we could just have "Any codes" as an option so that I don't have to remember to go in and check users when they're added/removed/etc.
Thank you!
This is already an option. Hover over the '- INFO -' and you'll get a little description of how the option works. You'll find the INFO's through out the app and in the 'Instructions' at the top of the app.
Thanks
Oddly, I tried that first, and it didn't work. I just tried it again, and it does. Gremlins, man...
Thank you.
OK, one other nit, and I promise this one is legit 
Is there any reason why this delay is limited at 60 minutes? With how broken the built in mode and motion app is, I want to make some motion rules that are measured in hours and not minutes... Can't see why it wouldn't work, but I might misunderstand a construct here...
1 Like
New version...
3.6.3 - 04/29/22 - Adjusted Time to Reverse (max 240 minutes)
1 Like
Any particular reason on 240? I actually have a use case (a presence sensor that's actually a switch) that I literally want a 12 hour timer on.
(In general I'm against long duration timers, but in this case it makes sense...)
Okay, you win,
3.6.4 - 04/30/22 - Removed time restriction for Time to Reverse ... 3, 2, 1... 
2 Likes
You rock, thanks!
1 Like
