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

Summary

@bptworld Updated and set the cog to condition too low. Set the cog to 75. Set the virtual to 65. Ran the cog and no speech.

app:47932021-06-16 12:52:52.832 pm trace********************* End - startTheProcess (3.1.4) - test Cog *********************

app:47932021-06-16 12:52:52.829 pm debugIn startTheProcess - Nothing to do - STOPING - whatToDo: stop

app:47932021-06-16 12:52:52.825 pm debugIn checkingWhatToDo - ********** whatToDo: stop **********

app:47932021-06-16 12:52:52.823 pm debugIn checkingWhatToDo - Using D - Stop

app:47932021-06-16 12:52:52.819 pm debugIn checkingWhatToDo - everythingOK: false

app:47932021-06-16 12:52:52.816 pm debugIn checkingWhatToDo - USING AND - totalMatch: 0 - totalMatchHelper: 0 - totalConditions: 0 - setpointOK: false - timeOK: true

app:47932021-06-16 12:52:52.812 pm debugIn checkingWhatToDo (3.1.4)

app:47932021-06-16 12:52:52.809 pm debugIn checkTransitionHandler (3.1.4)

app:47932021-06-16 12:52:52.806 pm debugIn setpointHandler - TEMPERATURE - setpointOK: false

app:47932021-06-16 12:52:52.803 pm debugIn setpointHandler (Between) - Device: cog temperature probe, Value: 65.0 is NOT BETWEEN setpointHigh: 75.0 and setpointLow: 75.0

app:47932021-06-16 12:52:52.800 pm debugIn setpointHandler - Direction - Setpoint value is going in the correct direction

app:47932021-06-16 12:52:52.797 pm debugIn setpointHandler - setpointValue: 65.0 - state.preSPV: 65.0

app:47932021-06-16 12:52:52.795 pm debugIn setpointHandler - spValue: 65

app:47932021-06-16 12:52:52.788 pm debugIn setpointHandler (3.1.4) - spName: [cog temperature probe]

app:47932021-06-16 12:52:52.784 pm debugIn startTheProcess - 1C - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true

app:47932021-06-16 12:52:52.781 pm debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: null

app:47932021-06-16 12:52:52.775 pm debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true

app:47932021-06-16 12:52:52.762 pm debugIn hsmStatusHandler - hsmStatus: null

app:47932021-06-16 12:52:52.758 pm debugIn hsmAlertHandler - hsmAlertStatus: null

app:47932021-06-16 12:52:52.754 pm debugIn modeHandler - modeMatch: true

app:47932021-06-16 12:52:52.751 pm debugIn modeHandler - No Mode selected so modeMatch = true

app:47932021-06-16 12:52:52.747 pm debugIn modeHandler (3.1.4)

app:47932021-06-16 12:52:52.744 pm debugIn dayOfTheWeekHandler - daysMatch: true

app:47932021-06-16 12:52:52.741 pm debugIn dayOfTheWeek (3.1.4)

app:47932021-06-16 12:52:52.739 pm debugIn checkSunHandler - timeDaysType:

app:47932021-06-16 12:52:52.735 pm debugIn checkSunHandler (3.1.4)

app:47932021-06-16 12:52:52.732 pm debugIn startTheProcess - whoHappened: cog temperature probe - whatHappened: 65 - whoText:

app:47932021-06-16 12:52:52.729 pm trace******************** Start - startTheProcess (3.1.4) - test Cog ********************

EDIT: THIS LINE SEEMS TO BE THE ISSUE AGAIN LIKE IN THE TOO HIGH CONDITION.

app:47932021-06-16 12:52:52.803 pm debugIn setpointHandler (Between) - Device: cog temperature probe, Value: 65.0 is NOT BETWEEN setpointHigh: 75.0 and setpointLow: 75.0

Try 3.1.5 - 06/16/21 - Adjustments to setpoints.

Make sure you check your Notification settings. :wink:

Summary

@bptworld It said Null.

app:47932021-06-16 01:57:59.429 pm trace********************* End - startTheProcess (3.1.5) - test Cog *********************

app:47932021-06-16 01:57:59.242 pm debugIn letsTalk (3.1.5) - Sending the message to Follow Me - msg: null

app:47932021-06-16 01:57:59.235 pm debugIn messageHandler - message: null

app:47932021-06-16 01:57:59.227 pm debugIn messageHandler (setpoint) - setpointHighOK: yes - setpointLowOK: no - setpointBetweenOK: yes

app:47932021-06-16 01:57:59.222 pm debugIn messageHandler (3.1.5) - doMessage: true

app:47932021-06-16 01:57:59.212 pm debugIn startTheProcess - actionType: [aNotification]

app:47932021-06-16 01:57:59.208 pm debugIn startTheProcess - HERE WE GO! - whatToDo: run

app:47932021-06-16 01:57:59.206 pm debugIn checkingWhatToDo - ********** whatToDo: run **********

app:47932021-06-16 01:57:59.204 pm debugIn checkingWhatToDo - Using A - Run

app:47932021-06-16 01:57:59.202 pm debugIn checkingWhatToDo - everythingOK: true

app:47932021-06-16 01:57:59.200 pm debugIn checkingWhatToDo - USING AND - totalMatch: 0 - totalMatchHelper: 0 - totalConditions: 0 - setpointOK: true - timeOK: true

