nowandthen

My PLM failed last week. I finally got the system back up and running with a new PLM. Everything for the most part seems OK. However, when I open a scene I no longer see the devices listed in the lower half of the screen. This is where one can set on level and ramp rate. The scenes are running at ramp rates I set prior to the PLM failure but now I have no way to change them. It seems I have to remove a device from the scene then put it back in order to see that device in the lower half. Please tell there's a more efficient way to fix this. I hate to think I have to remove and add all devices to my scenes. I have quite a few scenes and devices and I don't remember all the on levels and ramp rates for each scene. The scenes that have controllers show in the bottom but not the others.

Thanks!

Thanks Michel! I have only one X10 device left. I'll do as you mention after the PLM restores. However... I don't understand the "telnet in". This can't be done from the admin screen on my PC?

Hi Michel, I have the new PLM. The problem was the error message I got when I tried to restore. Please read my post just before and just after yours. I've rolled back the firmware to 3.2.6 and loaded a 5 month old 3.2.6 backup file. Can you explain the error message "Could not open config file to read [/CONF/FF0504.REC]" and should I be concerned? It seems to be restoring the PLM albeit to an old backup. Thanks

More guts... I rolled back my ISY from 3.3.10 to 3.2.6. Then loaded my last 3.2.6 back up 12-12-12. It loaded, it complained about devices no longer hooked up (Christmas stuff) but loaded. Then I did a restore PLM. It went a lot farther than before but still got the error message mentioned above. However the progress bar continues to advance. Progress is slow (was also slow before error message). Maybe I bailed too early the last time not realizing it would continue. Keeping my fingers crossed. Advances at a rate of about 1% every 30 seconds.

No guts no glory... So I get this error message: Could not open config file to read [/CONF/FF0504.REC] Could not open file [/CONF/FF0504.REC] I did do a backup before removing the old PLM.

I have my new PLM in hand. I read through the How-to on replacing the PLM. Seems straight forward. Last Saturday Insteon Support had me try to perform a factory reset on the old PLM and then a restore PLM. It didn't go very well. I finally got the PLM limping along until the new one arrived. A few programs run, many others do not. Many "complaints" of "can't communicate with" but later, most got resolved. However, I still couldn't communicate with most devices either through the ISY computer interface or through smartphone programs. Question: If I do a restore with the new PLM will it likely be OK? This assumes the original problem is with the old PLM and the new one will fix the issues described above. Of course I do not have a recent back up. I was very good at doing them regularly but had no reason to log onto the ISY for several months so no recent back up. Murphy's law. So just because many programs and devices don't work at the moment is the ISY file still good to load into the new PLM?

Called Insteon support this morning. He thinks the PLM is going bad. We couldn't get it to reset, tried a restore PLM and it failed. Now my PLM is really messed up. LOL Finally got the PLM "working", restore PLM is proceeding. I have a lot of "failed to communicate with". This evening the PLM LED was off. It must be on it's last legs. cycled power and it is back up, who knows for how long. I will order a new PLM and keep my fingers crossed. Lee, I forgot to ask about the 03 code, sorry.

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.