It seems like you might need a few cogs for this and perhaps a disable/enable switch tied to the motion cog.
Other thought is that your scenario sounds like it might be a good candidate for Room Lighting.
Leave the circled option deselected.
1 Like
@bptworld - can’t figure this one out. Getting these errors when I try to even open the “notification options.” The options screen even opens to an error screen that says to check the logs.
*not trying to have sound played through the device.
Under “push notifications” I selected my phone and iPad (using the “HE mobile device” driver). Erroring ever since so I can’t even get in there to deselect. Luckily cogs are easily re-made because I had to remove the instance completely.
Tried the same thing with push notifications again, same error.
New bundle...
3.8.3 - 08/29/22 - Minor changes
Looks like a whole bunch of experimental code was left in the last release. 
edit: if you downloaded this within the last 10 minutes, use search and download again. Made another quick adjustment. 
You are selecting the 'Run Cog when Saving' option? That would explain it (at least to me!). I put in a trap to catch the problem. You'll get a warning on save, but the cog should work fine after that.
I'll have to put on my thinking cap for this one...
I would think it should just be a simple override. If set to x, don't react to motion setting. One thing I have never understood, how is setting up a virtual switch different than (in this instance) setting the dimmer from the dashboard where you want? It seems to me like the dashboard setting should act as a form or virtual switch.
I have toyed with that, so far I havent had a whole lot of success. It seems to end up in the same place if Ican get it to work at all. However, I really have not had a chance to sit down and dig into it in depth .
Yes, I always have, is that not what I should have been doing? I thought it helped to set the cog to the current state so it would fire correctly the next time around.
Yeah, it’s a different paradigm from what @bptworld has shared with previous questions I’ve asked about EE.
I think this loosely applies to your question as well.
If you had an “if-then-else” conditional, it would be a bit too similar to RM’s logic, thus making EE a redundant app.
That said, I’m still trying to think of ways to use EE in my automations since I’m just now comfortable enough with RM. I’m sure it will just take some time for me to realize the potential.
@bptworld please correct me if I’m off-base here: I think the intent of EE is to simplify the automation process by intentionally limiting the complexity of each individual child app, creating smaller automations “cogs” which can then be intermingled with other cogs or apps from the developer to build the “engine.”
I just have no idea how to do that yet!!! 
2 Likes
Perfect!
2 Likes
Bryan:
Can't open any of my cogs...possibly due to hub beta FW 2.3.3...I believe you're in the beta program.
Reinstalled EE (insetalled over existing) and still can't open any cogs.
The cogs throw this error when I try to open one:
1 Like
That is weird!
3.8.4 - 09/03/22 - Fix for mystery 'contains' error
2 Likes
Cool! I created a mystery!! Right up there w/Sir Arthur Conan Doyle!!
Something is not right over there. I don't think it installed the new code. Open the code to 'Event Engine Cog' and see what version it is.
1 Like
“Fear is the path to the dark side … fear leads to anger … anger leads to hate … hate leads to suffering.”
Now show me line 231
1 Like
I'm so afraid... (just a sec)
DId the first capture on my phone, so didn't notice this oddity!
That's not right, right?! I'm awaiting your OK to delete the old version of the Cog that is somehow still in residence.
BINGO, one old version and one new version. Again, very weird. lol. Delete the one not associated with the Cogs and try to download again.
1 Like
Worked immediately after deleting the old cog code! 
Gracias.
1 Like
Howdy @bptworld - thanks for this great app! I've just installed it for the first time, so I know it's the latest version - and am seeing a bug when adding virtual presence sensor actions. I can select the sensor no problem for both open and close actions, and it works as expected for OPEN actions, but when I specify it for CLOSE - well, it shows as selected in the grey box, but the summary shows as " - Virtual Contact Sensor - Close Sensors: NA" - as though it didn't save it. I've tried deleting, recreating the rule a number of times and it keeps happening. Works fine for OPEN events.
Here's a screenshot of what I see. Any help appreciated!
Thanks and welcome to the community!
New version...
3.8.5 - 09/20/22 - Fixed a typo
