LeeG

Look at the ISY Log (not the event trace) to see if it reflects the errant actions of the device at the time they are occurring. The Log should reflect the device turning On or Off is the ISY is aware of the activity.

The first statement in the Then clause changes the value of the variable $Remote_Busy. As soon as the Wait is executed the If is reevaluated because of the change in variable value. The If is now False so the Else is executed. The statement after the Wait is never executed. Split the existing Program into two Programs. The first Program contains the existing If clause, with the Then clause running the second Program. The second Program contains a null If section with the Then statements from the current Program. With this split the reevaluation of the If does not affect the second Program

Web Sat 06/15/2013 01:33:01 PM : [iNST-TX-I1 ] 02 62 00 00 2E CF 11 00 Read one of my previous posts. The second PLM will not have the link records to support Scene (Group) 2E. The devices will not have the required responder link records for this Scene with the second PLM Insteon address. If using any I2CS devices the second PLM will not be authorized to control the I2CS devices. The ISY CANNOT directly control a Secondary KPL button. It has to be done through a Scene. I you study the hex string you are using to directly control a device you will see that it does not have any field for the Group number that is associated with every KPL button A=3, B=4, C=5, D=6. That is why the ISY CANNOT directly control a Secondary KPL button and why you CANNOT control a Secondary KPL button. With all due respect, without the most basic Insteon details knowledge you are really working in the dark. EDIT: 00.00.00.3 IS NOT the KPL Insteon address. 00.00.03 is the Group number of the button that was pressed. Standard KPL stuff. Every KPL has the same number for the same button. It is not unique to the KPL. There is no place to put that number (00.00.03) in an Insteon direct command. Again, which is why the ISY CANNOT directly control a KPL Secondary button and your second PLM CANNOT directly control a Secondary KPL button. I really suggest you get a developers subscription. We can go through ever detail one at a time this way but you have a hard time believing what is absolute fact, a Secondary KPL button CANNOT be controlled directly by the ISY nor the second PLM. There are many much more subtle details that you will have to take on faith.

Either you will have to disconnect the PLM from the ISY to send hex commands through it or use a second PLM. Scenes will be an issue if using a second PLM because Scene (Group) numbers are unique to the ISY PLM. A second PLM will not have the link records to support the ISY Scenes, the devices will not have matching responder links with the second PLM Insteon address and I2CS device will not be authorized to receive control commands from the second PLM. If the ISY PLM is disconnected the device status changes that occur while the ISY PLM is disconnected will be lost so the ISY will be out of sync with some of the devices.

The event viewer will show the hex scene commands

pjjameso Run Tools | Diagnostics | Event Viewer at LEVEL 3. It will show the commands being executed. The secondary KPL buttons are managed with a Scene as Direct commands cannot control secondary KPL buttons as a mentioned before. It sounds like you are not familiar with Insteon protocol. If you are trying to write an application that is interfacing directly with a PLM and devices there is much you need to learn. I suggest obtaining a Developer subscription from SmartLabs. It will give you access to the confidential information that is need to write an application.

There is no mechanism for passing a hex string to the PLM which would be outbound any. Take a look at the REST interface. It will do what you want.

"I cant for the life of me figure out how to address a 6 button KeyLinc pad for 1, A, B, C, D etc. Any thoughts?" Buttons A,B,C,D cannot be controlled with direct commands. How is the ISY involved in this? There is no hex command interface thru the ISY.

The new 994i has a different UUID. You chose the old network settings. Did you set up the router to recognize the new UUID rather than the one associated with the 99i. Since you went back to the 99i I suspect the answer is no. The correct answer was not to use the old network settings. Once up on the 994i then the network setting can be adjusted to what new definitions have been established in the router for the new UUID.

You are using a program to turn the 2487S Off after a certain amount of time? That will not result in the Secondary button(s) turning Off. Insteon does not propagate a command sent to the 2487S to turn Off to then turn the load control button into a Controller and have it turn its Scene Off. Insteon has never worked that way as it could lead to circular references. When you turn the 2487S OFF after time has elapsed the Secondary button has to be turned Off as well. The simplest way is to have a Scene with the 2487S ON/OFF and the Secondary buttons as Responders. The Program turns the new Scene Off rather than just turning Off the load. This will turn the load Off as well as turn any Secondary buttons Off.

