junkycosmos

Thanks Lee! I did Right click the SwitchLinc node, select Diagnostics | Query Insteon Engine and see the following showed in the log calibrating engine version Mon 01/21/2013 07:40:29 PM : [12 31 E6 0 ] May not fully support i2, reverting to i1 in the consul this switch lists av v.38 If that i1 is to be expected for it then I understand and am also glad to hear it is expected behavior. What you mentioned about version would fit my experience earlier of many needing power cycle as I do have a mix of v.38, v.40 and v.36 (on keypads). Another Q (to Lee or anyone else) if I may. While checking into the above I notice a lot of "activity" on my log here that looks a bit funny. Seems I see a lot of "IR press" and also "Previous message ignored". To be fair here it has been a while since I've looked at the log however this seems like a lot ?? Mon 01/21/2013 07:44:18 PM : [ 11 A1 B5 1] ST 255 Mon 01/21/2013 07:44:18 PM : [iNST-SRX ] 02 50 11.A1.B5 00.00.01 C7 11 01 LTONRR (01) Mon 01/21/2013 07:44:18 PM : [std-Group ] 11.A1.B5-->Group=1, Max Hops=3, Hops Left=1 Mon 01/21/2013 07:44:18 PM : [iNST-DUP ] Previous message ignored. Mon 01/21/2013 07:44:19 PM : [ IR] 02AA Press Mon 01/21/2013 07:44:29 PM : [ IR] 0155 Press Mon 01/21/2013 07:44:30 PM : [ IR] 0155 Press Mon 01/21/2013 07:44:30 PM : [ IR] 0155 Press Mon 01/21/2013 07:44:42 PM : [ IR] 012A Press Mon 01/21/2013 07:44:45 PM : [ IR] 012A Press Mon 01/21/2013 07:44:48 PM : [ IR] 0152 Press Mon 01/21/2013 07:44:49 PM : [ IR] 016A Press Mon 01/21/2013 07:44:50 PM : [ IR] 014A Press Mon 01/21/2013 07:44:58 PM : [iNST-SRX ] 02 50 11.A1.B5 00.00.01 C7 13 01 LTOFFRR(01) Mon 01/21/2013 07:44:58 PM : [std-Group ] 11.A1.B5-->Group=1, Max Hops=3, Hops Left=1 Mon 01/21/2013 07:44:58 PM : [ 11 A1 B5 1] DOF 1 Mon 01/21/2013 07:44:58 PM : [ 11 A1 B5 1] ST 0 Mon 01/21/2013 07:44:58 PM : [ IR] 0295 Press Mon 01/21/2013 07:45:03 PM : [ IR] 012A Press Mon 01/21/2013 07:45:04 PM : [ IR] 01AA Press Mon 01/21/2013 07:45:08 PM : [ IR] 0195 Press Mon 01/21/2013 07:45:15 PM : [ IR] 0295 Press Mon 01/21/2013 07:45:18 PM : [ IR] 0154 Press Mon 01/21/2013 07:45:20 PM : [ IR] 0155 Press Mon 01/21/2013 07:45:21 PM : [ IR] 012A Press Mon 01/21/2013 07:45:22 PM : [ IR] 012A Press Mon 01/21/2013 07:45:25 PM : [ IR] 02D5 Press Mon 01/21/2013 07:45:26 PM : [ IR] 014A Press Mon 01/21/2013 07:45:27 PM : [ IR] 0295 Press Mon 01/21/2013 07:45:31 PM : [ IR] 00AA Press Mon 01/21/2013 07:45:34 PM : [ IR] 01AA Press Mon 01/21/2013 07:45:38 PM : [ IR] 0095 Press Mon 01/21/2013 07:45:38 PM : [ IR] 012A Press Mon 01/21/2013 07:45:41 PM : [ IR] 012A Press Mon 01/21/2013 07:45:42 PM : [ IR] 02AA Press Mon 01/21/2013 07:45:47 PM : [ IR] 02AA Press Mon 01/21/2013 07:45:48 PM : [ IR] 0155 Press Mon 01/21/2013 07:45:48 PM : [ IR] 0155 Press Mon 01/21/2013 07:45:50 PM : [ IR] 0152 Press Mon 01/21/2013 07:45:52 PM : [ IR] 0155 Press Mon 01/21/2013 07:45:59 PM : [ IR] 0155 Press Mon 01/21/2013 07:46:01 PM : [ IR] 0155 Press Mon 01/21/2013 07:46:04 PM : [ IR] 015A Press Mon 01/21/2013 07:46:05 PM : [ IR] 012A Press Mon 01/21/2013 07:46:06 PM : [iNST-TX-I1 ] 02 62 00 00 15 CF 13 00 Mon 01/21/2013 07:46:06 PM : [iNST-ACK ] 02 62 00.00.15 CF 13 00 06 LTOFFRR(00) Mon 01/21/2013 07:46:06 PM : [ 15 61 C5 3] ST 0 Mon 01/21/2013 07:46:06 PM : [ 14 6B C4 1] ST 0 Mon 01/21/2013 07:46:06 PM : [iNST-TX-I1 ] 02 62 00 00 2A CF 11 00 Mon 01/21/2013 07:46:06 PM : [ 12 31 60 1] ST 0 Mon 01/21/2013 07:46:06 PM : [iNST-ACK ] 02 62 00.00.2A CF 11 00 06 LTONRR (00) Mon 01/21/2013 07:46:07 PM : [iNST-TX-I1 ] 02 62 00 00 2A CF 13 00 Mon 01/21/2013 07:46:07 PM : [ 15 61 C5 3] ST 255 Mon 01/21/2013 07:46:07 PM : [iNST-ACK ] 02 62 00.00.2A CF 13 00 06 LTOFFRR(00) Mon 01/21/2013 07:46:07 PM : [ 15 61 C5 3] ST 0 Mon 01/21/2013 07:46:08 PM : [iNST-SRX ] 02 50 13.FA.29 00.00.01 C7 13 01 LTOFFRR(01) Mon 01/21/2013 07:46:08 PM : [std-Group ] 13.FA.29-->Group=1, Max Hops=3, Hops Left=1 Mon 01/21/2013 07:46:08 PM : [ 13 FA 29 1] DOF 1 Mon 01/21/2013 07:46:08 PM : [iNST-SRX ] 02 50 13.FA.29 00.00.01 C7 13 01 LTOFFRR(01) Mon 01/21/2013 07:46:08 PM : [std-Group ] 13.FA.29-->Group=1, Max Hops=3, Hops Left=1 Mon 01/21/2013 07:46:08 PM : [iNST-DUP ] Previous message ignored. Mon 01/21/2013 07:46:17 PM : [ IR] 012A Press Mon 01/21/2013 07:46:17 PM : [ IR] 015A Press Mon 01/21/2013 07:46:18 PM : [iNST-SRX ] 02 50 13.FA.29 00.00.01 C7 11 01 LTONRR (01) Mon 01/21/2013 07:46:18 PM : [std-Group ] 13.FA.29-->Group=1, Max Hops=3, Hops Left=1 Mon 01/21/2013 07:46:18 PM : [ 13 FA 29 1] DON 1 Mon 01/21/2013 07:46:18 PM : [ 13 FA 29 1] ST 255 Mon 01/21/2013 07:46:18 PM : [iNST-SRX ] 02 50 13.FA.29 00.00.01 C7 11 01 LTONRR (01) Mon 01/21/2013 07:46:18 PM : [std-Group ] 13.FA.29-->Group=1, Max Hops=3, Hops Left=1 Mon 01/21/2013 07:46:18 PM : [iNST-DUP ] Previous message ignored. Mon 01/21/2013 07:46:18 PM : [ IR] 02AA Press Mon 01/21/2013 07:46:21 PM : [ IR] 014A Press Mon 01/21/2013 07:46:32 PM : [ IR] 0155 Press Mon 01/21/2013 07:46:32 PM : [ IR] 012A Press Mon 01/21/2013 07:46:33 PM : [ IR] 015A Press I have never made any use of the IR function on the ISY and about 30mins ago I did just place a piece of tape over the IR sensor. Thanks for any input on the DUP messages and the IR J

