LeeG

Does look like some glitch with Sunday. Only other thing I can suggest is to check all individaul days. Anybody see something I have missed?

Go to Help | About, check that there is a Firmware line and a UI line and both indicate 3.1.17.

Can you post a screen capture of the right pane showing the Program and its options. Does the Last Run Time show the Program was trigger but ran the Else clause (False) or was not triggered today?

You can use If Control Dusk/Dawn On rather than If Status Dusk/Dawn On which will stop the cycling. Only when the lamp is turned Off and after a 3.5 minute delay for the motion sensor to adjust to a different ambient light level will the next motion On turn the lamp on again. Or you can use the Dusk/Dawn node of another motion sensor that is not affected by the lamp turning On. You cannot access the Dusk/Dawn level in a Program.

It is confusing for sure. What is not obvious looking at the externals is the fact that when button A Controller is selected and button B & C sliders are moved to 0%, the Scene Responder On Level for those buttons is NOT being set. That is, the first of three bytes of data (On Level) in a Responder link record is NOT being changed. Internal KeypadLinc configuration information (much like Button Grouping) is being altered. Also why it only works for a physical button press on the KeypadLinc itself. The ISY tries to mask much of the complexities of Insteon which it is doing in the case. If you want to see the difference run the Event Viewer and watch what memory is changed when the button B & C sliders are moved to 0%. You will see that the link database memory is not even addressed let alone changed. When the ISY Scene is turned On using the Admin Console or Set Scene xxxx On, conventional link records between the Controller (ISY PLM) and the Responder device (KeypadLinc) are used. It is this area where KeypadLinc firmware has not supported turning a Secondary KeypadLinc button Off with a Scene On. All KeypadLincs starting from 2005/2006 have this limitation (see next). However, SmartLabs has changed the KeypadLinc firmware on the latest devices. The v.40 firmware in the latest Dual Band KeypadLinc Relay now supports turning a Secondary button Off with a Scene On command. It is possible the latest firmware in the KeypadLinc Dimmer has the same change but I have not yet confirmed that. The ISY will have to pick up support for this feature before the ISY UI can define this.

The other button LEDs turn Off because of the Mutually Exclusive definition you indicated has been established. Mutually exclusive definition works only where the button is physically pressed. A Scene On cannot turn a Secondary button LED Off. The KeypadLinc firmware does not support that (except maybe the very latest Dual Band KeypadLinc which the IYS does not have support for yet). Add buttons B and C as responders to Scene. Trigger a Program with a button A On press and Set Scene xxxx Off for the Scene with buttons B & C as responders.

A Scene On cannot turn Off Secondary KeypadLinc buttons. The Secondary buttons to turn Off must be Responders to a Scene and issue a Scene Off.

No.

You have not resolved the comm problems. Writing link records requires many commands all of which must work. What is the config file name it says cannot open? I don't think that has anything to do with adding the device to a Scene.

sectechie Put a Wait 2 seconds before issuing the first X10 command in both the Then and Else clause. I'm assuming the Mobilnc app is using the ISY (and therefore the ISY PLM) to issue the individual X10 commands. Does the Program Summary tab show the Program Last Run Time matching when the KeypadLinc On button is pressed? Also that it shows True if pressed during the Sunset/Sunrise window. Lee

The Water Cop is known for its lack of digital signal quality. Did we not go through this when you were using PH? The link database looks good. Below the post text window and posting options there is section for files.

UDI strongly recommends against the use of "Button Grouping" (alias Radio buttons, mutually exclusive buttons). Click on the KeypadLinc primary node. There is a Button Grouping button along the bottom of the right pane. The KeypadLinc User Guide explains the function.

Define a ISY Scene with the KeypadLinc buttons that should be turned Off. This may require more than one ISY Scene depending on how many buttons have overlapping devices. Trigger an ISY Program on a KeypadLinc button press and issue a Set Scene xxxx Off to turn the other button LEDs Off. If Control 'KPL Floor Dimmer 6 button / KPL Floor Dimmer 6 button-A' is switched On Then Set Scene 'SceneButtonB' Off Else - No Actions - (To add one, press 'Action')

