Noremac

Thanks for the suggestions about the power supply. I actually had a spare 12V power supply with the right connector and polarity. Upon trying it, however, the iSY power light still does not light. The iSY is still functioning ok as best I can tell, but the web server function can take a while to drop off. Any ideas about the iSY power light LED? Could it just be a bad LED? Or maybe an indicator of a looming problem?

Hi folks. My iSY Power Light (the blue one on the far left) is no longer lit. Is this a symptom of a problem? The only thing that I notice isn't working reliably is the device webserver (via a remote connection). Many times I have to reboot the iSY in order to restore the webserver function. Also, what is the warranty on the iSY (bought from SmartHome if that matters)? This one is only about 18 months old.

Thanks, larryllix! I assume you are offering two suggestions. What would your choice be? The second one that uses a variable seems more compact, but I'm not sure I understand it!

Hi all, I'm trying to start an otherwise simple timer with the following logic: 1. Turn on a scene/device at sunset (or relative to sunset); 2. OR, turn on the same scene/device at 7:00 pm, WHICHEVER COMES LAST (during the same day). How would I go about expressing this logic? Thanks!

Michel- You were on the right track regarding the possibility of interference. Although I still had the communication problem when shifting the PLM to a different outlet as you suggested, it started me thinking of possible causes of interference. After unplugging several nearby devices, I narrowed down the culprit to a Klipsch bluetooth speaker powered by a brick about 30 ft away. Although local scenes were still working in the same vicinity, the PLM must have been more sensitive and on the same circuit as the brick. All communication problems went away when I unplugged it. A lesson for anyone else searching and reading this thread in the future - don't count on Insteon dual band devices to save you from powerline interference which can manifest as bad PLM communications. ~Noremac

Thanks Michel! One question about the ISY restore: In this ordeal, one thing that I did was upgrade the ISY to the latest firmware (4.6.2), so the last "good" backup that I have was done with a prior firmware level. Is there any issue restoring the ISY with 4.6.2 using a backup from a prior firmware version (I can't remember which one it was, but it was fairly recent)? Finally, you indicate to perform a Restore Devices command, not just a Restore PLM. I assume that Restore Devices also takes care of the new PLM? ~Noremac

Thanks for the advice to perform the PLM restore locally, but after attempting it several times on the local ISY network, I still don't have function. The first time I tried it, I got the same set of error messages ("Could not open config file to read, [/CONF/INSTEON.OPT] and "Failed resetting the PLM",[-200000/-30]). Finally, the error messages stopped, but there doesn't seem to be any communication with the various Insteon devices in the home. All devices have the red "!" next to them, and all attempts to perform a Write operation seem to fail. Other things I've tried: 1. Restored the ISY with a known backup. 2. Performed another Factory reset of the PLM 3. Ran Restore Devices in addition to Restore PLM 4. Ran Diagnostics..PLM Info/Status. Result: PLM shows "Connected" with the correct PLM replacement serial # showing and v9E firmware. 5. Ran Diagnostics...Show PLM Link Table...Start. It tries to connect, stops, and the entry box remains blank. Why can't the PLM talk to the other devices? Is it possible the replacement PLM is also defective? (It is a Rev 2.3)

Thanks, but that's the procedure I followed. Just to be sure, I repeated it. I also did a factory-reset of the PLM, whereupon I got a different error message when attempting to restore the PLM: "Could not open config file to read [/CONF/INSTEON.OPT], followed by the original "Failed resetting the PLM" message. I then ran the restore PLM function again, and only got the original message. FYI - I am performing these functions remotely for a friends computer - over https. Would that somehow matter for performing the Restore PLM? Help!!

I got a replacement PLM from Smarthome under warranty, followed the instructions for rebooting the ISY, and attempted to perform a Restore PLM command. The progress bar continues up to 11%, but then I get an error dialog that says "Failed resetting the PLM [-200000/-30]" What's wrong?

Thanks for the advice on the old 2440 RemoteLincs. I deleted and re-added the one that was showing v.00, which now shows v.35. I also had success linking it after moving as far away from the PLM as possible. Thanks for all the links and suggestions!

Techman- Good catch. I have re-restored all again, and most things are working. However, the Remotelinc you noted (which is the original #2440) is still showing v.00. I actually like the old Remotelincs, but they don't seem to play well with other current Insteon hardware/software, and they are very difficult to get linked up.

Yes, I followed those instructions. I do have a backup ISY file. Is there a way to completely reset the ISY, the PLM, and all devices?

I had a bad PLM and replaced it today. From the ISY console, I restored the PLM, and also restored every Insteon device. I can query and command individual devices from the console. But the problem now is that the ISY console cannot control any scenes! When I select a scene, I can no longer see the settings for how the scene will be setup when commanded by the ISY. See attached screen grab. What did I do wrong?

Thanks for the approach, Jon. I too am hoping there is something simpler that makes use of if/then/else/and/or logic!

I have a light that I would like to come on at either 4:30pm, or 2 hours before sunset, whichever occurs LATER. With this criteria, the light would never come on before 4:30pm, but could come on well after 6pm on the longest days of the year. How would I capture this logic with a 994i timer? Many thanks!