nowandthen

Lee, Thanks for taking the time to help me I appreciate it! By the way, I think my PLM is dying or something is shutting it down? The LED was off again and none of the lights would respond from my RedEye or Mobilinc Pro. A reboot of both fixed it, the LED is on for now. Maybe PLM is the problem? I will open a ticket with UDI support. Thank you!

Went to power down ISY and PLM. The PLM Led was off. Is that normal? For some reason I thought it was always at a low level of green, but I normally don't look at it. How do I know when the PLM has rebooted? Or is it ready to go as soon as power is applied? I've been giving it a couple of minutes before powering up the ISY. The ISY seems to take several minutes to settle down as it runs "run at power up routines". The PLM LED occasionally blinks as the ISY comes up and runs routines. Here's the log: Fri 04/26/2013 06:55:30 PM : [ 21 C5 DF 1] ST 134 Fri 04/26/2013 06:56:08 PM : [22 a5 11 ] Added to list of devices to link to ISY Fri 04/26/2013 06:56:08 PM : [iNST-TX-I1 ] 02 62 22 A5 11 0F 0D 00 Fri 04/26/2013 06:56:08 PM : [iNST-ACK ] 02 62 22.A5.11 0F 0D 00 06 (00) Fri 04/26/2013 06:56:17 PM : [iNST-TX-I1 ] 02 62 22 A5 11 0F 0D 00 Fri 04/26/2013 06:56:17 PM : [iNST-ACK ] 02 62 22.A5.11 0F 0D 00 06 (00) Fri 04/26/2013 06:56:17 PM : [iNST-SRX ] 02 50 22.A5.11 0F.9D.42 A7 0D FF (FF) Fri 04/26/2013 06:56:17 PM : [std-Direct Nack] 22.A5.11-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 04/26/2013 06:56:17 PM : [iNST-TX-I2CS] 02 62 22 A5 11 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Fri 04/26/2013 06:56:17 PM : [iNST-ACK ] 02 62 22.A5.11 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01) Fri 04/26/2013 06:56:18 PM : [iNST-SRX ] 02 50 22.A5.11 0F.9D.42 27 09 01 LNK-ON (01) Fri 04/26/2013 06:56:18 PM : [std-Direct Ack] 22.A5.11-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 04/26/2013 06:56:18 PM : [LNK-BGN ] 02 64 01 00 03 Fri 04/26/2013 06:56:18 PM : [22 A5 11 0 ] Failed to add device Note PLM LED is off.

Both are 3.3.10

Lee, I forgot to mention I did click the finish button but no luck. Tried it several times. Here's the Event Viewer data after following your instructions: Fri 04/26/2013 05:46:43 PM : [22 a5 11 ] Added to list of devices to link to ISY Fri 04/26/2013 05:46:43 PM : [iNST-TX-I1 ] 02 62 22 A5 11 0F 0D 00 Fri 04/26/2013 05:46:43 PM : [iNST-ACK ] 02 62 22.A5.11 0F 0D 00 06 (00) Fri 04/26/2013 05:46:43 PM : [iNST-SRX ] 02 50 22.A5.11 0F.9D.42 A7 0D FF (FF) Fri 04/26/2013 05:46:43 PM : [std-Direct Nack] 22.A5.11-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 04/26/2013 05:46:43 PM : [iNST-TX-I2CS] 02 62 22 A5 11 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 Fri 04/26/2013 05:46:43 PM : [iNST-ACK ] 02 62 22.A5.11 1F 09 01 00 00 00 00 00 00 00 00 00 00 00 00 00 F6 06 LNK-ON (01) Fri 04/26/2013 05:46:43 PM : [iNST-SRX ] 02 50 22.A5.11 0F.9D.42 27 09 01 LNK-ON (01) Fri 04/26/2013 05:46:43 PM : [std-Direct Ack] 22.A5.11-->ISY/PLM Group=0, Max Hops=3, Hops Left=1 Fri 04/26/2013 05:46:47 PM : [22 A5 11 0 ] Failed to add device