Can someone remind me if this is usual behavior for the Insteon SwitchLinc Dimmer (2476D) ? Seems when I adjust the On Level [Applied Locally] % the change is updated in the ISY admin consul and insteon traffic does occur however the switch device behavior does not "take effect" unless I air-gap the switch for a few seconds. For example Dining Rec 12.31.E6 While in My Lighting click directly on the unit On Level [Applied Locally] 35% grab slider and move to 100% Following traffic is seen Mon 01/21/2013 06:40:33 PM : [iNST-TX-I1 ] 02 62 12 31 E6 0F 11 FF Mon 01/21/2013 06:40:33 PM : [iNST-ACK ] 02 62 12.31.E6 0F 11 FF 06 LTONRR (FF) Mon 01/21/2013 06:40:34 PM : [iNST-SRX ] 02 50 12.31.E6 0F.D9.29 2B 11 FF LTONRR (FF) Mon 01/21/2013 06:40:34 PM : [std-Direct Ack] 12.31.E6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 01/21/2013 06:40:34 PM : [ 12 31 E6 1] ST 255 Mon 01/21/2013 06:40:34 PM : [ 12 31 E6 1] OL 255 Mon 01/21/2013 06:40:34 PM : [iNST-TX-I1 ] 02 62 12 31 E6 0F 28 00 Mon 01/21/2013 06:40:34 PM : [iNST-ACK ] 02 62 12.31.E6 0F 28 00 06 SET-MSB(00) Mon 01/21/2013 06:40:35 PM : [iNST-SRX ] 02 50 12.31.E6 0F.D9.29 2B 28 00 SET-MSB(00) Mon 01/21/2013 06:40:35 PM : [std-Direct Ack] 12.31.E6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 01/21/2013 06:40:35 PM : [iNST-TX-I1 ] 02 62 12 31 E6 0F 2B 32 Mon 01/21/2013 06:40:35 PM : [iNST-ACK ] 02 62 12.31.E6 0F 2B 32 06 PEEK (32) Mon 01/21/2013 06:40:35 PM : [iNST-SRX ] 02 50 12.31.E6 0F.D9.29 2B 2B 59 PEEK (59) Mon 01/21/2013 06:40:35 PM : [std-Direct Ack] 12.31.E6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 01/21/2013 06:40:35 PM : [iNST-TX-I1 ] 02 62 12 31 E6 0F 29 FF Mon 01/21/2013 06:40:35 PM : [iNST-ACK ] 02 62 12.31.E6 0F 29 FF 06 POKE (FF) Mon 01/21/2013 06:40:36 PM : [iNST-SRX ] 02 50 12.31.E6 0F.D9.29 2B 29 FF POKE (FF) Mon 01/21/2013 06:40:36 PM : [std-Direct Ack] 12.31.E6-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Mon 01/21/2013 06:40:47 PM : [iNST-SRX ] 02 50 11.B2.80 0F.D9.29 07 6F 1C (1C) Mon 01/21/2013 06:40:47 PM : [std-Direct ] 11.B2.80-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Mon 01/21/2013 06:40:47 PM : [ 11 B2 80 1] CLIHUM 28 Manually click switch standard "ON" and the switch still only turns onto 35% (not 100% as set) Airgap the switch for 2 seconds Manually click switch standard "ON" and the switch still only turns onto 35% In attempting to change local ON levels for approx a dozen switchlinc dimmers tonight I ran into roughly 2/3 that needed to be power cycled to pick up the new On level for manual ON clicks. With unit above (12.31.E6) sticker says 2676D rev 4.5 I replicated the issue a few times. It has been a while (time and firmware) since I adjusted many ON levels or Ramp Rate for these dimmers so I might be forgetting the need to power cycle them to pick up the new levels. Appreciate any info or possibly a reminder that its always been this way?? Thx Junkycosmos ISY 99ir pro / 3.3.9 (but will be 3.3.10 shortly) PS: I've been ISY'ed for 3yrs or so now and I too would have ripped out my Insteon units (100+) without this forum and the UDI gang. In the last month I have a friend who is playing with Zwave a bit and trying out a micasa. While being a neat device it, the interface and capabilities are surprisingly unpolishied. After reaching out to their forums and support it was clear to me why. Huge difference here with this group and UDI !

