LeeG

Put the RemoteLinc into linking mode by pressing the Dim/Bright buttons at the same time until the RemoteLinc LED is blinking. Then add the RemoteLinc using Link Management | Link a RemoteLinc.

Bad combination. The ISY is running 3.1.17 but the Admin Console is 3.2.6. Go back to the 3.1.17 Admin Console to do the update.

I'm running that Java build with no problems. Turn Off security before starting the Admin Console. How was the image downloaded? Some browsers will unzip during the download which makes the image invalid to install.

When the Insteon devices are added to the ISY use the default option "Remove existing links". This insures the device link database is clean. I used the crawl method once when setting up an ISY for the primary house devices. I wanted to see how it worked as all my tests up to that point had added devices with the Remove existing links option. Devices are named the Insteon address and Scene names are in the form Scene xxxx where xxxx is a number. It took days to get all the devices named, the Scenes named, and the Scenes cleaned up from bad link information. Was an interesting exercise and certainly doable but not the best approach. Since the devices are known to HouseLinc note all the device Insteon addresses ahead of time with some meaningful names. Could save removing some cover plates down the line.

Some basics to check. Look at Programs | Summary tab. Is Program Enabled? Is it marked not saved? Does the Last Run Time column indicate it was ever triggered? What does the Status column say? What ISY firmware is being used?

If nothing else a simple mechanical timer to remove power for a few minutes. Why not fix the hang up rather than reboot every day.

Illusion Good catch! You are absolutely right. Scene On/Off shows correct I/O Linc Relay status for 100% On Level. However, it makes no adjustment for Relay command reversal indicated by 0% On Level. Since it does not mark the Relay Off with a Scene On the ISY must recognize the I/O Linc as not being a normal Insteon light control device but does not honor command reversal. Thanks for the catch.

The 0% On Level is universally taken as Off across the Insteon devices. The I/O Linc Relay is the exception. It would/will require an exception path in the ISY to handle the I/O Linc Relay. Is the I/O Linc Relay configured for Momentary mode?

There is no issue putting the ISY itself on a UPS. The PLM should not be powered from any outlet on the UPS. The powerline signals will be attenuated to the point of not being reliable. The UPS itself should be plugged into a FilterLinc along with any other PC gear on the same circuit as the PLM.

The following answers assume the ToggleLinc Red load wire is connected to the light. “Can I set the light level as a variable and then increment or decrement 25%?†No. “Is there a way to set up step sizes?†No. “Has anyone put this functionality into programming the switches?†No. The ToggleLinc internal programming cannot be changed.

See this topic viewtopic.php?f=51&t=7144&hilit=nest Apparently they were not willing to make their APIs public.

"I clearly do not understand when it tests IFs etc." The ISY is event driven. When a Program is triggered depends on what is coded in the If section. If time is 7:30PM causes the Program to be triggered at 7:30 PM If Control 'devciexxx' is switched On causes the Program to be triggered whenever an On command is received from devicexxx If Status 'deviceyyy' is On causes the Program to be triggered whenever deviceyyy Status changes If $StateVariablex is 0 causes the Program to be triggered whenever StateVariablex changes value. The If section can be a single test or a combination of conditions Ored and Anded together. When a Program is triggered by something in the If section, either the Then or Else clause runs depending on whether the If evaluation is True or False. The UDI Wiki has some good information on the above.

This is a Michel post earlier this year regarding SD card. viewtopic.php?f=7&t=7768&p=59471&hilit=sd+card+speed#p59471 "My preference is SanDisk ... we do not use SDIO; we use SPI interface which means that the maximum speed (regardless of what SD Card speed you get) is 10Mbps."

hbsh01 Yes. For those not familiar the UDI Wiki covers both. bsobel Very logical. Don't know if it is practical without knowing the internal of the ISY.

Glad it is working. Only necessary to Delete/readd for the new I2CS devices. The ISY firmware pre 3.2.x does not have the logic to correctly process the I2CS devices.

I have not seen an Insteon device with flash/blink function.

Was the OutletLinc Deleted and added under 3.2.6 and any Scenes containing the OutletLinc created under 3.2.6? This is necessary for an I2CS device to be set up correctly. Run Help | About. Be sure the Firmware and UI lines are both there and both indicate 3.2.6. How is the OutletLinc being controlled, Direct or Scene?

This is the test Program that has Run at Startup which did not turn On the ICON device. If Time is Sunset Then Set 'ICON Relay 2' On Else - No Actions - (To add one, press 'Action') What is needed is a Program specifically written to "fix" things. This Program has Run at Startup and is Disabled so it cannot be triggered by device activity. I chose the To time as Sunrise the next day. It could be anything that defines the desired range, If Status 'ICON Relay 2' is Off And From Sunset To Sunrise (next day) Then Set 'ICON Relay 2' On Else - No Actions - (To add one, press 'Action')

Program was triggered after reboot. The Else clause ran ( it was not Sunset so If was False) so the action in the Then clause to turn On the Insteon device did not execute.

I have a test set up for the specific question. Will post result tonight after Sunset.

Sorry, don't know that specific answer. Code it up and see what happens.

Under Schedule, first pulldown, select From. Then uncheck Daily.

Run Tools | Diagnostics | Event Viewer with Level 3 selected. Watch for X10 traffic. X10 is often unreliable. The X10 messages may not be arriving at the PLM. Also note tha if the X10 messages are flooding the powerline the Wait will never complete and the Insteon command never executed. Selecting run Then only invokes the Program for a single pass. It should not make any difference regarding it being triggered when X10 messages are received unless the Program is not Enabled or the Program is in a Folder with a False If condition.

Yes, the Program is triggered after the ISY boots up. What it does when triggered is entirely up to how it is written. Not trying to be vague here, just nothing about Run At Startup that is absolutely related to turning devices On or Off.

A KeypadLinc button can be defined as a Responder to a Scene and turn the Scene On/Off at some appropriate rate. However, flashing for more than a few seconds puts a lot of Insteon traffic on the powerline which can interfere with other Insteon activity. Flashing/blinking is not recommended.