Posts: 739
Threads: 33
Joined: Oct 2008
Duh. I was running CQCEventDump under windows command prompt and not cqccommand prompt. CQCEventDump is working now so let me do more testing before looking into anything.
Kevin
_______________
Denon 3808ci, 2112ci ,Sonos, NoVo Grand Concerto, Z-Wave(Lights,Locks), Hue, SmartThings,
iPads,Tivo,Hikvision,Elk-M1,TED5000,Somfy RTS blinds+ZRTSI, Amazon Echos+Dots, Polk XRT12,
Honeywell Wi-Fi 9000, Caleo Wi-Fi Thermostats, Rainmachine
Posts: 40,483
Threads: 491
Joined: Aug 2002
If you changed to the V2 driver, then definitely fields will be named differently, so you'll have to adjust for that.
You would almost never want to use "Fld Value Equals", as per the Event System Reference document. It goes back to the original field to read the value, but the value that caused the trigger was sent to you in the event.
Use "Is New Fld Value For", which lets you check the actual value that was sent out in the trigger.
If the event dump won't run, I would assume that you didn't open the CQC COmmand Prompt, but just a general command prompt? If so, then the environmental stuff required wouldn't be there, so it wouldn't work.
Dean Roddey
Explorans limites defectum
Posts: 40,483
Threads: 491
Joined: Aug 2002
Oops, we posted at the same time...
Dean Roddey
Explorans limites defectum
Posts: 739
Threads: 33
Joined: Oct 2008
OK creaky door up and running with "Is New Fld Value For" and checking the new V2 field name "elk.SEC#Zone_FrontEntryDoor_Status". Will sort out the
rest of the V2 field names for elk motion sensors and relays tomorrow.
Maybe after you are done with a new HTML5 client
you can look again at playing a wav file directly from a triggered event(I now call VLC to play the wav)
Thanks again
Kevin
_______________
Denon 3808ci, 2112ci ,Sonos, NoVo Grand Concerto, Z-Wave(Lights,Locks), Hue, SmartThings,
iPads,Tivo,Hikvision,Elk-M1,TED5000,Somfy RTS blinds+ZRTSI, Amazon Echos+Dots, Polk XRT12,
Honeywell Wi-Fi 9000, Caleo Wi-Fi Thermostats, Rainmachine
Posts: 40,483
Threads: 491
Joined: Aug 2002
If you are using that field, then don't use a field trigger. It's already sending out a standard Zone Status trigger. Remove the trigger from the field, and change your triggered event to filter to "Is Zone Status For" (I think that's the right one, the one takes the field name and the value to filter for. Check it for Violated, Ready, or NotReady.
It's wasteful of resources to send out one when it's already being sent. And, since it's a standard one it won't be affected if you remove and reload the driver for some reason in the future.
Be sure in the Elk driver to enable that zone to send triggers.
Dean Roddey
Explorans limites defectum
