Bryan, looks like adding that setting isn't working...lights still came on tonight when the door was already open and the time condition was met.
Deets:
Bryan, looks like adding that setting isn't working...lights still came on tonight when the door was already open and the time condition was met.
Deets:
Sorry, I forgot about this... I take a look tonight.
New version...
3.1.1 - 06/09/21 - Added iCal Event support
Simply copy and paste your iCal addresses, answer a couple of questions and automatically create Triggers from you Google Calendar events!
Thanks to @mark.cockcroft for the inspiration! If you haven't seen it, check out iCal Viewer that puts your iCal events on a tile.
From this idea, I started from the ground up and created a way to make triggers out of the data instead!
Consider this a beta at this point since I'm sure you guys will want more options!
Give this a try: 3.1.2 - 06/09/21 - Adjustment to sunsetSunriseMatchConditionOnly
I am almost certain that it should be possible to trigger one Event Engine Cog from within another, but I am simply unable to find this. Any way you could point me in the right direction ?
What am I trying to achieve ? I want to use the BI integration to move my camera to a position and then take a screenshot. There doesn´t seem to be a way to accomplish this within a single Cog.
I have also in the past wanted to trigger Cogs from within Cogs.
I asked about this a couple of weeks ago and didn't get much of a response. I try again...
Yes, but remember, RM is written by one of the owners of HE. It can do stuff that us 'normal' folks don't have access to. Just have to wait for a response in the other thread.
@bptworld Wondering if this attribute is the correct one to speak the number of miles. Currently it just says "attention....lightning has been detected at miles"
I have the following in the speech text so I assume it is the wrong one. Nothing in the log.
Here is the cog.
Would need to see a debug log.
@bptworld This is with the debug logging selected. Sorry, I forgot you always need the logs.
app:2752021-06-14 08:15:31.512 pm trace********************* End - startTheProcess (3.1.2) - Lightning Detection *********************
app:2752021-06-14 08:15:29.835 pm debugIn pushNow - Sending message: Lightning Detection - attention....lightning has been detected at miles
app:2752021-06-14 08:15:29.832 pm debugIn pushNow (3.1.2) - Sending a push - msg: attention....lightning has been detected at miles
app:2752021-06-14 08:15:29.764 pm debugIn letsTalk (3.1.2) - Sending the message to Follow Me - msg: attention....lightning has been detected at miles
app:2752021-06-14 08:15:29.760 pm debugIn messageHandler - message: attention....lightning has been detected at miles
app:2752021-06-14 08:15:29.756 pm debugIn messageHandler (3.1.2) - doMessage: true
app:2752021-06-14 08:15:29.754 pm debugIn startTheProcess - actionType: [aNotification]
app:2752021-06-14 08:15:29.750 pm debugIn startTheProcess - HERE WE GO! - whatToDo: run
app:2752021-06-14 08:15:29.748 pm debugIn checkingWhatToDo - ********** whatToDo: run **********
app:2752021-06-14 08:15:29.744 pm debugIn checkingWhatToDo - Using A - Run
app:2752021-06-14 08:15:29.742 pm debugIn checkingWhatToDo - everythingOK: true
app:2752021-06-14 08:15:29.738 pm debugIn checkingWhatToDo - USING AND - totalMatch: 0 - totalMatchHelper: 0 - totalConditions: 0 - setpointOK: true - timeOK: true
app:2752021-06-14 08:15:29.735 pm debugIn checkingWhatToDo (3.1.2)
app:2752021-06-14 08:15:29.732 pm debugIn checkTransitionHandler (3.1.2)
app:2752021-06-14 08:15:29.729 pm debugIn setpointHandler - LIGHTNINGDISTANCE - setpointOK: true
app:2752021-06-14 08:15:29.727 pm debugIn setpointHandler (Low) - Device: WH57 Lightning Detect LR, Value: 24.0 is LESS THAN setpointLow: 25.0 (Bad)
app:2752021-06-14 08:15:29.724 pm debugIn setpointHandler - Direction - Setpoint value is going in the correct direction
app:2752021-06-14 08:15:29.721 pm debugIn setpointHandler - setpointValue: 24.0 - state.preSPV: 24.0
app:2752021-06-14 08:15:29.719 pm debugIn setpointHandler - spValue: 24
app:2752021-06-14 08:15:29.716 pm debugIn setpointHandler (3.1.2) - spName: [WH57 Lightning Detect LR]
app:2752021-06-14 08:15:29.713 pm debugIn startTheProcess - 1C - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true
app:2752021-06-14 08:15:29.710 pm debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: null
app:2752021-06-14 08:15:29.708 pm debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true
app:2752021-06-14 08:15:29.705 pm debugIn hsmStatusHandler - hsmStatus: null
app:2752021-06-14 08:15:29.702 pm debugIn hsmAlertHandler - hsmAlertStatus: null
app:2752021-06-14 08:15:29.700 pm debugIn modeHandler - modeMatch: true
app:2752021-06-14 08:15:29.695 pm debugIn modeHandler - No Mode selected so modeMatch = true
app:2752021-06-14 08:15:29.692 pm debugIn modeHandler (3.1.2)
app:2752021-06-14 08:15:29.690 pm debugIn dayOfTheWeekHandler - daysMatch: true
app:2752021-06-14 08:15:29.687 pm debugIn dayOfTheWeek (3.1.2)
app:2752021-06-14 08:15:29.684 pm debugIn checkSunHandler - timeDaysType:
app:2752021-06-14 08:15:29.682 pm debugIn checkSunHandler (3.1.2)
app:2752021-06-14 08:15:29.677 pm trace******************** Start - startTheProcess (3.1.2) - Lightning Detection ********************
When attempting to install Event Engine with the latest version of Package Manager, the following error results.
An error occurred while installing the package: Failed to install app https://raw.githubusercontent.com/bptworld/Hubitat/master/Apps/Event%20Engine/EE-child.groovy. Please notify the package developer..
New version available.
3.1.3 - 06/15/21 - Added 'Event Engine' actions, Added more logging
Not fixed but I added more logging. Please try again and post the debug log. Thanks
Try again...
@bptworld Here is the log. I updated to latest of EE and reran.
app:47902021-06-16 08:54:17.444 am trace********************* End - startTheProcess (3.1.3) - Lightning Detection *********************
app:47902021-06-16 08:54:17.332 am debugIn letsTalk (3.1.3) - Sending the message to Follow Me - msg: attention all....lightning has been detected at miles away
app:47902021-06-16 08:54:17.325 am debugIn messageHandler - message: attention all....lightning has been detected at miles away
app:47902021-06-16 08:54:17.313 am debugIn messageHandler (3.1.3) - doMessage: true
app:47902021-06-16 08:54:17.304 am debugIn startTheProcess - actionType: [aNotification]
app:47902021-06-16 08:54:17.302 am debugIn startTheProcess - HERE WE GO! - whatToDo: run
app:47902021-06-16 08:54:17.300 am debugIn checkingWhatToDo - ********** whatToDo: run **********
app:47902021-06-16 08:54:17.299 am debugIn checkingWhatToDo - Using A - Run
app:47902021-06-16 08:54:17.298 am debugIn checkingWhatToDo - everythingOK: true
app:47902021-06-16 08:54:17.296 am debugIn checkingWhatToDo - USING AND - totalMatch: 0 - totalMatchHelper: 0 - totalConditions: 0 - setpointOK: true - timeOK: true
app:47902021-06-16 08:54:17.294 am debugIn checkingWhatToDo (3.1.3)
app:47902021-06-16 08:54:17.292 am debugIn checkTransitionHandler (3.1.3)
app:47902021-06-16 08:54:17.290 am debugIn setpointHandler - LIGHTNINGDISTANCE - setpointOK: true
app:47902021-06-16 08:54:17.288 am debugIn setpointHandler (Low) - Device: WH57 Lightning Detect, Value: 0.0 is LESS THAN setpointLow: 5.0 (Bad)
app:47902021-06-16 08:54:17.286 am debugIn setpointHandler - Direction - Setpoint value is going in the correct direction
app:47902021-06-16 08:54:17.284 am debugIn setpointHandler - setpointValue: 0.0 - state.preSPV: 0.0
app:47902021-06-16 08:54:17.282 am debugIn setpointHandler - spValue: 0
app:47902021-06-16 08:54:17.270 am debugIn setpointHandler (3.1.3) - spName: [WH57 Lightning Detect]
app:47902021-06-16 08:54:17.263 am debugIn startTheProcess - 1C - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true
app:47902021-06-16 08:54:17.261 am debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: null
app:47902021-06-16 08:54:17.258 am debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true
app:47902021-06-16 08:54:17.257 am debugIn hsmStatusHandler - hsmStatus: null
app:47902021-06-16 08:54:17.251 am debugIn hsmAlertHandler - hsmAlertStatus: null
app:47902021-06-16 08:54:17.245 am debugIn modeHandler - modeMatch: true
app:47902021-06-16 08:54:17.243 am debugIn modeHandler - No Mode selected so modeMatch = true
app:47902021-06-16 08:54:17.242 am debugIn modeHandler (3.1.3)
app:47902021-06-16 08:54:17.241 am debugIn dayOfTheWeekHandler - daysMatch: true
app:47902021-06-16 08:54:17.237 am debugIn dayOfTheWeek (3.1.3)
app:47902021-06-16 08:54:17.235 am debugIn checkSunHandler - timeDaysType:
app:47902021-06-16 08:54:17.234 am debugIn checkSunHandler (3.1.3)
app:47902021-06-16 08:54:17.230 am debugIn startTheProcess - whoHappened: - whatHappened: - whoText:
app:47902021-06-16 08:54:17.228 am trace******************** Start - startTheProcess (3.1.3) - Lightning Detection ********************
app:47902021-06-16 08:54:17.217 am trace*
app:47902021-06-16 08:54:11.894 am debugIn checkSunHandler - timeDaysType:
app:47902021-06-16 08:54:11.892 am debugIn checkSunHandler (3.1.3)
app:47902021-06-16 08:54:11.862 am trace***** Initialize (3.1.3) - Lightning Detection *****
There isn't anything for it to say. What else is triggering it? Screenshot the Cog Description.
@bptworld I added in the %whoHappened% at the beginning of the speech statement and it got left out also. Thought you would want to know.
app:47902021-06-16 09:18:40.296 am trace********************* End - startTheProcess (3.1.3) - Lightning Detection *********************
app:47902021-06-16 09:18:40.123 am debugIn letsTalk (3.1.3) - Sending the message to Follow Me - msg: attention all....the has been detected at miles away
app:47902021-06-16 09:18:40.118 am debugIn messageHandler - message: attention all....the has been detected at miles away
app:47902021-06-16 09:18:40.113 am debugIn messageHandler (3.1.3) - doMessage: true
app:47902021-06-16 09:18:40.107 am debugIn startTheProcess - actionType: [aNotification]
app:47902021-06-16 09:18:40.104 am debugIn startTheProcess - HERE WE GO! - whatToDo: run
app:47902021-06-16 09:18:40.103 am debugIn checkingWhatToDo - ********** whatToDo: run **********
app:47902021-06-16 09:18:40.101 am debugIn checkingWhatToDo - Using A - Run
app:47902021-06-16 09:18:40.100 am debugIn checkingWhatToDo - everythingOK: true
app:47902021-06-16 09:18:40.098 am debugIn checkingWhatToDo - USING AND - totalMatch: 0 - totalMatchHelper: 0 - totalConditions: 0 - setpointOK: true - timeOK: true
app:47902021-06-16 09:18:40.096 am debugIn checkingWhatToDo (3.1.3)
app:47902021-06-16 09:18:40.094 am debugIn checkTransitionHandler (3.1.3)
app:47902021-06-16 09:18:40.092 am debugIn setpointHandler - LIGHTNINGDISTANCE - setpointOK: true
app:47902021-06-16 09:18:40.090 am debugIn setpointHandler (Low) - Device: WH57 Lightning Detect, Value: 0.0 is LESS THAN setpointLow: 5.0 (Bad)
app:47902021-06-16 09:18:40.088 am debugIn setpointHandler - Direction - Setpoint value is going in the correct direction
app:47902021-06-16 09:18:40.086 am debugIn setpointHandler - setpointValue: 0.0 - state.preSPV: 0.0
app:47902021-06-16 09:18:40.084 am debugIn setpointHandler - spValue: 0
app:47902021-06-16 09:18:40.079 am debugIn setpointHandler (3.1.3) - spName: [WH57 Lightning Detect]
app:47902021-06-16 09:18:40.073 am debugIn startTheProcess - 1C - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true
app:47902021-06-16 09:18:40.071 am debugIn startTheProcess - 1B - daysMatchRestic: null - timeBetweenRestric: null - timeBetweenSunRestric: null - modeMatchRestric: null
app:47902021-06-16 09:18:40.067 am debugIn startTheProcess - 1A - betweenTime: true - timeBetweenSun: true - daysMatch: true - modeMatch: true
app:47902021-06-16 09:18:40.065 am debugIn hsmStatusHandler - hsmStatus: null
app:47902021-06-16 09:18:40.060 am debugIn hsmAlertHandler - hsmAlertStatus: null
app:47902021-06-16 09:18:40.054 am debugIn modeHandler - modeMatch: true
app:47902021-06-16 09:18:40.052 am debugIn modeHandler - No Mode selected so modeMatch = true
app:47902021-06-16 09:18:40.047 am debugIn modeHandler (3.1.3)
app:47902021-06-16 09:18:40.045 am debugIn dayOfTheWeekHandler - daysMatch: true
app:47902021-06-16 09:18:40.024 am debugIn dayOfTheWeek (3.1.3)
app:47902021-06-16 09:18:40.023 am debugIn checkSunHandler - timeDaysType:
app:47902021-06-16 09:18:40.021 am debugIn checkSunHandler (3.1.3)
app:47902021-06-16 09:18:40.017 am debugIn startTheProcess - whoHappened: - whatHappened: - whoText:
app:47902021-06-16 09:18:40.014 am trace******************** Start - startTheProcess (3.1.3) - Lightning Detection ********************
Sorry, but still failing, after 4 attempts in a row, Each yields identical errors. Sorry its not working, but a wink will not resolve the problem for anyone.
app:1692021-06-16 11:38:02.346 am infoFatal error occurred, rolling back
app:1692021-06-16 11:38:02.312 am errorError installing app: groovyx.net.http.HttpResponseException: Server Error
app:1692021-06-16 11:37:30.308 am infoInstalling Event Engine Child
app:1692021-06-16 11:37:27.177 am infoInstalling Event Engine
app:1692021-06-16 11:37:26.854 am infoDownloading Event Engine Child
app:1692021-06-16 11:37:26.616 am infoDownloading Event Engine
That cog won't speak correctly until it gets triggered by the Lighting device. I just did a test using a virtual temp device based on your cog description and it worked great each time it went below the setpoint.
This is the test Cog I setup:
In letsTalk (3.1.3) - Sending the message to Follow Me - msg: Test Virtual Temp Sensor on APPS is now 20.
In letsTalk (3.1.3) - Sending the message to Follow Me - msg: Test Virtual Temp Sensor on APPS is now 0.
Feel free to reach out again the next time there is lighting in your area. Going to have to get one of those sensors too. My acurite has the sensor but doesn't expose it in the api.
@bptworld Could the fact that the lightning detector is showing 0 miles at the moment cause any issues because it is a 0.