hart2hart

Thanks. I’ll be on lookout for announcements.

Are you using it?

Given what you have learned about the PLM, I’d likely stay put and replace it with new PLM since a reset will clear it with no guarantee that it will let links be written back to it.

When was 6.0.0 released?

@Blackbird I updated Restore PLM instructions above (for someone reading later) to correctly state hold until beeping stops. The PLM reset instructions are: o Unplug the PLM from the power source. o Press and hold the black "set button" on the PLM. o While holding the button, plug the PLM back into power. o Continue holding the button until the PLM beeping stops then release it.

Keep us posting how its going for you.

I agree with Brian and would not use that PLM as there were several issues as I recall. You'd be better served to get a current Serial PLM. The PLM reset instructions are: Unplug the PLM from the power source. Press and hold the black "set button" on the PLM. While holding the button, plug the PLM back into power. Continue holding the button until the PLM beeping stops then release it. This procedure performs a factory reset and clears all linked devices, requiring you to re-establish communication. Did you mention doing the reset to Michel and then seeing if all the queued up restore PLM links would process after the reset. I don't want you to do something that complicates the situation as I've never had a PLM fail like this and not allow a Restore PLM. Same applies to doing another restore where a different PLM will be plugged in and it goes through updating all devices. I know what I would do if it were my setup, but I don't want to roll the dice at this point for you.

I would say good morning but…. Are you contacting UD to confirm next steps? Likely gonna either be a factory reset of PLM to see if that takes and the Restore can finish or somehow confirming all the queued links to current PLM are cleared so you can replace it with the other one. No worries. It looks like it may have fully upgraded to replace PLM VS restore current PLM.

This is a major error and I read it that the PLM is refusing to be written to. What do you get when you check PLM status? It feels the best advice I can give at this point is to enter a critical UD ticket. Firstly, the PLM does sound bad but a factory reset and then another restore may fix it. However, when doing a Restore PLM, it queues up all the PLM links and then executes them one at a time. Taking additional steps would be best under UD direction to ensure you don’t compound a simple problem that they know how to fix quickly.

Restore PLM with same PLM does not impact devices or programming. I did it about a month ago. It just rewrites all links inside PLM. Again, make sure you have good backup in case something goes wrong.

You are describing Restore PLM where the PLM is being replaced. (I think having a Replace PLM would make it clearer but command does double duty) I commented on when you restore PLM and it’s same PLM so nothing changes in devices. It’s in effect just a refresh PLM.

Restoring existing PLM just rewrites the links inside PLM without the labor intensive need to update every other Insteon device. It’s quick and simple or has always been for me. Regardless, make sure you have great backups. I get your logic about receiving vs sending but line noise has always been tricky to diagnose for me. Michel is the king. It could be that the PLM receives signals fine but its signal strength for sending signals has reduced inside PLM or noise or signal suppression very near PLM plug is distorting or attenuating it. I once used a long extension cord to “move” PLM to another plug that I confirmed was on opposite 120 v leg and away from original location in breaker box as a test. Is your PLM dual band because others reported plugging it into a FilterLinc to in effect force it to go RF to closest dual band device(s) which would eliminate a level of line noise.

As Larry pointed out, it can be a time consuming process but it is actually an eISY strength. On tool bar put battery operated devices into delayed write mode. By doing this you can pick each battery operated device on at a time to put in linking mode and then write updates to them. I had 8 motion sensors and many leak sensors and it never took me more than an hour or two. With that number of devices, 292 links sounds reasonable depending on how may scenes you created. Did Michel have you to Restore PLM to ensure it’s got correct information. Even if it’s going bad, it might tell you it’s PLM as they are typically going bad over time not all at once. You just notice it when gets really bad. I do a restore once a 6 months to a year as a little insurance. All that said, it could be line noise which more likely coming from an electronic devices so when I asked about adding devices, I meant things like chargers, TVs, etc as their power circuits are notoriously bad at either filtering/ suppressing the Insteon signal thinking it’s noise or injecting noise. Sure wished many times that I had a meter to see noise on the AC line. Long ago I added FilterLincs on every thing possible to minimize noise and have a list of devices without them (larger amperage) so if these issues crop up I can unplug them to test. Did you try turning off breakers one at a time to see if issue stopped? Did Michel think it was noise or PLM?

It could be either. There are the old noise trouble shooting steps of turning off breakers one at a time to see if the problem goes away. Typical question is was anything new added to house in the timeframe. However, it’s often a device that’s starts generating noise. The only way to know for sure on PLM is getting a replacement or repairing it by doing capacitor replacements. I’ve been using serial PLM with serial to usb cable since Polisy came out FWIW so getting a new serial may be only way to be sure and I don’t think they have that big a downside. How many devices do you have? Your link count appears to be about 292.

I usually get away by making sure everyone knows I’m doing a test and get a good count. If no one is doing it, it’s likely coming from programs so disable top most folder(s). If motion detectors or leak sensors are part of your setup, it’s more difficult to control. Also, you can look at log during the time frame to see what device had activity and then determine how to stop it for test.

The show PLM links and count needS to be done with no Insteon traffic occurring.

Sorry, I’m just now seeing this update. Virtual is a fabulous plugin. I’ve been using it for great things and it got so much better when you took over development. Is any additional input or testing needed before you public it to production store?

The if folder true will be reevaluated every time the noaa temp changes.

Yes, It’s 401BC51 Insteon address. Those starting my with n are nodes created by plugins.

Take a look in admin console its node address will be something link n02_99 and what you show is its name.

The only update I would like in programming is synchronous execution for runif. As in wait for called program to exit/return before going to next step in current program.

You can update variables via REST interface.

Was the scene turned on by a program? If so it’s a common issue. The eISY sends the scene on/off command but there is no direct feedback from each device in scene so eISY reports that all onto the desired state. I typically issue the scene command followed by a wait of 5 or 10 second and then same scene command again. If it happens a lot for a specific device in a scene then other more detailed trouble shooting should occur to locate underlying cause.

I moved to Rachio this Spring to control 10 zone system because I wanted master valve across the 10 zones. It has been good and I’ve written several programs to integrate it with Flume so I can detect a zone that has locked open or a zone that is not opening. Additionally, in my box of stuff, I have the two retired ez-flora if you’re interested.

Do you have eISY config for catch up at restart?