toggle mode won't change on keypadlinc

[johnnyt]

Have tried several times to change from toggle mode to non-toggle "always off" mode on a v.36 keypadlinc but I keep getting "Request failed" message. The following lone event shows up in the event viewer (set to level 3):

 

Sun 08/26/2012 12:50:48 PM : [All ] Writing 0 bytes to devices

 

Strangely too, the first time (of about 8+ times I tried) I got a message about DHCP Renew error. Can't see how a DHCP error would be related so it appears to have been a fluke occurrence (maybe displaying a previously stored or coincidental error message?) but I thought I would mention it anyway.

[LeeG]

Right click the KeypadLinc Primary node, select Diagnostics | Query Insteon Engine.

 

With the Event viewer running Level 3 change the KPL button to something different as the ISY will not write an option to the KPL it thinks has already been set. Then change the button toggle mode to the desired setting. See if button works after the Query Insteon Engine.

 

If not please post the event trace.

[johnnyt]

Ran query insteon engine and nothing came up. I ran it again with event viewer, followed by several attempts to change the toggle mode to all the available options then repeating some of them. Here's the event log:

 

Sun 08/26/2012 08:13:24 PM : [All ] Writing 1 bytes to devices

Sun 08/26/2012 08:13:24 PM : [iNST-TX-I1 ] 02 62 16 74 D5 0F 0D 00

Sun 08/26/2012 08:13:24 PM : [iNST-ACK ] 02 62 16.74.D5 0F 0D 00 06 (00)

Sun 08/26/2012 08:13:24 PM : [iNST-SRX ] 02 50 16.74.D5 19.71.CB 2B 0D 01 (01)

