JeremyLaurenson Posted January 14, 2013 Share Posted January 14, 2013 I have an ELK zone I am monitoring. When the sensor is tripped, the lights brighten to 99% (No 100% available!?) When I am off the call (video call, by the way) they are supposed to dim to 75%. They actually turn off and then go to 75% If Elk Zone "Office Call Sensor" is Normal Then $incall=1 Set 'Jeremy Office Overhead Lifghts' 99% else $incall=0 Run Program 'Office Lights On Normal' (Then Path) Office Lights On Normal: if - No conditions then Set 'Jeremy Office Overhead Lights' 70% Else - No Actions Link to comment
LeeG Posted January 14, 2013 Share Posted January 14, 2013 Set 'xxxxxx' On turns the device to 100% On Level. Run Tools | Diagnostics | Event Viewer with LEVEL 3 selected. Run the Programs and post the trace. From the posted information the device is physically reacting in an unexpected way. What type of device is being controlled by the Program? Link to comment
JeremyLaurenson Posted January 14, 2013 Author Share Posted January 14, 2013 The device is a dual mode insteon high-load dimmer 2477DH- theres also a lamp being controller. I see that its sending off and then on again. Mon 01/14/2013 10:59:31 AM : [ELK 0 40 0] Zone : Ofc Call Sensor : Normal (51/0/0) Mon 01/14/2013 10:59:31 AM : [iNST-TX-I1 ] 02 62 1F 02 73 0F 11 FC Mon 01/14/2013 10:59:31 AM : [VAR 2 1 ] 1 Mon 01/14/2013 10:59:31 AM : [iNST-ACK ] 02 62 1F.02.73 0F 11 FC 06 LTONRR (FC) Mon 01/14/2013 10:59:31 AM : [ELK 0 40 0] Zone : Ofc Call Sensor : EOL (52/2/0) Mon 01/14/2013 10:59:31 AM : [iNST-SRX ] 02 50 1F.02.73 1F.22.3C 2B 11 FC LTONRR (FC) Mon 01/14/2013 10:59:31 AM : [standard-Direct Ack][1F.02.73-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 01/14/2013 10:59:31 AM : [ 1F 2 73 1] ST 252 Mon 01/14/2013 10:59:36 AM : [ELK 0 40 0] Zone : Ofc Call Sensor : Violated (51/2/0) Mon 01/14/2013 10:59:36 AM : [VAR 2 1 ] 0 Mon 01/14/2013 10:59:36 AM : [iNST-TX-I1 ] 02 62 1F 02 73 0F 13 00 Mon 01/14/2013 10:59:36 AM : [iNST-TX-I1 ] 02 62 0A B9 2B 0F 13 00 Mon 01/14/2013 10:59:36 AM : [iNST-ACK ] 02 62 1F.02.73 0F 13 00 06 LTOFFRR(00) Mon 01/14/2013 10:59:37 AM : [iNST-SRX ] 02 50 1F.02.73 1F.22.3C 2B 13 00 LTOFFRR(00) Mon 01/14/2013 10:59:37 AM : [standard-Direct Ack][1F.02.73-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 01/14/2013 10:59:37 AM : [iNST-ACK ] 02 62 0A.B9.2B 0F 13 00 06 LTOFFRR(00) Mon 01/14/2013 10:59:37 AM : [iNST-SRX ] 02 50 0A.B9.2B 1F.22.3C 2B 13 FE LTOFFRR(FE) Mon 01/14/2013 10:59:37 AM : [standard-Direct Ack][0A.B9.2B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 01/14/2013 10:59:38 AM : [iNST-TX-I1 ] 02 62 1F 02 73 0F 11 CC Mon 01/14/2013 10:59:38 AM : [iNST-TX-I1 ] 02 62 0A B9 2B 0F 11 FC Mon 01/14/2013 10:59:38 AM : [ELK 0 40 0] Zone : Ofc Call Sensor : Open (52/1/0) Mon 01/14/2013 10:59:38 AM : [ 1F 2 73 1] ST 0 Mon 01/14/2013 10:59:38 AM : [iNST-ACK ] 02 62 1F.02.73 0F 11 CC 06 LTONRR (CC) Mon 01/14/2013 10:59:38 AM : [ A B9 2B 1] ST 0 Mon 01/14/2013 10:59:38 AM : [iNST-SRX ] 02 50 1F.02.73 1F.22.3C 2B 11 CC LTONRR (CC) Mon 01/14/2013 10:59:38 AM : [standard-Direct Ack][1F.02.73-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 01/14/2013 10:59:38 AM : [ 1F 2 73 1] ST 204 Mon 01/14/2013 10:59:38 AM : [iNST-ACK ] 02 62 0A.B9.2B 0F 11 FC 06 LTONRR (FC) Mon 01/14/2013 10:59:39 AM : [iNST-SRX ] 02 50 0A.B9.2B 1F.22.3C 2B 11 FE LTONRR (FE) Mon 01/14/2013 10:59:39 AM : [standard-Direct Ack][0A.B9.2B-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Mon 01/14/2013 10:59:39 AM : [ A B9 2B 1] ST 255 Link to comment
LeeG Posted January 14, 2013 Share Posted January 14, 2013 As noted the device is being commanded to turn Off then On to a less than 100% On Level. Check the Programs being triggered. The ISY does not turn a device Off on its own. The trace suggests two different Programs are being triggered, each turning Off a separate device. Check Programs | Summary tab, Last Run Time column should show Programs that are being run at that time. Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.