MarkJames

Thanks for the links, Stu, and for your input as well, Nadler. I have one other thing that I'm going to look into before dealing with any possible PLM firmware issues. My PLM is at 9B so it may well be the problem. I'm not sure what rev my last one was but it was at least as old as the 9B one. I am interfaced with an Elk M1G. I only have a handful of devices that were exported to the Elk for control but since the PLM change none of those devices work under Elk control. It's been so long since I set the Elk up to control any of the Insteon devices that I don't remember if I was controlling scenes or devices. I'm guessing (correct me if I'm wrong) that I would have to re-export any scenes I want to control and re-import them into the Elk otherwise I'll be dealing with incorrect/broken links. I've disabled all Elk automation of Insteon/ISY and will see if that makes a difference. It may take a few days to find out, though. Thanks all for your input. mark

Thanks for that. I read the wiki entry - but nothing lengthy. Perhaps you're referring to another article that might be of interest to me? The wiki refers to scenes/control conflicts. If I didn't have those before the PLM change I don't see why I should have them now. The other reference in the wiki entry is to the wireless motion detectors sending multiple signals when their batteries get low. I'll check on that as I do have a few of those kicking around and I've not touched their batteries in some time. The curious thing is that it only started when the PLM was changed. I've made no other program/device changes whatsoever. As for making it happen again? I've been scratching my head trying to duplicate it but there's nothing very unusual in the log around the time it happened. I think I'll start saving the logs and comparing what's going on at the time it happens. That might give me a clue if I have some kind of program conflict overloading the PLM. Thanks, mark [edit] Actually I do see something weird in the log. There's a whole whack of 2 lights turning on in rapid succession about the time the ALL ON happened. This bears investigation. Thanks again!

I had a 2413S fail last week. These seem to be a weak point in the general scheme of ISY - I've had a number of them fail over the years so I always keep a spare handy. I replaced it with a new one and restored the database to it. All went reasonably well - there's always a few links that don't seem to write properly but given enough time I manage to sort them out. The second night after replacing it I had my burglar alarm go off at around 3am and every single light in the house turn on. Turns out my garage door had opened and set off the alarm. I'm not sure why all the lights were on but I closed the door, turned off all the lights and went back to bed. This afternoon at around 1:55pm the exact same thing happened. I've figured out why it is that the door is opening - there's an ioLinc relay attached to it and when it gets an ON signal it triggers the door opener. So the garage door opening is part of the overall issue of everything in the house turning on. This is a bit of a problem as I have somewhere around 200 ISY devices in my network - pretty much everything in the house. The ioLinc on the garage door is not controlled by anything BUT the PLM so it seems that the problem must lie there. This is a pretty well established system - it's been in place and operating trouble free for 10 or more years. I've checked the program run logs and nothing has run at that time. I'm not sure what to do next.... restore the PLM? Thanks for any input. mark

I don't have any add-on boards - just the Elk and Web modules but those are just software. It always ran OK with just 200mA - but I never noticed this UPS problem as the power doesn't fail that often. Always good to have a slightly larger than necessary psu than one that's bordering on not enough, though. mark

Thanks - experience is always the best teacher. I couldn't count the hours I've spent troubleshooting Windows issues having started with Windows on an Apple PC and migrated along with it from 3.1 to 95 to 98 to XP, ME, Vista, 7, 8, and 10 along with being an MCSE and maintaining a 300 user environment running under NT. I usually troubleshoot problems WAY faster than the folks I've worked with - not cuz I'm smarter - just cuz I've probably already wasted 3 days somewhere in my past finding out what they're trying to solve. I'll separate them out on the UPS - I have 4 UPS's in my closet so whatever I plug into it's going to have potential issues with something else unless I get a separate UPS for each device and that's just not within my pocketbook. Thanks again, mark

on a separate power strip? Or on separate outlets on the same UPS? I only ask because it's a bit of a proximity issue. mark

I replaced the power supply and can confirm that it's now working properly. The specs from the ISY said 5-30V but 300mA minimum. My psu at 200mA must have been threshold. All is good now happily Thanks so much for the help! mark

It looks like the original got swapped around sometime over the years. This is a replacement to my original ISY 99ir. The adapter is a 9V 200mA one. I have a 12V 1.5A one I can swap with - is 12V within range of the ISY? I can try that instead. [edit] I looked up the specs and I should be good till 30V Looks like 200mA was too small for the ISY as well - perhaps that was part of the problem I've swapped it to 12VDC 1.5A - and will report back