A Secondary KeypadLinc button can be turned On or Off only with a Scene that has the Secondary KeypadLinc button as a Responder. An Insteon Direct command will not affect a Secondary button as Direct commands do not have a placeholder for button number. How are you trying to turn Off each Secondary KeypadLinc button at present?

jcedot2 Do the 4 tap Set button test on both Access Points. Do both Access Points pass the test?

I have not played with sensitivity for a few years but from what I remember it was a noticeable reduction inside in a controlled environment. Be sure to follow the user guide instructions about tapping Set button and waiting 10 seconds. As I remember just putting jumper 1 in place did not change the sensitivity.

Sensitivity cannot be adjusted programmatically. I believe the sensitivity jumper is independent of Jumper 5. In other words the sensitivity should be reduced when Jumper 1 is installed regardless of whether Jumper 5 is in place or not. Be sure to follow the instructions regarding Set button tap and 10 second Wait before generating motion detection. I have found it better to adjust the field of view of the motion sensor rather than reducing the sensitivity. Provide some feedback on reducing sensitivity.

You have identified the problem. SmartLabs/Smarthome does not provide information regarding features versus device hardware/firmware level. If a device Beeps it has the feature. If it does not Beep do not include it in the Scene. I know that is pretty crude but I don't know of any document that has the information you are looking for. You might find some informal information at this link. http://www.madreporite.com/insteon/Inst ... e_list.htm This is a user site that accumulates information users have sent in or direct observation. It is not a definitive source but may have some information.

Some should be as easy as defining a Scene with KeypadLinc button A as Controller and the ApplianceLinc as Responder. What will not work is manually controlling the ApplianceLinc locally. The ApplianceLinc is a Responder Only device so turning the ApplianceLinc on locally is not reflected back to the ISY nor to the KeypadLinc. Also if a Program turns On the ApplianceLinc it needs to turn On the Scene with the KeypadLinc button and the ApplianceLinc. Turning On the ApplianceLinc directly with a Program will not be reflected in the KeypadLinc button.

The old ICONs do not have the Beep feature. Do not know how they will react when receiving a command they are not defined to handle. Since they are discontinued I suggest using a Scene that contains only devices that have the Beep feature.

Thanks Xathros - I've not used that feature in the 4+ years of working with the ISY. Learn something new almost every day.

arw01 The Bathroom light has to be a Controller in a Scene for it to appear as a selection for the Adjust Scene 'Set Scene' parameter.

I thought Java 7 was a requirement.

I can understand all that clutter causing confusion as it should not be there and is not on my 4.0.5. What is the Java level as it sounds like a Java issue?

There is no need for parens until the If becomes complex which is why there are no paren options for a single line If. The statements can be moved up or down and the parens can be moved up or down. Post the Program that is not working with a description of what is not executing correctly.

The Program is changing the Scene Responder On Level and Responder Ramp Rate. To change the Local On Level and Local Ramp Rate the Adjust Scene statements must specify the node name of the ToggleLinc in both the 'In Scene' and 'Set' parameters. When both parameters have the node name the ISY knows to adjust the 'Local' values rather than 'Responder' values.

“Should a 2420M motion sensor update its Current State in the ISY console to OFF even when configured to only send ON commands?†No. “After 30 seconds have passed, its state changes to OFF.†The only way this can happen is for the motion sensor to send an Off command.

Not easily. The pre 100% On Level change can be checked at a gross level, 0-20%, 21-40%, 41-60%, etc with individual Programs, saving some restore value in a variable. ie If the current On Level is 41-60% set a variable to 50. These are completely arbitrary values to keep the number of programs involved to a reasonable number. When it is time to restore the On Level another series of programs is needed to check the value in the variable and set the On Level accordingly. A series of Programs is needed for each device. Not a pretty process. A future enhancement to variables may allow the current device On Level to be saved and used later.