Hi All ! Quick report that I just upgraded from 3.1.17. Hey no laughing, its been a while I know. Anyways upgrade went smooth as usual. Thanks again Team for another great update. Junkycosmos (99ir pro)

thanks Lee! Now I follow why my manual tests were not working. I did check back and found a single email alert from 7/28 when last report would have been 24 hours old. Hence indeed these programs are working exactly as they should. For some reason my I was thinking they would repeat but I see now they would not. Any idea on a way to get the alert to repeat? I did just check to see if I could set condition of last run time in a range but it does not appear work. Suppose what I am looking for is Last Run > X hours but I am not seeing an obvious method. Thanks for the info on prior post and if you have any other suggestions here. J

Hi All I have been using the program posted here by wrj0 for a few months now. What I have noticed though is inconsistent results. Sometimes I recieve reports sensor watch and other times I have not when batts have died. Looking for any ideas on what I have done wrong here please. I do not understand why "SensorReport 0 in 24hrs DwnMotion2" program is showing as false. My "Dwn Motion" sensor that looks to have died on 7/27 Choosing "Run If" on Sensor Report I get nothing and program stays false. I did try resaving program and also tested run then which does send notificaiton thanks for any suggestions J ****** Program: SensorWatch DwnMotion Enabled LastRun Time: Fri 2012/07/27 01:29:02 AM If Control 'Sensors / DwnMotion-Sensor' is switched On Or Control 'Sensors / SensorDusk / DwnMotion-Dusk/Dawn' is switched On Or Control 'Sensors / SensorDusk / DwnMotion-Dusk/Dawn' is switched Off Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action') ******* Program: SensorReport 0 in 24hrs DwnMotion2 Enabled Status False If Time is Last Run Time for 'SensorWatch DwnMotion' + 24 hours And Status 'KeyPadLincs / JOffice.E' is not On Then Send Notification to 'J_All' content 'MyTemplate' Else - No Actions - (To add one, press 'Action') *********

Thanks Michel. Just sent email with details. Look forward to hearing from you. here is an updated Stats from switch for port ISY is connected to: no errors I reset the counters day I moved ISY to warm cabinet. Port 3 TX Bytes 291531819 UnicastPkts 1218485 DropPkts 0 MulticastPkts 796259 PausePkts 0 BroadcastPkts 248689 FrameInDisc 0 DeferredTransmit 0 Collision 0 LateCollision 0 ExcessiveCollision 0 RX Bytes 307564793 UnicastPkts 1214850 DropPkts 0 MulticastPkts 42488 PausePkts 0 BroadcastPkts 609 ExcessSizeDisc 0 UnderSizePkts 0 OverSizePkts 0 Jabbers 0 Fragments 0 FCSErrors 0 SAChanges 0 64 BytePkts 595309 65 to 127 BytePkts 200376 128 to 255 BytePkts 2652 256 to 511 BytePkts 258345 512 to 1023 BytePkts 132495 1024 to 1522 BytePkts 68770

