LeeG

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.

Was the lockset tested with the MorningLinc unplugged? I could see the MorningLinc sending a constant RF signal to the lockset but that would have been corrected when the MorningLinc was unplugged. Note that when the MorningLinc was factory reset the authorization link between the ISY PLM and the MorningLinc was erased. It will have to be Deleted from the ISY and added back. Also note that factory reset of the MorningLinc does not affect the link (not an Insteon link) between the MorningLinc and the lockset as that information is maintained in the lockset. A reset of the lockset would remove the link between the MorningLinc and the lockset. The MorningLinc has to be positioned close to the lockset and the link between the MorningLinc and the lockset reestablished. Of course if the MorningLinc is defective it has to be replaced. I have two MorningLincs linked to one lockset for around a year. Both are working fine.

Unfortunately I'm not sure if a Restore Device will put back bad configuration data. An issue with the v.41 KPL firmware was resolved but I don't know if the underlying ISY configuration data is right or wrong when created before 4.0.5. If the ISY data is wrong the Restore Device is going to restore bad configuration information. This is something UDI will have to respond to. Of course the Scenes can be defined from scratch which should eliminate the question but I understand that may require lots of work.

The button is not in non-toggle mode if it does not blink twice. Would the 6.9 be the hardware revision. The KPL firmware is displayed on the second line of the individual node display. There is a correction for the v.41 firmware in 4.0.5 that requires the device be deleted from the ISY and added back. The solution proposed by Xathros is not dependent on the internal KPL configuration information so I would expect it to work in with other issues.