MarkJames

My home automation webpage is working well now but it polls ISY using the REST interface. I'd like to recode it using websockets. I'll preface this by saying that I can get websockets working - thanks to the help of mWareman - if my site is hosted by the ISY. However I'd like to be able to host my page on a raspberry pi 3 running apache. The reason for this is that I would like my site accessible across the WAN with no VPN but I want access control such as I can get from a php login page or by setting users up with .htaccess. I've not found a way to control access to an ISY based web page without using the cloud module or a VPN. AFAIK the isy webserver doesn't support php (correct me if I'm wrong as tbh I haven't tried) Mwareman was kind enough to backport his apache to my version and make changes to the virtuahosts.conf file which allowed him to subscribe from a server within the LAN but not on the ISY. However my application also uses the REST interface to turn lights on/off. That requires me using isyProxy.php (again, correct me if I'm wrong). With forward and reverse proxy setup in the virtualhosts.conf file and the rewrite rule that curls things through isyproxy.php I can't even load my page - it just stops - likely due to the rewrite rule. Is there a documented way to both subscribe to ISY AND use the REST interface to control it from a non-ISY hosted page? Or a way to control the ISY other than by a method which requires isyproxy.php? Thanks in advance, mark

Thanks Michael! I'd found the repository on github with a full implementation but it was for a test server and had little documentation with it - I think it was for more advanced programmers than myself. This is more my speed. Out of curiosity - before I rewrite chunks of code - is websockets compatible across most browsers? I've got a raspberry pi 3 hosting my site and it's not bothered by the constant polling. If the ISY isn't hurt by it either then I'm inclined to leave it the way it is if websockets might cause me some browser compatibility issues. mark

Thanks Michel, I've been learning javascript for the sole purpose of creating this page. I wasn't aware that subscribing/websockets was even an option. I'll see if I can find some more info about or some sample code in the wiki. mark

I've got a custom page designed to display the status of all the El;k zones, keypads, and areas in my house. There's about 45 total items to display. I'm using the REST interface to call /rest/elk/get/status and then parsing the xml to update all my html elements. I haven't found a way to specifically query an individual zone/area/keypad - all I've found is all or nothing. The REST call returns the status of, from what I can tell, everything known to the Elk - including the default 208 outputs. Anyways - it happens right quick and to give the appearance of 'real time' monitoring I've been updating the status of my html every few seconds - basically changing the color/text of a series of buttons according to their corresponding zone state - Violated, Normal, Bypass My question is at what point will the ISY start seeing degraded performance because of the frequent REST calls? Is there a recommended minimum interval between calls? Will frequent REST calls slow program flow/trigger? Thanks, mark

Definitely not a scene - just single devices. I'm just getting around to coding my site for scenes so I know there's none in there. I was thinking it might be a timing issue or collision issue between the REST interface and the 'regular' communication.... asynchronous stuff can be funny that way. I suspect ISY internally regulates it's communication to prevent collisions but has no way of knowing when I come along and throw a REST call into the mix mark

I'm finishing up a personal webpage for lighting control that uses the rest interface to turn lights on and off. It works fine but I've noticed that once in a while after the rest calls to turn on a light I'll get a 'cannot communicate with <light I just switched>' error from ISY admin console related to the light that I just controlled or polled via the rest interface. It doesn't matter, really, and if the admin console is closed then I wouldn't even know it. I'm just curious if there's something quirky that I'm doing with my rest calls or if this is just normal behavior when controls and queries come from the rest interface.. Thanks, mark

I think (hope) that the problem is solved. The recent PLM swap I did was to a v9B that I had as a spare. It caused a LOT of all-ons so I pulled it and replaced it with a 1617 v9E. Turns out my wife saw the v9B sitting on the counter, thought it was a 2443 access point and plugged it in. So I had 2 PLM's running - one of them the v9B. Hopefully the problem goes away now. Plus - on a bright note - the vendor (Aartech Canada) is swapping my 9B for a new 9E even though it's well out of warranty. Kudos to them for going above and beyond. mark