I have 2 new 2477S ON -OFF relay switches. They control florescent lights. I always have to add noise filters on florescent lights, these do not have them yet so I took the bulbs out as they are hardwired. Hope that prevents interference during linking. But even with switches off (florescent lights off) the linking window closes after a few seconds, sometimes almost instantaneously. I unplugged the ISY and PLM. Plugged the PLM in, waited a couple of minutes. It doesn't seem to do anything after a few seconds, bright LED then dull LED, but still I waited a while. Then I plugged the ISY in. It took a minute or two to settle down, was running "run on power up routines", as the hall lights I was using shut off. The hot recirc pump turns on then times out. Kind of strange as it is X10, but let's not get side-tracked. So I tried New Insteon Device: I entered the device address, gave it a name and choose the type of device, says adding but after about 10 seconds I get an error message that states "Cannot determine Insteon Engine". I also tried auto discover. No luck. The devices are in my detached garage but my system communicates with other Insteon devices in the garage. And why would that have any effect on the Start Linking window closing so quickly? Lee, I appreciate your help. Any more ideas? I don't think it is Java or corrupt software installation as this problem existed with the previous version. Do I try clearing java again?

Unplugged PLM and yet another reboot and ISY is now responding to motion sensors. I am afraid to try and add the switches. Giving up for today.

Message says most likely my PLM is defective. My PLM has been working just fine until I tried to add the switches.

After reboot I get the system in safe mode message again. UGH!

Thanks Lee, Upgrade to 3.3.10 was a bit of a challenge, not sure why this is always an issue for me, I must be kind of dense. LOL I did eventually get the system up and running again, run on start up has turned on lighting (upgrade knocked out the ISY at sunset). BUT... motions sensors "see" me, but lights do not turn on. UGH! And I still can't link the new switches. This is extremely frustrating! This is why I HATE to upgrade the firmware, something always goes wrong. I'm rebooting the ISY again.

Been a while since I added an Insteon device. Trying to add a new Insteon switch. I click Link Management, then Start Linking. Linking window opens for a few seconds then closes. I unplugged the ISY then let it reboot. Tried again, window stayed open but it did not see the device (after putting device into linking mode well within 4 minutes). Next attempt reverted back to linking window closing after a few seconds. Any ideas? Firmware version 3.2.6. I see 3.3.10 is available but I hate having to go through the update process. Is there a bug in 3.2.6 with regards to linking?

Figured it out. For some reason the program line was refering to Insteon device for the X-10 line. Changed it to X-10 and also had to re-enable the amplifier/bridge. Not happy about that as it seems to cause Insteon problems. Hoping Smarthome will offer their year-end sale soon. I suddenly need to replace a lot more X-10.

Installing Christmas decorations and it seems the ISY will no longer control my X-10 outlets, appliance modules etc. I used to have the ISY X-10 add-on software but sold that with my old ISY99i. The module seemed to only add X-10 names to the tree, but without it I could still control X-10, at least I could some time ago. I have a program that I use daily, it watches for an X-10 signal (from and X-10 switch) then runs a countdown timer. That still works. So is X-10 defeated if you don't have the X-10 module or do I have some other problem? Clearly the program that watches for an external X-10 event is still working. I have an X-10 amplifier/bridge. Since adding more dual band devices (had a lot of "normal" insteon before) I started experiencing less reliability of Insteon switches (worked fine before adding dual band). So i turned the amplifer/bridge off at the breaker panel. Insteon performance improved. HOwever, turning the amplifier/bridge back on does not fix the lack of x-10 control. The x-10 devices shows "unsupported device".

I don't link anything to my motion sensors. I use programs as you suggest. Like you there are times I just want to buy my way out of a problem. It's been several days and it's working fine since removing and adding back (knock on wood).

Thanks Michel! I removed the motion sensor and added it back, with some frustration.Iit seems to be working OK.Hopefully it will not complain anymore. Thanks for the help! Todd

I get this error message every time I log on to the ISY console. It interrupts what I am doing (like replace with) which is very annoying. Can you make it not interrupt the procedure in process? I changed the battery a few months ago, but continue to get this message. The motion sensor is communicating just fine as every time I enter the dining room the lights come on, then go off after the time out. So there isn't a communication error, yet the ISY continues to think there is. Any ideas as to what the problem is? i have other motion sensors with no issues. Motion sensor is the 2420.

The original switch was a non-RF Insteon switch and was 100% reliable. A few months ago I replaced the back porch Insteon switch with a dual band Insteon switch in an effort to spread RF around. The RF switch did not reliably respond to the motion sensor whereas the original non-RF switch was 100% reliable. Odd that a non-RF worked just fine, and dual band is intermittent... Hoping the old dual band switch is defective. Will know in a few days. So far I'm not buying 'Dual band is more reliable". I think it's just more expensive.

