[RELEASE] Event Engine - Automate your world with easy to use Cogs. Rev up complex automations with just a few clicks!

New version on GitHub...

3.5.0 - 02/17/22 - Changes to reverse, hopefully no more flash before turning off

1 Like

Awww. I'll miss little flashy... :wink:

1 Like

I can confirm, no more flashy ! it works as it should, Thank-you !

There is a problem with using Color Temperature with Lifx. I don't know why but everything works fine using colors (even "soft white", "day light", etc) but if I dial 2700K, 3000K, etc. The light does not follow the light Level. e.g. asking for 100% gives me 12% sometimes, I still need to do some testing, the problem seems intermittent.

Check this out...

Based on this thread, I've created an UI enhancement for Event Engine! You can find the code on my GitHub. All thanks goes to @tomas1 for his original script.

Note: this script doesn't contain any of the other great features of the original script. It only adds EE to the menu and creates the nice 'by room' page. Consider this an 'add-on' script to his multi-feature script. But it can also work without it.

2 Likes

If I could give 10 "Likes" I would... :smiley: :smiley: :smiley:

1 Like

Could someone take a look at this cog and tell me if you see something I am missing? It fires off like it should on weekend mornings at 0500, but for some reason it isn't shutting off at 0600 (impacting WAF). I cant seem to figure out why. I forgot to set up to run logs this weekend, but was hoping maybe Simeone sees something I'm just missing. Thanks!

Remove the 'Restriction' on 'Between two times'. It's keeping anything from happening when the conditions become false.

1 Like

When a cog fires, does EE do a refresh before capturing device states? Or does it just capture whatever is currently reported in HE?

I have a bunch of kasa wifi switches that don't actively report their state to HE. Their state in HE is only accurate as of the most recent poll unless a refresh command is sent.

Hoping someone can help me. I have blue iris. I am wanting to do the following. Set up a virtual switch so that when it is on, I receive no alerts from my outside cameras. When it is off, I receive alerts from blue iris. So, I made a profile in Blue iris that essentially stops alerting me to activities. I named this profile 7. I can get event engine to change the blue iris profile to profile 7. How can I get event profiler to make blue iris go to the previous profile (prior to the change to profile 7)? If I go into blue iris, I can press the 'pause' symbol next to the shield and blue irsis will go back to the current active schedule. How do I send this type of command to go back to the current active schedule with event engine? Thanks. Brock

EE uses what is in HE. To refresh every device, every time would be waaaay too much traffic.

Sorry, I don't have any way of doing this. Best you can do is use the same command to set the profile to what ever you want at that time.

Ah shucks. It's only a couple devices for certain specific rules that I've needed this. The only other option was to increase polling frequency on those devices, which seemed like way more unnecessary traffic vs just actively polling the device when needed.

I've built some rules in RM to get around this limitation but it's not as elegant as apps like EE. It's a simple specific device refresh and wait a couple milliseconds before capturing the state.

I'm sad there's no toggle for "refresh before capture" in most apps. But I guess I'm kind of an edge case. Although I think some older zwave devices also don't actively report their state changes? :man_shrugging:

Anyways, thanks for all your hard work. I'm still learning everything EE can do but it's great so far!

That got me thinking. I already have a 'Refresh' action in EE. So I just went ahead and changed the order of operations to make the 'Refresh' run before anything else. This should do what you want/need. Please update EE, then give it a try and let me know how it goes.


New version available...

3.5.1 - 03/04/22 - Change to make the Refresh Action run first. Other minor changes

1 Like

Oh wow thank you so much!

I'll try testing later today after work..

When I was building my rules I did have to add in a delay of around 0.06s from refresh to capture. Otherwise it would capture before the state could update. I'm not sure how much that varies between devices or if it's matter of wifi vs ZigBee vs zwave. This was using kasa wifi switches and the HE kasa integration app. My states were updating around 0.030-0.045s after the refresh command.

1 Like