I'll try that but at the moment I've got a 10.14gig file downloading so I've gotta wait a bit. Could it be that the wall wart I'm using to power the ISY doesn't regulate well at 109 or so volts? mark

As an aside - if I follow minimum voltage as I unplug the UPS the voltage drops as low as 109.1. Perhaps I need a more well regulated power supply for the ISY? mark

Same problem I'm afraid. Within a session it immediately goes to Socket failed open.... - ISY reboots and catchup happens again.

The ISY is plugged into a power bar with those 4 devices (2 routers, ISY and cable modem). The power bar is plugged into the master backed up outlet on the UPS. The meter is plugged into 1 of the adjacent battery backed up outlets

Using my Fluke 87V I get 112.4V while powered and 115.6 under battery backup mark [edit] using min/max - under power I get a min of 111.5 and a max of 115.8

So this is probably not related to my ISY but I'm a bit confused by this so I thought I'd start here. I have a 994 controlling my home. I just bought a new UPS - an APC2500 - to maintain/protect a few devices. It has the 994, my Asus router, a VoIP router, and my cable modem all plugged into it - so all low current devices. The UPS is plugged in and fully charged. For some reason when I unplug the power to the UPS - simulating power loss - it seems to do what it's supposed to do and everything stays powered up - but the ISY restarts. The cable modem and 2 routers don't even flinch but the ISY reboots. I can't 'see' it reboot - the lights remain lit - but any sessions will be dropped and a 'catch-up' occurs. I've checked that things are plugged in properly - in my last trial I plugged everything into a power bar and the power bar into the backed up port on the UPS - but the ISY still reboots. This is likely a UPS problem - but any ideas? mark

That's not what I'm saying. What I'm saying is that it acts as if the program condition is being evaluated despite the folder condition being false. I don't know exactly what's going on but what it looks like is that the program condition gets evaluated and runs because it's true - motion *has* been detected. The thing is that it shouldn't get as far as evaluating the program condition because the folder condition is false. As posted above - I tried both integer and state variables and find that both result in an instant change in folder status. So I don't believe that the type of variable is the issue. What would be interesting to know is if ISY continually evaluates program conditions - even in folders that are false - and then when the program is true decides whether to run them on the basis of whether the folder is true. I would suspect it would be the contrary - that so long as the folder is false it wouldn't look at the program at all.

Interesting.... So you're saying that ISY treats time conditions and integer variable conditions differently? I ask because I use time conditions on folders all the time with no problem. If what you say is true then ISY must poll the condition differently when it's not an integer. I've experimented and I don't find this to be true. Regardless of whether the variable is integer or state it still results in an immediate change of the folder condition (green to red or back). I created two variable s_send alert and i_send alert - one a state, one an integer - both work the same. I'm going to play with this some more - it'll be more difficult now that I don't have 80 or 90 people milling about my yard causing sensors to go nuts. In the meantime it'd be interesting to get a firm answer - perhaps from Michel - as to the need for a folder condition variable to be a state variable mark

I'll give it a whirl but I'm not sure I follow your reasoning. With that said you may well be right and I misunderstand the folder variable. I use state variables quite a bit - for programs that need to execute at the time the variable value changes state. The folder condition variable doesn't work that way. When the variable changes state nothing runs. It just allows the programs in the folder to run if/when they evaluate true. The wiki makes no reference to a folder condition requiring a state variable. Indeed it makes no sense for that to be required as the folder condition can be a schedule condition - not a variable. Here's the entry Description There are situations where it is desirable to limit when a set of programs is allowed to run. An office for example may want to limit the hours in which certain lights or appliances are allowed to be turned on, and also automatically turn them off at those times. Folder conditions provide a means of doing this without having to modify each individual program. Adding conditions to a folder is identical to adding conditions to a program. Conditions for a folder must first be met for any of the programs in that folder (or its sub-folders) to run. Folders by default have no conditions, and therefore do not limit when the programs within them run.

