LeeG

The I/O Linc Sensor can be reversed by using the other magnetic switch wires (green/black). There is an I/O Linc Trigger Reverse option that reverses the On/Off commands issued but this option can create confusion because a device Query returns the actual I/O Linc Sensor not the command reversed values. The EZIO6I has configuration options (not settable with the ISY) that can be used to reverse the On/Off commands. The Simplehomenet Utility Suite (free download from SHN) and a PLM can be used to set the EZIO6I configuration. The first thing is to decide what do you want. Should the I/O Linc Sensor be On with the door Open or the door closed. The Green LED on the I/O Linc shows the true Sensor On/Off state. Chose the wires (red/black or green/black) which give that result. Best to not use the Trigger Reverse option if it can be avoided. Depending on the above choice both the I/O Linc and the EZIO6I might report the same way. If not then either change the EZIO6I magnetic switches to the opposite of what is currently being used (simplest choice) or use the SHN Utility Suite and another PLM to configure the EZIO6I to reverse the On/Off commands sent.

Unless something has changed in the latest KeypadLinc firmware LED brightness adjustments apply to all the buttons including ON/OFF. That is, button A cannot be set to one brightness level and button B to a different level. What results are being seen and what is the KeypadLinc type (relay or dimmer) and what is the firmware level?

thedishking What is the firmware level of the 6 button KeypadLinc? Is the KeypadLinc a Relay or a Dimmer? EDIT: I set up a Scene with Secondary button A & B as Controllers and ON/OFF as Responder. A & B turn the Primary load ON/OFF On and Off as A & B cycle On/Off. I am using a 6 button Relay with v.40 firmware. I’ll try to recreate your configuration once I know type and firmware of KeypadLinc. EDIT2: did the same set up with a 6 button KeypadLinc Dimmer with v.36 firmware. A & B cycle the Primary Load ON/OFF as A & B cycle On/Off. Perhaps there is some additional configuration that is affecting the operation. Did you do any Button Grouping along with the Scene definition.

The InLineLinc is the alternative if a new larger box is not installed inside.

The OP has the same question on the Smarthome forum. I raised the same question. The wiring diagram the OP posted describes and shows a momentary NO contact. I suggested using the NO Relay contact with one of the I/O Linc momentary modes. Have not seen additional posts on the subject.

The device controlled by Start1 never turned On during the tests because all reboots were done before Sunset. When the reboot was done without Run At Startup Start1 did not get triggered. The Last Run Time column was not set. When the Run At Startup option was added to Start1 the Program was triggered but the device did not turn On because the If was False.

That is (would be) a file on the SD card. Nothing to do with the FanLinc itself. EDIT: when are you seeing that message. I saw it during device add but that was at the beginning of the process before the device was added. If this is happening during a restart it would explain why the On Level (Applied Locally) value is not being restored.

Perhaps some examples will help. I defined three Programs, NONE have the Run At Startup Start1 If From Sunset To Sunrise (next day) Then Set 'ICON Relay 1' On Else - No Actions - (To add one, press 'Action') Start2 If Time is 6:00:00AM Then Set 'ICON Dimmer 1' On Else - No Actions - (To add one, press 'Action') Start 3 If Status 'IO Linc1-Sensor' is On Then Set 'SwitchLinc Dimmer' On Else - No Actions - (To add one, press 'Action') Rebooted the ISY in the afternoon, before Sunset. Start 1 was not run because the time range in the If condition has not arrived. Start2 and Start3 ran at Reboot. The Start2 Status was True as the trigger time had already occurred and the device controlled by Start2 should have been On and was turned On during the Reboot. Start3 ran with a Status of False because the I/O Linc Status was not On. This one can be tricky because the Query will return the actual state of the I/O Linc Sensor which could be opposite to what you think if Trigger Reverse option is being used. I turned On Run At Startup for all three Programs and Rebooted again. The only difference was Start1 was run because of the Run At Startup (even though Sunset had not arrived) but the Status was False because it was not in the time range. The Run At Startup does not override the If Conditions. Look at Run At Startup as an option on a Program that should run at Reboot and perform functions so the If section may not be useful. It can be, there are no absolutes. Look at the Programs | Summary tab. The Last Run Time and Status column will show if the Program Ran and what the Statue (true/false) was.

Are 4 buttons being used for Off, Low. Med, High or trying to move through each of the 4 possible settings with a single KeypadLinc button. If the later a variable reflecting the last setting so a different Program can be triggered by the single KeypadLinc button to move to the next setting. A single button requires 4 Programs (maybe three if creative with True/False condition). Each Program triggers with a button press and a different variable value to move to the next Fan speed. Also updates the variable value so next button press invokes the next Program.