Hi Michel Thanks for the reply. Pardon if I was not completely clear. I understand your question on network and I did try removing it during troubleshooting. Switch is a sits behind a Cisco router and a Sonic wall. ISY has worked great with this switch since I started with it. Prior setup: Network switch <-- 60 foot cat6 drop, 1 foot cat5 jumper --> ISY <--1 foot cat5--> PLM which is plugged into outlet next to service panel in garage Leaving the PLM plugged into the outlet right next to my service panel/circuit breaker box gives benefit of PLM (with piggybacked AP) as close to all branch circuits as possible. Last spring when I moved it to this location I immediately noted improvement in Insteon communications; near complete reduction of errors and also improvement in Insteon query speeds. Disadvantage was when the temperatures got cold this winter I ran into strange issues. Had posted prior of Ethernet packet /network errors and we concluded possible Ethernet line noise. I went through a bunch of experiments: new cables, new connectors, even tried a different network switch, straight to router, replaced original SD card with san disk extreme, all no dice. More crazy yet was the mysterious problem would only come when temps were rather cold AND problem was only for Ethernet communications (ISY to PLM and powerline traffic was fine). Setup now: Network switch <--1 foot cat5--> ISY <-- 60 foot cat6 drop, 1 foot cat5 jumper --> PLM which is plugged into outlet next to service panel in garage. This moves the ISY into an temp controlled environment along with the network gear. Was originally slightly concerned on spanning the serial connection from the ISY to PLM over such a distance but all appears to be running just fine after move yesterday and from other posters. I did not move the PLM into the same location for two reasons: the environment box is only UPS powered (insteon traffic outside of UPS only) and I did not want to add back in a 60 foot span of romex for all PLM power line communications. I surely do not blame the ISY for not handling temps under freezing well but I also could see others running into since it is a common scenario to mount your ISY close to your service panel. thx J

Thank you all for the input. I really like the UDI Forum! For some reason I was recalling a max suggested length of 5' or something on the serial cat5 link between ISY and PLM. Great to hear others are having success with longer serial cat5 cable runs. Have moved ISY into environment box that keeps 45-75 degrees (with network gear). ISY is now connected to PLM via approx a 60 foot cat5/6 cable. All appears to be running great. Noted ISY board does have a capacitor, a crystal and a battery; suppose one of those might be who was giving trouble staying loosing sync with Ethernet traffic in temps under 25 while the Insteon traffic and programs still ran fine. As Lee noted PLM does generate some internal heat so clearly the components in it are not actually facing the lower temps although the air temp around the PLM has dropped well below 0F. Thanks Again. J

This time of year the garage is rather cold and I have found that having my ISY mounted on the wall next to my service panel where it occasionally experiences very cold temps has given me trouble. Specifically what I have noticed is any time the ISY is under 20 degrees F it looses ability to communicate on the Ethernet. This manifests in poor backup speeds (15mins vs usual 2min), loss of connection to mobilinc, no longer receiving any communication emails. Checking the switch that the ISY is connected to reveals lots of packet errors coming from ISY. Interesting (and thankfully) all Insteon related communications, programs etc remain fully functional. And when temps return to above 25 the ISY regains full Ethernet connection ability. Now I really cannot blame ISY for being semi non functional in the artic temps however I am looking to resolve my issue. Currently the ISY is connected to the PLM by a 1 foot cat5 cable. The PLM then plugs into an outlet right next to main service panel. I should note that having my PLM right next to my panel worked magic to fix remaining Insteon issues I had prior. I am interested to know if others have tried a longer Cat5 cable between their ISY and PLM with much success. If so how long ? Has anyone run into troubles, if so what were the symptoms you encountered? Appreciate any input here or other ideas as my next step may be moving the ISY to an inside location while leaving the PLM in place but this would mean using nearly a 35 foot cat5 between the ISY and PLM. Stats from switch for ISY port. I have tried other drop cables and other ports with same results. Port 3 TX Bytes 2416799963 UnicastPkts 9145633 DropPkts 0 MulticastPkts 6763038 PausePkts 0 BroadcastPkts 2257165 FrameInDisc 0 DeferredTransmit 0 Collision 0 LateCollision 0 ExcessiveCollision 0 RX Bytes 2215242106 UnicastPkts 8911522 DropPkts 0 MulticastPkts 319600 PausePkts 0 BroadcastPkts 4551 ExcessSizeDisc 0 UnderSizePkts 0 OverSizePkts 0 Jabbers 0 Fragments 1873 FCSErrors 2328 SAChanges 0 64 BytePkts 4441348 65 to 127 BytePkts 1483523 128 to 255 BytePkts 19835 256 to 511 BytePkts 1850860 512 to 1023 BytePkts 953916 1024 to 1522 BytePkts 493443 thanks J (isy 99irpro)

Was just now trying to use the download link from 1st post of this thread for 3.1.15 on 99i of http://www.universal-devices.com/update ... 3.1.15.zip and it is re-directing to http://pagesinxt.com/?dn=www.universal- ... s&nxte=zip Also noted that if I go to universal-devices.com it redirects to http://www.universal-devices.com which looks to be the under contruction topics page my network solutions. This is all on DNS server 8.8.8.8 (google public one). GLuck with fast recovery. J

Another option might be the beep function to help get attention. You will need to test it with your keypad as some versions of switches and keypads support it.

