I Have an event that works perfectly if the easytrigger timeframe Is not there... but the minute I put it in as "AND IF",... it no longer seems to work. Best way to debug? 
Announcement
Collapse
No announcement yet.
Event doesn't work when using trigger
Collapse
X
-
Is your system time correct?
To troubleshoot, try to create a much simpler event with a trigger on a virtual device, the same schedule condition and a simple Speak action.
Comment
-
System time correct
Turned debug on for EasyTrigger
Stopped/Started the PI and saw the following:
Jun-03 4:38:40 PM EasyTrigger DEBUG Device 1249 changed Jun-03 4:38:40 PM EasyTrigger DEBUG Device 1248 changed Jun-03 4:38:32 PM EasyTrigger INFO Found 0 device group value triggers Jun-03 4:38:32 PM EasyTrigger INFO Refreshing list of device group value triggers to monitor Jun-03 4:38:32 PM EasyTrigger INFO Found 0 random triggers Jun-03 4:38:32 PM EasyTrigger INFO Refreshing list of random triggers to monitor Jun-03 4:38:32 PM EasyTrigger INFO Found 0 schedule triggers Jun-03 4:38:32 PM EasyTrigger INFO Refreshing list of schedule triggers to monitor Jun-03 4:38:32 PM EasyTrigger INFO Found 0 device's value conditions that need monitoring Jun-03 4:38:32 PM EasyTrigger INFO Found 4 device's value triggers Jun-03 4:38:32 PM EasyTrigger INFO Refreshing list of device's value triggers to monitor Jun-03 4:38:32 PM EasyTrigger INFO Found 0 device's string triggers Jun-03 4:38:32 PM EasyTrigger INFO Refreshing list of device's string triggers to monitor Jun-03 4:38:31 PM Plug-In Finished initializing plug-in EasyTrigger Jun-03 4:38:31 PM Starting Plug-In EasyTrigger loaded in 532 milliseconds Jun-03 4:38:31 PM Starting Plug-In Plugin EasyTrigger started successfully in 84 milliseconds Jun-03 4:38:31 PM EasyTrigger INFO EasyTrigger version 3.0.0.54 Jun-03 4:38:31 PM Starting Plug-In Initializing plugin EasyTrigger ... Created a new Schedule (Monday between 8am and 10pm) called FrontDoorJun-03 4:38:31 PM Info Plugin EasyTrigger has connected. IP:127.0.0.1:51127
Saw this in log:
Created a simple on/off virtual device with this eventJun-03 4:40:59 PM EasyTrigger DEBUG Device 401 value changed from 72 to 71.8
IF Test Unknown EasyTrigger Test Device changes and becomes On
AND IF The time is in FrontDoor time range
Then Set Device Light Office Overhead to On
and turned on the VD
saw this in log... so it did work
Jun-03 4:52:07 PM EasyTrigger DEBUG Device 124 value changed from 0 to 99 Jun-03 4:52:07 PM Z-Wave Device: Light Office Overhead Set to 99 Jun-03 4:52:07 PM Device Control Device: Light Office Overhead to On (99) Jun-03 4:52:07 PM Event Event Trigger "Test events EasyTrigger Test" Jun-03 4:52:07 PM EasyTrigger DEBUG Device 1329 value changed from 0 to 100 Jun-03 4:52:07 PM Device Control Device: Test Unknown EasyTrigger Test Device to On (100) by/from: CAPI Control Handler
so at a loss why the other one won't work.
Comment
-
I'm back.. I still can't get this to work. I actually separated into two events, one that is triggered by the VD motion device (that is triggered by Blue Iris). This even manually kicks off the second event (set all tablets to view the front door camera), and then sets the VD motion device back to 'no motion'. This is set to not run again for 10 minutes.
On the second event, I use easytrigger to only run this certain times of the day. I ran this as a test this morning with the easy trigger set to debug... and a time outside the range set for friday. HS3 time is correct.... and the even still ran.
All screen shots are below...No idea why this is not working.
Comment
-
Originally posted by Tomgru View PostI'm back.. I still can't get this to work. I actually separated into two events, one that is triggered by the VD motion device (that is triggered by Blue Iris). This even manually kicks off the second event (set all tablets to view the front door camera), and then sets the VD motion device back to 'no motion'. This is set to not run again for 10 minutes.
On the second event, I use easytrigger to only run this certain times of the day. I ran this as a test this morning with the easy trigger set to debug... and a time outside the range set for friday. HS3 time is correct.... and the even still ran.
All screen shots are below...No idea why this is not working.
Comment
-
Originally posted by spud View Post
In your "Run event" action you did not check the "Run only if other event conditions are true" checkbox so the Easytrigger schedule condition is ignored.
edit nevermind ...i finally found it.
Comment
Comment