I really find it annoying how helpful and responsive @bptworld is...such a show-off. :wink:

2 Likes

@bptworld Doesn't seem to be working..

I set up a simple motion cog. Turn on "hallway light" when "motion sensor - hallway" is active. Reverse to previous state immediately when no longer active.

I deliberately set the poll interval on the "hallway light" to 10 minutes then manually turned on the switch so HE would have the incorrect state (HE shows switch as OFF). Then I trigger the motion sensor. Once the motion sensor goes inactive, the switch is being turned off. I'm pretty sure the state isn't being captured.

If I turn on the "hallway light" in HE or refresh/poll the device prior to triggering the cog, then it functions correctly.

dev:1152022-03-05 09:23:28.605 am info[Plug Switch / 6.5.1 / Hallway Light]| setSysinfo: [switch:off]
app:3562022-03-05 09:23:28.601 am trace*
app:3562022-03-05 09:23:28.596 am trace********************* End - startTheProcess (3.5.1) - Event Engine Cog - appStatus: inactive - appRevStatus: round1 *********************
app:3562022-03-05 09:23:28.541 am debugIn switchesOnReverseActionHandler - Reversing Hallway Light - Previous status: off - trueReverse: false
app:3562022-03-05 09:23:28.537 am debugIn switchesOnReverseActionHandler - switchesOnMap: [HallwayLight:off]
app:3562022-03-05 09:23:28.533 am debugIn startTheProcess - GOING IN REVERSE - appStatus: active - appRevStatus: round1
app:3562022-03-05 09:23:28.528 am debugIn startTheProcess - REVERSE - appStatus: active - appRevStatus: round1
app:3562022-03-05 09:23:28.524 am debugIn checkingWhatToDo - **********  whatToDo: reverse  **********
app:3562022-03-05 09:23:28.520 am debugIn checkingWhatToDo - Reverse
app:3562022-03-05 09:23:28.516 am warnIn checkingWhatToDo - everythingOK: false
app:3562022-03-05 09:23:28.511 am debugIn checkingWhatToDo - USING AND - totalMatch: 0 - totalMatchHelper: 0 - totalConditions: 1 - setpointOK: true - transitionOK: true - securityOK: true
app:3562022-03-05 09:23:28.507 am debugIn checkingWhatToDo (3.5.1)
app:3562022-03-05 09:23:28.503 am debugIn startTheProcess - NOT using transitions - Setting value based on triggerAndOr: false
app:3562022-03-05 09:23:28.499 am debugIn startTheProcess - NOT using Setpoint Devices - Setting value based on triggerAndOr: false
app:3562022-03-05 09:23:28.496 am debugIn startTheProcess - NOT using Security Keypad - Setting value based on triggerAndOr: false
app:3562022-03-05 09:23:28.491 am debugIn deviceHandler - (condition) - MOTION - AND - count: 1 - totalMatch: 0 - totalConditions: 1
app:3562022-03-05 09:23:28.487 am debugIn deviceHandler - (condition) - Using AND
app:3562022-03-05 09:23:28.483 am debugIn deviceHandler - (condition) - type: true - deviceMatch: 0 - theCount: 1 - typeAO: false
app:3562022-03-05 09:23:28.479 am debugIn deviceHandler - Adding to deviceTrue2: 1
app:3562022-03-05 09:23:28.475 am debugIn deviceHandler - Working 2: inactive and Current Value: inactive
app:3562022-03-05 09:23:28.471 am debugIn deviceHandler - Checking: Motion Sensor - Hallway - motion - Testing Current Value - inactive
app:3562022-03-05 09:23:28.467 am debugIn deviceHandler (3.5.1) - MOTION - data: condition
app:3562022-03-05 09:23:28.463 am debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: null - snRestric: null
app:3562022-03-05 09:23:28.459 am debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true - snMatch: true
app:3562022-03-05 09:23:28.455 am debugIn safetyNetHandler - Safety Net NOT being used - snMatch: true
app:3562022-03-05 09:23:28.451 am debugIn hsmStatusHandler - NOT being used.
app:3562022-03-05 09:23:28.448 am debugIn hsmAlertHandler - NOT being used.
app:3562022-03-05 09:23:28.444 am debugIn modeHandler - modeMatch PASSED - modeMatch: true
app:3562022-03-05 09:23:28.440 am debugIn modeHandler - Mode NOT being used - modeMatch: true
app:3562022-03-05 09:23:28.437 am debugIn modeHandler (3.5.1)
app:3562022-03-05 09:23:28.433 am debugIn dayOfTheWeekHandler - daysMatch PASSED - daysMatch: true
app:3562022-03-05 09:23:28.429 am debugIn dayOfTheWeek (3.5.1)
app:3562022-03-05 09:23:28.426 am debug********** In checkSunHandler - timeBetweenSun: true **********
app:3562022-03-05 09:23:28.422 am debugIn checkSunHandler - sunrise/sunset NOT being used - timeBetweenSun: true
app:3562022-03-05 09:23:28.419 am debug********** In checkSunHandler (3.5.1) - timeDaysType:  - **********
app:3562022-03-05 09:23:28.415 am debugIn startTheProcess - whoHappened: Motion Sensor - Hallway - whatHappened: inactive - whoText: Motion Sensor - Hallway is inactive
app:3562022-03-05 09:23:28.411 am trace******************** Start - startTheProcess (3.5.1) - Event Engine Cog - appStatus: active - appRevStatus: round1 ********************
app:3562022-03-05 09:23:28.407 am trace*
app:3562022-03-05 09:23:28.367 am debugIn startTheProcess - Starting - appStatus: active - appRevStatus: round1
dev:1182022-03-05 09:23:28.340 am infoMotion Sensor - Hallway is inactive
dev:3542022-03-05 09:22:59.696 am infoMotion Sensor - Front Yard is active
dev:1152022-03-05 09:22:54.399 am info[Plug Switch / 6.5.1 / Hallway Light]| setSysinfo: [switch:on]
app:3562022-03-05 09:22:54.394 am trace*
app:3562022-03-05 09:22:54.389 am trace********************* End - startTheProcess (3.5.1) - Event Engine Cog - appStatus: active - appRevStatus: round1 *********************
app:3562022-03-05 09:22:54.340 am debugIn switchesOnActionHandler - Turning on Hallway Light
app:3562022-03-05 09:22:54.336 am debugIn startTheProcess - actionType: [aSwitch] - Sat Mar 05 09:22:54 GMT-10:00 2022
app:3562022-03-05 09:22:54.332 am debugIn certainTimeHasPassedHandler - state.certainTimeHasPassed: true
app:3562022-03-05 09:22:54.327 am debugIn certainTimeHasPassedHandler (3.5.1)
app:3562022-03-05 09:22:54.323 am debugIn startTheProcess - HERE WE GO! - whatToDo: run
app:3562022-03-05 09:22:54.318 am debugIn startTheProcess - RUN - appStatus: inactive - appRevStatus: round1
app:3562022-03-05 09:22:54.314 am debugIn checkingWhatToDo - **********  whatToDo: run  **********
app:3562022-03-05 09:22:54.310 am debugIn checkingWhatToDo - Run
app:3562022-03-05 09:22:54.306 am debugIn checkingWhatToDo - everythingOK: true
app:3562022-03-05 09:22:54.301 am debugIn checkingWhatToDo - USING AND - totalMatch: 1 - totalMatchHelper: 0 - totalConditions: 1 - setpointOK: true - transitionOK: true - securityOK: true
app:3562022-03-05 09:22:54.297 am debugIn checkingWhatToDo (3.5.1)
app:3562022-03-05 09:22:54.293 am debugIn startTheProcess - NOT using transitions - Setting value based on triggerAndOr: false
app:3562022-03-05 09:22:54.288 am debugIn startTheProcess - NOT using Setpoint Devices - Setting value based on triggerAndOr: false
app:3562022-03-05 09:22:54.284 am debugIn startTheProcess - NOT using Security Keypad - Setting value based on triggerAndOr: false
app:3562022-03-05 09:22:54.280 am debugIn deviceHandler - (condition) - MOTION - AND - count: 1 - totalMatch: 1 - totalConditions: 1
app:3562022-03-05 09:22:54.275 am debugIn deviceHandler - (condition) - Using AND
app:3562022-03-05 09:22:54.271 am debugIn deviceHandler - (condition) - type: true - deviceMatch: 1 - theCount: 1 - typeAO: false
app:3562022-03-05 09:22:54.267 am debugIn deviceHandler - Adding to deviceTrue1: 1
app:3562022-03-05 09:22:54.262 am debugIn deviceHandler - Working 1: active and Current Value: active
app:3562022-03-05 09:22:54.258 am debugIn deviceHandler - Checking: Motion Sensor - Hallway - motion - Testing Current Value - active
app:3562022-03-05 09:22:54.253 am debugIn deviceHandler (3.5.1) - MOTION - data: condition
app:3562022-03-05 09:22:54.249 am debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: null - snRestric: null
app:3562022-03-05 09:22:54.245 am debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true - snMatch: true
app:3562022-03-05 09:22:54.241 am debugIn safetyNetHandler - Safety Net NOT being used - snMatch: true
app:3562022-03-05 09:22:54.236 am debugIn hsmStatusHandler - NOT being used.
app:3562022-03-05 09:22:54.233 am debugIn hsmAlertHandler - NOT being used.
app:3562022-03-05 09:22:54.229 am debugIn modeHandler - modeMatch PASSED - modeMatch: true
app:3562022-03-05 09:22:54.225 am debugIn modeHandler - Mode NOT being used - modeMatch: true
app:3562022-03-05 09:22:54.222 am debugIn modeHandler (3.5.1)
app:3562022-03-05 09:22:54.218 am debugIn dayOfTheWeekHandler - daysMatch PASSED - daysMatch: true
app:3562022-03-05 09:22:54.214 am debugIn dayOfTheWeek (3.5.1)
app:3562022-03-05 09:22:54.211 am debug********** In checkSunHandler - timeBetweenSun: true **********
app:3562022-03-05 09:22:54.207 am debugIn checkSunHandler - sunrise/sunset NOT being used - timeBetweenSun: true
app:3562022-03-05 09:22:54.204 am debug********** In checkSunHandler (3.5.1) - timeDaysType:  - **********
app:3562022-03-05 09:22:54.200 am debugIn startTheProcess - whoHappened: Motion Sensor - Hallway - whatHappened: active - whoText: Motion Sensor - Hallway is active
app:3562022-03-05 09:22:54.191 am trace******************** Start - startTheProcess (3.5.1) - Event Engine Cog - appStatus: inactive - appRevStatus: round1 ********************
app:3562022-03-05 09:22:54.138 am trace*
app:3562022-03-05 09:22:54.098 am debugIn startTheProcess - Starting - appStatus: inactive - appRevStatus: round1
dev:1182022-03-05 09:22:54.071 am infoMotion Sensor - Hallway is active

@user32 , please post a screenshot of the debug log. My eyes are going crazy trying to scroll up/down AND left/right.

Sorry, didn't know which format is easiest for debugging

1 Like

Perfect! Notice this line is missing from the log...

In devicesToRefreshActionHandler - Refreshing ...

Looks like you didn't select any devices to Refresh? Like this:

Oh wow thanks for the quick reply. Sorry I didn't realize it was a separate action I had to enable. I did enable it but it still doesn't work:

I see it refreshing the switch, but at what point is the device state capture happening? It looks like it turns the switch on immediately after refresh.

Okay, let me put in some delay...

Edit:

3.5.2 - 03/05/22 - Added delay to Refresh

2 Likes

Download the Hubitat app