app:47932021-06-16 01:57:59.197 pm debugIn checkingWhatToDo (3.1.5)

app:47932021-06-16 01:57:59.194 pm debugIn checkTransitionHandler (3.1.5)

app:47932021-06-16 01:57:59.190 pm debugIn setpointHandler - TEMPERATURE - setpointOK: true

app:47932021-06-16 01:57:59.188 pm debugIn setpointHandler (Low) - Device: cog temperature probe, Value: 65.0 is LESS THAN setpointLow: 75.0 (Bad)

app:47932021-06-16 01:57:59.185 pm debugIn setpointHandler (High) - Device: cog temperature probe, Value: 65.0 is LESS THAN setpointHigh: 75.0 (Good)

app:47932021-06-16 01:57:59.181 pm debugIn setpointHandler - Direction - Setpoint value is going in the correct direction

app:47932021-06-16 01:57:59.179 pm debugIn setpointHandler - setpointValue: 65.0 - state.preSPV: 65.0

app:47932021-06-16 01:57:59.164 pm debugIn setpointHandler - spValue: 65

app:47932021-06-16 01:57:59.113 pm debugIn setpointHandler (3.1.5) - spName: [cog temperature probe]

app:47932021-06-16 01:57:59.104 pm debugIn startTheProcess - 1C - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true

app:47932021-06-16 01:57:59.101 pm debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: null

app:47932021-06-16 01:57:59.097 pm debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true

app:47932021-06-16 01:57:59.096 pm debugIn hsmStatusHandler - hsmStatus: null

app:47932021-06-16 01:57:59.090 pm debugIn hsmAlertHandler - hsmAlertStatus: null

app:47932021-06-16 01:57:59.083 pm debugIn modeHandler - modeMatch: true

app:47932021-06-16 01:57:59.081 pm debugIn modeHandler - No Mode selected so modeMatch = true

app:47932021-06-16 01:57:59.078 pm debugIn modeHandler (3.1.5)

app:47932021-06-16 01:57:59.077 pm debugIn dayOfTheWeekHandler - daysMatch: true

app:47932021-06-16 01:57:59.054 pm debugIn dayOfTheWeek (3.1.5)

app:47932021-06-16 01:57:59.052 pm debugIn checkSunHandler - timeDaysType:

app:47932021-06-16 01:57:59.050 pm debugIn checkSunHandler (3.1.5)

app:47932021-06-16 01:57:59.022 pm debugIn startTheProcess - whoHappened: cog temperature probe - whatHappened: 65 - whoText:

app:47932021-06-16 01:57:59.018 pm trace******************** Start - startTheProcess (3.1.5) - test Cog ********************

Did you??

Yes I checked those. They are still the same as when I started. Ah, you got me. Changing it now.

1 Like

@bptworld EXCELLENT!! It is working great. After you put in the 2 phrases for low and high and when you change your virtual to either below or above the setting in the cog it speaks the appropriate phrase! Great job!!

1 Like

Awesome, thanks for the help. Setpoints work much better now.

You are very welcome.

Why not one more...

3.1.6 - 06/16/21 - More adjustments to setpoints

New version...

3.1.7 - 06/17/21 - Added 'Certain Time Has Passed' to Time Conditions

Was working on a Cog for my new Ecowitt lighting detector and realized I didn't want it to notify me every time there was a strike. So I added this condition. Now it will only warn me once every 10 minutes! :grinning:

@bptworld Awesome addition! This will come in handy for sure especially with the lightning detector!

Also, this will come in very handy when you have a cog that deals with temperature. One of the difficult ones to deal with because it is constantly changing. You can have a cog that is looking for a temp being exceeded but with the option of only running once in a set time it will not constantly keep triggering a speech. Cool.

1 Like

@bptworld In the new "Certain Time has Passed" you created do you have any desire to allow a longer time than the 60 minutes?

Technically, I could make it any length. What's the use case?

The only lame one I have for now is for temperature. If I wanted to know when a temp inside a greenhouse exceeded a desired temp I would then turn on a fan and when that same inside temp went below the desired temp to shut off the fan. This can be done other ways but I don't want the cog to run every time the temp changes. Bad for the hub. So if I set the can't rerun for 24 hours then it will only run once to turn on and off the fan. Unless I am not seeing something correctly.

The cog will still run each time the temp changes, it just won't do the actions (turn the fan on/off) if the time hasn't been reached.

As for bad for the hub. This is how all apps work... trigger happens, cog runs, checks conditions and either does the actions or stops. Over and over and over, each time it's triggered.

I have over 60 cogs running everything in the house.... smooooth as silk! :grinning:

@bptworld Ok, I was under the wrong impression. I thought the whole cog would be halted for the time set and not just the action. Stopping the action is enough I guess, so that it doesn't send an on or off each time the temp changes. Is there any chance of the time being extended?

You got it. It's still in minutes but there is no max.

3.1.8 - 06/19/21 - Adjustments

@bptworld Thank you Bryan.

1 Like

Hi,

Tonnes of info!

Just wondering if there's a way to easily disable a BI camera using this app?

I'd like a cam in the bedroom, for the sake of baby monitoring, but I don't want it active all the time for obvious reasons =p

Ta!

1 Like

New version...

3.2.0 - 07/03/21 - Added BIControl - Enable/Disable Camera