IndyMike

@Tmc, my apologies - I was wrong. I just deleted a device from my system and the PLM responder links are still are still there. I'm scratching my head at the moment... Event Viewer: Mon 02/10/2025 06:22:32 PM : [58 C9 B0 1 ] Start : Removing device from ISY Mon 02/10/2025 06:22:32 PM : [58 C9 B0 1 ] Finish : Removing from ISY was Successful PLM Table:

@Tmc, you are correct that there is a record with your device address still in the PLM. If you look at the flag column you should see a "22". This is the sign that the ISY has marked the record as "Unused". In order to completely remove the information, all of the links following the record would need to be removed. Simply marking the record Unused gets the job done quickly. If you find that you have many "unused" records you can perform a PLM restore to rewrite the entire PLM. The ISY will remove the unused records. The same technique applies to devices. The "22" is used to mark records unused, and a Device Restore will rewrite and remove the unused records.

@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

@BRMeeke, 26 KPL's is a lot. That consumes a lot of links in the PLM (1024 max) and nodes in the ISY (1000 max). Keep an eye on both.

@richtimpa, conventional wisdom dictates that the PLM should be located at the Panel since it is the central point for your electrical system. It is also normally the electrically quiet location. In your case, the Powerwall flips things upside down. Whether the Powerwall is absorbing signals or polluting the powerline, the Panel is where you do NOT Want your PLM. As @bigDvette indicated, moving the PLM far (electrically) from the Panel should reduce both noise and signal absorption. Your electrical wiring has a characteristic Inductance, resistance, and capacitance per foot of wire. Moving away from the panel will allow the wiring to attenuate noise and buffer against absorption. This also happens with Insteon signals, but each device repeats the communication to keep the signal level above the noise floor. Another option would be to put your PLM behind a filterlinc in an attempt to "force" rf communication.

@dleduc, I think you may be misinterpreting how the variable is being used in this statement. The Set 'Mister' On '$Timer %' will transfer the value of the variable as the ON LEVEL for the "mister" device. Valid range is 0 to 100%. The Example Program below sets the On Level of one of my dimmers to 4 different levels specified by the Variable 'IOnLevel'. 100 = 100% and 0 = off. The event viewer shows the ISY commanding the dimmer through the 4 different states. Note that this applies to devices only. If you attempt to assign a variable % to a scene you will only be able to command ON/OFF (anything >0 = ON, 0=OFF). Variable On Level - [ID 0070][Parent 0067] If - No Conditions - (To add one, press 'Schedule' or 'Condition') Then $IOnLevel = 100 Set 'Basement / BSMT Video Cans' On '$IOnLevel %' Wait 1 second $IOnLevel = 50 Set 'Basement / BSMT Video Cans' On '$IOnLevel %' Wait 1 second $IOnLevel = 10 Set 'Basement / BSMT Video Cans' On '$IOnLevel %' $IOnLevel = 0 Wait 1 second Set 'Basement / BSMT Video Cans' On '$IOnLevel %' Else - No Actions - (To add one, press 'Action') Event Viewer (IOnLevel =100) Sun 02/09/2025 08:19:03 AM : [INST-TX-I1 ] 02 62 17 F7 B6 0F 11 FF Sun 02/09/2025 08:19:03 AM : [INST-ACK ] 02 62 17.F7.B6 0F 11 FF 06 LTONRR (FF) Sun 02/09/2025 08:19:03 AM : [INST-SRX ] 02 50 17.F7.B6 53.BC.3A 2F 11 FF LTONRR (FF) Sun 02/09/2025 08:19:03 AM : [Std-Direct Ack] 17.F7.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 (IOnLevel =50) Sun 02/09/2025 08:19:04 AM : [INST-TX-I1 ] 02 62 17 F7 B6 0F 11 80 Sun 02/09/2025 08:19:04 AM : [INST-ACK ] 02 62 17.F7.B6 0F 11 80 06 LTONRR (80) Sun 02/09/2025 08:19:04 AM : [INST-SRX ] 02 50 17.F7.B6 53.BC.3A 2F 11 80 LTONRR (80) Sun 02/09/2025 08:19:04 AM : [Std-Direct Ack] 17.F7.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 (IOnLevel =10) Sun 02/09/2025 08:19:05 AM : [INST-TX-I1 ] 02 62 17 F7 B6 0F 11 1A Sun 02/09/2025 08:19:05 AM : [INST-ACK ] 02 62 17.F7.B6 0F 11 1A 06 LTONRR (1A) Sun 02/09/2025 08:19:05 AM : [INST-SRX ] 02 50 17.F7.B6 53.BC.3A 2F 11 1A LTONRR (1A) Sun 02/09/2025 08:19:05 AM : [Std-Direct Ack] 17.F7.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=3 (IOnLevel =0) Sun 02/09/2025 08:19:06 AM : [INST-TX-I1 ] 02 62 17 F7 B6 0F 13 00 Sun 02/09/2025 08:19:06 AM : [INST-ACK ] 02 62 17.F7.B6 0F 13 00 06 LTOFFRR(00) Sun 02/09/2025 08:19:06 AM : [INST-SRX ] 02 50 17.F7.B6 53.BC.3A 2F 13 00 LTOFFRR(00) Sun 02/09/2025 08:19:06 AM : [Std-Direct Ack] 17.F7.B6-->ISY/PLM Group=0, Max Hops=3, Hops Left=3

