LeeG

Jumper 5 allows the ISY to configure the Motion Sensor options. I recommend having Jumper 5 in place. The use of Jumper 5 has no affect on the decision to link the Motion Sensor as a Controller of a Scene or have the Motion Sensor trigger a Program to perform the activity. That choice is dictated by how much control you want/need over what the Motion Sensor does. Having the Motion Sensor directly turn On a Scene has the best Responder response time. Some users want to prevent the Motion Sensor from activating Responders for some period of time during a given day. Others want the Motion Sensor to turn On a Responder at some lower On Level and then be able to override that level by manually turning the Responder 100% On. I do that in the Master Bathroom. Neither can be done when the Motion Sensor as a Controller of the Scene. Some users have the Motion Sensor turn the Responder(s) On and trigger an ISY Program to control when the Responders turn Off. Provides the flexibility of turning the Responder(s) On as quickly as possible with the power of an ISY Program controlling when the Responder(s) turn Off.

That will work. Thats probably what you were trying to explain earlier. Sorry.

Cannot do that. The EZFlora does not allow turning On more than one Zone On at a time. When Pump Control is Disabled (default) Zone 8 cannot be turned On with any other Zone. Turning any Zone On automatically turns Off any Zone that is On. When Pump Control is Enabled Zone 8 cannot be controlled at all. When Pump Control is Enabled the EZFlora turns On Zone 8 when any of the Zones 1-7 are turned On.

You can produce the LED Off state as the final state by removing the Secondary buttons as Controllers of all Scenes. Trigger a Program with button A Status On. Have the Program perform the Scene activity you want to accomplish along with issuing a Set Scene xxxx Off that has the 4 Secondary buttons as Responders. This way button A produces only the effect you want regardless of single/double tap and all the Secondary buttons are turned Off. The down side is there will be a slight delay triggering a Program versus direct Scene control. Also the KPL button will blink On until the triggered Program turns all the buttons Off. The On command directs the device(s) to turn On to some % On Level. Turning On to 0% On Level has the effect of turning the device(s) Off. There is no logical counterpart for the Off command. The Off command directs the device(s) to turn Off. There is no concept of an Off command turning a device On.

The ISY does not have an Admin Console function that sets the Pump Control Enable/Disable option. The Pump Control Enabled option works fine with the ISY when it is set by the SHN Utility. When Pump Control is Enabled the EZFlora automatically turns On Zone 8 whenever any Zone 1-7 is On. There is nothing unique about wiring Zone 8 to the Master Valve. It is wired as any Zone to Value would be wired. Zone 8 from each EZFlora is connected to the Master Valve. Whether a Zone on both EZFloras should be on at the same time is a matter of water supply capacity versus Zone requirement. Zones are often sized based on the water supply capacity. If a Zone on each EZFlora is turned On at the same time the capacity of the water supply could be exceeded.

The Pump Control Zone (Master Valve) is Zone 8. Zones 1-7 control valves, Zone 8 controls the Master Valve. Running Zone 8 from each EZFlora to the Master Valve insures the valve is On when any Zone is On. The ISY does not support setting the Pump Control option. The Simplehomenet Utility Suite (free download from Smartenit/Simplehomenet web site) must be used to set the Pump Control option. The SHN Utility requires a PLM as a powerline interface. If a spare is not available the ISY PLM can be connected to the serial port on a PC, temporarily used as the powerline interface for the SHN Utility. The SHN Utility makes no changes to the PLM.

Put one of the RF devices into linking mode. Right click the Primary node and select Write to Device. When one device is complete and it is no longer in linking mode, put the other device into linking mode. Right click Primary node and Write Updates to Device. This ISY has something it wants to write to each RF device. Any time updates are made in general the ISY tries to write pending updates. Once the updates have been written the ISY will no longer attempt to write to these devices until some change is made that involves these devices.

I agree that the Backlight level for buttons which are Off can be set to what is LEDs visually Off. I want to know how to set the BackLight level so that buttons which are On and Off have the same non visible LED level. That is to say it is impossible by looking at a button to know if the button is On or Off. I have never been able to achieve this using commands through the ISY or through the manual adjustment level. It is this state that I want to know how to achieve. The state where it is impossible to know if a button is On or Off.

oberkc “I can tell you that my understanding is that keypads CAN be set to zero backlight.†If you mean by this that all the buttons on a KeypadLinc can be set in such a way as to not turn On when a button is pressed please explain how this is done.

If the objective is to test the Then clause it is easiest to right click the Program name selecting Run Then. There is nothing that will simulate a Fast Off from the device.

There is no mechanism to stop the A-D button LEDs from turning On when the buttons are in Toggle mode. It would not be possible to know when a button is On or Off if the LEDs did not work. They can be put into non-toggle Off mode such that after blinking twice they turn Off. They would be of little use for Scene control. An ISY Program can be triggered when an Off command is received from one the Secondary buttons and perform whatever activity is needed.

Something is blocking the push of data from the ISY to the Admin Console. Things like Kaspersky and Avast are common sources. Be sure the ISY is in the trusted/white list of devices in the AV.

