I have dimmable Keypadlinc installed in my basement that I have yet to get to work properly. I have set it up as per the instructions included in Altsteon. Everything seems to go fine, the switch is added and eventually shows up in Vera. However, I am unable to control it, it does not respond to on/off or dim commands. It also does not report it state correctly. When I go into settings > Device Options and try and select the button configuration (using the radio buttons), I can select one, but as soon as I leave the screen, that selection has been removed.
Also, I cannot seem to get the scene controller to show up.
I have the 8 button dimmable model running on a Vera Lite.
I am sure I have something screwed up, so if I need to reset my KeypadLinc and start fresh, I can certainly do that. Thanks all.
Determine the sub category of your KPL. The easiest way is to go to the advanced tab of your device and look at subcat. If it is ‘12’, your subcat is ‘0C’. Alternatively you can fire up putty, run altsteon_cli and run the command ‘xx.xx.xx info’ (xx.xx.xx beeing the address of your device). It should return the devcat and subcat.
Next look at the file I_InsteonPLM.xml. You can modify it to include your subcat if it is not there (search for ‘1B’ - there are 2 places to update the code). Upload modified file. Next is where I am a bit unclear. The KPL only started working after I reloaded altseon daemon and physically unplugged vera to force a reboot.
Alternative approach (untested by me, but may work in theory and is easier): Delete the device and recreate it. But for the device ID dont use just xx.xx.xx
Instead use xx.xx.xx,01,1C
This should force the devcat and subcat. According to a insteon device list on the web the 8-button kpl may be ‘0C’ or ‘1C’ (and maybe others), but Altsteon only supports ‘1C’ as far as I can tell. If at first this does not work try re-loading altsteon daemon and rebooting. If it still does not work you may have to go with option A
I found it usefull to have putty with altsteon_cli running in the background to see what was going on. Also check in the advanced tab of the device what the device_type is. Mine kept on defaulting to Dimmer until I added ‘0C’ to I_InsteonPLM.xml
Well that did it, I can now run scenes from my keypad linc!!! Thanks for the help. ;D
The only issue I have now is that I cannot control the load on the keypad linc from the UI5 interface. I can send a command via the CLI and control the keypad. The strange thing is if I press off while the load is on, it will switch to off on the interface, but the percentage will stay at 100% and the light will stay on. I will go back through some older posts to see what I did the last time.
Try resetting the KPL. I mucked so much with mine trying to get it to work that I had the ramp rate, max on level etc all messed up. Reset it to default and re-set it the way you want. I am not positive this is your issue but it’s worth a try.
Yes, the second “scene” device shows up and it functions perfectly. All of the buttons on the kpl work great. The only issue is that when I try toggling the load on and off, nothing happens. When I toggle it on from the physical switch, the interface shows the change. When I use cli, I can turn the load on and off without issue. I just can’t use the interface to turn the light on and off.
When looking at the cli, I see the interface pass the command to the PLM, but it differs slightly from when I use the “xx.xx.xx on” command.
I will look through the xml files to see if the “0C” is missing.
I tested last night. Seems I have the same issue. Never noticed because I use the web interface only for admin. We’ll have to wait for this to be open-sourced to dig into the code.
I have not had any issues with my kpl’s or fanlincs with altsteon. What version are you running. Did you upload all the files? By the way altsteon is already open sourced. Look at the open source thread.
[quote=“garrettwp, post:10, topic:173129”]I have not had any issues with my kpl’s or fanlincs with altsteon. What version are you running. Did you upload all the files? By the way altsteon is already open sourced. Look at the open source thread.
Garrett[/quote]
Garrett. The issue is our specific KPL’s subcat is not included in Altsteon, so the daemon does not recognize the device as a kpl. Look at the post #2 for details.
I just realized it is now open sourced. When I get enough time I will dig into it. But for now the workaround mostly gives me what I need.
Can you post the devcat and subcat for your devices? Faking the devcat and subcat might work, but that wasn’t really what I had in mind when I added that functionality so I can’t promise everything will work. You will probably also run in to issues with the version of the device. (Is it I1, I2, or I2CS?) So, the best way to fix the issue is to see if it is a subcat we don’t recognize, and get it added. (FWIW, if you change the subcats that are looked for in the LUA and don’t change them in the daemon, you will probably get some strange results.)
I’ll also pull the latest device list and make sure that we have all of the subcats listed. However, I know that they sometimes take devices off, so getting your devcat and subcat information would be good.
The strange thing is if I issue the command “xx.xx.xx on” or “xx.xx.xx off” via the CLI, the light responds. But when I do it via the vera interface, it does not.
The strange thing is if I issue the command “xx.xx.xx on” or “xx.xx.xx off” via the CLI, the light responds. But when I do it via the vera interface, it does not.[/quote]
I probably should have been more clear, but now I have to ask a stupid question. What command did you use, or log file did you read to get those values? All of them could be either hex or decimal, and I think the log puts them out in hex and the UI puts them out in decimal. (Not really ideal. We should probably fix that.)
For DevCat 1, SubCat 12, if I assume those values came from the UI which means in hex it would be 0C. For DevCat 01, the current Subcats that are known are
(in hex) : 09, 0A,0C,1B, and 1C. 1A is also in there for the current build, but according to the Smarthome documentation, 1A is actually an in-line link dimmer, so I pulled it out.
For DevCat 2, SubCat 44 (2C in hex) there is no listing in the current documentation. (But, it is obviously wrong. For DevCat 02, the current Subcats that are known are 09 and 1E. And in a second when I push this commit it will include 2C.
Can you guy verify for me where you got your subcat numbers so I can be sure that I am reading this correctly?
BTW - I am going to make a post about nightly builds some time tonight. You may want to check that out to see how you can verify the changes.
The DevCat 2 SubCat 44 was the result of the list command in altsteon_cli. Thanks for your support on this. It’s so much better than the native insteon support.
For DevCat 02, the current Subcats that are known are 09 and 1E. And in a second when I push this commit it will include 2C.