LeeG

"So at best I would say it is 6 degrees out, 7 at worst." On the Smarthome forum a user found several new thermostats arrived with various calibration offsets already established. Once they were cleared the thermostats were accurate. Calibration is described in the thermostat guide. The user on the Smarthome forum reported he did not press one of the Program buttons long enough so it looked like calibration was not working. "Also can I make this thing show me the temp in C?" The thermostat guide describes how to cycle between C and F. I changed my 2441TH and T2491t1E to C to test something another user posted earlier today. "Also, can I program it from my ISY994?" Things like the thermostat mode and set points can be controlled by the ISY. Calibration and F/C mode cannot be set with the ISY.

There are definitely issues with this KeypadLinc starting with the fact that the ON button should never turn the load Off. It sounds the KeypadLinc is in 8 button mode with a 6 button frame installed. However, if it were that simple the ISY should have detected it as an 8 button KPL and defined 8 nodes rather than 5 node. I recommend Deleting the KPL from the ISY. Factory Reset the KPL, they add it back with Device Type set at default Auto Discover. EDIT: the OFF button will not have a unique node. The 1 button reflects the ON and OFF buttons. Press ON turns the load and 1 button On, pressing the OFF button turns the load and 1 button Off.

There is no means to selectively disable the motion Off message. The approach is to put the Motion Sensor into On Only mode so the Motion Sensor never generates Off messages. Then use an ISY Program triggered by Motion On to turn the SwitchLinc Off after the desired amout of time. The following Program Waits for some number of minutes. If additional Motion On messages are received before the Wait completes the Wait is terminated, the Program triggers again and the Wait starts over. If Control 'Motion Sensor - Sensor' is switched On Then Wait x minutes Set 'switchlinc' Off Else A second Program is triggered by the SwitchLinc being manually turned On (no need for special double tap Fast On/Off). The second Program Disables the first Program, preventing the automatic Off. When the SwitchLinc is manually turned Off the second Program Enables the first Program reestablishing the programmatic automatic Off. Also the Then has a 10 minute Wait to reestablish automatic operation if someone forgets to manually turn SwitchLinc Off. If Control 'switchlinc' is switched On Or Control 'switchlinc’ is not switched Off Then Disable Program 1 Wait 10 minutes Enable Program 1 Set 'switchlinc' Off Else Enable Program 1 These are examples to establish ideas for a starting point. Usually when something like this is put into actual there is a 'gee it would be nice if it did this' so things are often tweaked along the way. Also there are other ways to accomplish this.

A 2456S3 is an ApplianceLinc (rather than a LampLinc) and I believe it does require a Load to physically turn On. Easy test, plug something into it and see if Query no longer reports Off after being turned On . The suggestion was to set an ISY Variable to 1 for example to indicate Home and 0 to indicate Away. Any numbers you chose. Then test the value in the Variable rather than the state of the ApplianceLinc to determine Home/Away.

Depends on the device. What type device is being used? For example, an I/O Linc Sensor with the Trigger Reverse option, Query will change the status. The other possibility is the device state change message did not reach the PLM/ISY at the time and Query corrected the actual status. Another possibility is certain devices will not physically react to an On command if a load is not attached. The ISY marked it On as that was the last command which the device ACKed but a Query will return the true state of Off. An OutletLinc Dimmer will not physically turn On if the magnetic key is not in place. All gets back to what type device.

As an FYI, the Program is not using a Scene. The Scene definition, not the Set command, define the temperature setting when using a Scene. A separate Program can be defined to trigger at each of the various times and issue a Set for the desired temperature. I must live in the uncivilized world, no information on Celsius.

It is not normal for a SwitchLinc to go to 100% and then dim down from a single On command from a Controller. I assume the SwitchLinc LEDs go to full On and then dim to 40%. The event trace may show some other activity going on at the same time. If that does not show anything perhaps there is a link record issue in the SwitchLinc, one that directs it to 100% and one that directs it to 40% On.

This was from the Motion Sensor turning the SwitchLinc On and not from pressing the SwitchLinc paddle? What type of load is the SwitchLinc controlling, Incandescent light, CFL, LED, etc? If turned on by the Motion Sensor only what is the SwitchLinc firmware level? It is displayed on the second line in the right pane when the SwitchLinc node is select in the My Lighting/ISY Lighting tree. Run Tools | Diagnostics | Event Viewer at LEVEL 3. Enter the Motion Sensor field of view to have it turn the SwitchLinc On. Confirm the SwitchLinc went to 100%, then down to 40%. Post the event trace.

