Write to device fails after PLM replacement

[walkman9999]

Hello -

I have a previously working switchlink dimmer v.40 that will not accept updates from EISY. This occurred after PLM replacement, not sure if coincidence or not. I have tried hard reset.

Logs are attached for an attempt to write to device, and separate log for attempt to restore device. Neither is successful, but it does seem to be some comms between EISY and the device (I think). Comms to other devices in same are seem to be healthy.

Let me know if an more info needed to help diagnose. Any insight is appreciated.

TY

EDIT: attached log from device query

_restore-ISY-Events-Log.v5.8.4__Sun 2025.02.09 14.12.35.txt _write-updates-ISY-Events-Log.v5.8.4__Sun 2025.02.09 14.13.38.txt

_Query-ISY-Events-Log.v5.8.4__Sun 2025.02.09 14.28.42.txt

Edited February 9 by walkman9999

[IndyMike]

@walkman9999, your Switchlinc Dimmer appears to be a 2476D that is powerline only.  Communication with the device isn't great and that can be a problem when trying to restore a device.

It might be possible to install a dual band LampLinc or other RF device electrically near the Dimmer to help with communications.  It's also possible that the noise or signal absorption is temporary due to a problem device in the vicinity.  Try inspecting for typical problem devices (PC's, chargers, UPS's, etc) in the vicinity.  

Another thing that is not in your favor is that the ISY is using and old I1 programming mode with this device.  The Event Viewer  communication below is from your Restore sequence.  The Red section is where the ISY attempted a I1 write sequence that timed out after 3 tries.

The following green section is a successful write that was performed using I2 (much faster).  You could try to "force" the ISY to use I2 communication by going to Link Management/Advanced Options and selecting "Device Reported".  The I2 protocol allows the ISY to transfer data in far fewer command sequences than the I1 mode.  The communication is still susceptible to noise/absorption issues, but there are far fewer opportunities for failure.

 

Sun 02/09/2025 14:11:28 : [  1B B0 CC 1] Preparing Device 'Shed Bathroom' for Restore

Sun 02/09/2025 14:11:28 : [  1B B0 CC 1] Device 'Shed Bathroom' ready for Full Restore

Sun 02/09/2025 14:11:28 : [All         ] Writing 28 bytes to devices

Sun 02/09/2025 14:11:28 : [INST-TX-I1  ] 02 62 1B B0 CC 0F 0D 00

Sun 02/09/2025 14:11:28 : [INST-ACK    ] 02 62 1B.B0.CC 0F 0D 00 06                 (00)

Sun 02/09/2025 14:11:30 : [INST-SRX    ] 02 50 1B.B0.CC 71.1B.41 27 0D 01           (01)

Sun 02/09/2025 14:11:30 : [Std-Direct Ack] 1B.B0.CC-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sun 02/09/2025 14:11:30 : [1B B0 CC 0  ] Calibrating engine version

Sun 02/09/2025 14:11:30 : [1B B0 CC 0  ] May not fully support i2, reverting to i1

Sun 02/09/2025 14:11:30 : [1B B0 CC 1  ] Link    0 : 0FF8 [A200711B41FF1F01] Writing [A200711B41FF1F01]

Sun 02/09/2025 14:11:30 : [INST-TX-I1  ] 02 62 1B B0 CC 0F 28 0F

Sun 02/09/2025 14:11:30 : [INST-ACK    ] 02 62 1B.B0.CC 0F 28 0F 06          SET-MSB(0F)

Sun 02/09/2025 14:11:39 : [INST-TX-I1  ] 02 62 1B B0 CC 0F 28 0F

Sun 02/09/2025 14:11:39 : [INST-ACK    ] 02 62 1B.B0.CC 0F 28 0F 06          SET-MSB(0F)

Sun 02/09/2025 14:11:48 : [INST-TX-I1  ] 02 62 1B B0 CC 0F 28 0F

Sun 02/09/2025 14:11:48 : [INST-ACK    ] 02 62 1B.B0.CC 0F 28 0F 06          SET-MSB(0F)

Sun 02/09/2025 14:11:52 : [1B B0 CC 1  ] Link    0 : 0FF8 [A200711B41FF1F01] *Failed Writing [A200711B41FF1F01]

Sun 02/09/2025 14:11:52 : [1B B0 CC 1  ] Memory : Write dbAddr=0x0264 [0C] cmd1=0x2E cmd2=0x00

Sun 02/09/2025 14:11:52 : [INST-TX-I2  ] 02 62 1B B0 CC 1F 2E 00 00 03 0C 00 00 00 00 00 00 00 00 00 00 C3

Sun 02/09/2025 14:11:52 : [INST-ACK    ] 02 62 1B.B0.CC 1F 2E 00 00 03 0C 00 00 00 00 00 00 00 00 00 00 C3 06        (00)

Sun 02/09/2025 14:11:54 : [INST-SRX    ] 02 50 1B.B0.CC 71.1B.41 27 2E 00           (00)

Sun 02/09/2025 14:11:54 : [Std-Direct Ack] 1B.B0.CC-->ISY/PLM Group=0, Max Hops=3, Hops Left=1

Sun 02/09/2025 14:11:54 : [1B B0 CC 1  ] Memory : Write dbAddr=0x0032 [FF] cmd1=0x2E cmd2=0x00

[walkman9999]

This is very useful, TY! I've decided to replace the device with a dual-link model.

[walkman9999]

Older, single-band devices and some noise on the wire contributed to this. The devices have been replaced and comms are as expected. TY @IndyMike for the decoding help, I've found the explanations useful in other troubleshooting of I1 vs I2 devices. Marking solved.