LeeG

I suggest running Tools | Diagnostics | Event Viewer at LEVEL 3. Delete the Mini Remote, add it back and post the event trace showing both the delete and add. It still sounds like the PLM does not have the responder link records needed for it to receive messages from the Mini Remote.

I deleted and added back a Mini Remote under 4.0.5 on my 994i successfully so it is not a systemic problem with either. Is there anything common about the 994i's?

That is exactly right. Programs that can execute concurrently should not be updating the same resource. It would require an Enqueue/Dequeue function to serialize access to the resource which does not exist in the ISY.

It does not execute Program 1 to completion before executing Program 2 if that answers the question. Multiple Programs are logically executing at the same time although not physically simultaneously. The processor can execute only one physical instruction at a time.

The initial post describes different symptoms with different origins. The 9 minute Ramp Rate is a zero value because the ISY cannot (or could not with Avast active) push the configuration data to the Admin Console. 3.3.1 firmware is still very old. The 99i should be updated to 3.3.10 which is an official release and the last update that can be installed on a 99i. Why was the ISY Restore done after updating the ISY image to 3.3.1? Did that backup image have the new LampLinc definition? Was anything else restored when the ISY Restore was done? Try running a Scene Test for the Scene that has the LampLinc in the Scene? What are the results of the Scene Test?

It sounds like there is an issue with the fireware/AV blocking the push of data changes from the ISY to the Admin Console. Is Kaspersky or Avast being used?

"does this sensor re-transmit a detected solid wet condition more than once" The Wet node sends an On command once (assuming a SOLID Wet condition). The Heartbeat message every 24 hours also carries the current state of the Leak Sensor. Unless very unlucky and the power loss is a few minutes after the last state change, it is likely less than 24 hours but it is true that the next opportunity for a Wet indication is the Heartbeat message. Being a battery powered device the Leak Sensor cannot be queried when power is restored.

widnerm It will dependent on the device firmware and what the ISY supports. Check Help | About and verify that the UI line shows 4.0.5. If not clear the Java cache and make sure the URL used to invoke the Admin Console is correct for 4.0.5.

It can be added to either ISY. The Insteon address is printed on a label located on the Printed Circuit Board (PCB) inside the Open/Close Sensor. Open the case as would be done to replace the battery.

The Variable should be a State variable if it needs to trigger a Program when the value changes

A RemoteLinc2 (Mini Remote) has no actual Status. As a battery RF device it sleeps so nothing can be queried. The ISY simply uses the last command sent as Status which is lost over a reboot. The solution is to use a Variable to keep track of True/False status. By setting the Variable Init value along with the Variable value itself the Variable is insured of remaining at a given value even across a reboot. If Control Switch ... is switched On Or Control Switch ... is not switched Off Then $IAway Init To 1 $IAway = 1 else $IAway Init To 0 $IAway = 0

The rev 7.0 is the hardware level of the KPL. The 1.65 is the decimal cat/subcat (device type) of the new KPL. The KPL firmware would be something like v.42 I agree completely with the suggestion to move to a 994i. There are many changes in the 4.0.x images which will only increase with time.

Support for the 2334-222 and 2334-232 was added at 4.0.1 Have you tried selecting the equivalent non Dual Band KPL in the Device Type list.

"Should this screen know that the Away program happening in a few days will then trigger the other away programs and should I be seeing all of them in the summary?" No. The ISY does not analyze what the Folder condition might be some days in the future and then predict that other Programs may run because of the various If conditions in the Programs. Keep in mind that a Folder turning True does not cause programs in the Folder to trigger. The Folder condition changing to True only allows the Program If conditions to be evaluated when an event the Program is checking occurs.

There is no way to physically prevent the KPL button from turning On and Off if pressed which might cause problems depending on what is triggering the Programs in the Folders. An ISY Program can count the number of KPL button presses within a time period and set a Variable if pressed x times within y seconds. There should be examples of this in the forum as the technique has been discussed before. Then use the Variable value as condition in the Folders. That way the Folder condition is not cycling from True to False to True as the KPL button is pressed. The Program can insure the KPL button is set Off if the x times in y seconds is not satisfied.

From the KeypadLinc User Guide Beep on Button Tap or Press Buttons can be set to Beep Mode so KeypadLinc will beep every time a button is used. (Default = Off) If KeypadLinc in 6-Button Configuration Simultaneously tap the B and C buttons KeypadLinc will beep Keypad’s Beeper will toggle to on (if was off) or off (if it was on) If KeypadLinc in 8-Button Configuration Simultaneously tap the D and E buttons KeypadLinc will beep Keypad’s Beeper will toggle to on (if was off) or off (if it was on)

Click Help | Purchase Modules for a list of modules. There is an Add to cart in the right column for each module.

"The large Insteon label has Model 2442-222 under the large "INSTEON" label." Sorry, I have no idea what you have as the 2442-222 is the Micro Dimmer Module

The 2412N is the discontinued SmartLinc which was not Dual Band. The 2242-222 is the Hub. Which device are you discussing?

The Hold button applies to Programs within the thermostat itself. The ISY has no support for defining/managing programs in the thermostat itself.

If Control 'Motion Sensor I2CS -Low Ba' is switched On Then Notify ...... Else - No Actions - (To add one, press 'Action')

I did not find a REST command to move the SetPoint +/- 1. CLImate ST is STatus. – not a mistake – all the Insteon device primary state is stored in Status. Guess temp is considered the thermostat primary state. My 2441TH does not have a Holding mode/state. What does Holding do?

Refer to the WSDK category in the forum. It has links to all the current developer documentation which includes all the REST options. The answers to all the questions are covered in the REST section. Node Command: CLISPH, CLISPC It appears that you must set 2x the desired temperature. I assume this is to allow for a setting +/- 0.5 degrees The thermostat interface is spec’ed to exchange temp in .5 degree increments. CLIFS What is the paramater? Numeric (0= off, 1=on; or string "On" or "Off") 7=On 8=Auto – there is no Off as that could damage the heating system CLIMD Same question, what are the legal mode setting parameters (Cool, Heat, Off, On as strings or numeric values, and i numeric what value for what mode. Refer to the documents in the WSDK for the various values. Too many to repeat from memory CLIHUM I assume this will be a returned parameter being Humidity (0-100) with UOM being % Yes CLIHCS Is this the reply for Mode? What are the possible values? String or Numeric? Indicates if the HVAC is Off, Cooling, Heating (versus the mode) CLIEMD"> This seems to be obvious ( 0 = Off, 1 = On) Not familiar with this one Will a get command bring back the desired value e.g. http://192.168.2.2/rest/nodes/1D 6C D6 1/get/CLISPC Yes

Example of setting Cool Set Point of 80 http://192.168.2.2/rest/nodes/1D 6C D6 1/set/CLISPC/160 http://192.168.2.2/rest/nodes/11 22 33 1/set/CLISPC/160 Example of setting Mode Heat http://192.168.2.2/rest/nodes/1D 6C D6 1/set/CLIMD/1 http://192.168.2.2/rest/nodes/11 22 33 1/set/CLIMD/1

If the previous ideas do not resolve suggest doing a Restore Modem (PLM). It sounds like the link records needed for the PLM to receive messages from the mini remote were not created. This can happen when the PLM link database becomes full. Often there are duplicate and out dated link records that can be compressed out with the Restore Modem (PLM).