LeeG

The SwitchLinc has two modes of local operation. In one mode it turns On to the last On level. It sounds like that SwitchLinc is operating in that mode, going to 75%. That is why Fast On going to 100% becomes the last local On level. Check the User Manual for how to change the local mode operation.

Click on My Lighting/ISY to display a list on all nodes with the various information. Click on Address heading to sort by Insteon address. That should help relate Insteon address to node name without taking up space in the node name itself.

I do not include the Scene name in the button node name. That information is available in the Admin Console display of the button. Use a node name that provides the information that is important to you.

The Keypad button cannot send a Fast On followed by an On followed by an Off or Fast Off. It will alternate between a Fast On or On followed by a Fast Off or Off. This is toggle mode operation. It gets more complex if the button LED On/Off state is managed. Non-toggle On sends only On/Fast On. Non-toggle Off sends Off/Fast Off Secondary KPL button LEDs can only be turned On/Off with a Scene. Normally done with an ISY Scene that has the KPL button as a Responder. Need to define how you want to produce the command sequences within the capability of the KPL.

The question from matapan is whether 3.3.10 (ISY-99i) supports the 2441TH.

Will need another report from someone with v.43 to see if a manufacturing error or change that dropped Multi Scene

Sure. The first two lines are generated when the device sends an Off command (DOF is Off command, STatus 0 = Off) The last two lines are generated when the device sends an On command (DON is On command, STatus 255 is On) 1. Fri 04/17/2015 12:15:59 AM : [ 36 FB EF 1] DOF 1 2. Fri 04/17/2015 12:15:59 AM : [ 36 FB EF 1] ST 0 3. Fri 04/17/2015 12:16:01 AM : [ 36 FB EF 1] DON 1 4. Fri 04/17/2015 12:16:01 AM : [ 36 FB EF 1] ST 255 A LEVEL 3 trace shows the actual messages containing the commands. 0x11 is On command Fri 04/17/2015 01:07:20 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 11 01 LTONRR (01) Fri 04/17/2015 01:07:20 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:20 AM : [D2D EVENT ] Event [31 BD 14 1] [DON] [1] uom=0 prec=-1 Fri 04/17/2015 01:07:20 AM : [ 31 BD 14 1] DON 1 Fri 04/17/2015 01:07:20 AM : [D2D EVENT ] Event [31 BD 14 1] [sT] [255] uom=0 prec=-1 Fri 04/17/2015 01:07:20 AM : [ 31 BD 14 1] ST 255 Fri 04/17/2015 01:07:20 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 11 01 LTONRR (01) Fri 04/17/2015 01:07:20 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:20 AM : [iNST-DUP ] Previous message ignored. Fri 04/17/2015 01:07:20 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 11 01 LTONRR (01) Fri 04/17/2015 01:07:20 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:20 AM : [D2D EVENT ] Event [31 BD 14 1] [DON] [1] uom=0 prec=-1 Fri 04/17/2015 01:07:20 AM : [ 31 BD 14 1] DON 1 Fri 04/17/2015 01:07:20 AM : [iNST-SRX ] 02 50 31.BD.14 22.80.0B 41 11 01 LTONRR (01) Fri 04/17/2015 01:07:20 AM : [std-Cleanup ] 31.BD.14-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 04/17/2015 01:07:20 AM : [iNST-DUP ] Previous message ignored. Fri 04/17/2015 01:07:21 AM : [iNST-SRX ] 02 50 31.BD.14 11.01.01 C7 06 00 (00) Fri 04/17/2015 01:07:21 AM : [std-Group ] 31.BD.14-->11.01.01, Max Hops=3, Hops Left=1 Fri 04/17/2015 01:07:21 AM : [iNST-INFO ] Previous message ignored. Fri 04/17/2015 01:07:21 AM : [iNST-SRX ] 02 50 31.BD.14 11.01.01 C7 06 00 (00) Fri 04/17/2015 01:07:21 AM : [std-Group ] 31.BD.14-->11.01.01, Max Hops=3, Hops Left=1 Fri 04/17/2015 01:07:21 AM : [iNST-INFO ] Previous message ignored. 0x13 is Off command Fri 04/17/2015 01:07:28 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 13 01 LTOFFRR(01) Fri 04/17/2015 01:07:28 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:28 AM : [D2D EVENT ] Event [31 BD 14 1] [DOF] [1] uom=0 prec=-1 Fri 04/17/2015 01:07:28 AM : [ 31 BD 14 1] DOF 1 Fri 04/17/2015 01:07:28 AM : [D2D EVENT ] Event [31 BD 14 1] [sT] [0] uom=0 prec=-1 Fri 04/17/2015 01:07:28 AM : [ 31 BD 14 1] ST 0 Fri 04/17/2015 01:07:28 AM : [iNST-SRX ] 02 50 31.BD.14 00.00.01 CB 13 01 LTOFFRR(01) Fri 04/17/2015 01:07:28 AM : [std-Group ] 31.BD.14-->Group=1, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:28 AM : [iNST-DUP ] Previous message ignored. Fri 04/17/2015 01:07:28 AM : [iNST-SRX ] 02 50 31.BD.14 22.80.0B 41 13 01 LTOFFRR(01) Fri 04/17/2015 01:07:28 AM : [std-Cleanup ] 31.BD.14-->ISY/PLM Group=1, Max Hops=1, Hops Left=0 Fri 04/17/2015 01:07:28 AM : [iNST-DUP ] Previous message ignored. Fri 04/17/2015 01:07:28 AM : [iNST-SRX ] 02 50 31.BD.14 13.01.01 CB 06 00 (00) Fri 04/17/2015 01:07:28 AM : [std-Group ] 31.BD.14-->13.01.01, Max Hops=3, Hops Left=2 Fri 04/17/2015 01:07:28 AM : [iNST-INFO ] Previous message ignored.