Michel, Thanks for the reply and suggestions on the FCS errors. I am now investigating the drop, switch port (although prior tested), PoE line to ISY, plug on ISY for possible line noise etc. Will post back when I have something conclusive. **** Sorry to shift gears here but I do have one small/minor thing to note in my move from 3.10 to 3.12. Just noticed a slight change one of my alert emails, looking back it appears to have happened with changed to 3.12. The status in body "ON" changed to "DON". Program Driveway: If Control 'TriggerLincs / DrivewayMotionLink-Opened' is switched On And Status 'JOffice.E' is not On Then Send Notification to 'J_All' content 'MyTemplate' Else - No Actions - (To add one, press 'Action') Customized Content: "My Template" Subject ISY ${alert.program.name} Body ${alert.event} at ${alert.date} ${alert.time24} On 3.10 (and prior) alert email example read as follows: ISY Driveway 'DrivewayMotionLink-Opened' set On at 2011/11/19 17:55:38 After 3.12 update alert email example now reads as follows: ISY Driveway 'DrivewayMotionLink-Opened' set DON at 2011/11/22 13:36:11 Very minor thing in terms of usability but I wanted to report/note incase it’s a sign of something larger. Maybe you already have a quick explanation or the new result is expected? Thanks Much J

Thx Michel for the reply. I do not have an ELK system (at least not yet..) Understood on the benign errors although I did just still see a "UDQ:Queue Full: LOG" when ISY rebooted on 3.12 for change of IP address I just did at 10:17:19. Still would like to sort out the ongoing network errors as they do not seem normal. Checked my network switch again this AM and while I do not see any noticeable slowdown with ISY on admin as I did days prior my switch is still seeing TCP/IP transmission errors from ISY. Have tried new network cables, switch ports, change of IP to ensure no IP conflict, tested clean with laptop (no port errors etc) SWITCH PORT STATISTICS (reset yesterday evening post 3.12) Tx 553609 RX 352928 Tx Error 0 Rx Error (coming from ISY) 76 Error log in ISY shows ongoing network errors. Here is a sample but these network errors go on continually. Tue 2011/11/22 10:11:16 AM System -170001 [Network] Established Tue 2011/11/22 10:11:31 AM System -100 No network connection Tue 2011/11/22 10:11:35 AM System -170001 [Network] Established Tue 2011/11/22 10:11:50 AM System -100 No network connection Tue 2011/11/22 10:11:59 AM System -170001 [Network] Established Tue 2011/11/22 10:15:34 AM System -100 No network connection Tue 2011/11/22 10:15:38 AM System -170001 [Network] Established Tue 2011/11/22 10:16:58 AM System -5012 43 Tue 2011/11/22 10:17:53 AM System -170001 UDQ:Queue Full: LOG Tue 2011/11/22 10:18:03 AM System -170001 UDQ:Queue Full: LOG Tue 2011/11/22 10:18:13 AM System -170001 UDQ:Queue Full: LOG Tue 2011/11/22 10:18:32 AM System -170001 UDQ:Queue Full: LOG Tue 2011/11/22 10:18:42 AM System -170001 UDQ:Queue Full: LOG Tue 2011/11/22 10:18:52 AM System -170001 UDQ:Queue Full: ERROR_LOG Tue 2011/11/22 10:17:19 AM System -5 Start Tue 2011/11/22 10:17:36 AM System -100 No network connection Tue 2011/11/22 10:18:57 AM System -100 No network connection Tue 2011/11/22 10:19:01 AM System -170001 [Network] Established Tue 2011/11/22 10:22:27 AM System -100 No network connection Tue 2011/11/22 10:22:31 AM System -170001 [Network] Established Tue 2011/11/22 10:26:25 AM System -100 No network connection Tue 2011/11/22 10:26:30 AM System -170001 [Network] Established Tue 2011/11/22 10:30:35 AM System -100 No network connection More details on from switch port that ISY is connected to Port 3 TX Bytes 68395827 UnicastPkts 337553 DropPkts 0 MulticastPkts 165910 PausePkts 0 BroadcastPkts 50432 FrameInDisc 0 DeferredTransmit 0 Collision 0 LateCollision 0 ExcessiveCollision 0 RX (from ISY) Bytes 100017821 UnicastPkts 343130 DropPkts 0 MulticastPkts 9880 PausePkts 0 BroadcastPkts 125 ExcessSizeDisc 0 UnderSizePkts 0 OverSizePkts 0 Jabbers 0 Fragments 5 FCSErrors 28 SAChanges 0 64 BytePkts 153072 65 to 127 BytePkts 63875 128 to 255 BytePkts 1874 256 to 511 BytePkts 69361 512 to 1023 BytePkts 35005 1024 to 1522 BytePkts 30019 Thanks for any input or suggestions. J

