nowandthen

Update, in case anyone cares. The device I was using to control the ISY was "Insteon Automation", in fine print it also said ISY-99i. At some point Roomie must have neutered this device. Roomie told me to use "Universal Devices", in fine print ISY-994i. Now all the commands are back. THe command are being sent, but they are red which means there are not getting through to the ISY. More investigating...

I have contacted Roomie, but the reply wasn't on point. I will respond to that email and keep my fingers crossed, but I don't think they have much experience with the ISY. My Various activities have Insteon buttons in the remote screens. However the Roomie is not sending out any Insteon commands from the previously working buttons (worked in January of this year). It’s as if the “Program run then” command has been removed from Roomie. Almost all of my Roomie Remote buttons execute the Insteon “Program run then” command. I tried to add a test button, but the only commands available are for various “Light” and “Scene” control (e.g.Light on, Light dim, Scene on, scene off etc). I cannot find the "Program run then" option any more. Did Roomie remove this? Roomie does not send out any commands that have the “Program run then” command. I know about the program IDs, and they are correct. Like I said, they used to work, now Roomie seems to no longer understand the Program command. I have a couple of button sliders that command individual insteon switches. Rommie does send the command (I can see it at the top of the screen). But nothing happens. These too used to work. The buttons use the switch ID (the 6 digit hex code). If I can find the “Program run then” command I can start trouble shooting why none of the lights respond, but at this point Roomie seems to no longer understand ‘Program run then”. Anyone out there use Roomie Remote? It's always been tricky setting up, at least for me, but once set, it's a good remote. I see the UD wiki has info on i-rule but I didn't find anything on Roomie Remote.

Thanks Lee, That does make sense. I have done it backwards in the past with success. Dumb luck maybe. Next time I will click on the dead/gone device and use replace with. Luckily my friend has not reprogrammed the modules we traded so I can get them back temporarily and hopefully get things squared away..

Hi Stu, Sorry, I failed to mention that I did add the new devices. I added one first. The device showed up in the top level of the tree, with Insteon address. I clicked on it and selected replace with. When I realized the problem I added the second new device, but obviously that does nothing as each device is now looking for a device that is no longer there. The problem is I changed out 2 devices in the same group (they were linked together). But the second replaced device obviously has a new Insteon address. Now the first one is trying to find the original 2nd device but it is no longer there. I can't "replace with" on the second device because it can't find the original first device (it too was replaced at the same time). I have 2 replaced devices linked together but they can resolve themselves because each is looking for the other original, which is no longer there. Put simply, I hope, how does one change 2 devices that fail at the same time that were linked together? Hope this makes sense.

A friend needed older lamplincs as he still uses some x-10. Newer lamplincs do not support X-10. So I swapped him for 2 of my older, slightly used lamplincs. I thought, oh this is easy, I've replaced with before. WRONG! I plugged in the first new module and used replace with. All linked devices are updated except for the other "new" one in the group. Obviously (now, duh) the device it is trying to "replace with" is no longer there. Likewise for the other new lamplinc. Now both have an exclamation point next to them. And cannot resolve the links. Any way to resolve this? Should I go get one of them back and plug it back in to resolve this? He hasn't used them yet. For the sake of a situation where 2 in a group die (surge, etc), what is the solution to this kind of situation? Is there a way to "replace with" when 2 or more in a group die? Any tips are greatly appreciated.

I've had KPLs for years, and never realized until now, that if I press and hold the button (.1 button (load) not sure about .b .c etc) that the switch now retains that level the next time I turn it on. I don't want that. My preference is if I manually brighten or dim for some reason, the next time I turn the light on I want it to go back to the level set in the ISY, but it goes back to the last local level setting. Is there a way to disable this? I did not see it in the user manual. I have 2486D's which seem to be superseded by 2334-222.

Got it! I set button H to Non-Toggle [Off] mode, I didn't realize what it was asking when I went to set it to non-toggle mode. So with the button in Non-Toggle [Off] mode, I also had to change the lamp level to 100% (previously I had it at 0% and even in Non-toggle[Off] it would not dim.) Works great! Thanks Lee! You are amazing!

It shows "Non-Toggle [On]" and it is not illuminated. I figured I would deal with illumination later.

This is for an 8 button KPL. I would like to define button G to be On and brighten when held down. I would like to define button H to be Off and dim when held down. I set button G and H to each be non-toggle. I put button G in a scene with the desk light. I clicked the red button under the scene name and set the on level of the light (listed on the lower half) to 30% and set a ramp rate. I put button H in a different scene with the desk light. I clicked on the red button G in the scene and set the light level to 0%. Button G works. Press and release and it goes to 30% as set in the scene. Press and hold, and it will brighten. (Locally the light goes to 60%, so I know the scene is controlling the level.) I cannot get button H to dim. It will only turn the light off, it will not dim. What am I doing wrong? The 6 button KPL comes with this ability out of the box, can we not make other buttons behave the same way? Thanks. The 6 button KPL comes with this ability out of the box, can we not make other button behave the same way?

I had to move the ISY ethernet cable from the old router to the AT&T router/modem. Now it works.

I just changed from AT&T DSL to AT&T Uverse Internet. Now when I launch the ISY Console it returns ISY Finder: Not Found. What do I need to do? Todd

Thanks Lee! You are a fountain of knowledge.

Lee, I found instructions in the manual on restoring the ISY and just completed that. Are you saying I shouldn't have done that? Now that I have what should I do now? Do a full restore devices? Curious if anyone else has had this happen.

A lot of my Insteon devices suddenly turned on (if Off) or went to full bright. I never saw this before and it scares me. If I am not home, they could burn a lot of kilowatts and I wouldn't know it. Has anyone had this happen to them? I know I changed a scene to 50% last night, but after this "hick-up" he scene is 70% (what is was before I changed it to 50%). I have made numerous backups as I have added additional Christmas lighting. How do I restore from a back up? The restore option sounds ominous and I don't want to mess things up. I am looking for a restore from back up but do not see it. I downloaded the ISY manual but only looked at the index, I did not see a save backup ISY or Restore ISY listed in the index. Thanks for any help. Todd

Michel, The problem is the scenes don't show any modules on the lower half of the screen, so I can't set ramp rates or light level. The scenes are running at the ramp rates that the old PLM used so the ISY or PLM knows what to do. Is this related to the RF issue you referred to? I do have RF motion sensors and 3 Insteon thermostats. I need a way to refresh the ISY and/or PLM to repopulate the devices in the lower half of the scene screens so I can adjust ramp rates and light levels.

MY old PLM has V1.0 on the back. The new PLM is V1.B date code is 1305 so it is pretty new. PLM Insteon address is the same as the ISY shows.

Thanks Lee, PLM info/status: 22.81.49 V98 / connected. I had a rough time getting the PLM swapped out. It took about 50 minutes on first pass then seemed to be stuck in a loop of 20 minutes cycles of System Busy 0 -100%. I spent about 4 1/2 hours getting it going last night Any suggestions? I'll contact UDI support tomorrow.

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.