LeeG

The Ramp Rate used when the paddle is pressed is set under the device itself. Click the SwitchLinc node in the My Lighting tree and set the “Ramp Rate (applied locally)†slider to the desired Ramp Rate. This is the value that is used when the SwitchLinc paddle is used. The Scene Responder Ramp Rate for the KeypadLinc button applies only when the KeypadLinc button is pressed. If the Ramp Rate (applied locally) setting does not work and the ISY Firmware is 3.2.x do a Restore Device on the KeypadLinc and then set the Ramp Rate again. It will be necessary to move the slider to a different value, allow that value to be written (Progress Bar appears), then move the slider to the desired setting.

Move the slider to a new position and release the mouse button. A Progress Bar should display. Then move the slider to the desired location. The ISY will not write an existing On Level. That is why it is necessary to move to a different location first.

LeeFleishman The FanLinc Query does not return the actual On Level of the Fan side of the device. The number that comes back on the Query is in the Low speed range thus the On Level is changed to Low. Same number comes back on the Query regardless of the actual current Fan speed or Off. It may take a command other than the standard Query to get the actual On Level of the Fan. I tried an extended command I thought might do the job but it does not provide an accurate Fan speed. I think the Light responding when the Fan motor is turned Off is an issue with the FanLinc hardware. You can verify that by disconnecting the Fan (motor) connection of the FanLinc. Light does not seem to be affected when the motor is not connected to generated a back EMF (that may not be the correct term) when the motor is turned Off.

Some additional actions to take. With the device listed as Unsupported it is impossible for the ISY to establish a Scene that controls the Fan. The Fan is operated with a Group number the ISY does not use unless the device type is FanLinc. This means that any Fan response to a KPL button press is left over from the manual Set button links. Do a Restore Device to the KeypadLinc that had manual Set button links established with the Fan. Otherwise there will be conflicts between what the ISY writes to the KeypadLinc link database when it understands it is a FanLinc Fan and what was established with the Set button. When the FanLinc has been added under 3.2.1 and shows a FanLinc device type with two nodes and the KeypadLinc is clean of Set button links, the ISY Scenes defined to control the FanLinc Fan node will work as defined. The only thing that may be necessary is be sure a Progress Bar is displayed when the Fan On Level slider is positioned to the desired speed. I saw Java fail to notify the Admin Console the slider had been moved (no Progress Bar). I had to move the slider to a different position and then back to the desired speed before a Progress Bar was displayed indicating the change was being written to the FanLinc.

The ISY Scene that has the KeypadLinc button and the switch (SwitchLinc ?), both the KPL button and the switch must be defined to the ISY Scene as Controllers. It sounds like the KPL button was added as a Controller and the switch added as a Responder. With the switch as a Responder it is not cross-linked back to the KPL button so manual switch activity is not reflected back to the KPL button. For the KPL button to stay in sync with manual switch activity both must be Controllers so the ISY will cross-link the KPL button and the switch. Once the Help | About show 3.2.1 for both the Firmware and UI lines, the FanLinc must be Deleted and added back. It will no longer show as Unsupported device when using 3.2.1 ISY and Admin Console. Also you will now have two nodes for the FanLinc. The Fan node is used in Scenes that affect the Fan speed.

Depends on what the power on button is switching. The I/O Link relay is rated at 5A @ 30V (AC or DC). If the power on button is switching 120V the I/O Line relay could not handle. Could use a 5V relay driven by the I/O Linc relay that has contacts rated for 120V.

Go to Help | About and see what is displayed for Firmware and UI. Both lines must be present and both must indicate 3.2.1. If both lines are not there or the UI line does not indicate 3.2.1 then either the cache did not get cleared or the URL to invoke the Admin Console is not the correct one to invoke the 3.2.1 version. EDIT: for the ISY to indicate the FanLinc is an unsupported device the Admin Console that is running is not 3.2.1.

