LeeG

The PLM does not have to be Dual Band. The TriggerLinc does have to be within RF range of a Dual Band device. The TriggerLinc is normally asleep to save battery life so it is necessary to put it into linking mode by pressing the Set button for 3-5 seconds. The LED will blink continuous. Then use New INSTEON Device, selecting the Device Type as a TriggerLinc. If that does not work move the TriggerLinc closer to one of the Dual Band devices. Also note that the TriggerLinc is likely an I2CS device which requires 3.2.6. The Motion Sensor has I2CS firmware for months so It is very likely the TriggerLinc does also. EDIT: just relalized 3.2.6 was noted in the initial post. Run Help | About and verify the UI line indicates 3.2.6.

You can have the lamp program Disable this Program such that it cannot be triggered until the time range of the first Program has passed. This Program can be broken into two Programs, separating the From/To in one Program and the If Status in another Program that is marked Disabled. That way the Program with the If Status never triggers itself. It can only execute when invoked at the From and To times in the first Program. Maybe the reverse of that. Put the If Status in the first Program and have the Then and Else clauses invoke different Programs that have a From/To time frame. That way Program two only runs when in the time range and the door is open. Program three only runs when in the time range and the door is closed. Again, the thinking about Programs has to shift from Programs "running" to Programs being driven by events, time based events or device Status based events, even Variable value based events. I'll provide examples that demonstrate an approach but I don't like to provide a complex solution. You learn nothing from that and the effort to maintain a complex solution goes on forever, Sorry. There are likely others who are willing to provide you with working Programs for anything you want to do but that does not help you learn ISY Programming.

An "If Status" triggers the Program any time the Status changes. When the door closes the Status changes to Off triggering the Program. The If is False (Sensor is not On) so the Else clause runs. To clarify something in your last post, the Program is NOT "running" from 10:10 to 1:10. The Program is triggered at the From time, at the To time, and when the Sensor Status changes. Once the Program is triggered the If is evaluated for True or False. When the If is True the Then clause executes, when False the Else clause executes. This is not like a PC Program where the exe is invoked at 10:10 and continues to execute until 1:10. ISY Programs are event driven, triggered by the conditions in the If, driving either the Then or Else when triggered. There is no running ISY Program in the conventional sense.

There does not appear to be any conflicts. What Scene contains the bedroom light? Try running a Scene Test against that Scene to see how reliable communications is with the devices in the Scene. Have Tools | Diagnostics | Event Viewer with Level 3 running when running the Scene Tests and post the event log.

You can have as many lines in each section, If/Then/Else as is needed to so accomplish the tasks. Suggest posting the Program as there may be something changing the Status the If is checking which could prevent all the Then statements from executing when there is a Wait.

Simply add the TriggerLinc to the ISY. Write a Program If section that triggers with an On Status of the TriggerLinc Opened node. Impossible to say if TriggerLinc will be received by an AP on the other end of the house. That will have to be determined by testing.

Sounds like the device was not responding to commands and that aborted some of the other command activity associated with removing/deleting the KeypadLinc. Perhaps not much use now but the correct way to handle that situation is to physically install the new KeypadLinc and add it to the ISY under some device name that does not matter as it will be deleted. Then right click on the old KeypadLinc Primary node and select Replace xxxx with ... which replaces all Insteon address references to the old KeypadLinc with the new replacement KeypadLinc address. The ISY assumes the old KeypadLinc is no longer available so makes no attempt to communicate with it. You can try adding the old KeypadLinc back but that may be a problem if the ISY cannot talk to it at all. It can be connected to an Appliance Cord and plugged in if it has been physically removed from the wall. The other solution is to restore a backup before the old KeypadLinc was removed/deleted. Then follow the steps above for replacing a device. Final thought. Are you sure the link records you are looking at in the other devices are “active� When the ISY deletes a link record it changes the flag byte to inactive leaving the rest of the link record alone. You will see the old device address but the link record itself is not active. An inactive link record will not have an A2 or E2 In the first byte.

My 2441TH (different device obviously) is an I2CS device which requires 3.2.6. With so many device types now being shipped with I2CS firmware, moving to the latest Official 3.2.6 release seems prudent. The other side of the coin is there are issues with the current 2441TH support at 3.2.6 so something after that will likely be required for the 2441ZTH

C Martin If it responds to Scenes some of the time but not others that indicates a communications problem with the device. Try running a Scene Test a few times and see what the results are.

Yes, per Michel post. See Michel post in this topic viewtopic.php?f=27&t=8114&hilit=zigbee+upgrade

