keypadlinc brightness adjustment error - w/strange message

[johnnyt]

Not sure if this is Insteon Comm issue or something else. Have had problems for some time adjusting the LED brightness on a KPL using ISY. The first time I try it I get a DHCP error message and "can't open log file". This is particularly strange. See attachment 1. The second time I try it (right after) I get a "Request Failed" message (attachment 2). Both messages happen every time I try.

 

The LED brightness is not altered by this but I am able to alter it at the KPL itself. When I restored this device recently it reverted to the out-of-the-box brightness (I did have to factory reset it before the recent restore as it was stuck ON, even with the air gap pulled! - that's fixed now.) I'm pretty sure I was able to use ISY to change it when I first installed it, meaning it may not "restore" brightness either. I can't remember that for sure, though.

 

I am able to alter the LED brightness of the KPL right next to it (same junction box) using ISY and my insteon network seems to be working fine otherwise, including to/from the KPL next to it. That said, though, it is very slow to restore and read device links from both these KPLs, like 10 mins. (One has 73 links, the other 68. is that normal?)

 

Am running firmware and GUI v3.1.17

 

Any ideas?

[Michel Kohanim]

Hello johnnyt,

 

I just tested this with my 6 button KPL v36 and it works fine. Can you please open the Event Viewer on the last level, retry, capture the events, and copy/paste here?

 

With kind regards,

Michel

[brookbphx]

Well, this thread has been idle a while, but unfortunately, I have to say "Me too".

 

I have three 2486D keypadlincs with v.40 firmware. Running ISY Firmware and UI software version 3.3.2.

 

I can set the LED brightness on one KPL just fine. When I try to set it on either of the other two, I get the same error the previous poster mentioned, "Request Failed"

 

I have Event Viewer up at Level 3 when this happens. When programming the KPL that works, there are 4 events that are logged to set the brightness (shown below). However, when attempting to program the KPL that does NOT work, there are NO EVENTS that occur. The "Request Failed" simply pops up. So there must be something in the ISY database that makes it think that it can't program the LED brightness, because it appears to not even try.

 

The following log is from a KPL the DOES work. There is nothing added to the log when it DOESN'T work.

 

Sun 09/23/2012 06:49:53 PM : [iNST-TX-I2  ] 02 62 1C 8B 20 1F 2E 00 01 07 14 00 00 00 00 00 00 00 00 00 00 B6

Sun 09/23/2012 06:49:53 PM : [iNST-ACK    ] 02 62 1C.8B.20 1F 2E 00 01 07 14 00 00 00 00 00 00 00 00 00 00 B6 06        (00)

Sun 09/23/2012 06:49:53 PM : [iNST-SRX    ] 02 50 1C.8B.20 13.21.82 2B 2E 00           (00)

Sun 09/23/2012 06:49:53 PM : [standard-Direct Ack][1C.8B.20-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

If there's a way to resolve this without having to remove the KPL from the ISY and re-add it (which would be a major pain in the ...) I'd really love to hear it.

 

Thanks!

[LeeG]

What is the KPL firmware level of those that do not work?

 

Some of the older KPLs could not have LED brightness set programmatically.

 

Could try a right click on the Primary KPL node, select Diagnostics | Query Insteon Engine to see if that helps with the KPL that does not work.

[brookbphx]

Hi Lee,

 

They are all brand new - v.40.

 

I have two 'installed', and one is hanging loose to use for testing. One of the installed ones works, and the other doesn't. The 'loose one' didn't work either, although I had loaded lots of scenes programmed onto it previously for that load control problem we've been talking about in another thread. The Installed ones have lots of pretty complex scenes programmed and I really don't want to 'remove' them from the ISY to try to fix the problem unless that's the only solution. However, I did remove the 'loose' 2486D from the ISY, factory reset it, and then added it back in. It then DID work! It let me set the dim level.

 

So I think there's probably something getting hosed in the ISY database for the device which makes the ISY software think that it can't update the dim levels. Like I said earlier, when the problem exists, the ISY doesn't even try to send any commands to the device. It just fails. Removing and re-adding the device resolves it, but then you've got to re-create all of your scenes settings, so its not a great solution. Hopefully UD can find this bug and fix it.

 

Thanks!

[Michel Kohanim]

Hello brookbphx,

 

Are all of them reporting the same version in the Admin Console?

 

With kind regards,

Michel

[brookbphx]

Hi Michel,

 

Yes, they all report v.40. They all were purchased at the same time and arrived in the same box from Smarthome. So they really should be equivalent.

 

Thanks!

[Michel Kohanim]

Hi brookbphx,

 

The only time you would see Request Failed without any INSTEON traffic in the event viewer is if the device in question does not meet the requirements for LED brightness. If they are all "reporting" as 4.0, then I suspect that to be a bug. I have also sent you a PM.

 

With kind regards,

Michel

[johnnyt]

Hello johnnyt,

 

I just tested this with my 6 button KPL v36 and it works fine. Can you please open the Event Viewer on the last level, retry, capture the events, and copy/paste here?

 

With kind regards,

Michel

Just realize I forgot to answer this post.

 

Here's a screen shot showing err msg I get and event viewer on level 3 for the KPL that will not allow me to change LED brightness. It's a v36 and the same one that has problems setting button toggle mode that seems to have been related to my having done a "replace with" at some point in the past. (see support ticket I opened and the following post viewtopic.php?f=27&t=9297 for more info)

 

Last I heard, it's an intermittent issue that has been hard to replicate and remains unsolved. Maybe with more folks reporting it, there will be better luck at finding a solution. I don't particularly want to reprogram this or any other KPL's I have to replace - just too many scenes.

 

Am now on 3.2.6 (firmware and GUI) and have since upgraded my PLM (a week ago) to v9B (from v98)

[Michel Kohanim]

Hello johnnyt,

 

Please wait for our next release, remove, add back and test and let us know.

 

With kind regards,

Michel

[johnnyt]

Hello johnnyt,

 

Please wait for our next release, remove, add back and test and let us know.

 

With kind regards,

Michel

Hi Michel, Do you mean remove KPL and add it back manually? It's part of several scenes (has about 70+ device links) and programs. I've been able to work around by manually setting brightness and toggle mode. Not ideal but better than trying to remember every scene it's in and every program that turns off buttons to make up for the fact that another kpl it's paired with can't turn buttons off on it... Am I risking something by not doing that, e.g. future "replace with's" or complete failure, by leaving it alone? Is next release guaranteed to fix it if I do all that work?

 

Just trying to understand / gauge the trade-offs.

 

Thanks.

[Michel Kohanim]

Hi johnnyt,

 

Unfortunately you might have to. This said, you can try a restore first and report back the outcome.

 

With kind regards,

Michel

[johnnyt]

Hello johnnyt,

 

Please wait for our next release, remove, add back and test and let us know.

 

With kind regards,

Michel

If I go through and remove / re-add problematic KPL now (using 3.2.6) will the problem go away and stay away provided I don't do "replace with" until I've upgraded?

 

Am a little hesitant to move to latest beta at this point. I would only need the fix for "replace with" and don't actually need that right now - the problematic KPL does otherwise work, as do my other ones.

 

I would like to fix the toggle mode issue in particular as I do have other buttons to re-program in the queue.

[Michel Kohanim]

Hello johnnyt,

 

If your KPL is v40 and I2CS, then the answer is NO.

 

With kind regards,

Michel

[johnnyt]

It is v.36. I don't have any i2cs devices, which is why I'm not in a hurry and would like to wait before upgrading.

 

I'll assume the answer is YES with v.36 kpl but please let me know if that's not the case, including if the answer is actually "maybe".

 

Thanks

 

 

Sent from my iPod touch using Tapatalk

[Michel Kohanim]

Hi johnnyt,

 

Yes!

 

With kind regards,

Michel