foxcob

Michel, Thanks for your work on this and thanks to any others who are behind the scenes! Looking forward to trying the next beta now. Jacob

Got it, You can see the last record is incorrect. This happens after attempting to set the KPL backlight brightness. Jacob

IndyMike, I'll have to look and see if I still have a screencap of my table comparison around. I do remember off hand that it had a mis-compare on the very last entry of the offending KPL. Jacob

Michel, I know you posted the question to rahnee, but I experienced the same thing. My KPLs worked correctly until I attempted to set the backlight brightness. After that, my button configurations seemed to be all messed up. Specifically, I noticed that button H on one of my 8 button KPLs was acting completely differently than it had before causing other buttons to light up and triggering other scenes. Don't know if this helps. Jacob

JCBond, I have experienced the same thing as you. For now I have returned my system to 3.2.6 and restored from my backup when I was at 3.2.6. Everything went back to normal after I restored my KPLs from there. I cannot get them to work right from 3.3.x. Unfortunately I cannot beta test in this state since my KPL's all stop working and my wife's patience would be much shorter than mine with these conditions. I hope they figure this out soon. Jacob

In case you're wondering, I got the command documentation by searching for "insteon commands table" in google. Top item listed was a PDF from insteon.net.

The KPL is a dimmer.

So I looked up the command in the insteon command table and found that the command decodes as so: 02 62 16 7D 60 1F 2E 00 00 03 05 00 00 00 00 00 00 00 00 00 00 CA 02 - STX 62 - Extended Message 16 7D 60 - Address 2E 00 - Extended Get/Set 00 - Button/Group number 0 03 - Set LED-Off mask for button 05 - Mask (if bit = 0, LED not affected, if bit = 1, LED turns off when button pressed) Rest ignored This makes some sense since after issuing this command the keypad LED's misbehave, but the link table is corrupted as well which I don't understand. The 07 in place of the 03 would set the Global LED brightness. Jacob

Both the UI and firmware report version 3.3.6 with the exact same date code after them. The progress bar does seem to complete now. BTW, I tried setting a different KPL backlight and it worked. I noticed the commands were different preceding the brightness HEX value when talking to the other KPL. Obviously the address was different, but the commands looked different too. Could the ISY be retaining some config for this KPL after deleting it? This is just weird. When I tried the upgrade again BTW, all the KPLs exhibited the problem again. Restoring from my last 3.3.5 backup which have all but the one KPL working restored the other KPLs to a working status. So something is going wrong during the upgrade of my configuration I would think. Jacob

This was supposed to be attached to my last post...

LeeG, I went back to 3.3.6 like you requested and deleted the troublesome KPL from the ISY. I then re-linked it and wiped all existing links from the device. Just in case I had also hard reset the KPL before re-linking. After the ISY had added the KPL, the first thing I attempted to do was set the led brightness. Nothing seems to happen on the KPL. I attached a screenshot of the following levels being set: 0/5, 2/10, and 7/15. Jacob

Alright, I'm back to 3.2.6 for now. Every time I upgrade to 3.3.6, I run into this problem. Unfortunately, this means that twice a day I end up with a KPL that is corrupted and misbehaves. I'm totally willing to try something if anyone has a specific procedure they want me to try. I haven't tried going to 3.3.6 and recreating the KPL from scratch. Maybe I can do that later, but I'm out of time for now. Thanks again to those who have helped! Jacob

Just downgraded and restored from backup 3.2.6 and everything works normally again. I'm going to attempt to go directly to 3.3.6 now. Hopefully everything goes correctly this time. Jacob

LeeG, I think you're probably on to something. Just to note though, that I originally went back to 3.2.6 because this problem showed up when I went from 3.2.6 to 3.3.4. When I did go back to 3.2.6, I also restored the ISY from the 3.2.6 backup, so I shouldn't have had 3.3.4 config with 3.2.6. I think something is wrong with the upgrade process converting the configuration from a prior version. This time it messed up the config of the one KPL, but not the others. Like I said, everything was working with 3.3.5, then I upgraded to 3.3.6 and it failed again. I'm going back to 3.2.6 and restoring from my 3.2.6 backup to see if everything goes back to normal. At that point I'll try a direct upgrade from 3.2.6 to 3.3.6. Jacob

LeeG, I opened the admin console and did exactly what you said, here's the result. The busy dialog is still stuck open as well... I was attempting to set a keypad brightness of 1/9. The keypad currently has the off state at 0 (no light) with the on level at about 5. I didn't see any change when trying to issue this command from the console. Jacob