LeeG

“There is also no on level that I can find for A-D keypad buttons.†Do not under this question. In the posted image there is an On Level slider for Reagan Keypad D and Living Room C which look like Secondary buttons.

alphamale78 What is being referred to as Scene settings apply when the Scene is turned On/Off with a Program or the Admin Console. When a Scene has multiple Controllers (the PLM is always one Controller), each Controller has a unique set of Responder On Level and Ramp Rate settings. I cannot tell from the posted image as it does not include the left side which would show whether the Scene name is selected (which makes the Controller the PLM) or whether another Controller is selected. Click on a Controller node name (KeypadLinc button) below the Scene name for another set of On Level and Ramp Rate values that apply when the KeypadLinc button is pressed which makes the Controller the KeypadLinc button. Each Controller of the Scene has a separate set of On Level and Ramp Rate values for each Resonder.

alphamale78 With Insteon each Responder has a different set of On Level and Ramp Rate values for each Controller. Turning the Scene On through the ISY the PLM is the controller which is what the 50% On Level was set for. To set a 50% On Level when the KeypadLinc button is pressed, click on the KeypadLinc button node name below the Scene name and set the On Level and Ramp Rate values for when the KeypadLinc button is the Controller.

Sorry, no example. That is half the fun of having an ISY, creating them.

The KeypadLinc button is acting like a KeypadLinc button. Press it and the LED toggles On or Off immediately. That is what a KeypadLinc button does. It has no logic to say since an I/O Linc Sensor is linked to the button and the I/O Linc is connected to a garage door it should do something different. That would be attributing a level of intelligence to the KeypadLinc it does not have. The KeypadLinc button is being used for two purposes. Move the door and reflect door status. It cannot do both the way you want. Putting the KeypadLinc button in non-toggle On mode the button will blink twice and remain On. The I/O Linc Sensor will turn it Off when the door closes. It will still not reflect the fact that the door moved when asked to open as the button will be On from either a toggle On or a non-toggle On. If you want absolute accuracy use two buttons, one to drive door movement and one to reflect door open/close status. As an alternative a few ISY Programs could be written to sense when the KeypadLinc button is pressed On and check the I/O Linc Sensor Status a few seconds later to confirm the door actually moved . It the I/O Linc Sensor did not turn On the Program would turn the KeypadLinc button Off which would indicate the door did not open. Same thing with the KeypadLinc Off press. Check the I/O Linc Sensor 10 seconds later to make sure the Sensor turned Off. If not turn the KeypadLinc button On to indicate the door did not close.

I have a 2442TH working on 3.3.3. I deleted and added it under 3.3.3 to be sure add is working. Suggest deleting definition. Factory reset the thermostat and be sure it is Off. Use New INSTEON Device with Auto Discover. The Admin Console display is showing Mode and Set Point changes made at the thermostat. Check Help | About to be sure both Firmware and UI show 3.3.3 before adding 2441TH. Note: it takes a second or two before the thermostat sends the change. That way if the Set Point is being moved through a range only the final Set Point is sent to the ISY.

JMC The UI (Admin Console) is 3.2.6. The UI should always be at the same level as the Firmware. Clear the Java cache and be sure the correct URL is being used. It is not good to be running a back level Admin Console.

The sequence is to remove all power from ISY and PLM. Connect new PLM. The 2413 requires an external power supply for the ISY. Power up PLM and ISY. Issue File | Restore Modem (PLM). This could/will take a far amount of time as every link record with a reference to the PLM has to have the Insteon address changed to match the new PLM.

SmartLabs/Smarthome did not publish that information. I researched the chip characteristics.

The 3.3.3 beta which is scheduled for later today will have that device type.

Yes, the SwitchLinc can be powered that way. I connect all my wired devices that way for testing before installing. Most any hardware or home improvement store sell appliance cords. They have a plug on one end and bare wires on the other. Makes it easy to wire nut the Neutral and Line connections. Using an appliance cord is also an easy way to change plug/power points if the device is having communications problems.

Using the Admin Console click the Motion Sensor - Sensor node. In the right pane click Set Options. The popup instructions will direct the Motion Sensor be put into linking mode by pressing the Motion Sensor Set button until the Red LED blinks continuously. When the Set Options popup displays check Sensing Mode: and probably Night Only: check boxes if the motion sensor should work at all times.

Occupancy Mode or Sensing Mode as it is labeled on the ISY Set Options causes the Motion Sensor to send a Motion On message every time motion is sensed. If not in Occupancy Mode the Motion Sensor waits until the timeout interval has expired before sending the next Motion On message.