I did a "replace with". I did this one time before with success but this time no love. The replaced device showed a green tag with 1011 in it. So I had to go through my scenes and programs reconstructing what was once there (to the best of my knowledge: What ramp rate? What brightness?). Maybe a routine could be added that tests communications to ensure replace with really "takes". If not it gives you another shot. Not sure why I ended up with the green tag and 1011? I deleted the new device, added it back, then rebuilt from scratch. Average bear.

Thanks Lee. Glad to hear there are 99i's with blue LEDs and the 994i-like case. His ISY is working just fine using 99i firmware so I think we are in good shape.

Thanks Michell, It does say 99i on the bottom. The guy may have been mistaken when he said 993i. Did you ever make 99i's with blue LEDs and case like the 994i? My old 99i had green LEDs and a different looking case. Todd

My friend bought one off eBay and the guy said it was a 993i, but was same as a 99i. It has the same style box as my 994i with blue LEDs, not the older 99i with green LEDs. We updated with the 99i firmware. The PLM is V1.5. What is a 993i? A search returned no results. Any concerns with this setup?

As always Lee, many thanks! You have helped me many times and I very much appreciate that!

I'm leaving for work in the morning right around Sunrise -10 minutes, three exterior motion sensors detect me and turn on their corresponding lights as it is not yet sunrise - 10 minutes (program below). The lights are not turning off after two minutes. I'm wondering if the IF becomes false before the ISY counts down the 2 minutes and therefore the THEN stops running. Is this how the ISY "thinks" or do I have another problem? This worked just fine last year but maybe I'm at that threshold of the IF time period. The program works fine after sunset +10 minutes and a short period of time (> 2minutes) before Sunrise - 10 minutes. I waited this morning and same problem, so I manually turned off the lights with my phone. Below is one of my motion sensor programs. The kitchen KPL button is my lockout for not allowing the program to run the THEN path. I turn the KPL button on when I want the exterior light to not change state. If From Sunset + 10 minutes To Sunrise - 10 minutes (next day) And Control 'Exterior / Porch, Side Motion-Sensor' is switched On And Status 'House / 1st Floor / Kitchen Sink KPL / Kitchen Sink KPL - F' is Off Then Set Scene 'Exterior / Porch, Side Lights' On Wait 2 minutes Set Scene 'Exterior / Porch, Side Lights' Off Else - No Actions - (To add one, press 'Action') Maybe I need to add a command in the ELSE to turn the light(s) off? Edit: A command in the ELSE to turn the lights off would turn them off if I turned on Kitchen Sink KPL -F, I don't want that as generally I am defeating this program to keep the lights on. So this won't work. Maybe a separate program that always turns off all exterior lights at sunrise? Not a bad idea for those rare occasions where Insteon fails to turn lights off.

I unplugged my PLM and ISY just before sunset. I have a number of programs that run from sunset to sunrise (next day) or from sunset + 5-10 minutes to sunrise (next day). They do not have the status line in the If section like Lee's program, just a From/To. I waited until about 20 minutes after sunset then plugged the PLM and ISY back in, hurray! the lights caught up! That's all I was looking for, a simple, ISY for dummies switch. I suppose if the power goes out at 2 AM then comes on at 3 AM, the lights won't catch up as it is already next day (If from sunset to sunrise (next day)). But nothing is really critical and if they don't turn on for the rest of the night then so be it. Off to figure where this "Missed Schedule Grace Period" setting is located, and try to understand what that means...

Hi Michel, I guess I find it unusual that you have to check the status of the device, as shown in Lee's program. Perhaps checking the status is not necessary? His program that worked also had a from/to unlike his first program that didn't work. My front porch is basically as Lee's working program is written except I don't check status in the IF section. It's a From/To program. I'll unplug my ISY and see if my from/to program will catch up on start up.

I'm hoping UDI will chime in. I understand Lee's program but it seems that most users would not figure that out (I didn't without Lee's help). I wonder if UDI would modify the Run At Startup to do just that, run any program that is checked as Run At Startup. If power goes out and a program or programs have Run At Startup checked, then upon restart, those programs test the IF statement in such a way that if it should be on then turn it on. Seems to me to be an easy way for most non-sophisticated users to catch-up after a power outage without coming here for help. More intuitive = more happy users.