Updated to 3.1.12 today with help from Rand and Daryl (thanks again guys!) while troubleshooting a very strange slow network (tcp/ip not insteon) performance in Admin consul and Mobilic over last day after running 3.10 for few weeks. The slowness issue is gone and appeared to ghost away from Daryls call and turning off windows defender however I can not reproduce the issue turning defender back on so it remains a bit of a mystery. I do have two questions regarding errors I see now (and did so in 3.10): A. on occasion I see a popup in the consul of system busy FileOpen ] Open failed for [/CONF/ELECMTR.CFG] ®. B. checking error log I see a lot of entries, some mentioning UDQ: Queue Full: LOG. Any input on what these are about would be great. thx much J (non ELK ISY 99ir/pro) Mon 2011/11/21 02:55:47 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:05 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:15 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:25 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:35 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:46 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:56:56 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 02:55:08 PM System -5 Start Mon 2011/11/21 02:55:24 PM System -170001 [Network] Established Mon 2011/11/21 02:55:27 PM System -80004 n/a Mon 2011/11/21 04:03:49 PM System -100 No network connection Mon 2011/11/21 04:03:53 PM System -170001 [Network] Established Mon 2011/11/21 04:32:56 PM System -5012 28 Mon 2011/11/21 04:51:41 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:51:53 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:52:04 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:52:14 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:52:25 PM System -170001 UDQ:Queue Full: LOG Mon 2011/11/21 04:51:07 PM System -5 Start Mon 2011/11/21 04:51:24 PM System -170001 [Network] Established Mon 2011/11/21 07:01:46 PM System -140005 CLI-WBug Mon 2011/11/21 09:12:56 PM System -10011 n/a Mon 2011/11/21 09:27:37 PM System -5012 27 Mon 2011/11/21 09:28:04 PM System -100 No network connection Mon 2011/11/21 09:28:12 PM System -170001 [Network] Established Mon 2011/11/21 09:28:32 PM System -100 No network connection Mon 2011/11/21 09:28:36 PM System -170001 [Network] Established Mon 2011/11/21 09:29:01 PM System -10011 n/a Mon 2011/11/21 09:29:26 PM System -100 No network connection Mon 2011/11/21 09:29:31 PM System -170001 [Network] Established Mon 2011/11/21 09:31:24 PM System -100 No network connection Mon 2011/11/21 09:31:29 PM System -170001 [Network] Established Mon 2011/11/21 09:34:24 PM System -100 No network connection Mon 2011/11/21 09:34:29 PM System -170001 [Network] Established Mon 2011/11/21 09:36:13 PM System -5012 30

Thank you (again) Lee. Adjusted as you suggested and works. I was thinking of this from a scene perspective and not who controls the scene level (the motion sensor). Corrected day program If From Sunrise To Sunset - 1 hour (same day) Then In Scene 'Sensors / SunPorch-Sensor' Set 'SunPorchbyFR' 10% (On Level) Else - No Actions - (To add one, press 'Action')

Q here for those knowledgeable on "scene adjust" Can I control on level of a scene that is directly called by a motion sensor ? I have a scene "Sunporch" that contains four members. 2420M motion sensor 2486D keypadlinc dimmer button B 2485S keypadlinc relay button B 2476D switchlinc dimmer v.38 "SunPorchbyFR" The switchlinc is wired to entrance way light. I have all four linked directly to this scene as controllers, motion sensor included as so there is no delay in turning on the light via ISY program. What I would like todo is set "on level" for this scene to 10% during the daytime hours and at 50% or so during evening time hours. I have programs below set and running ok but the actual on level of the light when motion sensor sets the scene on does not change. In the admin consul clicking on Scene "SunPorch" I can see the On Level changing but clicking on the member of that scene "SunPorchbyFR" the On Level [Applied Locally] does not change. Was looking at using these two programs: DayProgram If From Sunrise To Sunset - 1 hour (same day) Then In Scene 'SunPorch' Set 'SunPorchbyFR' 10% (On Level) Else - No Actions - (To add one, press 'Action') NightProgram If From Sunset - 1 hour To Sunrise (next day) Then In Scene 'SunPorch' Set 'SunPorchbyFR' 50% (On Level) Else - No Actions - (To add one, press 'Action') I have been successfully using nearly the same for a bathroom setup that dims at night however that setup has the ISY calling the scene when control of motion is turned on. Thanks for any input. J

Upgrade of files went smooth. ISY took a long time with initial a status bar scroll after 1st reboot (3-5mins). All start up programs ran quickly in background during scroll and it completed fine. ****** Very nice addition on the Remote Linc2 support - thank you ! small stumbles I had adding Remote Linc2 1st time I tired to add (via add device, specified address and device) I forgot to put RL2 into linking mode. Did not receive warning message to place RL2 into linking mode but instead received error of "Failed writing the high water mark, Node not added - failed removing links". On my 2nd try I started with putting the RL2 into linking mode than did add device ... This time ISY placed new device names in My Lighting but they had i/o/i/o/i/o green mark. Clicked green button at top of screen to automatically write to devices, received nice pop up message informing me to battery powered devices into linking mode. 1 sec after clicking OK all green marks cleared (super quick). Device added 8 entries in My Lighting; small note that devices are numbered slightly off to start instead of lettered. No big deal to rename but order stays slightly off in list. remote linc = controlled by button B remote linc - 2 = controlled by button A remote linc - 3 = controlled by button D remote linc - 4 = controlled by button C remote linc - 5 = controlled by button F remote linc - 6 = controlled by button E remote linc - 7 = controlled by button H remote linc - 8 = controlled by button G ****** Thermostats: Confirmed the query V2 Thermostats for Fan Mode and Heat/Cool status is also working nicely with two Tstats on v.92. Thank you again. Noticed set the "Set Options" button on the Tstat page which reveals option to report humidity. On the default setting here: One Tstat had the option checked by default (TstatUp) but the other Tstat has the option unchecked (Tstat Down). Will we need to check that option now to have HUM updates to ISY ? ****** Agreed with prior posters here about how good this product is both from the continued updates and excellent support. Thank you and nice work UDI Team

