LeeG

jkraus There was something similar posted and I think it was the result of defining it as a RemoteLinc rather than a RemoteLinc2. Can't find the post right now. What does the Admin Console display as the device type? Lee

Sounds like the download was not successful. The ZIP file is 4,640 KB on my system. Try another download.

The Motion Sensor must be set for Sense (Occupancy) Mode to get Motion On messages before the Timeout expires. The number of Motion On commands can be reduced by turning Off Sense (Occupancy) Mode and setting the Timeout value to some number of minutes. This may defeat the purpose for which you installed the Motion Sensor. For light control that works well. For security that may not be what you want. There is no built in configuration option to indicate email requests should be ignored for a given amount of time or Motion On messages that were configured to come quickly should be ignored. Was the Save button clicked after changing the variable name? I am not able to recreate the variable name changing back unless I forget to use Save. Running 3.1.9.

Define an Integer variable initialized to 0. To the If statement that is triggering on Motion On add an ANDed check of the Integer variable equal to 0. The existing Program will send an email only when motion is sensed and the Integer variable is 0. Define a new Program with a null If, a Then that sets the Integer variable to 1 followed by a Wait of 15/30 minutes followed by setting the Integer variable to 0. So long as the Integer variable is not 0 the Program sending the email will not be triggered. Change the existing Wait in the email Program to a Run Then of the new Program. When motion is detected an email will be sent. A second Program is run that will set the variable to a value that prevents further email for the specified time. If not on a V3 image where variables are available a Program True/False state can be used as a binary switch rather than an Integer variable.

Regarding setting the Responder On Level to 0% so that an On command turns a device to an On Level of 0% which effectively turns it Off, It does not work on Secondary KeypadLinc buttons. Some day they may update the KeypadLinc firmware to support that characteristic but for now an Off command is needed to turn a KeypadLinc Secondary button LED Off. Regarding the slider not staying at the new location there have some reports of Java slider not reacting as expected. A work around that seems to work is to move the slider to a mid point in the range. Assuming Java notifies the Admin Console of the slider change an update will be written to the device as evidenced by a progress bar. On 3.1.9 the Admin Console displays a popup message for a KeypadLinc Secondary button because it knows a Secondary KeypadLinc button cannot be dimmed. When the update is complete move the slider to 0% keeping the cursor within the bounds of the slider. Again there should be a progress bar indicating the Admin Console was notified of the slider change and reacted to it. Also, again a Secondary KeypadLinc button can be set to a 0% On Level but the KeypadLinc will still turn the KeypadLinc button LED On with an On command even though the Responder On Level is set to 0%.. Mutually Exclusive button definitions are established with the Button Grouping option button. The problem with that approach is the definition only applies to buttons pressed on that KeypadLinc. KeypadLinc buttons that are reacting as Responders in a Scene do not honor the Mutually Exclusive definition. If used the buttons on the KeypadLinc where the button is physically pressed will not match the button LEDs on linked KeypadLincs. Just another of the oddities of the KeypadLinc. An ISY Program must be used to establish the visual aspects of Mutually Exclusive buttons on Responder KeypadLincs. Note: having two Controllers in the Scene does not automatically establish a Mutually Exclusive (Button Grouping) relationship.

Describe the Scene definition. It sounds like Secondary buttons A and B have been assigned as Controllers of the same Scene. This means that when button A is pressed it blinks and stays On because it is in non-toggle On mode and Secondary button B turns On because the command from the A button is On. When button B is pressed it blinks and stays Off because it is in non-toggle Off mode and turns Secondary button A off because the command from button B if Off. With multiple KeypadLincs involved it will be necessary to manage the Secondary button LEDs with an ISY Program and a Scene that has both Secondary B buttons as Responders of the Scene. The Program is triggered by a Secondary button A press from either KeypadLinc which turns the Scene Off to turn Off button B LEDs Off. KeypadLinc Secondary button LEDs do not the flexibility other devices have where a Scene On can turn a device Off. Also Secondary KeypadLinc buttons cannot be controlled with Direct commands. Thus the need for the buttons to be Responders of a Scene. Could have two Scenes, one for A buttons and one for B buttons such that the buttons are not cross-linked. Are you sure it is really than important to have both the ON/OFF buttons and the A/B buttons control the loads?

