piconut

I've held off on updating the firmware because I had alot of issues going from v4x to v5, which is why I'm still on v.5.0.14. If I want to go ahead and install 5.3.4 on my system, are there any additional notes about the upgrade other than what can be found here? I've got both Insteon and Z-Wave devices and I think I have a series 500 of the Z-Wave controller (Z-Wave version 6.81.00). Do I need to install v.5.0.16C or any other versions first?

Now I'm confused. When I click on one of my few devices that are in a scene, it shows the device with the little circle icon (movie reel?) like this image. But the image of the PS04.1 On-Off Module I posted above doesn't show that icon so doesn't that mean it isn't in a scene?

I don't know if it helps but these are the options that have been selected for the On/Off module for some time.

There has been no load plugged into the ON/OFF module during these random ON events. There is also no program that includes any reference to the module (with the exception of the one program that watches for an ON event). I should mention too that it is not part of any Scene. At some point in the past, I had a "night-light" lamp plugged into it but it kept going ON when it wasn't supposed to which is what prompted me to just leave it plugged in without any load attached to it and see if it continues to have the random ON events.

Thank you @Techman, restoring the device fixed the links table mismatch problem or that dimmer. I'm now thinking that I have multiple issues/problems going on at the same time which of course make it hard to troubleshoot the problem(s). For instance, I found that I have a plug in On/Off module (Insteon 2635-222) that ghosts ON randomly. I checked the links table and compared it to what the ISY had and there were only 3 entries and no mismatches. I setup a program to send me an alert when that module goes ON. It has gone ON twice in the last two weeks and each time I reviewed the log to see if any other things occurred around the same time but didn't find anything. I also did a FIND in the programs for all instances of that device and I have none, except for that simple program. I also did a factory reset on the device but the problem still occurs. Any suggestions as to what I can do to try to resolve this random ON event with this device?

I had another anomaly occur with one of the same devices as before. In this case, I have a program which changes the On Level and Backlight of the Insteon 2477D dimmer to be substantially less during the overnight hours and then switches back to full in the morning. Once again the dimmer didn't get the commands, or didn't take the commands from the ISY. I opened the ISY console and tried to manually adjust the On Level and then make sure to write the changes to the device and the dimmer doesn't accept it. However, I can control the dimmer at the switch and also from the ISY console. When I compared the device links with the links in the ISY I got these errors:

I realized after I read your post that the only place I was looking for errors was in the main LOG. I guess I've never used the Error Log before. When I ran the Error Log, there seemed to be alot of issues but I have no idea how to interpret it. I didn't find any Error 0 references in the error log. Is there a reference somewhere that I can lookup these other error codes to see if this relates to the intermittent issues I'm seeing? Here is the last two weeks of my error log:

First of all, thank you again for all of the help from everyone who has responded here! My system is comprised of all dual band modules, approximately 95 Insteon modules and 21 Z-Wave modules (purchased since about 2012). It occurred to me that since some of those Insteon devices have multiple nodes (not sure if that is the correct terminology) like an 8 button switch, maybe I have exceeded some limit of total nodes within the ISY? I've got at least 7 of those 8 button wireless switches (2342-222), and 12 motion sensors (2842-222) which create 3 nodes each. All of my dimmers are the 2477D and switches are 2477S. I also have about 15 hidden door sensors (2845-222) which also create 3 nodes each. I have a few inline modules like the 2442-222 micro module dimmer as well as 3 fanlincs (2475F). If this helps, it takes 10 seconds to initially load the console and another 50 seconds to load the Programs tab. I'm embarrassed to say that I have approximately 600 programs. Unfortunately I don't have any experience in programming so I know that I've been very inefficient in writing my programs which probably accounts for my over abundance of programs. I also have 190 integer variables and 30 state variables. I hope that helps explain my installation. I hear ya on the difficulty in troubleshooting intermittent problems. I'm trying to determine if there is some pattern when each anomaly occurs, including looking at the log to see what other events happened around the time of the light not turning on or not turning off. I did have a Philips Sonicare toothbrush charger which started adding noise and I removed that (4 years ago) and things were much better after that. So maybe I do have something else now causing noise. So it sounds like my PLM is not the issue and since I haven't figured out the problem, things might get worse if I tried swapping my old PLM for the new one.

Yes, the 2.6 is on the sticker of the PLM. I just assumed that it was the firmware version. Thank you for the clarification. So are there any risks to installing the new PLM even though I don't know for sure what is causing the anomalies I'm occasionally seeing (haven't seen one since Saturday)?

I have a new PLM in the box that I ordered when it looked like they were going to start to be hard to get. The date code is 1123 (I assume 2023?) and the firmware is 2.6. Does this one have the updated electronics in it?

I'm sure I'm not using scenes. I have about 4 scenes set up but the light problems I'm having are not in a scene or related to the controllers. I only got the "cannot communicate with...device" on the dimmer or switch that was not working correctly at the time. So only one "cannot communicate with...device" message when I logged into the ISY. If no devices seem to be exhibiting the anomaly I'm seeing, then I'm not seeing any "cannot communicate with...device" messages. I also have no devices with the green 1011 so that is good.

The green light on the PLM is lit. The info on the sticker is 2413S , V2.2, 1621

For the last several weeks I've been seeing some anomalies with my Insteon devices where the device will be on when it is supposed to be off (controlled only by a program, not in a scene) or off when it supposed to be on. The issue seems to affect random Insteon devices in my network which are typically either a dimmer or a switch. The problem seems to go away after 24 hours but then crops up in another device (that doesn't respond to a timed command being sent to it). I have an ISY 994i/IR Pro running v5.0.14 (I haven't upgraded to v5.3.4 yet because everything has been running smoothly for several years). I don't remember when I last replaced my PLM but it has been at least 8 years. Here is an example of the latest anomaly. I send a command at 11 PM to a bathroom dimmer switch to change the On Level to 30% and then back to 100% again at 8 AM. Today it didn't work as the on level was stuck at 30% after 8 AM. I was able to double click the switch (Fast On) and the lights came on at 100% but when I just single pressed the ON button, it came on at 30%. I should mention that the dimming functions of the switch worked fine. I logged into the console and ran the THEN statement of the program that sends the command to the dimmer switch to go back to an ON Level of 100% but the switch would never update. I rebooted the ISY and tried resending the command to set the On Level to 100% but it still didn't work. Most of the other cases where I've seen random problems with my Insteon devices have been with a light being on when it is not supposed to be or vice versa. One more thing to add: When I logged into the console and looked at the On Level that was currently set for the bathroom light, it showed it as 100% as it should, even though the when activate by a button press, the light only comes on at 30%. SO that means at least the ISY has updated that parameter value based on the timed program. What do I need to do to track down the issue of these program commands occasionally and randomly not being sent to an Insteon device?

Running v5.0.14 on ISY994i/IR PRO I'm using Network Resources to send the Pushover alert

I have a test program where the IF is just a time and day, so my test program actually runs (and I'm not just selecting the "Run Then"). The test program send a Pushover Alert and also an email alert and they both contain the same two variables ${sys.program.#.name} and ${sys.node.#.name}. In the email alert, it shows up like this: Pushover PROGRAM NAME Test for the ${sys.program.#.name} variable and node[#] for the ${sys.node.#.name} variable. In the Pushover alert, it shows up like this: program[0] for the ${sys.program.#.name} variable and node[#] for the ${sys.node.#.name} variable. So there is a little difference as to what is returned by the variable but I still can't figure out what the problem is.