remedy1234 Thanks for the additional information. Is the problem when button A is pressed On or when the Scene is turned On through the Admin Console? Does the Fan physically turn On to Low and the Admin Console shows it as Off or neither the Fan itself nor the Admin Console go to Low? I set up a Scene which I think is what you described SceneFanControlLowA when Scene name selected when button A selected KPL button A is Controller KPL button B is Responder On Level 0% KPL button C is Responder On Level 0% KPL button D is Responder On Level 0% FanLinc-Fan is Responder Low Low When button A on the KPL is pressed On the Fan turns On to Low and the Fan state is changed to Low If the problem is the Fan does not turn On to Low and the Admin Console does not change to Low, move the Fan On Level slider to a different position and confirm a Progress Bar is displayed. Then move the slider to Low and confirm a Progress Bar is displayed. EDIT: I've added a FanLinc Show Device Link Table. The entry at FD8 is the link that supports button A. The 03 in the second byte indicates button A. The 3F in the third from the right end is the Low speed setting. A Show Device Links Table of the FanLinc should show a similar link. It may not be at FD8 as that depends on what else the FanLinc has been assigned to. However, there must be a record with a 03 in the second byte. The three bytes after that will be the KeypadLinc Insteon address and the byte after that will be 3F if the speed is set to Low. EDIT2: made another test Scene using a KeypadLinc Relay (was using Dimmer in previous test) with the same configuration. Button A as Controller, buttons B,C,D as responders set to 0% On Level and a different FanLinc as Responder set to On Level Low. Same results, pressing KPL button A On turns the FanLinc Fan On and the Admin Console show speed as Low.

bipto The SwitchLinc with the v.41 firmware could be an I2CS device which requires 3.2.1 for I2CS support. This would explain the Scene issue. Without the I2CS support the link database cannot be read or written correctly. Run Tools | Diagnostics | Event Viewer with Level 3-Device communications events selected. Create an ISY Scene with the SwitchLinc v.41 firmware as a Responder. Post the event trace. The trace will show if the link database can be read/written under 3.1.17.

As far as the new ISY Scene, both SwitchLincs should be added to the same ISY Scene as Controllers, not Responders. This will cross-link the devices so the LEDs stay in sync when either SwitchLinc is operated with their paddle. The ISY assumes Controllers are also Responders so the ISY Scene can be used to turn both SwitchLincs On or Off. With multiple symptoms, device not controllable with a new Scene and a Scene not being created when the devices were added to the ISY I'm thinking a comm problem to the device that does not get controlled from the ISY Scene. Run a Scene Test on the ISY Scene that has the two switches as Responders. That will confirm the link records are correct if both device are successful. Passing a Scene Test but not responding to the Scene itself from the Admin Console or a Program strongly suggests a comm problem

Apologies for slow response. The forum would not let me login Creating a Scene for each speed is one way of doing it. Four Scenes, each with its own KeypadLinc button as Controller and the FanLinc Fan node as Responder. Selecting each KeypadLinc name listed below the ISY Scene name will display the Fan node On Level slider for that KeypadLinc button. Adjust the Fan node On Level slider to the desired Fan speed. When the On Level slider is moved there must be a Progress Bar displayed showing Java passed on the change in slider position. If no Progress bar is seen move the slider to a different position, release the mouse button, then move the slider to the desired location. That should result in a Progress Bar being displayed when the slider is set to the desired Fan speed.

remedy1234 There are a number of things I'm not following. When the KeypadLinc button A name listed under the ISY Scene name is selected as the Controller of the Scene there is no Button A On Level slider setting as it is the Controller. There are no sliders for other Secondary buttons in the Scene as they cannot be turned Off with an On command. The very newest KPL v.40 firmware does have the ability to turn a Secondary button LED Off with an On command but the ISY has not picked up support for that yet. What Status is not updated on the Admin Console?