The Program triggers only at the specified times. If the Adjust Scene Statements were not set before reaching 11:30 PM or 11:30 PM has not yet occurred the link record in the SwitchLinc has not been changed. Run a Show Device Links Table for the SwitchLinc and post the result including the Insteon address of the Motion Sensor. If the image cannot be posted Save the Show results which will be an XML file and post the full XML file The Adjust Scene settings in the Then clause would not get set until 7:00 AM After making changes to the Adjust Scene statements, right click the Program name and select Run Then or Run Else to have the statements executed.

"I really have a simple question: Can the LED indicator on a ToggleLinc Dimmer switch be programed to indicate (only temporarily) the opposite of what the load actual state is?" No. Sorry.

The Adjust Scene is not correct. The first parameter, In Scene, has to be the name of the Controller. It needs to be the name of the Motion Sensor since it is controlling the SwitchLinc. The second parameter, Set is the name of the SwitchLinc. The Adjust Scene above only changes what happens when the Motion Sensor turns the SwitchLinc On. If you also want to affect what happens when pressing the SwitchLinc paddle, an additional Adjust Scene is needed. The In Scene parameter must specify the name of the SwitchLinc, and Set also contains the name of the SwitchLinc. This additional Adjust Scene is not necessary if the SwitchLinc paddle is not used. The second Program turns the Scene Responders Off and the On 20 minutes later. A Scene cannot be Disabled. Do you want the Motion Sensor to no longer turn the SwitchLinc On or no longer turn the SwitchLinc Off or both. What needs to be implemented depends on what the objective is.

Run Tools | Diagnostics | Event Viewer at LEVEL 3. Press a ControLinc button that has an X10 address assigned for controlling X10 devices. I suspect the X10 messages are not reaching the PLM location. The following are what X10 messages should look like when they reach the PLM. If they are not in the trace move the ControLinc closer to the PLM plug point and try the test again. Wed 02/13/2013 03:08:33 PM : [X10-RX ] 02 52 5F 00 Wed 02/13/2013 03:08:33 PM : [ X10] G10 Wed 02/13/2013 03:08:34 PM : [X10-RX ] 02 52 52 80 Wed 02/13/2013 03:08:34 PM : [ X10] G10/On (3) Wed 02/13/2013 03:08:41 PM : [X10-RX ] 02 52 55 00 Wed 02/13/2013 03:08:41 PM : [ X10] G7 Wed 02/13/2013 03:08:42 PM : [X10-RX ] 02 52 53 80 Wed 02/13/2013 03:08:42 PM : [ X10] G7/Off (11)

Try a different command such as Query rather than Beep. I suspect it is the powerline traffic in combination with a dimmer driving LEDs rather than a specific command code or the device actually beeping.

Make sure PLM is connected to the ISY using Port A on the ISY. Make sure the cable between the PLM and the ISY is fully seated and clicked when the cable was inserted into the RJ45 jacks. The PLM needs to have power for at least several seconds before providing power to the ISY.

That is the problem. The RemoteLinc2 being a battery RF device sends multiple messages when a button is pressed. It triggers the Program immediately which sets the light On but the RemoteLinc 2 is not done sending its Scene control commands. The solution is to extend the Wait to perhaps 4 seconds to allow the RemoteLinc2 processing to complete. An Event trace of the sequence should help identify how much time is needed to Wait before turn the light On with the Program.

