KPL Failed Writing

[Jimbo.Automates]

This is a 2334-2 that works fine, even controlling 2 large scenes, but it has a change and won't write.  I'm not good at reading Insteon log but looks like the communication is good but still get a Failed Writing error?  Any help would be appreciated.

Mon 06/03/2024 06:17:05 PM : [22 F4 37 1  ] Link    1 : 0FF0 [A27A500143FF1F02] Writing [A27A500143FF1F02]
Mon 06/03/2024 06:17:05 PM : [INST-TX-I2  ] 02 62 22 F4 37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1
Mon 06/03/2024 06:17:05 PM : [INST-ACK    ] 02 62 22.F4.37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1 06        (00)
Mon 06/03/2024 06:17:05 PM : [INST-SRX    ] 02 50 22.F4.37 50.01.43 AB 2F FF           (FF)
Mon 06/03/2024 06:17:05 PM : [Std-Direct Nack] 22.F4.37-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Mon 06/03/2024 06:17:10 PM : [INST-TX-I2  ] 02 62 22 F4 37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1
Mon 06/03/2024 06:17:10 PM : [INST-ACK    ] 02 62 22.F4.37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1 06        (00)
Mon 06/03/2024 06:17:11 PM : [INST-SRX    ] 02 50 22.F4.37 50.01.43 AB 2F FF           (FF)
Mon 06/03/2024 06:17:11 PM : [Std-Direct Nack] 22.F4.37-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Mon 06/03/2024 06:17:16 PM : [INST-TX-I2  ] 02 62 22 F4 37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1
Mon 06/03/2024 06:17:16 PM : [INST-ACK    ] 02 62 22.F4.37 1F 2F 00 00 02 0F F7 08 A2 7A 50 01 43 FF 1F 02 F1 06        (00)
Mon 06/03/2024 06:17:16 PM : [INST-SRX    ] 02 50 22.F4.37 50.01.43 AB 2F FF           (FF)
Mon 06/03/2024 06:17:16 PM : [Std-Direct Nack] 22.F4.37-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Mon 06/03/2024 06:17:16 PM : [22 F4 37 1  ] Link    1 : 0FF0 [A27A500143FF1F02] *Failed Writing [A27A500143FF1F02]
Mon 06/03/2024 06:17:16 PM : [D2D EVENT       ] Event [22 F4 37 1] [ERR] [0] uom=0 prec=-1
Mon 06/03/2024 06:17:16 PM : [22 F4 37 1      ]      ERR   0

 

[Jimbo.Automates]

Never mind all fixed.  Tried air gapping for 10 seconds, then writing, still failed.  Tried air gaping again and full reset by holding button in until beep stops, then restore device and write changes was successful.

 

[paulbates]

I had keypads at my last house for a long time... After long periods of being installed they occasionally showed weird behavior or wouldn't update.

Either air-gap or reset/restore was the fastest path to getting it going again

[IndyMike]

@Jimbo.Automates, the "NACK" in your event viewer is a dead giveaway.  You apparently have an I2CS device and the link record listing the PLM as a controller is missing or corrupt.   It's interesting that your device still responds to and controls scenes.  That means that some/most of the link table was still intact.

The highlighted entry below is the responder link in one of my KPL's.  This was apparently missing from your KPL.  Without the entry, the KPL will refuse to accept writes from the PLM.

A description of the link table entries was provided by LeeG here : https://forum.universal-devices.com/topic/9525-how-to-read-a-link-table/

If this occurs frequently on this device, you may have a failing device power supply.

If this occurs frequently on multiple devices, you have have a failing PLM or SD card.

 

[IndyMike]

@Jimbo.Automates,

Your issue sounds suspiciously similar to one encountered by @John Chen - https://forum.universal-devices.com/topic/43645-is-my-isy994-done/

Do you happen to use Google Home as described in John's post?

[Jimbo.Automates]

8 minutes ago, IndyMike said:

@Jimbo.Automates,

Your issue sounds suspiciously similar to one encountered by @John Chen - https://forum.universal-devices.com/topic/43645-is-my-isy994-done/

Do you happen to use Google Home as described in John's post?

Yes, I do use Google Home. That's a really long post I'll try to read later to get those details.

Before I reset the device I tried to look at the links table but  it just failed, and I neglected to record the actual error message.

Really appreciate you looking into this.  The KPL has been working fine so far.