LeeG

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Press the ON button to turn the FanLinc Light. Press and HOLD the OFF button for a few seconds which would normally reduce the FanLinc Light Level. Press and HOLD the ON button for a few seconds which would normally increase the FanLinc Light level. Post the event trace so we can see the commands issued when the ON button is pressed and held for a few seconds and the same with the OFF button. The commands issued by a KPL Relay and a KPL Dimmer controlling a responder should be exactly the same. Of course the load control circuitry would work differently but the Red wire is capped. Not sure what is happening here since the commands would be that same.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Turn the I/O Linc Relay On 3-4 times allowing time for the door to cycle open and closed. Post the event trace. That will provide a general sense of the communication between the PLM and the I/O Linc by looking at the Hops Left=x count. Run Tools | Diagnostics | Show PLM Links Table. When the display completes click Count to produce a count of the link records in the PLM. This sequence, Show PLM Links Table followed by Count should be done 3-4 times. If any Insteon traffic reaches the PLM during the Show PLM Links Table processing the link record display will not accurate and the subsequent Count will not be correct. Only when the same number of link records is obtained from a series of Show/Count sequences can the Count be considered accurate. If the PLM is still full the Count will be 992. The I/O Linc can be moved to the PLM plug point and two pieces of wire connected to GND and Sensor. Touch the wires together to turn the Sensor On (Green LED at wire connections will be On when the Sensor is On). There is no danger of electrical shock as these wires carry very low voltage (less than 5 volt DC). Connect and disconnect the wires which should turn the Sensor On and Off. (Green LED will turn On and Off). Does this change in Sensor state register at the Admin Console. Once the I/O Linc was factory reset a Restore Device must be done to rebuild the link database.

In Insteon each Controller of the Scene has a unique set of Responder values. When using the Scene name itself works (where the PLM is the Controller) and pressing a KPL button does not yield the desired result the KPL button as a Controller has not had its Responder values set. Click on the Red KPL button node name listed below the Scene name. A set of Responder values will be displayed that apply when the KPL button is pressed. Set those values as needed. I assume the Red load wire of the KPL has been capped and the FanLinc Light node is being controlled because ON/OFF buttons have been defined as a Controller of the FanLinc Light node. If this is the definition the ON/OFF buttons should have control over the FanLinc Light node functions of Dim and Bright.

From the Keypadlinc User Guide To set KeypadLinc’s Local-On-Level: 1. Press & hold On and/or Off (or Main in 8-button configuration) until the connected light is at the brightness desired when turned on locally (turn the light off if you wish to use the “Resume Bright†feature) 2. Tap KeypadLinc’s Set button KeypadLinc will (Beep) 3. Test the Local On-Level settings by tapping the On/Off or Main

The links necessary for the I/O Linc Sensor are created when the I/O Linc is initially added to the ISY. However, it does sound like a link record problem. Right click on the Sensor node, select Diagnostics | Show Device Links Table. When the display completes click the Compare button which causes the ISY to compare the links read against what the ISY thinks should be there. It is possible for the PLM link database to become full of duplicate and out dated link records. If the Show Device Links Table/Compare does not indicate a problem issue a Restore Modem (PLM) which will compress out duplicate and out dated links in the PLM. It sounds like the PLM has become full and did not accept the Responder link record necessary to receive Sensor state change messages. It could be a communication problem between the I/O Linc and the PLM but since the Query works and the I/O Linc Relay responds it is more likely the PLM is full.

Sounds like the backup is corrupted. 4.0.5 is capable of reading a 3.3.10 ISY backup file. Take another backup of the 99i 3.3.10 and try the new file. Do not unzip the backup file. .

What is being upgraded? The 99i is at 3.3.10. The new 994i would have 4.0.5. Neither ISY should be receiving new firmware. That message is seen when the image ZIP file was unzipped during the download.

Check the KeypadLinc User Guide "Local On-Level". It discusses the "Resume Bright" mode where the KPL returns to the last On Level after being turned Off. The "Resume Bright" feature can be disabled by tapping the Set button after setting to some On Level.

Volume does not help in determining how much water is being applied to a given area. Applying 50 gallons to a 10'x10' has a very different result than applying 50 gallons to a 100'x100'. Flow is very important in determining the requirement of a given Zone does not exceed the water supply capacity but not how much an area of grass is receiving in terms of inches per hour. Tuna can, water bucket (not so good because sides are generally tapered), something with vertical walls, it does not matter. If the container/collector covers 2 sq inches or 10 sq inches does not matter. It is the inches of water applied to whatever space the collector represents. I think the larger the area covered by the collector the better. I don't remember exactly what I used 10 years ago when I installed my irrigation system but it was much larger than a tuna can. Finding something large with vertical walls was the challenge. It was also useful to do that measurement in different areas within the same Zone. It verifies that head to head coverage is producing the needed results.

Duplicate post. See other.

The Wiki indicates Water Applied per Irrigation Cycle is specified in inches (of water applied). Go to this link and see display of Irrigation Settings http://wiki.universal-devices.com/index ... ion_Module Water Applied per Irrigation Cycle - amount of water the user's irrigation program applies to the soil during each run.

jtara92101 Apologies, that is what happens when I comment on something I should not have.

Using http://192.168.2.2/ brings up the Dashboard on my system. Ultimately resolves to http://192.168.2.2/WEB/INDEX.HTM

There is no doubt in my mind this is a communications problem or the issue with v.41 firmware. There are not 4 defective KPLs. If the event trace can be provided it will show if it is related to extended command execution only or a more general communications problem on the circuit(s) where the four KPLs are located..

