Athlon

Agreed

You Da Man!! That did it!!!! Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!

Thank for getting back to me. Using my browser, I went to Settings/Polyglot Settings and made my username and password the same as I use to log into my admin console using the ISY Finder. The message is still there, and I cannot add any NodeServers. Using my browser, I also changed my username and password in the Profile section to the same to see if that would help - it did not.

I have ISY running on my new Polisy, and I've added a few Insteon devices. They are working great. I've also linked some of those switches to Alexa - she's controlling them perfectly (even the dimming commands), so my Portal is all good as well. Next, I'm trying to add some NodeServers, however I cannot get past this message in red on my Dashboard: ISY automatically discovered at http://192.168.50.29:80 however the username and password need to be set in the settings menu. I've changed my password in a few different places in the settings menu: Settings/Polyglot Settings and Settings/Profile. Originally that red message had a different IP - something like 192.168.1.10 - however my new router's addresses all have 192.168.50.x. Although I removed Polyglot from my Raspberry Pi (192.168.50.115), I have that turned off for now just in case. I changed the IP to 192.168.50.29 (address of the Polisy) in: Settings/Polyglot Settings and in Settings/Policy Configuration. I'm stumped - I can see the Store and request a NodeServer, but I cannot add it.

Yep - I'm a tinkerer also, and forget to back it up each time as well. We just had a new roof installed which included blackout shades for the skylights in the family room. The look on my wife's face when she first used the remote for them was priceless. She said "I love these!". I'm currently looking for an automated solution for those as well. (Velux io-homecontrol) Like your's - my wife has embraced our 'smart' home over time as well.

Thank you! It's been a while since I set up my ISY and do not remember that. I have to say living 5 days without what my wife calls 'the brain' is weird ?. Imagine this - we have to walk to a switch to turn it on ?.

Just to be clear - I can go one room at a time after I plug in the new Polisy, install the ISY software and complete the setup?

I have a new Polisy on the way, and I have two questions about that: 1) @MrBill recommended in another thread of mine that I reset all of my Insteon devices for a smoother installation of my new Polisy. I got to thinking about that. Should I reset everything before plugging the Polisy in for the first time so it doesn't detect what I have now, or can I do that one room at a time after plugging it in for the first time. I guess I'm looking for the best order of things when it arrives. (I have about 40 Insteon devices.) 2) How do I remove Polyglot from my Raspberry Pi? (Obviously I won't be needing that on there anymore ?.) I watched those great videos by @einstein.42 to get it installed, but I cannot figure out how to remove it to reclaim some space on there. I've looked at a few websites about how to remove stuff, but if there is an easy method to target just the Polyglot install it would be great to know that command.

Well, I'm retired and enjoy doing puzzles. That is how I'm going to look at it. ? I would say I have have about 40 Insteon devices and an equal number of hidden TP-Link devices. I'll just do one room at a time and re-write my programs. I'm copying them to text files right now, as a matter of fact. Also - I'm currently running Polyglot with three nodes on my Raspberry Pi (along with a Plex server on that thing). Roomba (just to text me when it's recharged itself), TP-Link and Ecobee (3 smart thermostats). I'll actually enjoy the migration, but then again we'll see when I actually start the process. So I'll have to go to each Insteon device and reset them? Thanks for letting me know. I have one in a ceiling fixture (forget what it's actually called - micro switch I think.) Thank you for the heads up!

Thanks everyone! I just ordered a Polisy Pro. Hopefully one of my PLMs will be ok. Was going to get one later this year, but what the heck ?.

Will do and report back.

I'm certainly no expert here as some of you certainly are, but I'm beginning to suspect I have two bad PLMs (one right out of the box though - purchased this year) or a bad Port A on my ISY. What I don't know how to do is diagnose Port A - if possible.

Because Teken suggested I use that one. (About 4 messages above this one.) By the way - the PLM restore did not work.

Before doing so what does the system indicate as the PLM connection state? Not connected: 0.0.0 0v (From Tools/Diagnostics/PLM Status) Connected and displays the Insteon ID? No? If you also press on a switch (locally) does the status reflect the same in the AC and vs if you turn on / off via the AC? Nothing is showing the status of anything (even after physically using a switch). If you select query (right mouse click) and it turns back to normal you’re good. If it remains red dollars to donuts the PLM restore needs to be done for at least the new 2413S PLM. As you can’t just plug it in and hardware will operate as the PLM isn’t linked correctly to the Insteon hardware / ISY Series Controller. Going to do the restore now on the new one and post my results.

I've done that - did a firmware update (5.3.3 to 5.3.3) using the link with this text: "ISY 994i ZW, Z, or ZS Series (Z-Wave/Zigbee and/or if you do NOT have a PLM)" When I went back into the admin console I had to dismiss a bunch of dialog boxes - one for nearly each Insteon device I have. As expected, I did not get the little cry about safe mode. All of those Insteon devices have an exclamation mark next to them now. What do I do next? Restore the PLM from the file menu?

I get the little cry about safe mode. I'm not sure what you mean by the 'controller' to be updated.

I need a little help on how to change my SD card. The one I have is my Raspberry Pi backup - how should I reformat it before I stick it in my ISY?

Alternate PS (old 9v Asus wall wart) did not help. Now about to try a new sd card. @Teken - I may ask for a recommendation on a UPS when I get this thing up and running.

Because of what you said here, I went to the wiki and indeed it says if only the PS blue light is lit, it may be the PS. I'm searching for one now in my spare parts box. Will report back here again...

Thank you. I tried a new cable and still no joy. So, to recap, I've tried two different PLMs (including one that's never been used before) and I'm still in safe mode. What can I test next, if anything? By the way, the ISY finder works and I can log in.

Thank you for replying so quickly. By the way, we had a very brief power outage yesterday - less than 2 seconds - and that's when my ISY stopped communicating with the PLM. I unplugged both the PLM and the ISY. I first plugged in the PLM (the 'new' one) and waited about 3 or 4 minutes, then I plugged in the ISY. I still get the message about no communication with the PLM on my admin console. How do I know the PLM is fully powered up? The green light comes on immediately. Also - I have not tried a new cable yet - my wife and I are going out shortly - will try that in the AM and report back here. I have to say though that the cable on there has been on there since day one, and the ISY is in a very protected area.

My ISY is in Safe Mode. I rebooted it and the PLM a few times. I then installed a new PLM I ordered and received about a year and rebooted the ISY. The ISY still in safe mode. What do I do next?

@johnstonf I'm not going to presume to answer for larryllix, but my guess is the lesson is we are all at the mercy of any cloud services we use (in this case AWS). That's all he meant to say, I believe. UD is relying on AWS for the portal, and obviously by extension so are we. When AWS has issues, so will we. Thank goodness it does not happen very often. I use Gmail and even they 'went down' for a short time last week. It happens - that's the lesson. There is not much you can do about it except to minimize the number of cloud services you rely on. I'm sure UD did everything they could if AWS needed them to repair the issue. EDIT: I'm mentioning AWS because someone else did in this thread - I don't know exactly what caused this issue. I believe larryllix's comment was directed toward cloud services such as AWS, however.

I believe by 'we' he means all of us.

All is well here as well.