What I have are a series of programs that turn things off depending on flags that I've set. So the programs will run every ten minutes or so and turn lights off, say, if it's light out and it's an outdoor light, or if it's dark out, nobody is home, and it's a closet or something like that. The main program calls a series of sub programs something like this Run program ,<a> Run program <b> Run program <c> then I have program <a> turn off light 1 turn off light 2 turn off light 3 program <b> turn off light 4 turn off light 5 turn off light 6 program <c> - possible overlap here turn off light 5 turn off light 6 turn off light 7 turn off light 8 My understanding is that when ISY encounters a Run command in a program it starts that program running but doesn't wait for it to complete before executing the next line. Correct me here if I'm wrong. If that's true then it could be that I'm setting a dozen or more programs running nearly simultaneously that are all turning off lights and possibly causing the collisions? mark

I've modified my energy saver programs by adding a 2 second wait between each scene that it turns off. Does that seem like a reasonable first step? mark

Sigh.... So my ALL ON events continue. I'm back to one a day or so now despite having switched to a build 1617 v9E PLM This is the event viewer log of the minute or so leading up to the all-on. If you have a chance, Lee, could you see if anything looks 'suspect' to you? Sorry there's a bit here - I cut/pasted the last 15 seconds or so. At 8:09:25 a series of programs that turn off unneeded lights started - that's what sets all the traffic in motion. I can see that in the log file. I've highlighted an odd one with device 0C.80.93. It's a switchlinc Relay v.2C Thanks, mark Fri 06/10/2016 08:09:16 AM : [VAR 2 9 ] 1 Fri 06/10/2016 08:09:16 AM : [iNST-TX-I1 ] 02 62 10 A8 E0 0F 14 00 Fri 06/10/2016 08:09:16 AM : [iNST-TX-I1 ] 02 62 0C 80 93 0F 14 00 Fri 06/10/2016 08:09:16 AM : [ Time] 08:09:25 11(0) Fri 06/10/2016 08:09:16 AM : [iNST-ACK ] 02 62 10.A8.E0 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:16 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:16 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:16 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:17 AM : [iNST-SRX ] 02 50 0C.80.93 40.D1.EC 27 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:17 AM : [std-Direct Ack] 0C.80.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 06/10/2016 08:09:17 AM : [iNST-SRX ] 02 50 0C.80.93 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:17 AM : [std-Direct Ack] 0C.80.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:17 AM : [iNST-TX-I1 ] 02 62 00 00 57 CF 14 00 Fri 06/10/2016 08:09:17 AM : [iNST-TX-I1 ] 02 62 00 00 36 CF 14 00 Fri 06/10/2016 08:09:17 AM : [iNST-TX-I1 ] 02 62 10 A8 E0 0F 14 00 Fri 06/10/2016 08:09:17 AM : [iNST-ACK ] 02 62 00.00.57 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:17 AM : [iNST-TX-I1 ] 02 62 0C 80 93 0F 14 00 Fri 06/10/2016 08:09:18 AM : [iNST-ACK ] 02 62 00.00.36 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:18 AM : [iNST-ACK ] 02 62 10.A8.E0 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:19 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:19 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:19 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:19 AM : [iNST-TX-I1 ] 02 62 00 00 58 CF 14 00 Fri 06/10/2016 08:09:19 AM : [iNST-TX-I1 ] 02 62 00 00 18 CF 14 00 Fri 06/10/2016 08:09:19 AM : [iNST-ACK ] 02 62 00.00.58 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:20 AM : [iNST-SRX ] 02 50 0C.80.93 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:20 AM : [std-Direct Ack] 0C.80.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:20 AM : [iNST-TX-I1 ] 02 62 3D 2A 20 0F 11 FF Fri 06/10/2016 08:09:20 AM : [iNST-TX-I1 ] 02 62 00 00 4C CF 14 00 Fri 06/10/2016 08:09:20 AM : [iNST-ACK ] 02 62 3D.2A.20 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:20 AM : [iNST-TX-I1 ] 02 62 08 66 4B 0F 14 00 Fri 06/10/2016 08:09:21 AM : [iNST-SRX ] 02 50 3D.2A.20 40.D1.EC 2B 11 FF LTONRR (FF) Fri 06/10/2016 08:09:21 AM : [std-Direct Ack] 3D.2A.20-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:21 AM : [iNST-SRX ] 02 50 3D.2A.20 40.D1.EC 23 11 FF LTONRR (FF) Fri 06/10/2016 08:09:21 AM : [std-Direct Ack] 3D.2A.20-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:21 AM : [iNST-ACK ] 02 62 00.00.4C CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:21 AM : [iNST-TX-I1 ] 02 62 23 7D A0 0F 11 FF Fri 06/10/2016 08:09:21 AM : [iNST-TX-I1 ] 02 62 00 00 16 CF 14 00 Fri 06/10/2016 08:09:21 AM : [iNST-TX-I1 ] 02 62 00 00 5A CF 14 00 Fri 06/10/2016 08:09:21 AM : [iNST-ACK ] 02 62 08.66.4B 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:22 AM : [iNST-SRX ] 02 50 08.66.4B 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:22 AM : [std-Direct Ack] 08.66.4B-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:22 AM : [iNST-ACK ] 02 62 23.7D.A0 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:22 AM : [iNST-TX-I1 ] 02 62 00 00 30 CF 14 00 Fri 06/10/2016 08:09:22 AM : [iNST-TX-I1 ] 02 62 00 00 21 CF 14 00 Fri 06/10/2016 08:09:22 AM : [iNST-TX-I1 ] 02 62 23 7E 01 0F 11 FF Fri 06/10/2016 08:09:22 AM : [iNST-ACK ] 02 62 00.00.16 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:23 AM : [iNST-SRX ] 02 50 23.7D.A0 40.D1.EC 2B 11 FF LTONRR (FF) Fri 06/10/2016 08:09:23 AM : [std-Direct Ack] 23.7D.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:23 AM : [iNST-TX-I1 ] 02 62 10 A8 E0 0F 14 00 Fri 06/10/2016 08:09:23 AM : [iNST-TX-I1 ] 02 62 0C 80 93 0F 14 00 Fri 06/10/2016 08:09:23 AM : [iNST-TX-I1 ] 02 62 00 00 2C CF 13 00 Fri 06/10/2016 08:09:23 AM : [iNST-ACK ] 02 62 00.00.30 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:23 AM : [ Time] 08:09:32 11(0) Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 00 00 57 CF 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 00 00 36 CF 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 10 A8 E0 0F 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-ACK ] 02 62 00.00.21 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 0C 80 93 0F 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 00 00 58 CF 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-TX-I1 ] 02 62 00 00 18 CF 14 00 Fri 06/10/2016 08:09:24 AM : [iNST-ACK ] 02 62 23.7E.01 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:25 AM : [iNST-SRX ] 02 50 23.7E.01 40.D1.EC 2F 11 FF LTONRR (FF) Fri 06/10/2016 08:09:25 AM : [std-Direct Ack] 23.7E.01-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 06/10/2016 08:09:25 AM : [iNST-ACK ] 02 62 10.A8.E0 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:25 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:25 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:25 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:26 AM : [iNST-TX-I1 ] 02 62 3D 2A 20 0F 11 FF Fri 06/10/2016 08:09:26 AM : [iNST-TX-I1 ] 02 62 00 00 4C CF 14 00 Fri 06/10/2016 08:09:26 AM : [iNST-ACK ] 02 62 00.00.2C CF 13 00 06 LTOFFRR(00) Fri 06/10/2016 08:09:26 AM : [iNST-TX-I1 ] 02 62 08 66 4B 0F 14 00 Fri 06/10/2016 08:09:26 AM : [iNST-SRX ] 02 50 0C.80.93 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:26 AM : [std-Direct Ack] 0C.80.93-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:27 AM : [iNST-TX-I1 ] 02 62 23 7D A0 0F 11 FF Fri 06/10/2016 08:09:27 AM : [iNST-TX-I1 ] 02 62 00 00 16 CF 14 00 Fri 06/10/2016 08:09:27 AM : [iNST-ACK ] 02 62 00.00.36 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:27 AM : [iNST-TX-I1 ] 02 62 00 00 5A CF 14 00 Fri 06/10/2016 08:09:27 AM : [iNST-ACK ] 02 62 10.A8.E0 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [iNST-TX-I1 ] 02 62 00 00 30 CF 14 00 Fri 06/10/2016 08:09:28 AM : [iNST-TX-I1 ] 02 62 00 00 21 CF 14 00 Fri 06/10/2016 08:09:28 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [iNST-ACK ] 02 62 0C.80.93 0F 14 00 06 LTOFF-F(00): Duplicate or ACK for a different device Fri 06/10/2016 08:09:28 AM : [iNST-TX-I1 ] 02 62 23 7E 01 0F 11 FF Fri 06/10/2016 08:09:28 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:28 AM : [iNST-ACK ] 02 62 00.00.58 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [iNST-SRX ] 02 50 10.A8.E0 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:28 AM : [std-Direct Ack] 10.A8.E0-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:29 AM : [iNST-ACK ] 02 62 00.00.18 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:29 AM : [iNST-ACK ] 02 62 3D.2A.20 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:30 AM : [iNST-SRX ] 02 50 3D.2A.20 40.D1.EC 2B 11 FF LTONRR (FF) Fri 06/10/2016 08:09:30 AM : [std-Direct Ack] 3D.2A.20-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:30 AM : [iNST-ACK ] 02 62 00.00.00 CF 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:30 AM : [iNST-SRX ] 02 50 3D.2A.20 40.D1.EC 23 11 FF LTONRR (FF) Fri 06/10/2016 08:09:30 AM : [std-Direct Ack] 3D.2A.20-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:30 AM : [iNST-ACK ] 02 62 08.66.4B 0F 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:31 AM : [iNST-SRX ] 02 50 08.66.4B 40.D1.EC 2B 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:31 AM : [std-Direct Ack] 08.66.4B-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Fri 06/10/2016 08:09:31 AM : [iNST-SRX ] 02 50 08.66.4B 40.D1.EC 23 14 00 LTOFF-F(00) Fri 06/10/2016 08:09:31 AM : [std-Direct Ack] 08.66.4B-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 06/10/2016 08:09:31 AM : [iNST-ACK ] 02 62 23.7D.A0 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:31 AM : [iNST-SRX ] 02 50 23.7D.A0 40.D1.EC 2F 11 FF LTONRR (FF) Fri 06/10/2016 08:09:31 AM : [std-Direct Ack] 23.7D.A0-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 06/10/2016 08:09:31 AM : [iNST-ACK ] 02 62 00.00.16 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:32 AM : [iNST-ACK ] 02 62 00.00.5A CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:32 AM : [iNST-ACK ] 02 62 00.00.30 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:33 AM : [iNST-ACK ] 02 62 00.00.21 CF 14 00 06 LTOFF-F(00) Fri 06/10/2016 08:09:33 AM : [iNST-ACK ] 02 62 23.7E.01 0F 11 FF 06 LTONRR (FF) Fri 06/10/2016 08:09:33 AM : [iNST-SRX ] 02 50 23.7E.01 40.D1.EC 2F 11 FF LTONRR (FF) Fri 06/10/2016 08:09:33 AM : [std-Direct Ack] 23.7E.01-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 Fri 06/10/2016 08:09:47 AM : [FileOpen ] Open failed for [/CONF/NET/WOL.CFG] ® Fri 06/10/2016 08:10:15 AM : [VAR 2 9 ] 0

