InsteonMiniBroker and KeyPadLinc8

John,

I am still loving your Insteon driver and using it more and more in a production environment. My wife loves the lights coming on magically when she arrives home at night as well as several other features you have made available.

I have been away for 6 months on a contract and upon returning home I installed your latest driver 2.0.1.3. As you will recall I have been anxiously awaiting unique load support for the KeyPadLinc8.

I started by verifying that my existing functionality had not changed with the new version of the mini broker. There were no ill effects. Regression testing complete I then added a new light in my MasterBedroom and bound it to Switch3 on the KeyPadLinc8. For good measure I rebooted and restarted Builder. I then checked the PowerState property for Home.House.SecondFloor.MasterBedRoom.KeyPadLinc3.Stairs. This is bound to Switch_3 on the KeyPadLinc. Nothing happened. I then went to the KeyPadLinc8 and manually activated Switch_3. Both attached SwitchLinc’s responded and the status light on Switch_3 came on. I then checked the PowerState property in builder and found it was still showing PowerState=OFF.

I also tried from builder changing the PowerState of the KeyPadLinc device itself, not Switch_1 and found that the attached load would not respond. In the past this has worked without fail. I then tried adding a new light and bound it to Switch_1. I then repeated the above testing and found that no matter what I did. I could not communicate with the KeyPadLinc8.

Let me know if there is further testing I can do.

Thank you John.

Kaz

Kaz,

I'm sure your family is glad you're back!!! I did the consulting thing for a couple of years and it wasn't much fun being on the road all the time.

Maybe I wasn't clear on how the KeypadLinc functionality is implemented. There's really no way for my driver to command the keypadlinc to command another device to turn on (unless it's the attached load). It sounds like that's what you're trying to do. What you can do is attach a keypad link switch to a script which then turns on another device.

The issue you describe with the attached load is weird. I don't have a KeypadLinc 8 to test, but it does work for a KP6, and I wouldn't expect the attached load portion to be different between the two devices. Have you tried relinking the KP8 to Premise? I don't remember if you were using generic device support or explicit KP8 support in the driver. The generic Multiswitch controller doesn't support a load. You'll need to relink both ways. I've also found that with certain firmware versions of the KP6, a simple PING of the device will add it to the PLC in a way that support bi-directional control.

-John