LeeG

There is a forum topic dedicated to variables viewforum.php?f=68

This Program uses a KeypadLinc button Status, On or Off, to set different Cool Set Points. If Status 'KPL Floor Dimmer 6 / KPL Floor Dimmer 6 - C' is On Then Set 'T2491T1E - Main' 78° (Cool Setpoint) Else Set 'T2491T1E - Main' 82° (Cool Setpoint)

The current Set Point value cannot be accessed and used later in another command. Nor can the current On Level of say a LampLinc or other Dimmer be accessed and used later. Perhaps when variables are enhanced in the future but not now.

The LampLinc is not going back to the condition before being turned On. If the LampLinc was set at 50% On before the Scene On turned it On full, the Scene Off turns the LampLinc Off. It does not return it to the previous 50% On. Insteon does not have a command that directs a device to return to a previous state. Changing a Set Point is an action with no Off equivalent. The thermostat does not have a command that says go back to where you were before the last command changed the Set Point. To establish a new Set Point a different Scene is needed or a Program can be run that defines a new Set Point.

Define an ISY Scene. Add both devices as Controllers of the ISY Scene. The ISY will cross-link them just as you did manually with the Set button. The difference is the ISY is now aware of the links that it wrote. Also the ISY Scene name can be used to turn both devices On/Off. When you press a device button/paddle a Scene is being controlled. Individual Insteon devices cannot send Direct commands when a paddle/button is pressed. Only an HA application can send Direct commands. That is why you are seeing a difference when using the Admin Console or MobiLinc without a Scene definition. Direct commands are being used. There are times when an individual device should be controlled regardless of what other devices are linked to it. This is done with Direct commands. Again, I believe when the Scene is defined and the MobiLinc is sync’ed the device button will cause the Scene to be turned On/Off as the MobiLinc is aware the device is a Controller of the Scene.

Click on the Scene name. What is listed for the Set Point in the right pane?

I think if MobiLinc finds the device is a Controller of a Scene MobiLinc will turn the Scene On/Off rather than issue Direct commands to the device.

That is bad. Devices should never be linked outside of the ISY. The ISY is not aware of those links and will eventually overwrite or delete them. Define an ISY Scene, adding both switches as Controllers. This will result in ISY cross-linking the devices. Then use the ISY Scene to turn both devices On/Off together.

Controlling a device with an Insteon Direct command affects that device only. Insteon does not propagate a Direct command to other devices. To control multiple devices together turn the ISY Scene On/Off that was used to link the two device together.

I believe both SwitchLinc and KeypadLinc factory reset to full brightness. There have been cases where devices arrive with information residual from the test process. We have seen devices have X10 addresses, link records, etc. Do not remember a post about LED bright level being at some lower level but anything is possible. It is always a good idea to factory reset new devices. I also prefer to put new wired devices on an appliance cord to test before installing in a wall. I’ve not gotten a DOA but I have seen devices with various information that a factory reset clears.

There is no list of hardware/firmware versus features. I wish SmartLabs would publish this information but they do not. As much of an impact I2CS devices are they have not published anything about what devices are I2CS and when the other devices will be. If the last trace is from a v.36 KPL, right click on KPL Primary node, select Diagnostics | Query Insteon Engine. After that I believe ISY will use the later extended commands to set the LED bright level. The trace will look like the following rather than the Peek/Poke sequence now being used. Sun 08/05/2012 11:52:08 AM : [All ] Writing 1 bytes to devices Sun 08/05/2012 11:52:08 AM : [15 9A F9 1 ] Memory : Write dbAddr=0x0264 [7F] cmd1=0x2E cmd2=0x00 Sun 08/05/2012 11:52:08 AM : [iNST-TX-I2 ] 02 62 15 9A F9 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B Sun 08/05/2012 11:52:08 AM : [iNST-ACK ] 02 62 15.9A.F9 1F 2E 00 01 07 7F 00 00 00 00 00 00 00 00 00 00 4B 06 (00) Sun 08/05/2012 11:52:08 AM : [iNST-SRX ] 02 50 15.9A.F9 19.70.06 2B 2E 00 (00) Sun 08/05/2012 11:52:08 AM : [standard-Direct Ack][15.9A.F9-->ISY/PLM Group=0] Max Hops=3, Hops Left=2 Sun 08/05/2012 11:54:36 AM : [iNST-SRX ] 02 50 1D.6C.D6 19.70.06 01 6F 26 (26) Sun 08/05/2012 11:54:36 AM : [standard-Direct][1D.6C.D6-->ISY/PLM Group=0] Max Hops=1, Hops Left=0 The device firmware is displayed on the second line of the Admin Console detail device information in the right pane. There is no reason to think memory was not changed by a Peek/Poke sequence. The hardware memory is very solid. The only exception, which is not a hardware problem, some commands have been removed from I2CS devices. The event trace may look like they worked but the firmware did not do anything with the commands. This is generally only a problem for an ISY running down level firmware (below 3.2.6) trying to add a new device that contains I2CS firmware. I2CS is an enhanced version of Insteon messages which have features for added data validation and security.