Twice a day for 10 years would be 7300 updates against a projected 1,000,000 update service life.

Normally Motion Sensor options are set through the ISY using Jumper 5 which enables programmatic setting of options. If Jumper 5 is in place the other jumpers have no affect (except for the sensitivity jumper). Click the Set Options button to display and change the motion sensor options if Jumper 5 is in place. Need to be on 3.3.2 if a relatively new Motion Sensor. If not using Jumper 5 it is necessary to power cycle (remove the battery) for other jumper changes to take effect. IMPORTANT - in On Only mode no Off commands are issued by the Motion Sensor so the Sensor will show On after the first motion is sensed. Each motion sensed refreshes the motion timeout interval unless using Occupancy (Sensing) mode. EDIT: in case it was not clear the On Only mode has no affect on establishing a new timeout interval when motion is sensed.

Xathros The signature information at the bottom of all the posts shows the wrong ISY level (3.2.6).

That approach eliminates the programming challenges. It also introduces a delay in the lights turning On.

Requirement Motion Sensor Motion On message sets a SwitchLinc Dimmer to 60%. An individual manually changes the 60% On Level to 80% On Level by pressing and holding the On paddle. The next Motion On should leave the SwitchLinc at 80% On Level rather than lowering the On Level to 60%. Implementation Concept is simple, use an Adjust Scene to change the Motion On message Responder On Level in the SwitchLinc to 80%. Changing the Responder On Level with an Adjust Scene Action Statement is commonly done. It is often done at specific times of day so that Motion On turns the Responder On to different On Levels based on time of day for example. Brighter during the day, dimmer when it is dark. Less shock to the eyes. I do that with mine and others have as well. Implementation is difficult in this case because the ISY currently has no means of dynamically changing the Adjust Scene Responder On Level value.

oberkc The OP is not looking to change the Motion Sensor, he is looking to change the Responder On Level of the SwitchLinc Dimmer (when MS is Controller) to match the device current level. Sixburg It is a very messy implementation. The current On Level value cannot be stored anywhere the actual value can be used in the Adjust Scene statement. If you need the absolute On Level then approx 99 Programs are needed. Each Program tests for a specific On Level value Program 1 If Status xxxx is 100% Adjust Scene Responder On Level to 100% Program 2 If Status xxxx is 99% Adjust Scene Responder On Level to 99% and so on. The number of Programs can be reduced if a range of On Levels can resolve to a single Responder On Level Program 3 If Status 'SwitchLinc Dimmer' <= On And Status 'SwitchLinc Dimmer' >= 90% Then Adjust Scene Responder On Level to 90% Using 10% increments takes it to 10 Programs Using 5% increments takes it to 20 Programs Some day when device Status can be assigned to a Variable and that Variable used in other Program Action statements it will be easy. Until then it is messy.

Thanks, the All Devices Scene should not be driven when the Secondary KeypadLinc button is toggled On/Off. I understand that the ON button LEDs being On will mean either all the devices are On or only the KeypadLinc load will be On but that is what the user asked for. The Secondary button LED will differentiate whether ON indicates All devices (Secondary button LED Off) or only KeypadLinc load On (Secondary button LED On).

What is the firmware level of the KeypadLinc? The outside lights, are they connected to the Red Load wire of the KeypadLinc? Assuming they are, define an ISY Scene with all the other Insteon devices as Responders and the KeypadLinc Primary button as Controller. When ON button is press they will all turn On. When the OFF button is pressed they will all turn Off. Define another ISY Scene with the KeypadLinc Primary button as a Responder and whatever KeypadLinc Secondary button to toggle the KeypadLinc outside lights On/Off as a Controller. Pressing the Secondary KeypadLinc button should toggle the KeypadLinc load On/Off. This part may require 3.3.3 which will be released soon.

I think using the new switch is a good idea. They also carry a NO magnetic switch but it is not a wide gap switch like the one you ordered. The 3AM Program is called QueryAll. It could invoke a new Scene that has whatever devices you actually want to Query at 3AM. However, it defeats the purpose to Query only selected devices.

The I/O Linc option is fixed in 3.3.2. Trigger Reverse will reverse the commands issued by the I/O Linc Sensor. When the Sensor turns On it will send an Off command and vice versa. The problem is the 3AM Query returns the true state of the I/O Linc Sensor, not the reversed commands generated by Trigger Reverse. This means the I/O Linc Sensor will change to On Status at 3AM assuming the garage door is closed.

Was a Restore Modem (PLM) issued after installing the new PLM and after rebooting the ISY to pick up the new PLM address?

My Pendigital picture frame has a slide On/Off switch.