pgovotsos Run Tools | Diagnostics | Event Viewer at LEVEL 3. Perform the Auto Detect that does not work and post the event trace.

Under the forum Category “Current Releases, Betas and Bug Report†viewforum.php?f=25 go the Release post for the Release/Beta of interest. The one for 3.3.10 is below. That topic has a link to the 3.3.10 downloads. There are actually three downloads at 3.3.10 which apply to the various 99i/994i hardware combinations available at the time. viewtopic.php?f=25&t=10602 Finger Check is a typing error. Looking where you were looking rather than a specific post I think they represent the three possible 3.3.10 downloads. I suggested making the PLM available so the front LEDs would not be indicating the lack of a PLM along with whatever else was going on. Simpler to evaluate when looking at one symptom at a time.

The 3.3.10 backup is installed on the 994 at 4.0.5. Do not down grade 994. There is only one official 3.3.10. Sounds like finger checks. Can you post a link to where these are mentioned. What was the solution to not obtaining an IP address through DHCP?

The ISY User Guide indicates the Mem and Err LEDs blinking indicate the ISY was not able to communicate with the Router and/or was not able to obtain an IP address from the Router DHCP services. Some things to check at the router would be that DHCP is enabled and the IP addresses allocated for DHCP assignment do not conflict with the static IP addresses that have been assigned to other devices on the network.

Hi Guys The key, as Xathros has noted, is the To time arrival triggers the 2nd Program independent of the Status of the 'nightlight'. The If must evaluate to False independent of the Status of the 'nightlight' because it is now past the To time value. Assuming the only thing in an If is a From/To time range, the From time trigger is always True, the To time trigger is always False. The 2nd Program has a null Else so the only thing functional that happens is the cancel of an active Wait (if the Program was in a Wait) which prevents the 2nd Program from turning the Scene On after the To time.

If the objective is have the Program turn the KPL button On/Off every time the Program turns the ApplianceLinc On/Off the Program should be turning the Scene On/Off that has the KPL button as Controller and ApplianceLinc as Responder. There is no need for the Scene I suggested that has the KPL button as a Responder IF the Program should be controlling both the KPL button and ApplianceLinc at the same time.

You should explain how the ApplianceLinc is turned On to begin with. The ApplianceLinc is a Responder Only device. Turning it On/Off locally does NOT result in that Status change being reported back to the ISY because the ApplianceLinc is a Responder Only device. It has no capability of reporting Status/State changes that occur locally.

If an ISY Scene has been defined with KPL button C as Controller and the ApplianceLinc as a Responder. Turning the KPL button LED On/Off with a Scene that has the KPL button C as a Responder does not affect the ApplianceLinc even though button C may be a Controller of the ApplianceLinc. Insteon does not chain or cascade Scenes. If the Program should be turning On the button LED and turning On the ApplianceLinc at the same time, turn the ISY Scene On that has the KPL button as Controller and ApplianceLinc as Responder. The KPL button acts as both a Controller and Responder. .

Variables cannot be set that way. It is expected that variables can be set to current device Status with some future ISY release. The ISY Log will have the thermostat temp changes as the thermostat reports them, assuming the thermostat is sending temp change messages. There have been issues with some thermostats not reporting temp changes. Examples of thermostat temp messages. The thermostats were reporting in Celsius at the time which is why the Status number are low values. 2441ZTH - Main Humidity 37% Tue 2013/06/18 11:39:12 AM System Log T2491T1E - Main Status 27° Tue 2013/06/18 11:48:07 AM System Log 2441ZTH - Main Humidity 36% Tue 2013/06/18 12:00:18 PM System Log 2441ZTH - Main Humidity 35% Tue 2013/06/18 12:03:14 PM System Log 2441ZTH - Main Humidity 37% Tue 2013/06/18 12:09:02 PM System Log T2491T1E - Main Status 26° Tue 2013/06/18 12:10:44 PM System Log T2491T1E - Main Status 27° Tue 2013/06/18 12:13:58 PM System Log 2441ZTH - Main Humidity 38% Tue 2013/06/18 12:21:32 PM System Log 2441ZTH - Main Humidity 37% Tue 2013/06/18 12:23:29 PM System Log 2441ZTH - Main Humidity 36% Tue 2013/06/18 12:24:29 PM System Log T2491T1E - Main Status 26° Tue 2013/06/18 12:25:51 PM System Log 2441ZTH - Main Status 27° Tue 2013/06/18 12:26:30 PM System Log 2441ZTH - Main Humidity 37% Tue 2013/06/18 12:29:26 PM System Log 2441ZTH - Main Humidity 38% Tue 2013/06/18 12:37:08 PM System Log 2441ZTH - Main Status 27.5° Tue 2013/06/18 12:41:57 PM System Log 2441ZTH - Main Humidity 36% Tue 2013/06/18 12:46:46 PM System Log

No. Secondary KeypadLinc button LEDs cannot be controlled with Direct commands. The Direct On/Off command does not have a field to identify which KPL button should be controlled. Define an ISY Scene with KPL button C as Responder. Turn the ISY Scene Off (or On) to turn button C LED Off/On.

Not independent Programs but Yes the 2nd Program would have to change. Assuming that there are multiple load controlling devices in the Scene and any of the load controlling devices being turned Off should reestablish the entire Scene. If only the 'nightlight' being turned Off should reestablish the Scene then the Program is good as written. If From Sunset To Sunrise (next day) And ( Status ‘nightlight’ is Off Or Status 'device2' is Off Or Status 'device3' is Off ) Then Wait 10 minutes Set Scene 'IL Night Timer' On Else