Try using a Scene with a 2 second ramp rate to turn the LampLinc On.

"From the Event Viewer, I see the Fast Off notification going to the ToggleLinc," This may be the issue. If Control is looking at commands coming "from" the device, not a Fast Off going "to" the device.

This can be done with Scenes if the KPLs are v.40 or higher. At that KPL firmware the KPLs support another Controller turning Secondary KPL buttons Off with a Scene On. If the KPLs are at lower firmware level then ISY Programs and additional Scenes are required to turn Off the Secondary buttons on the Responder KPL that is below v.40 firmware Scene Low KPL1 button A – Controller KPL1 button B – Responder 0% On Level KPL1 button C – Responder 0% On Level KPL2 button D – Responder 0% On Level KPL2 button A – Controller KPL2 button B – Responder 0% On Level KPL2 button C – Responder 0% On Level KPL2 button D – Responder 0% On Level FanLinc Motor – Low Scene Med KPL1 button B – Controller KPL1 button A – Responder 0% On Level KPL1 button C – Responder 0% On Level KPL2 button D – Responder 0% On Level KPL2 button B – Controller KPL2 button A – Responder 0% On Level KPL2 button C – Responder 0% On Level KPL2 button D – Responder 0% On Level FanLinc Motor – Med Scene High KPL1 button C – Controller KPL1 button A – Responder 0% On Level KPL1 button B – Responder 0% On Level KPL2 button D – Responder 0% On Level KPL2 button C – Controller KPL2 button A – Responder 0% On Level KPL2 button B – Responder 0% On Level KPL2 button D – Responder 0% On Level FanLinc Motor – High Scene Off KPL1 button D – Controller KPL1 button A – Responder 0% On Level KPL1 button B – Responder 0% On Level KPL2 button C – Responder 0% On Level KPL2 button D – Controller KPL2 button A – Responder 0% On Level KPL2 button B – Responder 0% On Level KPL2 button C – Responder 0% On Level FanLinc Motor - Off

Post an event trace at LEVEL 3

Define an ISY Scene, add the desired KeypadLinc Timer button to the Scene as a Responder. For example, adding KeypadLinc Timer button B as a Responder equates to the 5 minute button. Define an ISY Program that triggers a Program at the desired On time. The Program issues a Scene On from the Then Clause. The KeypadLinc Timer will turn Off when the time interval associated with the particular button expires. Or the ISY Program can turn the KeypadLinc Timer On with a Direct command, Wait the desired amount of time and turn the KeypadLinc Timer Off.

Using the Dim/Bright buttons to put RemoteLinc into linking mode? Only thought I have is try a new set of batteries.

Suggest posting the Program. Right click Program name, select Copy to Clipboard and paste to forum post. The Program If will be reevaluated only while in a Wait or Repeat. A simple Wait 20 seconds to allow the Status to settle down before doing anything functional should have been enough (without Enable/Disable) unless the InLineLinc cycling On/Off is occurring over a period longer than 20 seconds.

The Replace xxxx with .... changes the old existing node definition (device being replaced) Insteon address to the new device Insteon address. The new device is Deleted as part of the process but the current Admin Console session now has two devices with the same Insteon address. Terminating the current Admin Console session insures the new session will have an accurate picture of the devices and their Insteon addresses.

danncas Thanks for adding the warning. The discussion was directed at the logistics within the ISY regarding handling of a Relay link database, moving to a Dimmer link database. It was not meant to be a discussion of the implications of the load being controlled. To that end I have some ICON Relay devices that control purely incandescent loads. At the time of their install more than 5 years ago I saw no need to dim those circuits. A change in usage for two of the areas makes dimmers a better choice now. It would be convenient to use the Replace function so that I would not have to rebuild the Scenes that will be affected by having to Delete the Relay and add a Dimmer. Not a major effort on my part and it is a one time effort. However, the Replace with .... function would make that change easier if it allowed replacing a Relay with a Dimmer. Of course the restrictions you mentioned about not using a Dimmer for a non-dimming load apply.

Michel We may be describing different situations. The OP End Of List has the remains of a previous link record as is the case below. Maybe I am remembering the 00.....00 equals 00.......00 case and the situation below never had an ignore.

Apologies. The "ignore" annotation has been removed. Checked on my 3.3.10 and 4.0.2, it is not there anymore.

The RemoteLinc nodes reflect the last command received from the respective button. If On is the last button press that is what will be shown. Likely the same with the X10 motion sensor but I have no X10 motion sensors

bbrally As Xathros has already indicated that mismatch can be ignored. The first byte of that link record is 00 which indicates End Of List. None of the 7 bytes after the 00 mean anything. You have the required E2 01 ........ link record and should now be seeing status updates without generating dummy scenes with these SwitchLincs as Controllers You are running an older level of ISY. That End of List link record carries an "ignore" annotation on later levels of ISY. I suggest moving to 3.3.10 Official release at least. There were some issues with the ISY and link records in much earlier ISY images. That may explain how the Controller E2 01 link record was lost. Had to do with file management on the SD card.