Thanks for the trace. I found a v.2C KPL here. The LED levels do not change. That KPL cannot have the LED Bright level changed programmatically. EDIT: in fact my v.2C cannot be manually cycled through various LED bright levels. I found an old KeypadLinc User Guide which describes the LED bright level adjustment as toggling between two bright levels only. The LED variable brightness came in a later hardware/firmware version.

One solution is to split the Program into two Programs. The first Program has the current If statements with the Then clause invoking the second Program. The second Program has nothing in the If section and the Then clause contains the logic from the existing Program. That way when the If conditions change before the 2 minute mark, the second Program is not affected. That also solves the problem of a motion violation within 2 minutes of the To time. When the To time occurs the If is reevaluated to False which can also prevent the statement after the Wait from executing. Splitting into two Programs prevents this from happening.

The I/O Linc is an I2CS device which requires 3.2.6. That is, 3.2.6 must have been running when the I/O Linc was added to the ISY. If on 3.2.6 suggest running a Restore Device to rebuild the link database in the I/O Linc. Sensor State changes should be seen immediately by the ISY. If not either links records are missing or there is a comm problem with the I/O Linc location.

I've used an ICON Relay on my dock for more than 5 years. It is in a weather resistant box with a hinged cover to access the switch. The foam seal on the hinged door has worked well. Probably exceeds operating range at times (NC) but I've had not trouble.

NNilsen Would you please repeat setting the LED Brightness levels but with a different set of numbers. The ISY does not write values if they have not changed from what they were previously. Again, with Tools | Diagnostics | Event Trace with Level 3. Posting the trace as before is fine. Note that this KeypadLinc has poor communication with the ISY PLM. The message coming from the KeypadLinc shows Max Hops 3 with Hops Left 0. That is as the outer edge of reliability. Scene problems from a device with Hops Left 0 when Max Hops 3 would not be unusual. Sat 08/04/2012 10:13:22 AM : [standard-Direct Ack][0A.E4.17-->ISY/PLM Group=0] Max Hops=3, Hops Left=0

Yes, the 7 is Off LED bright level, 15 is On LED bright level. The KeypadLinc firmware requires a differential of 8 so the LED On and Off levels are visually detectable. I'll have to do some research for a KeypadLinc with v.2C firmware. That is very old as firmware goes, v.40 is the latest. Not sure that level of firmware supports changing the LED bright level programmatically. Are you able to change the backlight level with the KeypadLinc buttons themselves?

The first statement in each clause sets the Responder On Level to 20% for when the "Main" SwitchLinc is turned on by "2nd SW". The second statement sets the Local On Level for when the "Main" SwitchLinc paddle is physically pressed. To the SwitchLinc these are different things, reacting as a Responder to another Controller versus reacting to a physical paddle press. It is not uncommon for different buttons on a KeypadLinc to turn On the Responder to different On Levels. In that case more Program statements would be necessary to time adjust the Responder level for each Controller button along with the Local On Level. Insteon is pretty flexible in this area but with that flexibility comes the complexity of setting multiple values.

"I'm wondering if I should try to up the amperage on the fuses a bit. " Under no circumstances! Potential fire hazard as well as invalidating fire insurance if they find the oversize fuses.

Run Help | About, verify that both the Firmware line and UI line show 3.2.6. As Michel suggested opening a Ticket with UDI support is appropriate as the 3.2.6 code does not normally operate as you are experiencing.

To turn both lights On or Off together use the Scene that has both SwitchLincs as Controllers. To change the Scene Responder On Level for the devices in the Scene each device has to be changed individually as your posted example does. The change of On Level information is written into each Responder device link database. There is no means of changing all the Responder On Levels with a single Action statement.

Set the Motion Sensor options as follows: Sensing Mode - checked On Only Mode - unchecked Night Mode - checked Add the Motion Sensor - Sensor node to the Scene as Controller This combination uses the Motion Sensor to turn the Scene On directly with no delay waiting for the Off Timeout value to elapse and no delay in invoking a Program. The Motion Sensor never sends an Off command so it is necessary to use a Program to send the Scene Off. Trigger a Program with If Control 'xxxx- Sensor' is switched On This Program will contain a Wait for as long as the Scene should stay On followed by a Set Scene Off. The Responder Ramp Rate can be set to whatever speed is desired.

What ISY firmware level are you running?

That is odd as those numbers (without minus) work on my 3.2.6.

You are very welcome. You may want to consider turning the KeypadLinc button Off from the second Program after performing whatever it is with the 3 button press. The same Scene the first Program used to turn the button Off if 5 seconds exceeded can be used in the second Program.