Main-A is the upper left button of an 8 button KeypadLinc. It is the dedicated button that controls the local load. Secondary buttons of an 8 button KeypadLinc are labeled B-H. Main-A has had various labels over time. Looks like Main On/Off is the label on my latest 8 button KeypadLincs. It is the primary KeypadLinc node in the My Lighting tree. ON/OFF buttons of a 6 button KeypadLinc are the functional equivalent to Main On/Off of an 8 button KeypadLinc. Secondary buttons of a 6 button KeypadLinc are labeled A-D. Both the ON and OFF buttons are represented by the single primary KeypadLinc node in the My Lighting tree. Even though OFF is a separate button the Off Status/Control in a Program is received by the primary KeypadLinc node. Sorry for the delay in posting back. Forum is back to its old habits of not letting folks login.

The local load control function cannot be redirected to other buttons. Other buttons can also control the local load but ON/OFF and Main-A cannot be changed to not control the local load.

starmanj What does the Admin Console show for v.xx of the KeypadLinc? What does the prompt popup say when trying to set non-toggle On mode? Lee

matapan I don't think it is possible to reach a true 100% network. It is a 120/240V electrical circuit with relatively low signals superimposed. Lots of equipment generating intermittent interference that is generally well tolerated and/or compensated for. I consider my network very reliable. If something becomes unreliable I find the cause. The last was the flat screen TV that caused some intermittent problems which a FilterLinc resolved. The key is not to let things go. When a situation surfaces find the answer. They rarely go away on their own. A KeypadLinc in the garage stopped working. It went dark from the power interruptions during a hurricane and it lost all its link records. Many of my KeypadLincs are very old and do go dark or lock up from power interruptions. An air gap power cycle clears the problem. The garage KeypadLinc is the only one to lose its link records. Also lost an ICON Relay in the basement which was probably caused by the same hurricane related power problems. I cannot remember the last time I saw a communications error popup but they do happen. I have FilterLincs on the UPS and associated computer equipment, a flat screen TV and two other UPS devices located around the house. A few CFLs, all in the basement that have not caused problems although CFLs are a common source of interference. I have distant runs to a dock and a detached garage both with reliable Insteon communication. Two very old RF SignaLincs that I started with and two Access Points. Just realized a few days ago that one of the Access Points is no longer working for RF. Suspect it was damaged during various power problems during the hurricane but it may have just failed. A 2413 PLM is covering that function until a replacement arrives. Not everyone sees problems with the v35 SwitchLincs but more than enough have to suggest they should be replaced. Those that have replaced them report much improved communication. I have no v35 SwitchLincs. I have no timing information for a Query. Lee

When the New INSTEON Device popup displays enter the Address that was found in the battery compartment xx.xx.xx Enter the Name you want the RemoteLinc known as. The Device Type should already contain RemoteLinc from selecting the Add a RemoteLinc option. Click Ok. The RemoteLinc stays in linking mode (LED blinking) or approx 4 minutes. There should be no delay in entering the Address and Name information and clicking Ok.

The Access Points are not added to the ISY. They have no configuration and no links. The RemoteLinc is not out dated but it might be defective. What is the symptom when using the Dim/Bright buttons to establish linking mode?

Use Link Management | Link a RemoteLinc. When prompted press the Dim/Bright buttons on the RemoteLinc to put it into linking mode so the ISY can communicate with the device. What type Dual Band device(s) are being used for communication with RF devices?

Change the To time from (same day) to "Next Day". The To time is before the From time.

Not as yet. Earlier post from UDI... "RL2 is not yet supported but it's high on our list."

Trigger a Program with the KeypadLinc button press. Wait long enough for all Responders to react to the KeypadLinc button press. Issue a Query for each Responder. After the last Query Invoke another Program with a complex If that checks the current status of each Responder. If the combined status of all the Responders is not correct, turn a Scene Off that has the KeypadLinc button as a Responder. This must be done with a Scene as Secondary KeypadLinc buttons cannot be controlled with Direct commands. EDIT: be sure the Wait is long enough for all Responders to react. This includes the possibility of multiple retries for some of the Responders. Since the presumption is the Group Broadcast does not reach all Responders because of powerline issues the need to retry some of the Group Cleanup Direct messages is possible.