Michel Two FanLincs installed, one I2, one I2CS. Both Light node On Level (Applied Locally) sliders are set to 0% after a Reboot even though I specifically moved both sliders to 100% and a Progress bar was displayed indicating the change in slider position was noted by the Admin Console. Have to move the On Level (Applied Locally) slider back to 100% before On button will turn On the FanLinc Light. EDIT: repeated this test several times while testing some examples for a different topic. In all cases a Reboot set the On Level (Applied Locally) slider to 0% for FanLinc.

andyf0 Sorry about that, it was a dumb suggestion in hind site.

The 2477S is not shown as an available device on the Smarthome web site. This a Beta device? Same with the a 2 wire RF dimmer which seems an odd dimmer device since a 2 wire device does not have a load. Anyway, you may be able to use these devices by entering a specific non Dual Band equivalent. Not sure what affect that will have on I2CS detection. There is no restriction listed in the 3.2.0 announcement so I would think I2CS detection will work.

Neither of those cat/subcat values (1.32 and 2.42) are listed in the Device Type pulldown at 3.2.0 which is why they are identified as unsupported. Would not think an unsupported device could be Replaced With since its type is unknown. UDI will have to add those types in the device type list.

nedsmith In addition to the On Level (Applied Locally) slider to 100%, move the Ramp Rate (Applied Locally) slider to 0.1 seconds. Also from the event trace it looks like the Device Type field specified FanLinc. Nothing wrong with that selection, I have installed one of the original FanLincs with that option and it works fine once the On Level (Applied Locally) slider is moved to 100%. However, the FanLinc Firmware level will indicate v.00 when Auto Discover is not used. Before getting too far along I suggest deleting the FanLinc and adding it back using Auto Discover so the FanLinc firmware level will be displayed. EDIT: the Ramp Rate (Applied Locally) can remain at 9 minutes. The FanLinc is one of those devices that treat a 9 minute ramp rate as 0.2 seconds.

andyf0 Just a thought, does the Help | About show UI at 3.2.0?

The existing manual switch located in the house I assume can be replaced with a SwitchLinc Relay 2476S. The 2420M Motion Sensor is not water proof so it has to be mounted in a location protected from the elements. The Motion Sensor can trigger an ISY Program that turns On the SwitchLinc to turn On the outside lights. How long they stay On can be controlled with the ISY Program. I do not see a need for the InLineLinc w/sense. It can be used with a motion sensor that is powered from 120V AC which is not the type of motion sensor you would be using. Also since there is already a manual switch inside that can be replaced with an Insteon switch there is no need to place an InLineLinc in the outside light fixture.

barryH Check Help | About display for the Firmware line and the UI line. Do both lines display and both indicate 3.2.0. If not clear the Java cache and be sure to use the URL for accessing the 3.2.0 Admin Console.

nedsmith The Event trace of the FanLinc device add does not show any errors. Do you see two nodes listed for the FanLinc after the device add? If so what happens when the Light node is select and the On button at the bottom of the screen is pressed? Does the FanLinc Light status LED turn Green? If not what is the On Level (applied locally) slider position? If in the left position 0% move the slider to the 100% position and try the On button again.

Need to determine what is happening. Once that is known then comes the how to fix. The ISY is not going to turn devices Off on its own. Do you have Scenes that contain all the devices that are turning Off and if so what drives the Scenes. If Programs drive the Scenes the Programs | Summary tab may provide some in site into what is going on. If the power was cycling during the outage it might be useful to remove power from the ISY and the PLM and restore now that power is back solid.

If you click on this link http://www.universal-devices.com/99i/3.2.0/ it should invoke the Admin Console using your ISY. It takes a little while because the Admin Console has to download from the UDI site. Have you installed 3.2.0 on the ISY and cleared the Java cache before attempting to use either of the links?

PM on the way.

Define a single ISY Scene that contains both KeypadLinc button As as Controllers and the Lamp as a responder. ISY will cross link the KeypadLinc buttons such that either button will control the Lamp and both button A LEDs will stay in sync.

First thing to try is a new battery. It will often send false On messages when the battery is low. If that does not resolve it look for something in the MS field of view.

“Do you think the FanLinc is defective?: No. How long have you had the FanLinc? The Factory Reset would normally wipe out the links the device add created. Suggest deleting the FanLinc and add it back. Two things to check first though. Click on Help | About and make sure the Firmware line and the UI line both say 3.2.0. I not then clear the Java cache and use the URL for accessing the 3.2.0 Admin Console. Second, run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Now perform the new device add and post the event log. .

There are various tools available with the ISY to do a detail analysis of the current situation but if Set button links have been done the best solution is to delete the KeypadLinc from the ISY and add it back. That will restore all the link records the ISY requires and removes the Set button links in the process. That provides a known clean starting environment. Once the device has been added back verify button press On/Off shows up on the Admin Console Current State column. Just to be sure some comm problem has not decided to show up now.