The Specs and User Manual indicate the pins should be there. What is the Open/Close 2843-222 firmware level? Are the two pins there without the jumper in place? My latest is v.40 firmware and it has the Jumper?

Happy to help.

"If Status 'xxxx' is On" does have a False evaluation when the device is no longer On.

The magnetic switch has to be "open/not shorted" for the Sensor to be Off with door closed. Up to you whether that is considered NC or NO. Devices used for security are named one way, for industry use they are named the opposite. For the NC/NO magnetic switch that would be the Black/Red wires.

Not sure how/where you want to control FanLinc

The "If Control 'xxxx' is switched On" never has a False evaluation. Add a check with not switched Off to have the Off command drive the Else If Control 'Upstairs / Den / Light' is switched On And Control 'Upstairs / Den / Light' is not switched Off Then

Do not use the same name for a Device and Scene. Creates issues with some Program commands such as Adjust Scene. Programs are displayed separately so those names are not in conflict with Devices/Scenes. Try using Group Devices (right click on KPL button) on one of the KPLs to cluster the KPL button names together. That tends to help with KPLs and other devices that have multiple nodes. Integer and State Variables should be IDed with i_xxx and s_yyy to make the variable type self describing. I'm sure others have their own style.

This tests for a Keypad button being On. Add functional statements to then or Else KPLButtonOn - [iD 008A][Parent 0001] If Status 'KPL 8 Dimmer v40 / KPL 8 Dimmer v40 - E' is 100% Then - No Actions - (To add one, press 'Action') Else - No Actions - (To add one, press 'Action')

A Controller in a Scene is also a Responder if the device can function as a Responder. A Motion Sensor - Sensor is an example of a node that can be a Controller only. A SwitchLinc can be a Controller and Responder when defined as a Controller.

There is no time limit. The ISY does a Query at 3AM but that would not help your situation. A Query or perhaps an On command since the bulb is On all the time. That is going to introduce Insteon activity 24 hours a day 7 days a week. If the switch was Insteon turning the switch Off would be detectable with an If Status 'switch' is Off. That would leave the bulb being unscrewed or a bulb failure as an open item to solve. Perhaps something that sensed light that would trigger an I/O Linc if the bulb stopped producing illumination.

I have v.3E and v.43 Leak Sensors, both have the Heartbeat node. No idea what 3.3.10 did with those levels. Must Delete and add the Leak Sensors back to get the Heartbeat node. Note that 4.2.30 is now the latest Official release.

The node is responding to commands. Not related to any specific command.

What does Help | About show for Firmware UI Is the router updated automatically by the Internet provider?

Grizzy After Java was updated were the cached and installed java applications deleted and the Admin Console installed again so it would have the latest Java code?

Updated Java "6 months ago".

Button B is the primary button (Group 1) on an 8 Scene Mini Remote. Same as button A is the primary button on a 8 button Keypad device. For the Mini Remote to be accessed when another unrelated Scene is updated there is something pending against the Mini Remote. Since it is battery powered it has to be put into linking mode to be able to clear the pending activity. Once the pending activity is cleared it should not happen again unless it is not in range of a Dual Band device during the clearing attempt.

Put one Mini Remote into linking mode, right click the B button and select Write Updates to Device. When complete take that Mini Remote out of linking mode before repeating process on the second Mini Remote.

"Well, I tried a couple of different approaches. After a factory reset of the sensor, and removing it from the ISY, I chose link management>>>New Insteon Device. Set to autodiscover, nothing happened." Of course the option is yours but I would like to see an Event Trace at LEVEL 3. Using New INSTEON Device, enter the sensor Insteon address, Name of your choice, and Auto Discover. Of course the sensor must be put into linking mode with Set button before clicking Ok on New Insteon Device. I certainly understand if you are not interested. Doing a factory reset before deleting device would cause errors during the delete because the link records were missing. That might have prevented the delete from completing.