Hi Michel, These are the big ones (though they're a couple of years older now) - the 2440's. I can write to them but not if they're right beside an AP or dualband device. I generally put them in a drawer or cupboard and then they write just fine. It may be that my situation is different as I have quite a number of access points (2443) in my install. My home has an unusual powerline system. Back in the early '80s the power company offered a program where they charged heating/cooling at a reduced rate. They would install a second meter in your home so that the power came in to the main meter and then a subpanel was fed from the main *through* a second meter. At the end of the billing cycle they would total up your use and subtract the amount that was used on the second panel. That difference was charged at regular rates while the heating meter rate was half that. We have that system to this day - we get charged 3.5 cents/kWh for heating power. Obviously I'm not giving up a great deal like that! Anyways - sorry to drone on - but the end result is that I have a meter interfering with my install. Most devices are on one side of it but some are on the other. Insteon (and previously X10) signals have a hard time flowing reliably through the meter so I've put in a number of AP's to wirelessly bridge this deficiency. It took some time to get my Insteon system (92 devices) running reliably. I've got a couple of the original Signalincs still in use as well as multiple Signal Bridges (I have 7 panels in the house). At this time it's pretty solid - though even with my recent v9E PLM I'm getting occasional ALL-ON events that I'm troubleshooting my way through. It could well be that it's the multiple AP's or Signalincs that cause the write trouble, though I've got at least a dozen or more dual band devices now as well that could be involved. Anyways - I just noticed this thread and figured that I had encountered a similar problem - 2440's directly beside a dual band (2413s) PLM won't write at all. As soon as I get some distance from the PLM or tuck it in a drawer it starts to write just fine. mark

This is a bit late of a response to this but I thought I'd throw this in here in case anyone else has this problem I have the same issue writing to my remotelincs. For some reason if I'm too close to an AP or dual-band device it won't write. Rather than walk around the house, though, looking for an area that works better I just put my remotelinc in a kitchen cupboard or desk drawer. That seems to weaken the signal strength to it enough to get a successful write. mark

Thanks Paul, I've put it in feature requests here http://forum.universal-devices.com/topic/19088-keypadlinc-button-numbers-be-displayed/ Cheers! mark

Yep - I definitely *could have* or *should have* put a designation of some sort with each of my 160 KPL buttons but you know what they say about hindsight... The alphabetizing is the problem. If there was either a way to turn the alphabetizing off or to have the UI indicate which button is which I think that would be an improvement. Perhaps I'll put this in as a feature request...

I'm not - I use the button names. It's just for organization. I wanted to make the left button on the second row into a controller for a different scene than it was already assigned to. Without going down and looking at it I didn't know which scene the left button on the second row was already assigned to. I suppose if I'd taken all the buttons off a KPL without noting what they were assigned to it would be a bigger problem - I'd have to reinstall it and press each button individually to figure out which was which. mark

lol - direct approach. I was sitting here in the house trying to reconfigure the buttons on a KPL down on my dock. I couldn't remember which button was which as I've changed their functionality quite a bit. I was trying to figure it out without walking down to the dock and either looking at it or - as you did - pressing the button. mark

I suppose... Seems like there *should* be a way to see this directly within ISY, though... mark

Could be... it would be a nice feature, though. How did you get your button to show in event viewer without writing to it? mark

Thanks Lee - I was just looking at that.... Didn't the UI used to display it before? I was sure that when you went into the Main tab and clicked on the root node of a KPL it brought up in the main properties window the name with the address and device type as it does now but with a suffix for which button it represented so that when you looked at the load button it would say KPL-GARAGE 0A.AB.1E-1 (2486D) Keypadlinc Dimmer v.2A but when you looked at button B it would say KPL-Driveway 0A.AB.1E-2 (2486D) Keypadlinc Dimmer v.2A Am I imagining this?

lol - no, I know that... Once you rename them, though, how can you tell which one is which without looking at your labels? When you first link it it will name it newdevice - A newdevice - B newdevice - C etc But once I change it to Room Light Table Lamp Reading light etc How can I tell which button is, say, A, from the ISY admin panel without looking at the physical KPL. I'm not sure if it was ISY or one of the other platforms I used prior to it that labelled them in the main device list with .1, .2, .3 or maybe it was .a, .b, .c... mark

I'm probably having a seniors moment here but maybe someone could refresh my memory. So if I look at a KPL-8, for instance, grouped in my admin console I see all 8 buttons with the meaningful names I gave them. But what happens if I can't see the KPL from where I'm sitting or I've pulled the buttons off it so that I don't know which is which. There was (is?) a place where the interface told me which button was which - if memory serves it used to look like the devices were like ab.cd.ef.1 and ab.cd.ef.2 etc. up to ab.cd.ef.8 Is that still somewhere that I'm not seeing or has that been deprecated? mark

apostolakisl, I was sitting down to plan out the GDO run by the Elk today. I figured I'd use the Elk to control the fireplace as well. The thing is that all methods I have to trigger the Elk to open/close the garage door/fireplace are going to be via Insteon buttons unless I use Elk keypads or keyfobs. I suppose that the ALL-ON problem is a responder event as I see no device ON commands in the event viewer so the Elk should be unaffected. Are you just using a program something like if control KPL-Fireplace is ON Elk Output GDO ON Off Timer 1 second Seems like that's all it should take... To ensure even greater security I could require a fast-on or fast-off event.... just thinking out loud

In recent years I've set up a few programs and variables so that things don't ever get stuck 'on' for a day. I have a motion sensor that I put facing out one of my windows. I don't use it for motion sensing - just for dusk to dawn sensing. It sets a variable indicating if it's dark or not. My old JDS Stargate used to just use your lat/long to determine sunrise/sunset and you could base things on whether it was dark or not. I miss that functionality. I was getting it back by setting variables in the ISY from the ISY interface to Homeseer but the motion sensor is easy and it works well so I've switched to that. I really miss having full calendar conditions in ISY - I've been hoping for that feature for 10 years now but it doesn't seem to be on the list. I've tried some of the calendar type programs in ISY but I find them way too kludgy to be of any real use. When many of my scenes get turned on by a controller, rather than by sensor or by some other condition or schedule, I set a variable that indicates that the light *should* be on or *should* be off. Just a simple 'garage_light_should_be_on' = 0 or 1 for instance. These variables time out depending on the location and whether it's dark out or not. Every 5 minutes a program runs that turns off scenes based on time of day, occupancy, etc. With these variables set I can leave lights etc. alone. I had to switch to these variables to avoid turning lights off right after someone had just finished turning them on. Or lights that *should* be on at night but then also get tripped by a motion sensor or door contact on a timer which turns them off after 5 minutes even though they were 'meant' to be on (if this makes sense). Or things that are normally on a timer but sometimes you don't *want* them to be on a timer but you *do* want them to go back on the timer after you're finished doing what you're doing. I found these problems infuriating. Many of my lights that are timed or cycled allow you to bypass that cycling by simply fast-on'ing them. The cycle/timed bypass will expire after a few hours or when you fast-off them. I started doing this a few years ago when I had to do some work in my attic. My kids would sometimes hit the attic light switch instead of the hall light switch so I had a routine that turned off the attic light every 5 minutes. Problem was that I had work to do in the attic and I kept getting plunged into darkness. This is what I came up with and it's gotten more and more elaborate over the years till it fits our lifestyle reasonably well now. The hardest part of automating for me has been having the automation system not make things worse and also not having to live your life according to the rules of the home automation controller! Anyways - I've been reconfiguring a lot in the last few days to avoid too many links. I used to have a scene that turned everything in the house off. It was just one big-assed scene with about a half dozen KPL buttons that controlled it and then a bunch more that triggered it through a fast-on or fast-off via program. But with a hundred or so devices and 40+ KPL 6's or 8's involved many of my devices held upwards of 100 links - it became quite unwieldy. You were definitely NOT getting a fully successful scene test out of that scene. It would also take the better part of an hour to do a restore on some of the controllers that held this scene. The reconfiguration has scenes that are just logical areas (kitchen, laundry, all of one floor, etc.). ALL ON/OFF is generally a KPL press that immediately turns on/off the local scene by direct link and also triggers an ISY program to turn off the other scenes desired. There's a lag but it's not that bad. Having come from X-10 this is pretty darned good.

An hour a year! Sounds like something else for us older, married guys than bathroom time

Thanks for your help, Lee. I'm going to make an effort to map all my devices and eliminate any non-linked ones. I've got ones dating back to the first years of Insteon that I recycle for various projects and so there may be ones that I don't know about. As I sit here watching links write I just watched a series of X10 addresses get sent a P7 P6 P5 P4 P4/On series. That would indicate that it comes from a very old device as I migrated to Insteon from X10 controlled by JDS Stargate. I'd appreciate your opinion on the value of changing some of my older devices out for newer dual bands. My installation is quite extensive and some of the more remote devices can be 300+ ft from the PLM. Though I have a number of 2443 access points around and a growing number of dual band devices I still find a lot of missed writes and reads - the 'max hops=3, hops left=0' or the Set-MSB(0) errors during link writes. My home has 2 meters - it's a bit unusual. It was an initiative from our power provider 30 years ago to charge one rate for regular electricity usage and a lower rate for heating usage. So the power comes into our home through a main meter then feeds a second panel through a second meter. This means that some of the Insteon signals must pass through a meter no matter where I put the PLM. I try to mitigate the problem by using phase couplers on the panels and access points to form a bridge past the meters but there's still issues. Do dual band devices help as much as access points and is an installation with a large number of dual band devices generally more robust? While it would be a fairly costly upgrade I've already got more than $10k invested in Insteon. Another $1500 or so to solidify it would be do-able. Thanks, mark