LeeG

The 2441ZTH is a room thermostat. The operating temp range is 39-104 degrees. Need something else to read temps in the range being discussed.

I went back and read this topic from the beginning even though it went back to 2012. The 2413 PLM has not changed, it supports 992 links as it did in 2012. Nothing has changed regarding Scenes and link records. Insteon works today as it did in 2012. What required a link in 2012 continues to need a link today. If the PLM links (992) have been consumed and cannot be reduced two ISYs running separate parts of the house could be an option. It is not a canned solution. Network communication between the ISYs would likely be needed unless the house can be separated where neither ISY would need to know about the other. Not a plug-an-play solution.

A Scene uses link records. Scenes are the only thing that use link records. Keep in mind that Scenes are used between a device and the PLM for the ISY to be aware of device operation so Scenes are not limited to those created by the user. A 2413 PLM supports 992 link records. First suggestion is to run a Restore Modem (PLM) which will compress out no longer used and duplicate links. Then run a Show PLM Links Table a few times to see how many link records are actually being used. Forty SwitchLincs would use 80 link records initially so that many new devices may not have raised the link count significantly. KeypadLincs use one link per button so 40 new 8 button KeypadLincs would bump the link count by 320.

Sure. I would recommend using a separate PLM. The ISY PLM could be restored just like any device added to HouseLinc but I prefer not to use any more ISY devices than necessary.

That type of diagnostic does not exist in the ISY. HouseLinc is now free. I have factory reset a device (necessary as HouseLinc would run the device links and pickup unwanted devices), added it to HouseLinc and run diagnostics against the specific device. Not as useful as running against the entire network but it does show results of repeated comm to a device. When done factory reset the device and run Restore Device under the ISY to restore the ISY information.

The ISY is aware that KPL 5 button B has been pressed, the command the KPL generated as a result of the button press, and the ISY knows what devices should react to the button press because the ISY created the Scene. However, Insteon does not tell the PLM (which is a Responder device to the button press) how the other Responders to that KPL button actually reacted. The KPL as the Controller of the Scene is informed of each Responder reaction. That is how the KPL knows to blink the button LED if an error occurred. That success/failure information is passed to the KPL as Controller of the Scene but not passed to any of the individual Responders such as the PLM. There is an insteondetails.pdf document on insteon.com web site that covers how Insteon Controller and Responder devices respond to Insteon Scene processing. There is Insteon detail in that document that is really not necessary to understand in day to day Insteon but there is Scene operation that may be useful.

The problem with the posted example is the Status of the motion sensor changed to Off before the Wait 5 minutes completes. The Wait is terminated and the Else clause runs so the Set to 50% is not executed. Change the If Status to If Control IF : From Sunset + 1 minute and 1 second To Sunrise + 1 second (next day) And Control 'Front PIR-Sensor' is switched On Then IF : From Sunset + 1 minute and 1 second To Sunrise + 1 second (next day) And Status 'Front PIR-Sensor' is On Then : Set 'Front Door' 100% Wait 5 minute and 10 seconds Set 'Front Door' 50%

Any time. I did not include Fast On which is physically possible if a button is tapped twice quickly. Did not seem likely in the described circumstance.

In non-toggle mode the Off command is not sent. The RemoteLinc2 alternates between Fade Up and Fade Down when a button is pressed and held.

Less typing. Sorry if that raised a question. There is a difference in what can be sent to a Dimmer from a Program. A Set 'xxxxx' Dim is different from Set 'xxxx' Fade Down / Set 'xxxx' Fade Stop. However, Dim/Bright commands are not sent by the RemoteLinc2. To be accurate I should have said On/Fade Up/Fade Down rather than On/Dim/Bright.

Can be done with a series of Programs to handle simple press or longer Fade Up or Fade Down. Each press On/Dim/Bright will toggle the controlled device On then Off regardless of how long the button is held. Put the RemoteLinc2 into 8 Scene non-toggle mode. Fewer button possibilities. RL2ButtonAOn If ( Control '1C.2A.4A - B / 1C.2A.4A - A' is switched On Or Control '1C.2A.4A - B / 1C.2A.4A - A' is switched Fade Up Or Control '1C.2A.4A - B / 1C.2A.4A - A' is switched Fade Down ) And Status 'SwitchLinc Relay' is Off Then Set 'SwitchLinc Relay' On Else - No Actions - (To add one, press 'Action') RL2ButtonAOff If ( Control '1C.2A.4A - B / 1C.2A.4A - A' is switched On Or Control '1C.2A.4A - B / 1C.2A.4A - A' is switched Fade Up Or Control '1C.2A.4A - B / 1C.2A.4A - A' is switched Fade Down ) And Status 'SwitchLinc Relay' is On Then Set 'SwitchLinc Relay' Off Else - No Actions - (To add one, press 'Action') Need 14 more Programs, two for each button, for buttons B-H

A Scene command issued by the Program (PLM is Controller) does not receive any confirmation messages regarding success/failure. A Scene initiated by a KPL button press does not indicate result to the PLM as it is only a Responder to the Scene. The ISY has nothing to react to as far as a retry/corrective action. Also that action would have to be initiated by the KPL. The user is notified of the issue by the flashing button. Insteon expects the user to decide what should be done such as pressing the KPL button again.

In addition to larryllix suggestion try doing a File | Restore Modem (PLM) command which will rebuild the PLM link database. The function is relatively quick and should have no adverse affects if that is not the problem.

For the garage implementation where the I/O Linc Sensor is used with Trigger Reverse, the I/O Linc Sensor will change state at 3AM Query because the I/O Linc Query does not honor Trigger Reverse. The I/O Linc Query returns the True state of the I/O Linc Sensor rather than the Trigger Reverse value. What happens as a result of the Sensor changing state at 3 AM depends on how your Programs are coded. The best solution is to change the magnetic switch to the version that is open when the garage door is closed so Trigger Reverse is not needed.

The limitations are based on the design of the lock set. There have been no changes and none are expected.

There is a Program "Synchronize Clock" but not sure if the T1700 supports the command. Set '2441TH - Main' Synchronize Clock

A Program that references a Deleted device will say something like 'not recognized' or something like that.. May need to restart the Admin Console to see that. Actually do not know for sure what the Program will say when the device is added back under the same name.

The devices have to be Deleted and added back under 4.2.8. The link records are created only when the device is added to the ISY.

The 99i is both discontinued and past End of Life. The 3.3.10 Admin Console should be on the 99i. Try http://your local 99i IP address/admin Example http://192.168.1.3/admin

piconut Because the ISY at 4.0.5 does not know the type of device the link records necessary for the ISY to be aware of the manual button press were not created. As Brian has posted move to 4.2.8 RC3 to pick up support for the 2635-222.

What ISY firmware level is being used? Does the device type indicate 2635-222?

Yes, thank you. UDI has just released 4.2.8 RC3. Suggest installing that image. Be sure to clear the java cache and erase the applications. Use one of the URLs in the 4.2.8 announcement to initially load the Admin Console.

What does Help | About show for UI?

The Dusk/Dawn node sends an On/Off state. The condition must exist for 3.5 minutes before the Dusk/Dawn node turns On/Off so that passing traffic for example does not affect the node state. It is accurate for the function it provides.

Yes it will, assuming the motion sensor sees the motion.