Sun 08/26/2012 08:13:24 PM : [standard-Direct Ack][16.74.D5-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Sun 08/26/2012 08:13:25 PM : [16 74 D5 0 ] Calibrating engine version

Sun 08/26/2012 08:13:25 PM : [16 74 D5 0 ] May not fully support i2, reverting to i1

Sun 08/26/2012 08:13:35 PM : [All ] Writing 0 bytes to devices

Sun 08/26/2012 08:13:41 PM : [All ] Writing 0 bytes to devices

Sun 08/26/2012 08:13:46 PM : [All ] Writing 0 bytes to devices

Sun 08/26/2012 08:13:50 PM : [All ] Writing 0 bytes to devices

Sun 08/26/2012 08:13:54 PM : [All ] Writing 0 bytes to devices

Sun 08/26/2012 08:14:03 PM : [All ] Writing 0 bytes to devices

[LeeG]

For some reason the change is not being written to the KeypadLinc.

 

What ISY firmware level is being used?

 

Run Help | About, verify Firmware and UI lines show same level.

[LeeG]

Is there anything pending/queued for the KeypadLinc or any chance it is marked Disabled. When I mark my v36 KPL disabled and change the toggle mode all I get is the 0 bytes message.

[johnnyt]

am running 3.2.6 in both cases.

 

no, the kpl is not disabled and there are no pending updates (would see gray arrows, right?)

 

I retried this morning and got a strange error again the first time. This time it was "Platform Errors -10108, Check log". I had a strange error the first time yesterday too but didn't note the err message so didn't mention it.

 

When I checked the error log I see a TON of 17001 errors which I recognize as DSCLink updates (0: GET-->/rest/vars/set/2/23/0) and which also point to the machine on which both DSCLink and HomeSeer run ([HTTP] 192.168.0.10:19848->80).

 

I think I should post separately on these errors because I can't see how it's related to the kpl problem I'm having. In fact it also looks to me like there's a bug in the error message display functionality, showing a previous message rather than the current one (another separate issue).

 

I did try changing the toggle mode on another kpl and it worked fine. Unless you have other ideas, I will try later to restore the device. I also suspect there's noise or something on the circuit to the kpl as updates to it are very slow (as, I suspect, will be the restore). Does the insteon command for changing toggle mode maybe give up quickly if it doesn't work right away?

[LeeG]

There were no commands issued in the posted event trace so not the case of the command failing.

 

EDIT: the command in one of the earlier event traces is the Query Insteon Engine. The toggle mode change did not initiate a command. A single Extended command is used to alter toggle mode

[johnnyt]

I pulled out a new (spare) KPL (18.58.D8) I keep on hand, linked it in, tested toggle and LED brightness (something else that was not working on the KPL in question) and everything worked fine so I went through the replace device and now the new KPL doesn't let me change toggle mode or LED brightness! - same "Request Failed" message

 

FWIW, there are 74 device links and they are identical to what the PLM has in it's table. Replacing the KPL was slow and painful. Had to be restarted twice.

 

Caught one of the failures in the event viewer (Mon 08/27/2012 01:03:23 PM : [18 58 D8 1 ] Link 60 : 0E18 [E2061A1D09FF1F06] *Failed Writing )

 

Watched progress along the way and for the most part "hops left" were 2, although I saw a few 1's and 0's - none right before the "Failed Writing" event, though. In fact the event just before was:

Mon 08/27/2012 01:03:19 PM : [standard-Direct Ack][18.58.D8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

 

Edit: re-linked in the "old" KPL and without replacing it back in I tested toggle/brightness and they work fine.

 

Help!

[LeeG]

I suspect there is something in the device definition that has gotten corrupted. The Replace xxx with... changes the Insteon address in the old definition which is why the new KPL worked until the old configuration was used with the new address.

 

The only thing I can think to try is to delete the KPL definition altogether. That will be a pain getting the links back for sure being a KPL. Could open a Ticket with UDI Tech Support to see if they have information about the Platform error message and this symptom. We are coming up on the 4 month mark since a new ISY image has been released. Could be this issue is known.

 

Note that when the Hops Left count is moving around, sometimes 2, sometimes 1 or 0, there is some comm issue. It is not causing the current issue but is something to look into as time allows.

[johnnyt]

okay, am going to open a support ticket.

 

Looking further through my event viewer logs I noticed an odd event while I was replacing my old KPL with the new one - a sign of data corruption?

 

-> Mon 08/27/2012 12:56:47 PM : [uNKNOWN ] 02 D8

 

 

Here are a few lines from before and after:

 

Mon 08/27/2012 12:56:47 PM : [standard-Direct Ack][18.58.D8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Mon 08/27/2012 12:56:47 PM : [iNST-TX-I1 ] 02 62 18 58 D8 0F 28 0F

Mon 08/27/2012 12:56:47 PM : [iNST-ACK ] 02 62 18.58.D8 0F 28 0F 06 SET-MSB(0F)

Mon 08/27/2012 12:56:47 PM : [iNST-SRX ] 02 50 18.58.D8 19.71.CB 2B 28 0F SET-MSB(0F)

Mon 08/27/2012 12:56:47 PM : [standard-Direct Ack][18.58.D8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

Mon 08/27/2012 12:56:47 PM : [iNST-TX-I1 ] 02 62 18 58 D8 0F 2B 61

 

Mon 08/27/2012 12:56:47 PM : [uNKNOWN ] 02 D8

 

Mon 08/27/2012 12:56:56 PM : [iNST-TX-I1 ] 02 62 18 58 D8 0F 28 0F

Mon 08/27/2012 12:56:56 PM : [iNST-ACK ] 02 62 18.58.D8 0F 28 0F 06 SET-MSB(0F)

Mon 08/27/2012 12:56:57 PM : [iNST-SRX ] 02 50 18.58.D8 19.71.CB 2B 28 0F SET-MSB(0F)

Mon 08/27/2012 12:56:57 PM : [standard-Direct Ack][18.58.D8-->ISY/PLM Group=0] Max Hops=3, Hops Left=2

[LeeG]

That is an unknown message type from the PLM. What type PLM (2412 or 2413) and what is the firmware level of the PLM (Tools | Diagnostics | PLM Info/Status).

[johnnyt]

2413 v.98

 

 

Sent from my iPod touch using Tapatalk