Bmiller Folders and Programs are separate from Scenes and Devices. The names entered below the folder are Program names which happen to be the same as device names but have nothing to do with those devices. The reasons for using a Scene are one, the Program that turns the devices On/Off does not have to keep changing every time a new device is added to the system that should also participate in the automatic turn On/Off programming. Second, as more individual devices are added to the time Program the longer it takes to get all the devices On/Off as each device has to be sent a command. Using a Scene allows a single Scene On/Off command to control all the devices in the Scene at once. Use Link Management | New Scene to define an ISY Scene. Drag the devices to the Scene name that should react to the timed Program. The devices should be added to the Scene as Responders. Then set up a Program something like If Status 'KPL Floor Dimmer 6 / KPL Floor Dimmer 6 - A' is On And From Sunset To 10:30:00PM (same day) Then Set Scene 'SceneTestLD3' On Else Wait 10 minutes (Random) Set Scene 'SceneTestLD3' Off This Program works only when the KeypadLinc button A is On. A Folder can be created with the If KeypadLinc button On as the If condition and the Program placed in the Folder without the KeypadLinc button check. It is probably better to do this with a Folder and Program under the Folder to prevent the Else from running when not expected. Otherwise the Program logic has to be split into two Programs.

KeypadLinc v.40 firmware supports turning Secondary buttons Off with a Scene On from another Controller. Previous KeypadLinc firmware does not support this feature. The KeypadLinc firmware cannot be updated. For KeypadLincs below v.40 the Secondary buttons controlled from another Controller have to be managed with ISY Programs and Scenes specifically set up for that purpose.

It is not necessary to create a Scene with the KeypadLinc button as Controller to trigger a Program with the KeypadLinc button press. If a Scene is created with the KeypadLinc button as Controller any other devices in that Scene will respond immediately when the KeypadLinc button is pressed. Define one ISY Scene containing the devices as Responders to be controlled by the Program. Switch the Program to use Set Scene 'xxxx' On/Off rather than a collection of individual devices. As new devices are added to the ISY which should be controlled by the time Program simply add the devcies to the Scene as additional Responders. No need to update the Program once it has been changed to using Set Scene.

That is a hardware design question that would have to be addressed with SmartLabs. An application (ISY in this case) cannot override the safety feature built into the OutletLinc Dimmer. The key is designed to prevent accidently plugging in a non-dimmable load into the OutletLinc Dimmer. I believe it is against the electrical code to have a dimmer driving an outlet because of the danger inherent in plugging in a vacuum cleaner, etc into a dimmable circuit. Two alternatives come to mind. Use an OutletLinc Relay which does not require a special Key. Since there is no load involved use an ISY variable to act as a Home/Away indicator. Yes, that is the Query result you are seeing. The OutletLinc Dimmer cannot be physically turned On without the Key in place. Anytime the device is queried it returns its actual state which will always be Off without the Key.

A flashing LED normally indicates the OutletLinc Dimmer Key is not in place. Issuing a Query to an OutletLinc Dimmer without the Key in place does return a status of Off as the OutletLinc Dimmer should not be On without the Key in place. Do you actually have a load plugged into the OutletLinc?

Thanks Brian for the power supply reminder. I keep forgetting to add that information when discussing the 2413.

bmiller Your idea is correct to change the To time to 10:20 with a Random Wait of 20 minutes. There is no facility that defines a Time where the Random activity happens before the defined time.

someguy The 2411T has no network capability. How are you thinking about interfacing to the 2411T? The only information on the Insteon interface to the 2411T is the Developer area of SmartLabs web site. This is considered confidential and proprietary information. A Developer Subscription is required to access this information.

There is only one Serial PLM being offered by Smarthome, the 2413S Dual Band PLM.

bmiller Add the Wait with the Random option as the first line in the Else clause, before the command to turn the light(s) Off. There will be a Random Wait time before the Action statement to turn the lights Off. Else Wait 10 minutes (Random) Set 'LampLinc DB' Off

You are very welcome. A pleasure working with you. Note that if it is ever necessary to do a Restore Device with the ISY the Configuration Register will have to be set again with the SHN Utility as the ISY will not preserve the Set Timers to Seconds setting. Also the EZIOxx Outputs work like the I/O Linc Relay. When an Output is turned Off with the Timers the EZIOxx does not report that change back to the ISY. The Output will show On even though the Output was turned Off with the Timer.

That is a really great job. The only thing missing is setting the actual timer values. In addition to setting the Configuration Register to Set Timers In Seconds the Output Timers have to be set using the SHN Utility Suite as well. There will be no change in anything the ISY displays. The ISY has no function for setting (or displaying) the Output Timer values.

Sorry, I could have been more specific. The Simplehomenet Utility Suite.

The ISY does not have function to set the EZIOxx options such as the output timer values. There is a free Utility download from Simplehomenet which can set those options. It requires a PLM for powerline communication. Or as you suggested, turn On the Output, Wait 1 second, turn Off the Output.

Good luck. Let us know if you find a better dedicated Insteon automation controller both technically and one that has as good product support as the UDI team provides. I did lots of research before getting my first ISY (I now have three) and found it the best of breed.