This is the folder with the condition. The variable is Integer with a value of 0 Alerts - [ID 0013][Parent 0001] Folder Conditions for 'Alerts' If $Alerts_Send_Email is 1 Then Allow the programs in this folder to run. This is the program that resides in the folder above - as simple as code can be Gate to path email - [ID 008D][Parent 008C] If Elk Zone 'Gate to yard' is Violated Then Send Notification to 'Default' content 'Deer - Gate' Else - No Actions - (To add one, press 'Action') And despite this I will receive the email alert when $Alerts_Send_Email is 0. Not always - just when the program condition gets triggered repeatedly Interestingly - if I add the condition to the program itself so that it looks like this Gate to path email - [ID 008D][Parent 008C] If Elk Zone 'Gate to yard' is Violated And $Alerts_Send_Email is 1 Then Send Notification to 'Default' content 'Deer - Gate' Else - No Actions - (To add one, press 'Action') This will work properly and will not trigger. It's as if the program condition is evaluated separately from the folder condition and when overwhelmed the folder condition doesn't get checked. I thought the folder condition would be evaluated first - and that the program conditions wouldn't even be evaluated if the folder conditions were false. This is a minor problem - I have no complaints - it's just curious. mark

Nope - the only way to that program is by the motion sensor going violated and it resides in a folder that requires the variable to be true. I confirmed that it was the program in question by adding the program data to the email sent There are no program references that assign a value to the variable - the only way to change it is manually I don't think so.... I don't actually 'trigger' the folder state to false - I assign the variable to false manually and that *should* be adequate to stop the programs in that folder from running. I experimented by adding an additional reference to the same flag within the program so that it reads If elk zone gate motion is violated AND flag send email is TRUE then notify etc. etc. That addition holds - and the program doesn't run. I'm not sure what that means other than that the condition itself is valid Imark

I've been rewriting some of my code recently and have moved a bunch of routines around. I have a flag called 'Send Email Alert' which I set to either True (1) or False (0). It's currently set to 0 and I've confirmed it. It's an integer variable. I have a program that senses Elk motion and, when an Elk PIR zone is violated, it sends an email to me. The code looks something like this If elk zone gate motion is violated then notify default blah blah blah That program lives inside a folder which *should* only allow the program to run if the flag 'Send Email Alert' is True/1 For the most part it works. But today we had a lot of company - like 80 people over. There were people tripping the motion sensor relentlessly and from time to time the email message would get sent despite the flag being false. Is it possible to overwhelm the condition processing on the folder? mark

Thank Michel, I haven't been keeping up so I didn't see that. It looks like with a bit of customization it will do just what I want. As always, thanks for the great support. mark

I can do some very basic (emphasis on basic) web page design. On my personal home page I have a table of devices in my home that I want to quickly be able to control. It's basically just a list of devices in one column then an 'on' and an 'off' button in two adjacent columns. It works *fine* - very 'no frills' but it gets what I want to do done. I'd like to, though, be able to display the status of the device - very simplistically - just change the color of the text to green for on and red for off or something like that. In addition I'd like to be able to set a color or other indicator on my web page depending on whether an ISY variable is 0 or 1. Is there a straight forward way to do this? This is the only web design that I want to do so I'm not looking for a big, complicated project. If it's going to be too much work I'd rather just either skip it or buy one of the pre-made apps. Thanks in advance, mark