That is the Access Point. Most folks who start using Insteon for one application move on to addition Insteon installation where you will need coupling for sure. You made the right decision. Starting out with an ISY is a substantial investment. The cost of an Access Point is noise by comparison. Measuring across circuit breakers on opposite 120V legs produces 240V. That is what constitutes a 240V circuit, two breakers on opposite 120V legs. Unless you have been handling electrical wiring and know what you are doing, NEVER take the power panel cover off, let alone go probing for various voltage readings (no disrespect intended hoopty). There is stuff in there that can easily be fatal. Welcome to the world of ISY. You will enjoy.

Not sure of the question. Are you asking how to determine if the Access Point and the Dual Band PLM are on the same or opposite 120V legs? If that is the question the Quick Start and User Guides for both the PLM and the Access Point describe the procedure for determining RF reception and correct coupling. The LED on both devices will indicate based on blinking and color. If that was not the question please expand.

The 2413S Dual Band PLM will provide half the coupling. A second Dual Band device such as an Access Point provides the other. There is some evidence the Access Point has slightly better range than some of the wired Dual Band devices. Plus it can be moved around to different outlets until one is found that is on the opposite 120V leg to the PLM and within RF range. The ISY itself has no RF or powerline communication capability. It uses the PLM for that.

Sounds like you have no Insteon installed presently. Along with what you have identified you will need at least one Access Point or other Dual Band device to couple the two 120V legs. The Smarthome web site covers the need to couple the 120V legs. A KeypadLinc is often used to indicate door status and control door movement for folks who do not want to have a computer running 24/7. Is not mandatory, all can be done from the computer but can be useful.

They are the only devices I am aware of that have All On/Aff buttons. Easy enough to generate an All On or All Off with some custom software and a PLM. Would not work for the same reason, the I/O Linc would not have a responder link for the Controller (PLM).

Only if the Controller you plugged into the outside outlet is linked to the I/O Linc Relay. All On/All Off uses a special Scene (Group) number but the responder (I/O Linc Relay) must have a responder link record for the Controller sending the All On/All Off.

I updated the example. Either before or after will work, I prefer before.

The network devices can be on a UPS. I keep my PC and DSL modem on a UPS without interruption from power outage so long as the DSL switch down the road does not lose power as well. This part works well. The problem with the PLM is I don't think the ISY knows it went down. Being on a Serial port connection nothing is aware of the other end going down. I support the SHN Utility which can communicate with a PLM over a Serial port connection. If I unplug the PLM the Utility is not aware the PLM is no longer available.

An ISY Program can be triggered with with button G On And button G not Off. The Then clause runs when the KeypadLinc button is pressed On and the Else clause runs when the KeypadLinc button is pressed Off. The Then clause turns the X10 devices On, the Else clause turns the X10 devices Off. If From Sunset To Sunrise (next day) And Control 'KeypadLinc 8 Button / KeypadLinc 8 Button - G' is switched On And Control 'KeypadLinc 8 Button / KeypadLinc 8 Button - G' is not switched Off Then Send X10 'I4/On (3)' Send X10 'I5/On (3)' Else Send X10 'I4/Off (11)' Send X10 'I5/Off (11)'

Can you post another Show Device Links Table for the EZIO2X4. For an Input to signal a state change three things have to exist. The Input must have the configuration data set which is Group 9 for Input 1 with the ISY. That same Group 9 must have an E2 09 "plm address" link record in the EZIO2X4 and the PLM must have an A2 09 "EZIO2X4 address" link record. Sounds like one of those pieces of information is missing if Input 2 will signal a state change and Input 1 will not. Since how the link database was corrupted is an unknown it might be best to delete the EZIO2X4 from the ISY and add it back. This should establish all three pieces of data for each input. If you decide to do this I would Factory Reset the EZIO2X4 after the Delete and before adding it back. Be sure to specify the EZIO2X4 Device Type. Auto Discover does not work with SHN devices. Was this EZIO2X4 updated by SHN? EDIT: another thing that can be tried is to swap the connections to Input 1 and Input 2. This will eliminate any possibility of the Input source being associated.

Yes, there are many Progress bars during a Restore Modem (PLM). Does the Current State column show any state information? If this column is completely blank the Admin Console has to be restarted. If the task that pushes data from the ISY to the Admin Console has some problem any Admin Console function involving Insteon traffic will not look like it is running.

Great news. The KeypadLinc where the button is physically pressed proceeds to communication with each of the responders to be sure they saw the button press. Likely the KeypadLinc was still trying to communicate with the other responders at the same time the Program issued the Set Scene xxxx Off. The Wait allows the KeypadLinc where the button is pressed to finish with its responders before the Set Scene Off command is issued.