| Author |
|
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: December 19 2012 at 15:15 | IP Logged
|
|
|
I have just added a new KPL device using the I2CS
protocol (SmartHome model 2487S) and find that I cannot
set two of the buttons on this 6-button keypad to be non-
toggle using PowerHome.
Attempts to do so using the Save/Refresh buttons in the
Insteon explorer KPL Config tab result in NAK responses
from the target KPL, and (not surprisingly) the actual
KPL buttons fail to change their Toggle/On/Off status
when the Insteon Explorer KPL Config tab settings for the
buttons are changed. Other (ie, Links) functions work
with this new KPL so my I2CS update to PH is clearly
working except for the KPL Config functions.
Since I have never had an issue doing this before, it
leads me to believe that the new I2CS protocol may not be
compatable with the "KPL Config" process.
Has anyone had any similar experience. Dave is this an
area that needs an update?
Edited by GadgetGuy - December 19 2012 at 15:16
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: December 19 2012 at 19:07 | IP Logged
|
|
|
The I2CS support Zip provides link record support only. No device configuration support is included. What is coming will be in 2.1.5.
__________________
Lee G
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: December 20 2012 at 07:03 | IP Logged
|
|
|
Lee -
I assume that means then that I cannot configure the KPL
with PH at this time, in any way?
If so, then I'll have to printout the manual "Changing
Button Behavior" instructions and do it the old fashioned
way! 
Thank goodness 2.1.5 is getting close! 
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: December 20 2012 at 07:43 | IP Logged
|
|
|
Manual configuration is the only option. The I2CS devices drop the Peek/Poke commands altogether which forces applications to move to extended commands for configuration. Extended commands are best anyway as they eliminate all the location dependency the Peek/Poke approach had.
__________________
Lee G
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: December 20 2012 at 10:54 | IP Logged
|
|
|
Lee -
Do these same limitations apply to other operations too?
For example, my ph_insteongroupcu()commands to set/clear
the KPL button LEDs also seem to have quit working?
Thanks.
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
grif091
Super User
Joined: March 26 2008
Location: United States
Online Status: Offline
Posts: 1357
|
| Posted: December 20 2012 at 11:28 | IP Logged
|
|
|
This is a device control command which I would expect to work. Being a Group command the link(s) will have to be created again on the I2CS KPL as there are special check sum requirements for the Extended ALDB command used to create links in I2CS devices.
__________________
Lee G
|
| Back to Top |
|
| |
GadgetGuy
Super User
Joined: June 01 2008
Location: United States
Online Status: Offline
Posts: 942
|
| Posted: December 20 2012 at 12:18 | IP Logged
|
|
|
Thanks for the heads up Lee. 
I will copy your comment and post it in the "AutoDetect/
Adding I2CS/ FlaggedCreate" thread I started. Seems
appropriate to keep that kind of info together in one place
as much as possible.
__________________
Ken B - Live every day like it's your last. Eventually, you'll get it right!
|
| Back to Top |
|
| |
Active Topics 
Memberlist 
Search 
Help
Register 
Login
PowerHome Messageboard : PowerHome General
Topic: KPL Configuration and I2CS