Thanks again Lee, I got to thinking about whether this device not working properly may be related to why my other wireless devices may not have been working properly (I mentioned that I gave up on 2420's). On a whim I unplugged my PLM for a few seconds along with the ISY and then plugged them back in again. The leak sensor is now working properly. I guess something went awry with the PLM that a reboot fixed. Now when I tap the button the states populate properly. W00t! Thanks for your patient help, Mark

Looks like I accumulated all my questions from the last 2 years for today. Three posts going at the same time - i promise not to start a fourth! I was looking at the scene test diagnostic feature today and was playing with it. I'm a little confused by the results and was hoping I could get some clarification. When I run a scene test - regardless of how big or small the scene - it appears to run successfully. All the devices that should turn on do, in fact, turn on and then they all turn back off again. But the result always shows 'fail'. I've noticed this in the past and never worried about it as everything still works as it should. But it did make me wonder what it is about the scene test that makes ISY think it's failing while it looks to me like it's passing just fine. Thanks, Mark

Thanks Lee and Teken (I used to love the video game Tekken btw), I removed the sensor from my system, did a factory reset on it and re-added it. I do have one question before I post what happened. When you press and hold the set button you get a slow, continuous blinking - if you press it during this slow, continuous blinking it changes to a double flash - pause style of blinking. Do you know the difference between these two modes? Ok... so I re-added it during the double flash-pause blinking. It added as it should. I'll comment here that it added quicker than usual and I think that's because I stoped all processes - including Elk traffic - so that I could get a clean log. It made me wonder if that should be part of my regular routine - minimizing insteon and elk traffic while adding devices or changing link tables. Anyways... it added but again the nodes didn't populate - all states show blank. I rebooted the ISY but no change. I then restored it to the dry sensor and the log is attached. It restored fine but still no state information. I'm wondering if this may be a faulty sensor. I will note, however, that I do have problems getting state information from some of the 2420 motion sensors and have pretty much stopped using them in favor of GE Crystal Elk sensors that are far more reliable and have much better battery life. It makles me wonder if the problem getting state information from wireless sensors may be symptomatic of a different problem..... Anyways, here's the log - and as always, thanks very much for your help! Fri 09/19/2014 04:48:19 PM : [ 28 51 25 1] Preparing Device 'Leak Sensor-Dry' for Restore Fri 09/19/2014 04:48:19 PM : [ 28 51 25 1] Device 'Leak Sensor-Dry' ready for Full Restore Fri 09/19/2014 04:48:19 PM : [All ] Writing 25 bytes to devices Fri 09/19/2014 04:48:19 PM : [iNST-TX-I1 ] 02 62 28 51 25 0F 0D 00 Fri 09/19/2014 04:48:19 PM : [iNST-ACK ] 02 62 28.51.25 0F 0D 00 06 (00) Fri 09/19/2014 04:48:28 PM : [iNST-TX-I1 ] 02 62 28 51 25 0F 0D 00 Fri 09/19/2014 04:48:28 PM : [iNST-ACK ] 02 62 28.51.25 0F 0D 00 06 (00) Fri 09/19/2014 04:48:31 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 27 0D 02 (02) Fri 09/19/2014 04:48:31 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 09/19/2014 04:48:31 PM : [28 51 25 0 ] Calibrating engine version Fri 09/19/2014 04:48:31 PM : [iNST-TX-I2CS] 02 62 28 51 25 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 Fri 09/19/2014 04:48:31 PM : [iNST-ACK ] 02 62 28.51.25 1F 2F 00 00 00 00 00 01 00 00 00 00 00 00 00 00 D0 06 (00) Fri 09/19/2014 04:48:31 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 27 2F 00 (00) Fri 09/19/2014 04:48:31 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 09/19/2014 04:48:33 PM : [iNST-ERX ] 02 51 28 51 25 18 CE 5D 12 2F 00 00 01 0F FF 01 E2 01 18 CE 5D 01 00 01 99 Fri 09/19/2014 04:48:33 PM : [Ext-Direct ] 28.51.25-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Fri 09/19/2014 04:48:33 PM : [28 51 25 1 ] Link 0 : 0FF8 [E20118CE5D010001] Writing [E20118CE5D010001] Fri 09/19/2014 04:48:33 PM : [iNST-TX-I2CS] 02 62 28 51 25 1F 2F 00 00 02 0F FF 08 E2 01 18 CE 5D 01 00 01 91 Fri 09/19/2014 04:48:33 PM : [iNST-ACK ] 02 62 28.51.25 1F 2F 00 00 02 0F FF 08 E2 01 18 CE 5D 01 00 01 91 06 (00) Fri 09/19/2014 04:48:33 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 27 2F 00 (00) Fri 09/19/2014 04:48:33 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 09/19/2014 04:48:33 PM : [MNG-LNK-RSP ] 02 6F 41 A2 01 28 51 25 10 08 00 06 Fri 09/19/2014 04:48:33 PM : [PLM ] Group 1 : Writing Responder Link matching [28 51 25 1 ] Link 0 : 0FF8 [E20118CE5D010001] Fri 09/19/2014 04:48:34 PM : [28 51 25 1 ] Link 1 : 0FF0 [E20218CE5D010002] Writing [E20218CE5D010002] Fri 09/19/2014 04:48:34 PM : [iNST-TX-I2CS] 02 62 28 51 25 1F 2F 00 00 02 0F F7 08 E2 02 18 CE 5D 01 00 02 97 Fri 09/19/2014 04:48:34 PM : [iNST-ACK ] 02 62 28.51.25 1F 2F 00 00 02 0F F7 08 E2 02 18 CE 5D 01 00 02 97 06 (00) Fri 09/19/2014 04:48:43 PM : [iNST-TX-I2CS] 02 62 28 51 25 1F 2F 00 00 02 0F F7 08 E2 02 18 CE 5D 01 00 02 97 Fri 09/19/2014 04:48:43 PM : [iNST-ACK ] 02 62 28.51.25 1F 2F 00 00 02 0F F7 08 E2 02 18 CE 5D 01 00 02 97 06 (00) Fri 09/19/2014 04:48:44 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 23 2F 00 (00) Fri 09/19/2014 04:48:44 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 09/19/2014 04:48:44 PM : [MNG-LNK-RSP ] 02 6F 41 A2 02 28 51 25 10 08 00 06 Fri 09/19/2014 04:48:44 PM : [PLM ] Group 2 : Writing Responder Link matching [28 51 25 1 ] Link 1 : 0FF0 [E20218CE5D010002] Fri 09/19/2014 04:48:44 PM : [28 51 25 1 ] Link 2 : 0FE8 [E20418CE5D010004] Writing [E20418CE5D010004] Fri 09/19/2014 04:48:44 PM : [iNST-TX-I2CS] 02 62 28 51 25 1F 2F 00 00 02 0F EF 08 E2 04 18 CE 5D 01 00 04 9B Fri 09/19/2014 04:48:44 PM : [iNST-ACK ] 02 62 28.51.25 1F 2F 00 00 02 0F EF 08 E2 04 18 CE 5D 01 00 04 9B 06 (00) Fri 09/19/2014 04:48:45 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 27 2F 00 (00) Fri 09/19/2014 04:48:45 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 09/19/2014 04:48:45 PM : [MNG-LNK-RSP ] 02 6F 41 A2 04 28 51 25 10 08 00 06 Fri 09/19/2014 04:48:45 PM : [PLM ] Group 4 : Writing Responder Link matching [28 51 25 1 ] Link 2 : 0FE8 [E20418CE5D010004] Fri 09/19/2014 04:48:45 PM : [28 51 25 1 ] Link 3 : 0FE0 [0000000000000000] Writing [00..............] Fri 09/19/2014 04:48:45 PM : [iNST-TX-I2CS] 02 62 28 51 25 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 Fri 09/19/2014 04:48:45 PM : [iNST-ACK ] 02 62 28.51.25 1F 2F 00 00 02 0F E7 08 00 00 00 00 00 00 00 00 D1 06 (00) Fri 09/19/2014 04:48:46 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 27 2F 00 (00) Fri 09/19/2014 04:48:46 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 09/19/2014 04:48:46 PM : [28 51 25 1 ] Link 4 : 0FD8 : Writing High Water Byte Fri 09/19/2014 04:48:46 PM : [iNST-TX-I2CS] 02 62 28 51 25 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 Fri 09/19/2014 04:48:46 PM : [iNST-ACK ] 02 62 28.51.25 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00) Fri 09/19/2014 04:48:46 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 23 2F 00 (00) Fri 09/19/2014 04:48:46 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=0 Fri 09/19/2014 04:48:48 PM : [iNST-ERX ] 02 51 28 51 25 18 CE 5D 12 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 E1 Fri 09/19/2014 04:48:48 PM : [Ext-Direct ] 28.51.25-->ISY/PLM Group=0, Max Hops=2, Hops Left=0 Fri 09/19/2014 04:48:48 PM : [iNST-TX-I2CS] 02 62 28 51 25 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 Fri 09/19/2014 04:48:48 PM : [iNST-ACK ] 02 62 28.51.25 1F 2F 00 00 00 0F DF 01 00 00 00 00 00 00 00 00 E2 06 (00) Fri 09/19/2014 04:48:49 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 27 2F 00 (00) Fri 09/19/2014 04:48:49 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 09/19/2014 04:48:49 PM : [iNST-ERX ] 02 51 28 51 25 18 CE 5D 11 2F 00 00 01 0F DF 01 00 00 00 00 00 00 00 00 E1 Fri 09/19/2014 04:48:49 PM : [Ext-Direct ] 28.51.25-->ISY/PLM Group=0, Max Hops=1, Hops Left=0 Fri 09/19/2014 04:48:49 PM : [iNST-TX-I2CS] 02 62 28 51 25 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9 Fri 09/19/2014 04:48:49 PM : [iNST-ACK ] 02 62 28.51.25 1F 2F 00 00 02 0F DF 08 00 00 00 00 00 00 00 00 D9 06 (00) Fri 09/19/2014 04:48:50 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 27 2F 00 (00) Fri 09/19/2014 04:48:50 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 09/19/2014 04:48:50 PM : [iNST-SRX ] 02 50 28.51.25 18.CE.5D 23 2F 00 (00) Fri 09/19/2014 04:48:50 PM : [std-Direct Ack] 28.51.25-->ISY/PLM Group=0, Max Hops=3, Hops Left=0