Hi Michel Good news to report here on the motion sensor and -2 errors. Since I deleted and successfully re-added to ISY above I had seen no more -2 errors from that motion sensor. One item I failed to note prior was that I accidentally renamed my motion sensor the same name it was prior to removal. Had not thought much about it but later I noticed that the re-added motion sensor seemed to be automatically recognized by a few previous programs (batt low and dusk). Said otherwise the programs did not state "unspecified device" like I am used to seeing when a device is removed. Almost as if the programs automatically recognized the old previously deleted device and placed it back into the program when I re-added it. No big deal but I wanted to mention. Separately I'll note that I do continue to see a few other -2 errors which date back long time from other units so I am curious actions I could take to clear those up eventually. Sensors / MOfficeM2-Sensor Tue 2011/09/06 10:46:31 AM System -2 Sensors / MOfficeM2-Sensor Tue 2011/09/06 01:17:05 PM System -2 ((removed and re-added MOfficeM2 sensor)) JeffOfficeFan2 Tue 2011/09/06 02:57:24 PM System -2 MOfficeR Tue 2011/09/06 04:27:37 PM System -2 Sensors / SunPorch-Sensor Tue 2011/09/06 06:07:54 PM System -2 Sensors / DwnMotion-Sensor Tue 2011/09/06 06:26:50 PM System -2 Sensors / MasterBath-Sensor Wed 2011/09/07 07:22:00 PM System -2 GarageMotionLight Wed 2011/09/07 08:04:38 PM System -2 Sensors / DwnMotion-Sensor Thu 2011/09/08 04:09:18 PM System -2

With the minor annoyance of the prior issues with the stat 2441 stat adaptor aside (SH issue with firmware) I have been very happy with our 2 zone setup. I went with a honeywell zone controller board in between the t1900s for some measure of safety after seeing a few horror storries of wireless going wacky. Might be isolated case noted here http://forum.universal-devices.com/viewtopic.php?f=25&t=4727&hilit=fried+ac but prior to zoning I also encountered something similiar of a "bouncing loop" with my own T1900 turning my humidifer on and off I would also note that the support guy at Venstar was very helpful but in the end we found no good explaination. Current setup with 2 t1900s both with a 2441V works great and the ISY makes programming simple while the zone controller by honeywell has reasonable safety limits and lock outs. Zone board has both overheat and overcool limits. Noted I did go with the higher end zone board with more than needed zones since it has options for multi stage heat that can be locked out by preset outdoor temp. I.E. Leaving windows open at night and the furnace will not kick into 2nd stage heat trying to warm the yard. Hope the links don't offend anyone but I have ordered from this place with success, unit appeared new non gray market. HZ432K https://www.pexuniverse.com/honeywell-t ... -panel-kit C7089U1006 https://www.pexuniverse.com/c7089u1006- ... oor-sensor J

Michel, understood and agreed tried adding device 3rd time .. this with remove links, specified address, and specified unit (10.01 2420 Motion) and received a weird failure.. Took the motion sensor out of linking mode and retried the exact same steps as 3rd try above and it added quickly (6 seconds or so). Now that sensor is re-added I will place back in original location and see if errors persist.

Hi Michel Thanks for the reply. Just removed the device and attempted to re-added it (remove links, auto discover type, specified address of 11.9F.F4). After about 1 minute I was given the error "Node not added - failed restoring device" Please see screen shot as it also mentions CLI WBug Tried second time to add unit back in and received similar error, again after 3 scrolls of status bar. Do I need to specify the device type ? Noted too that I only recently added this particular sensor to the ISY about a wee back to replace one that completely died. This unit is "new" but was in the closet for a while and is a v1.1. The other units which show the occasional -2 have been on the network for a few months.

Michel, Correct. Looking back I do have a few prior warning emails from April of this year. Sometime after that I did have three units die of dead batts with no warning. Looking now in the ISY current state of battery status is blank on all of them except for the one I just queried that now shows "off". Could it be that after a power cycle from prior version upgrade that the batt status just stayed as blank and never triggered to "On" ? Entirely separate note on the -2 errors noted in log. I have one motion sensor that is giving these pretty regularly. Few other devices on occasion give -2 but none give regular errors like this one. Noted that this Motion sensor is only linked to ISY, is about 10 feet from ISY's PLM, and has a few lithium batt. Sensors / DwnMotion-Sensor Tue 2011/09/06 06:31:45 AM System -2 Sensors / MOfficeM-Sensor Tue 2011/09/06 06:58:36 AM System -2 Sensors / MOfficeM-Sensor Tue 2011/09/06 07:35:53 AM System -2 Sensors / MOfficeM-Sensor Tue 2011/09/06 10:07:10 AM System -2 Sensors / DwnMotion-Sensor Tue 2011/09/06 10:08:07 AM System -2 Sensors / MOfficeM-Sensor Tue 2011/09/06 10:46:31 AM System -2