@walkman9999, your event viewer is showing an error during the PLM record read. The ISY is talking to the PLM but the PLM is returning a negative acknowledge. The ISY retries 2 times and then aborts the operation. 02 69 15 (15 indicates a Negative Acknowledge from the PLM). The proper response would be a 02 69 06 which would then be followed by the PLM link record. You could try power cycling the PLM to see if it recovers. If it does not, your spare will come in handy.

@Illusion, toggling the WAN MAY result in a new WAN IP address being assigned by your ISP. Disabling internet access to IoX should have no effect. Just pointing out the difference. I have no ability to test.

Hard to say - not many people with Tesla powerwall's to test. I you are willing to move away from Insteon, there are likely cost effective options out there than CAN communicate and Don't flicker. Obviously there are dimmers with better powerline filtering. I happen to like the Zooz Z-wave dimmers. They have some rather high end features (available reverse phase dimming) and I have never had an issue with flicker. Of course I don't have a powerwall. https://www.getzooz.com/zooz-zen77-s2-dimmer/ Moving toward the high end of the cost scale, there's Lutron. I linked to a Lutron white paper that explained their RTISS system that specifically addresses flicker. From what I can see, the RTISS capability is included on the PRO products. The links below are for their "dumb" dimmers. The include features like selectable forward and reverse dimming control. Amazon Maestro Pro Lutron Maestro Specifications If you want smart dimmers Lutron also makes the RA3 line. In the past, Lutron did not allow Homeowners to purchase/install their RA3 products. You have to register with them and take a training course in order to buy. Not exactly DIY. https://radiora3.lutron.com/us/en/lutron-advantage Personally, I would start at the low price end and "test drive" various dimmers until I found one that I liked. Just make sure that you've evaluated the dimmer for flicker over various Powerwall load conditions. If you do find a solution - PLEASE post your findings.

@pwmcmaho, the following table is what you posted 3 hours ago. It shows 21 unique device addresses and 23 total records. 19 of the devices are listed as "responders only" (FL=E2). These devices cannot send messages to the PLM (this is what you are seeing above). You should be able to turn these on/off from the admin console. 2 of the devices have control links for the PLM (FL=A2). I've highlighted these in the table. These 2 devices can communicate back to the PLM when they are manually activated. Again, you either had an aborted PLM restore, or a bad backup.

