LeeG

This will give you a starting point. Integer variable PressCount is required. Program TimedPress counts the number of times KeypadLinc button B is pressed with less than 5 seconds between each button press. KeypadLinc button B is set for non-toggle On mode so each press generates an On command. When button B pressed 3 times with less than 5 seconds between each press Program TimedPress3 is invoked. Scene TimedPressTooLong has KeypadLinc button B as a Responder. If more than 5 seconds passes the Integer variable PressCount is reset to 0 so count starts again and button B is turned Off. Program TimedPress If Control 'KeypadLinc 8 Dim V40 / KeypadLinc 8 Dim V40 - B' is switched On And $PressCount < 2 Then $PressCount += 1 Wait 5 seconds $PressCount = 0 Set Scene 'SceneTimedPressTooLong' Off Else $PressCount = 0 Run Program 'TimedPress3' (If) Program TimedPress3 If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then Send X10 'H5/On (3)' Else - No Actions - (To add one, press 'Action')

Try it without the minus sign on Longitude.

A change to the If conditions when in a Wait will allow the If to be reevaluated and the possibility that the Else clause will run rather than executing the statement(s) after the Wait. Simple solution is to split the If and Then clauses into two separate programs. That way Wait will complete because there is nothing in the second Program If section.

The Insteon address should be in upper case to match the way the address appears in the ISY. Not sure what you mean by commands. I use DON DOF etc in upper case http://192.168.2.2/rest/nodes/10334/cmd/DON

Do not use leading zero. What error is occuring? How is the REST command being issued, your program or browser command line http://192.168.2.4/rest/status/F 50 91 1/

Sample with actual device address http://192.168.2.4/rest/nodes/18 F5 40 1/ http://192.168.2.4/rest/status/19 21 DA 1/

The 6 button at v.36 should work. Not sure if the 8 button at v.2D can be adjusted programmatically. Let’s get the 6 button working first. When i asked about the backlight levels I was asking what numbers were being entered. Sorry for the confusion. Right click on the 6 button Primary node, select Diagnostics | Query Insteon Engine. Run Tools | Diagnostics | Event Viewer at Level 3. Change the backlight level with the Admin Console and post the trace. Note what Off level and On level numbers were entered.

Some system information will be helpful What is the KeypadLinc firmware level? What is the ISY firmware level? What backlight values are being set? did not understand the reference to buttons A/D. Individual button backlight level cannot be changed. A change to backlight level applies to all buttons on the KeypadLinc.

The solder spots are not accessible without taking it apart. Once the pieces are separated the thermostat is not functional. Don’t know of any way to verify without actually soldering.

I2CS is an enhanced Insteon message protocol. They added a checksum (CS) to extended messages for additional data validation as well as some new link record requirements. The device firmware containing I2CS has been rolling out in various device types since March.

Yes, I think so. It looks like the T2491T1E is a T1700 PCB with the dongle double sided taped to the base board.

Add the new devices under device names that do not conflict with existing device names. The new device entry will be deleted by the Replace process. Right click on the defective device node and select Replace xxxx with ..... Select the replacement device. The old device Insteon address will not be communicated with so the old device can be removed, physically replaced with the new device. The Replace xxxx with will update all Scene links along with Program references. When complete the old device name will still be there and contain the Insteon address of the new device. The new device name will be deleted.

Click the Main tab of Admin Console. The device nodes are listed in the left pain. You will see Network My Lighting or maybe ISY device nodes The entry just below Network is the name to use Would someone with a 994 please jump in here and post whether it is My Lighting or something else.

Anything in the 1-2 second range should be fine.

I use 2 seconds but whatever works with your door opener. The door openers with multiple buttons cannot have the two wires shorted for more than about .5 seconds or the clock setting is lost.

If you have a 994 it may say ISY at the top rather than the old My Lighting name. I renamed mine so the 994 would look like my 99i's. Can't remember for sure what the top name was. There is Network, then My Lighting (or maybe ISY). The entry below Network is what you use as the Scene name.

The Momentary hold time change will not display the next time but it should be in effect. The ISY is setting the Momentary hold time correctly, just not pulling the new value back the next time Set Options is invoked. The other I/O Linc options are not being set correctly. This is the result of the I2CS I/O Linc needing some command adjustments. I believe the next ISY release will resolve problems.

No. My Lighting should be at the top of the device node list.

This is the QueryAll Program .... If Time is 3:00:00AM Then Set Scene 'My Lighting' Query Else - No Actions - (To add one, press 'Action')

I am getting Humidity messages from my T2491T1E. There are solder buttons marked for Humidity and No Humidity on the Printed Circuit Board (PCB). Looks like the No Humidity solder buttons need to be jumpered to stop the messages.

I installed a T2491T1E using 3.2.6. I can change the Set Point when in Cool mode and the thermostat display changes to the new value. This thermostat is I2CS which requires 3.2.6. What procedure was used to add the thermostat to the ISY? I will be able to compare the event trace from my system with yours to see if there is any difference. To confirm there is good RF communication with the thermostat, the mode can be changed through the Admin Console?

The new T1700 equivalent (T2491T1E) that Brian discussed may have a jumper on the PCB to disable humidity readings.

I think that is true but I thought the 1700 was still using the external dongle.

See this link. It is old but I think it still applies to the 1700 where no humidity sensor exists. viewtopic.php?f=28&t=3513&start=15

Okay, thanks. Let’s see what the thermostat dongle did with the command. Run Tools | Diagnostics | Event Viewer with Level 3. Issue a Set Point change and post the event trace. Also in the same event trace, right click on thermostat primary node, select Diagnostics | Query Insteon Engine. Perhaps the new dongles have been updated to I2CS. Actuall do this query first, then trace the Set Point command.