Insteon bug? Scenes can be created in ISY, but ISY fails to write it to Insteon Keypads

[kar1024]

Trying to understand why ISY fails. Is it a bug in Insteon device? Are there known workarounds? Or am I trying to do something that ISY/Insteon simply cannot do.
Should I get more recent version of keypads? Can it be because I have 2 buttons on the same keypad set as responders to the same scene?

Setup

Two keypads that are used to control AV system. Both keypads are identical. Each keypad button is treated as two separate entities:

Indicator: Button light itself. Controlled via ISY scene. Only On/Off commands are sent.

Button: Events generated by user presses a button (DON, DOF, DFON, DFOF, etc) trigger a program that does something.

I can create this setup in the ISY, but ISY fails to write it to keypads. Tried with different keypads, but got the same result. Can you point me to what I may be doing wrong? Keep in mind that I don't have any programs running and nothing is connected to the ISY. All I am trying to do is write configuration to keypads (and PLM, of course).

Log

ISY log looks something like this:

Wed 06/19/2019 16:44:15 : [Std-Direct Ack] 19.47.65-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Wed 06/19/2019 16:44:15 : [INST-TX-I1  ] 02 62 19 47 65 0F 2B FF
Wed 06/19/2019 16:44:15 : [INST-ACK    ] 02 62 19.47.65 0F 2B FF 06          PEEK   (FF)
Wed 06/19/2019 16:44:24 : [INST-TX-I1  ] 02 62 19 47 65 0F 28 0F
Wed 06/19/2019 16:44:24 : [INST-ACK    ] 02 62 19.47.65 0F 28 0F 06          SET-MSB(0F)
Wed 06/19/2019 16:44:24 : [INST-SRX    ] 02 50 19.47.65 33.5C.B9 2B 28 0F    SET-MSB(0F)
Wed 06/19/2019 16:44:24 : [Std-Direct Ack] 19.47.65-->ISY/PLM Group=0, Max Hops=3, Hops Left=2
Wed 06/19/2019 16:44:24 : [INST-TX-I1  ] 02 62 19 47 65 0F 2B FF
Wed 06/19/2019 16:44:25 : [INST-ACK    ] 02 62 19.47.65 0F 2B FF 06          PEEK   (FF)
Wed 06/19/2019 16:44:29 : [19 47 65 1  ] Link    0 : 0FF8 [A229335CB9FF1F06] *Failed Writing [A229335CB9FF1F06]
Wed 06/19/2019 16:47:33 : [        Time] 16:47:37 0(0)

 

 

2Keypads ISY-Events-Log.v5.0.15A__Wed 2019.06.19 16.56.43

[simplextech]

By the name of it being "Desk" are these actually 8 button remotes?  Are they in linking mode before you try writing to them?

[paulbates]

You should be able to. I use 3 keypads at entrances to an area for lighting control in a similar way. A couple of things to try:

• Factory reset the keypad, right click on it and pick restore device
   
• Click on a couple of the desk scene responders and delete them, then drag them back in. 
   
• Since it happened to two; it might be line noise problems. Can you install the keypad somewhere else that's closer to the PLM, or set up a plug in jig to wire it up, and try updating closer to the PLM?

Paul

[oberkc]

I have an eight-button keypadlinc that seems resistant to updates also.  It is the second in this particular location.  I have always assumed there is something that makes communication difficult, but have not made a serious effort to figure it out.  I try is several times and, eventually, it works.  My favorite trick is to come back the next day, at a completely different time, and retry writing the updates.  I have learned not to get too frustrated.  It will be fine tomorrow.

[kar1024]

Thanks for your advice!   

I have tried all the basics (factory reset, recreate scenes one by one, move devices, etc).
Just wanted to ask the community if this is a known Insteon bug (similar to the dreaded ALL-ON problem). 

Next step - clean setup with just one PLM and 2 Keypads.

[lilyoyo1]

I would say it's not a bug otherwise the forums would be filled with people having the same issue. 

What's the firmware/UI of your isy, the Rev and model numbers of your devices, 

[kar1024]

18 hours ago, lilyoyo1 said:

I would say it's not a bug otherwise the forums would be filled with people having the same issue. 

What's the firmware/UI of your isy, the Rev and model numbers of your devices, 

Keypads:  19.x
PLM: 4D.x
ISY: Latest (5.0.15A)

This weekend I will try it with brand new KPLs. Version 50.x or higher.

[lilyoyo1]

The 19x doesnt give any information about your kpl. Whats the model number of the device and rev. it will be listed on the sticker that is on the device itset

[Techman]

 In the admin console, right click on the keypad then click on write updates to device.

If they still won't update then you have a communications problem between the keypad and the PLM

let me know the results.

 

[kar1024]

Finally got new KPLs and experimented with various configurations.

Old KPLs: v. 5.7
New KPLs: v. 8.8

2 old KPLs work well as a pair, but it takes more than a minute to write all links
2 new KPLs work just as well and it takes less than 10 seconds to write all links.
1 old + 1 new KPL did not work. Write never finishes and there are no errors.

I solved my problem by moving KPLs around so all pairs are from the same generation.

[Brian H]

If the older KPL switches. Where the original I1 protocol. The old Peek and Poke I1 commands took a very long time. As each bit of a link was sent individually.

The latest should be I2CS and use Extended Messages. Much faster.