@jkraus, another possibility might be that you had a device "misbehaving" on that circuit. When you replaced the breaker, you may have inadvertently corrected the issue by power cycling all the devices on the circuit. Only way to tell would be if the problem re-occurs, or to re-installing the suspect breaker. I am NOT asking you to re-install... Just keep in mind that if the circuit acts up again, you can try power cycling. If that works, you can narrow down to individual devices from there.

@pwmcmaho, an easier way to look at the device links (and compare them): "right click" on the device in the admin tree. This should bring up a menu that includes "diagnostics" (1st graphic below). Select "Show Device Links Table" and the ISY will read the Link Table and present all of the stored Links (second graphic). At the bottom of the displayed table is a "Compare" button. Select this and the ISY will display a second table of what I believes "Should" be in the device. It will also highlight discrepancies. If you can post tables for a device, we should be able to determine whether they are configured correctly. The above is the process, However, the PLM table that you posted contains only 21 links. That's simply not enough links. Either something went south during the upgrade process, or you had a bad backup. Please re-try the PLM replace using the procedure that @Techman posted. If things still don't work, we'll assume that backup is bad and revert to an earlier backup.

Flashing Red is normally an indication that a controller can't communicate with a scene responder. Depending on the size of a scene, it can take significant time for the controller to send cleanup messages to each scene responder. If retries are required, the time grows longer still. Additional button presses while the controller is attempting to executing cleanup communication will likely result in the controller abandoning the activity. This could also result in the controller "flashing" an error.

@CoolToys, are you saying that you have a Tesla Powerwall and an Inverter? If that is the case, take my suggestion of moving the PLM to the main panel with a grain of salt... As shown in the other threads, the Powerwall generates noise that appears to be close to the Insteon frequency. It MAY also generate noise near the 60Hz zero crossing - that's a double whammy. Given that the Powerwall is likely tied into your main panel (or sub), you want to put some distance between the Powerwall and the PLM. Line length = Inductance = noise attenuation.

I'm going to echo @Brian H's comments. I do not have a workaround. This has been requested in years past, and it's likely on a "to do" list somewhere. Unfortunately, it's a long list... As a test, I did try manually linking a 2456S3 Appliancelinc as a 2457D2 LampLinc. This would have allowed me to replace the existing LampLinc with the ApplianceLinc. In short - I lied to the ISY. The ISY994 correctly identified the ApplianceLinc and linked correctly for the device. In other words, the ISY outsmarted me. When the UDI team first came out with the Replace feature, it was a boon to the community. SmartLabs devices were having some teething issues with power supply and paddle switch failures that mandated early replacements. KPL power supply issues were particularly painful. Replacing an 8 button KPL could easily wind up being an all day affair depending on the number of scenes and programs involved. The ISY (ISY26 or ISY99??) paid for itself the 1st time I used the replace feature. While I'll admit that there have been times where an "unrestricted" replace might have been useful, these were few and far between. The UDI team has done many amazing things given their resources but, in the end, they are a small shop. Since the early Insteon days they have branched out to Z-wave, Zigbee, and now Matter. Focusing on new device definitions for the expanded protocols (likely) has much higher ROI.

Have a look at the Lutron white paper below. It goes into details on the types of powerline noise that can cause flicker in dimmers. One of the big offenders is noise at the zero crossing. Since Insteon communicates at the Zero crossing, noise at that point would absolutely detract from communication. In summary, the Inovelli devices you chose communicate well because to don't need the powerline (RF only). They don't flicker because they have a good powerline filter to provide consistent drive levels to the triac. https://assets.lutron.com/a/documents/power_quality.pdf

@CoolToys, It sounds like you have a lot of equipment that would be capable of absorbing/interfering with Insteon signals. My 1st suggestion would be to relocate the PLM as close as physically possible to the main panel. The panel is the Nexus of your electrical system and is (normally) the most stable/quite point. Even a temporary install can be extremely instructive. Edit: In addition to the PLM at the main panel -make sure you couple the phases at the panel... Place a dual band device (LL, APL, or range extender) on the opposite phase nearby the PLM. I would also be leery of installing the PLM on the same circuit as your A/V rack. Audio equipment incorporates very good powerline input filters. Unfortunately, many manufactures don't isolate the filters from the input - and they absorb powerline communication as a result. In other words, you may need filterlinc's (or something similar) to isolate your A/V equipment from the powerline.