Any time a clause has a Wait or Repeat statement the If can be reevaluated. The UDI Wiki has an excellent explanation of how Repeat and Wait statements can affect execution of statements after the wait or Repeat. One solution is to change the State variable in the Then clause If $GarageDoorSensor is 1 And From Sunset + 15 minutes To Sunrise (next day) Then Set 'Garage Exterior Light' On Wait 1 minute Set 'Garage Exterior Light' Off $GarageDoorSensor is 0 Else - No Actions - (To add one, press 'Action') Another solution is to move the Then logic to a second Program that has no If section. The current Program calls the second Program to perform the logic. The first Program cannot be reevaluated because there is no Wait. Even if it is reevaluated to False it does not affect the second Program.

The State variable is changing value before the Wait 1 minute completes. This causes the If to be reevaluated as False driving the Else clause so statements after the Wait are not executed.

If the I/O Linc Relay is not connected to the garage door opener what is connected to the garage door opener Insteon wise that puts the Insteon devices in play.

Did you make any determination why the I/O Linc Relay is being directed to turn On? Is the I/O Linc Sensor turning On/Off without the door moving? The ISY does not know it is raining. Not likely recycling the ISY is going to make any difference but there is no harm either.

Sure, if you have a Serial port to connect it to. I have done that in the past. The SHN Utility makes NO changes to the PLM. The PLM is simply means for passing commands to the powerline.

It is a onetime thing. Once the EZFlora configuration is set to use Zone 8 as Pump Control it will remain. The Pump Control configuration change has to be done after adding the EZFlora to the ISY. It would also be lost if the EZFlora was factory reset.

remedy1234 It is really great that UDI added the UI line as a positive indicator. Use to have to scroll down the Device Type list looking for devices that were newly supported. Once you get the Admin Console correct and Help | About shows 3.2.1 in both lines, the FanLinc will have to be deleted and added back. Once it was not identified (Unsupported device) the only correction is to delete and add it again with the latest Admin Console code.

remedy1234 Sounds like the FanLinc was added to the ISY before upgrading to 3.2.1. Delete the device and add it under 3.2.1. If it was added under 3.2.1 the Admin Console is not at the 3.2.1 level. Go to Help | About and check the Firmware line and the UI line. Both must be present and both must indicate 3.2.1. If UI is missing or not at 3.2.1 clear the Java cache and use the URL to invoke the 3.2.1 Admin Console. The 3.2.1 Available post has the list of URLs to use for 3.2.1. EDIT: the device will have to be Deleted and added back with the 3.2.1 Admin Console

Things were going well until the Master Valve question. The EZFlora does support what is referred to as a Pump Control function that turns On Zone 8 when any other Zone is On. Unfortunately the ISY does not support turning on that function. Simplehomenet provides a Simplehomenet Utility Suite (free XP program download from the SHN web site) that can configure the EZFlora to use Zone 8 as a Pump Control Zone. It would require another PLM to use as the SHN Utility Suite interface to the powerline to configure the EZFlora. Use of the Pump Control function is required as turning On any Zone in the EZFlora automatically turns Off any other Zone which is currently On. From an ISY Program it is not possible to turn two Zones On at once.

An EZFlora and an ISY Program are all that is needed to run the EZFlora. The WeatherBug and Irrigation modules provide environmental data that allow intelligent adjustment of irrigation schedules, length of watering cycles, etc. I don’t use either optional module. Just use a few different ISY Programs based on how much rain has fallen in the last few days and how hot. I irrigate from a large lake so water consumption is not an issue. I’m sure others who do use the irrigation module will jump in here with information on its advantages.

The FanLinc is a single Insteon device, one Insteon address, that has function to control a Light and a Fan. After adding the FanLinc to the ISY there will be two nodes, one for the Light and one for the Fan. The Fan node would be added as a Responder in an ISY Scene with a KeypadLinc button as a Controller. The Fan Responder On Level controls the speed of the Fan.

Use New INSTEON Device. Enter the device Insteon address, name (your choice) and use the Default Auto Discover. What problems are you having?

Click on the KeypadLinc button name listed below the Scene name in the My Lighting tree. The Scene Name (PLM is Controller) has a unique set of Responder On Level values which can be different from the Responder On Level values when the Controller is a KeypadLinc button.