msfujitsu

In previous versions of firmware, there was an option to set the amount of retries under advanced, PLM communications... which is still there, but now if you try to set the number of retries, you get an error popup with "request failed", yet you see activity in the event viewer scrolling by. When you check it again, the number of retries updated for the module. can someone also clarify when someone would want to use "no retries" versus 2 or even 9 retries? Does the higher number of retries "junk up" the messages on the powerline?

ok after getting the "unused" plm working, then starting the process over for the "repaired" plm, both are working now. I really wonder if there was something going on from Georgia Power because before everything crapped out, some of the lights were flickering on and off in the house. I imagine the "air gap" would have power cycled each insteon device, but pulling the air gap on 81 insteon devices individually was unfeasible. I think killing the power at the circuit panel would have taken care of it, but i had replaced the plm by hot-swapping, and that put a monkey wrench in things. Has anyone ever had something like this happen before? It was almost like i had a brownout before everything went haywire

@Upstatemike ... wouldnt polisy need a modem to communicate with insteon? i cant seem to find either the usb or the serial one on the market right now...

Hello again, I will be purchasing a home in the near future, and I would like to do a HA system again. I liked the ISY (originally purchased in 2011 or 12, upgraded to newest version in 2021), and I liked the ability to create programs to do what I wanted. I have a lot of "leftover" insteon devices that I was thinking of taking with instead of leaving with the existing house when i sell it, but after researching that the insteon plm's are virtually nonexistent in the marketplace, and the so called dual band devices dont seem to work with the ISY without the plm, what can you do? Get another ISY that does z-wave and do nothing but z-wave devices and not deal with a plm? another type of system? does anyone have any suggestions? thank you

thank you MrBill for your reply... I am going to try this again.

I had an earlier version of the isy994-pro that didnt have z-wave functionality. Earlier this year (june 28) I purchased a new ISY that also had z-wave integration. I had purchased additional insteon devices to "complete" the smart home installation in this house prior to putting it on the market. Today, all of a sudden, nothing worked via Alexa, or the UD app on the iphone, or even via the console on my pc. Years ago, I had a PLM die and found someone via this forum in Thousand Oaks to repair the PLM for me back in 2016. I had a spare that I had intended to send to the guy in Thousand Oaks to have him do a preventative re-cap on it, but never got around to mailing it... I checked the "repaired" PLM, and the green led was on and blinking here and there. I had noticed some lights flickering in the house earlier in the day and figured something was up with Georgia Power, when later I found out something had gone haywire. I pulled off the "repaired" PLM and replaced it with the unused one. I did a restore plm in the isy, and it didnt take too long to finish what it was doing, but i noticed i had a number of "ballbats" (!) next to a number of devices. The restore device function did nothing, I had rebooted the ISY and same thing... Finally I decided to kill the power in the entire house at the panel. Everything then showed up in the isy without ballbats, Alexa commands were working again, as well as via the console. I decided to make sure the repaired plm was indeed bad (and at this point it is indeterminate), so I reconnected it, did a restore plm, and it didnt take too long for it to finish. Stuff wasnt working again. The led on the plm was green. Put the "unused" plm back into the system and did another restore. This time, it seems like its taking forever, almost like it is restoring in an endless loop. Afraid to kill the power to the system or reboot the ISY for fear of bricking it. This almost seems like an ISY failure (which is under a year old).