Hi Michel, I have seven of the motion sensors 2420M. Long time back they used to alert in ISY with Low Batt signal before going completely out but now they do not anymore. I cannot recall exactly which ISY version used to display the low batt indicator. This was also way back when the low batt "on" would stay stuck in ISY after changing the battery in the motion sensors. My sensors are a mix of old and v2.0. ISY usually receives their on/off status updates (maybe 90% of the time), motion sensors directly linked to switchlincs or kpls trigger near flawlessly (99.5% of the time). would be great to increase the consistency of ISY reading motion sensors and would be great to have the low batt warning back If I can help test something for you all here just let me know. thx J (isy99ir pro 3.1.6) here are a few of the errors I noted from log related to motion sensors Sensors / MOfficeM-Sensor Sun 2011/09/04 12:46:53 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 01:18:57 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 05:23:36 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 06:49:45 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 10:07:47 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 11:51:45 AM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 12:51:40 PM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 01:00:39 PM System -2 Sensors / MOfficeM-Sensor Sun 2011/09/04 05:26:36 PM System -2 Sensors / DwnMotion-Sensor Sun 2011/09/04 08:47:41 PM System -2 GarageMotionLight Mon 2011/09/05 07:10:08 AM System -2 Sensors / MOfficeM-Sensor Mon 2011/09/05 07:54:23 AM System -2 Sensors / MOfficeM-Sensor Mon 2011/09/05 08:22:37 AM System -2 Sensors / DwnMotion-Sensor Mon 2011/09/05 11:18:52 AM System -2

same here; I did note some prior errors in separate thread http://forum.universal-devices.com/viewtopic.php?f=27&t=6556 Two nights ago I ran into issue with ISY also locking up. Noted I am still on 3.14 and this is maybe the 2nd lockup I have ever experienced in 3yrs of running betas etc. For me, my lockup occurred when I had admin console open on 1PC and was trying to open mobilinc (fresh install of) on iphone. Mobilinc was working on syncing my devices (I had clicked tap to sync) and I was doing no action in the admin console on PC. After about 2 mins with no response on sync I noticed the flag on bottom left of Admin was red. Tried closing admin and rebooting iphone just to be sure no connection was still open from client. Tried to relaunch Admin on PC and received no response from ISY. Gave up for a while then came back and noted that both power and tx light were locked on in the ISY. Power cycled the ISY and all came back just fine. When I look in my log I see a lot of -5011 rows all at same time stamp prior to the hang. Also I do have very regular errors from wBug. If anyone wants the log or has questions I can send. thx J Tue 2011/08/02 12:56:16 AM System -140005 CLI-WBug Tue 2011/08/02 01:00:17 AM System -140005 CLI-WBug Tue 2011/08/02 01:24:29 AM System -5012 n/a Tue 2011/08/02 01:30:56 AM System -5012 n/a Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:30:56 AM System -5011 uuid:00:21:b9:00:00:1e,210 Tue 2011/08/02 01:35:10 AM System -5012 n/a Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 01:35:10 AM System -5011 uuid:00:21:b9:00:00:1e,212 Tue 2011/08/02 02:52:36 AM System -5 Start Tue 2011/08/02 02:53:00 AM System -140005 CLI-WBug Tue 2011/08/02 02:53:57 AM System -140005 CLI-WBug Tue 2011/08/02 02:54:45 AM System -5012 n/a Tue 2011/08/02 02:59:17 AM System -170001 [uDSockets] RSub:26 error:6 Tue 2011/08/02 02:59:23 AM System -5012 n/a Tue 2011/08/02 03:01:51 AM System -140005 CLI-WBug Tue 2011/08/02 03:03:51 AM System -140005 CLI-WBug Tue 2011/08/02 03:06:51 AM System -140005 CLI-WBug Tue 2011/08/02 03:16:52 AM System -140005 CLI-WBug Tue 2011/08/02 03:18:04 AM System -5012 n/a Tue 2011/08/02 03:39:52 AM System -140005 CLI-WBug Tue 2011/08/02 03:44:53 AM System -140005 CLI-WBug Tue 2011/08/02 03:50:52 AM System -140005 CLI-WBug Tue 2011/08/02 03:58:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:05:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:09:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:15:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:18:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:23:53 AM System -140005 CLI-WBug Tue 2011/08/02 04:28:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:32:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:35:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:38:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:51:52 AM System -140005 CLI-WBug Tue 2011/08/02 04:52:52 AM System -140005 CLI-WBug Tue 2011/08/02 05:08:52 AM System -140005 CLI-WBug

Question on support of load status for the 2477SA2 220v normally closed load controller. I searched and found a few discussions on here regarding support for load sense but never saw full conclusion. There are a few entries in the beta 2.17 and 2.18 asking how the ISY displays what might be considered "node2" or load sense for this device. I have verified that the recent version unit received from SH (r1.0 2910 received 2wks ago) had load led that follows load status pretty well when 2477SA2 main relay is off. Closing and opening the load circuit while the main 2477sa2 is off had the load led follow correctly. Toggling 2477sa2 relay on/off quickly can cause the load led to getbstuck on however doing a status querry by isy of 2477sa2 always resets the load led. Having 2477SA2 main relay powered on results in load led staying on regardless of load circuit state being open or closed. So we might say load status led works half of the time: when the 2477SA2 main relay is powered off. Would still be of value to have the load status node reported in ISY even though it only works during power off. There are a few scenarios where it becomes useful to know the controlled load is calling for power when the 2477SA2 is off. This would be especially useful since relay of 247sa2 does not automatically follow load sense led: I.e. Isy could be used to decision when load calls for power run a program to turn on 2477SA2 relay or send notification etc. I see from this forum thread that others have been able to manually link insteon devices to 2477SA2s load sense viewtopic.php?f=27&t=5449 Is there a way to have the load sense report in the ISY ? Thanks much J