The latest Offical release is 2.8.16. The latest beta is 3.1.9

matapan The answer to 1,2,3 is Yes to all three with a clarification. There is a separate Group Cleanup Direct message sent to each Responder. If a button/paddle has three Responders then 4 messages flow from the Controller. One Group Broadcast and three Group Cleanup Direct messages, one to each Responder. "my understanding is that only a single group message can actually be sent reliably on the network." Two devices initiating a Group sequence that overlap, one device will cancel the other device out. If the powerline is good it does not make any difference. If the powerline is marginal or has transient interference then some Responder devices may not see the initial Group Broadcast and would not see the aborted Group Cleanup Direct. In practice having multiple paddle/buttons pressed at the same time is not common plus the situation has to exist along with some powerline issues. There is nothing at the device level to prevent this. Lee

matapan When a button/paddle is pressed it initiates a Group protocol message sequence. It starts with a Group Broadcast message that goes to every device on the powerline. Most of the time all the Responders of the button/paddle see the Group Broadcast message and react to it. To insure that all Responders react each Responder is sent a dedicated Group Cleanup Direct message. This message must be ACKed by the Responder and is retried by the Controller if an ACK is not received. On a good powerline the Group Cleanup Direct messages are redundant and perform no actual function. When the KeypadLinc button is pressed the above Group message sequence is initiated. When the SwitchLinc paddle is pressed the KeypadLinc sees the Group protocol sequence initiated by the SwitchLinc and aborts the remainder of the KeypadLinc Group Cleanup Direct messages. On a good powerline this has no affect because the Group Cleanup Direct messages that are aborted are redundant. If the powerline is not clean and some of the Responders must see their individual Group Cleanup Direct message to react, those Responders whose Group Cleanup Direct message is aborted do not respond. Insteon architecture has worked this way since Insteon was release in 2005. Every device button/paddle press initiates a Scene regardless of whether an explicit Scene has been defined for that Controller. The ISY PLM is a Responder to every button/paddle so that the ISY is aware of button/paddle press. This is necessary so that Programs can be triggered as well as maintaining device statue for the Admin Console and other applications. Lee

matapan I'm not clear about what is occurring. Toggle a device. Immediately toggle a scene. If "Toggle a device" is pressing a paddle/button the device hardware/firmware is driving a Scene. If "Immediately toggle a scene" is pressing a paddle/button that device hardware/firmware is driving a Scene. If this is the scenario there is no control over what is going to happen. The respective device hardware/firmware is in control. If my description of events is not correct please expand on what is actually happening. Lee

matapan Insteon does not allow multiple Scenes to be running at the same time. When a button/paddle is pressed multiple Insteon messages are issued by the Controller. How many depends on how many Responders are linked to the button/paddle. If another Scene is started before the current Scene is complete it is aborted by Insteon hardware/firmware. Lee

mrxmas Write a second ISY Program that is triggered at a different time or put a Wait in the first Program and turn the ApplianceLinc On after the Wait. I think it depends on how closely the two times are tied together. If the ApplianceLinc should turn On the second time say 30 minutes after the first regardless of the time of the first then one Program with a Wait. If the second On time is absolute, independent of the first On time then a second Program that triggers at the second time makes more sense. Lee EDIT: if the same processing is to be done at the different times the If can specify multiple times ORed together If Time is 8:40:00AM Or Time is 5:45:00PM Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

Yes. The ISY will write to the new device during the device add and again during the Replace.

iowaj The 2876DB is a new cat/subcat (device type) that is listed in the latest V3 Beta. I do not recommend going to a V3 Beta where you are with the ISY. Specify the 2876D3 for the Device Type, as the existing switches are. The 2876DB are relatively new devices. Are they being replaced because they are defective? Lee

iowaj When adding wired devices select the default Auto Discover option. The ISY will query the device to the specific device type. What firmware level are you running? Lee