Yes, I suggest that. Until resolved in some future image the toggle mode will have to be established manually with the KPL itself. Here is a sample event trace. The first command resulted from pressing the All Toggle button. The next set of trace entries is the On button press of the KPL button followed by Ok response to the popup that directed the KPL button be pressed. The KPL configuration is the same command for both the All Toggle and the setting of the non-toggle mode which is wrong. Plus the command is an Extended 2E command issued in Standard mode. This topic can be referenced for source of documentation of problem. Pressing the All Toggle button Tue 02/12/2013 01:04:01 PM : [iNST-TX-I1 ] 02 62 08 49 E7 0F 2E 00 Tue 02/12/2013 01:04:01 PM : [iNST-ACK ] 02 62 08.49.E7 0F 2E 00 06 (00) Tue 02/12/2013 01:04:01 PM : [iNST-SRX ] 02 50 08.49.E7 19.70.06 2B 2E 00 (00) Tue 02/12/2013 01:04:01 PM : [std-Direct Ack] 08.49.E7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2 Clicking Ok after pressing KPL button On Tue 02/12/2013 01:04:24 PM : [iNST-SRX ] 02 50 0B.4A.AD 00.00.06 CB 11 00 LTONRR (00) Tue 02/12/2013 01:04:24 PM : [std-Group ] 0B.4A.AD-->Group=6, Max Hops=3, Hops Left=2 Tue 02/12/2013 01:04:24 PM : [ B 4A AD 6] DON 0 Tue 02/12/2013 01:04:24 PM : [ B 4A AD 6] ST 255 Tue 02/12/2013 01:04:25 PM : [iNST-SRX ] 02 50 0B.4A.AD 19.70.06 41 11 06 LTONRR (06) Tue 02/12/2013 01:04:25 PM : [std-Cleanup ] 0B.4A.AD-->ISY/PLM Group=6, Max Hops=1, Hops Left=0 Tue 02/12/2013 01:04:25 PM : [iNST-DUP ] Previous message ignored. Tue 02/12/2013 01:04:31 PM : [iNST-TX-I1 ] 02 62 08 49 E7 0F 2E 00 Tue 02/12/2013 01:04:31 PM : [iNST-ACK ] 02 62 08.49.E7 0F 2E 00 06 (00) Tue 02/12/2013 01:04:31 PM : [iNST-SRX ] 02 50 08.49.E7 19.70.06 2B 2E 00 (00) Tue 02/12/2013 01:04:31 PM : [std-Direct Ack] 08.49.E7-->ISY/PLM Group=0, Max Hops=3, Hops Left=2

bsobel That activity Repeat 2 times Set Scene 'Housewide Scenes / Nightlights' On Wait 5 seconds only happens at Sunset-30. For it to be having an affect the RemoteLinc2 button would have to be pressed within those few seconds. Of course that may be what the OP is doing but I took it to be a scenario not related to the exact Sunset-30 time. Perhaps the OP can clarify when the RemoteLinc2 button is being pressed relative to Sunset-30

Post the Program that turns the light Off from the RemoteLinc2 button press.

brooknerk Setting non-toggle mode on the old KPL firmware is not working on 3.3.10. The commands being issued for toggle mode management on the v29 are not correct.

>does any of the above heart beat / node testing need to be done with low batt? A Program would be triggered when the Low Batt turns On if something like an email notify was to be done. The heartbeat requires a Program with a Wait of 24-?? hours with an email notify if the Wait completes. Not sure how accurate the heartbeat relative to actual 24 hours which is why perhaps a 36 hour Wait would work better.

It is the KPL firmware level that is driving this. I found a V29 in my inventory and see the same popup sequence. I think the popup message about physically pressing the button is referring to actually pressing the button on the KPL On or Off, not the popup button line, to establish whether the button should be non-toggle On or non-toggle Off. These old KPLs did not have the programmatic capabilities the newer firmware added. Give me some time to test the variations. I think having the KPL button On when setting the non-toggle mode sets it to non-toggle On mode and having the KPL button Off sets it to non-toggle Off mode but that is testing a very old memory (mine and the KPL).

I take it you have the optional ISY X10/A10 module that allows X10 devices to be defined by Name in the My Lighting/ISY Lighting tree. The X10 message generated by the ControLinc will appear as traffic on the power line and be traced by the ISY. Unfortunately I don't use the optional ISY X10 module so don't know if the ISY tracks the status of X10 devices. If it does the MobiLinc should also carry that On/Off status.

Now that the PLM and router are connected try power cycle of ISY. Not sure just plugging in the cables will get things initialized after the ISY would not have been able to communicate with the PLM or the router.

Insteon does not support an X10 address as part of a Scene. An ISY Program can be triggered with the ControLinc button. The Program issues an X10 On or X10 Off based on the ControLinc button pressed. The X10 module is not actually linked to the ControLinc button. An X10 address was assigned to the ControLinc button so any X10 device with that X10 house/unit code will respond to the ControLinc button press. If that is still working as desired just leave it alone.

What is the KPL firmware level? When the popup that lists all the KPL buttons displays, what is done to get the Confirm popup that says Physically click on Hall-KPL_Garage Open. The sequence I follow is to click the KPL button to change, then click Toggle On/Off button. I never see the Confirm popup in the last post. If this is done for a new KPL does the same sequence occur?