@jkraus, I don't have a Powerwall but I've used the Zooz Zen77 dimmers (Z-wave) in a number of problem installs where flickering was an issue. They are rather inexpensive compared to Insteon and can be used with mechanical switches in 3-way configurations (no need for slave switches). Since this appears to be an overall "power quality" issue affecting dimmers in general, Lutron would be another option (smart or otherwise). If shopping for Lutron, look for devices that incorporate RTISS (Real Time Illumination Stability System) https://assets.lutron.com/a/documents/power_quality.pdf

@CoolToys, sorry to hear you still have some gremlins running around. Your failed scene is rather curious. The 2476D dimmer is likely powerline only. Surprising that it's the one that responded. The KPL's (V.43 and V.45) are dual band. Would have expected those to have responded. The difference between the 2476D that responded, and the KPL's that didn't, is the path that your scene command took from the PLM to the devices. The path to the 2476d is from your PLM, to the panel, and then to the 2476D circuit. The path from to the KPL's is complicated since it uses RF. It should be better due to the dual band capability. Unfortunately, this isn't perfect. I've seen dual band devices Ignore RF communication due to a low level (below noise level) insteon signal on the powerline. My advice would be to investigate the circuit the KPL's are on for signal absorbers/noise. Beyond that, you can use the "scene test" to determine whether "verification" would help here. The scene test uses the Insteon standard method of activating a scene/interrogating the responders. The PLM will poll each device to determine if it responded correctly. If it does not, it will re-try up to 5x. In my experience, the "scene test" shows failures that do not exist with standard ISY scenes. Beyond that, we may need to understand your "house" configuration (plm placement, home sq footage, #' panels, number of devices, other "problem devices") to go forward.

@JJJ, you are correct. While there is a "feature" in the ISY programming to allow you to set a scene to a specific level, it doesn't work. Turning the scene on to any level above 0% will simply execute the scene command at the stored device on levels. Turning the scene on @0% will turn the scene off. Insteon protocol does allow for scenes to be turned on to a level. This feature may have been removed previously when other devices (Z-Wave) started to be included in scenes. https://forum.universal-devices.com/topic/25805-is-set-scene-on-possible/

Device level retries as explained be LeeG: Understanding Retries in ISY

I'm thinking you may have mis-stated things here. You can't activate a scene by turning one a Controller from the Admin Console. That will activate the controller by itself. You have to activate the "Scene" from the admin console tree (or a program). If this was the case, we need to start looking for noise/signal absorbers on the responder circuits.

Are these scenes locally activated (device) or activated from the ISY? Very different scenarios. Device activated scenes will attempt to determine the status of the responders. The ISY will not.

Right click on the program and "Export" to a file, or "Export to Clipboard". You resulting file is a jumbled mess. You can manually insert carriage returns using clipboard, or find a quick XLM viewer on the web.

I'm sorry, I'm not being clear... The following is my guess based on my recent experience with the ISY994 - Your program is not triggering properly because it is not saved properly. Said differently, the program that you posted is not what is saved in XML. It was corrupted some time back and "updating/re-saving" is not changing/fixing the corruption. I saved and copied my program several times to no avail. The XML was still wrong. When you re-save, you are resetting the "last run" status and the state (true/false) of the program. It's possible that is allowing the program to trigger once. Can't tell you why without seeing the XML. I don't understand what I did to screw up my program. It was an isolated case. I had been editing the program frequently throughout the day. The program is very long with numerous embedded waits. Suddenly it began to execute things that I couldn't explain. That's what drove me to look at the XML code.