Geddy

You stopped reading too soon. That multi function button when pressed as described "resets credentials". It doesn't "reset polyglot". I recall having to reset credentials using the button when I first got my Polisy (about a year ago). My assumption would be that it should still be functional that way. I've actually not tried it since IoP was running on the box. Would need to be a question for @Michel Kohanim or @bpwwer to answer. In this case Polisy = Polyglot It appears in the "old" PGv2 screen it's showing as "Polisy Version 2" logging in, but that's just the Polyglot v2 login screen. When you go for the PG3 login you see:

Nice catch. Yeah, wasn’t on my radar to check since FW/UI didn’t match. But power supply is a step in troubleshooting so glad it was noticed. sadly, I have my ISY behind doors so I don’t see the lights often. They’re so bright though! Glad you got things running again.

@Bumbershoot I'm not sure if it would be something I'd attempt on the IoP. I know @Michel Kohanim had advised against that method on ISY994 in the past in the 5.x process. And I'm not sure what he's doing to get people to the point of having that button available in IoP. I'd suggest opening a support ticket and see if there's a process to update specific IoP processes to get that button. Is there not the auto update function available in 5.4.3 IoP? From the release note there's this process: Either way, let us know what you end up doing. There's been several other posts about this and haven't heard back from anybody as to what process they went through to get it upgraded to have the button available. Apparently that button is introduced in 5.4.4 (the most current release).

@AndrewW If you do get the PLM repaired make sure you make a backup before you send it in!

@AndrewW agreed...it's strange, but still...I don't think things were set up correctly from the beginning. They worked as you perceived them to work as you originally set them up. When hub went away you went 100% ISY994/PLM. Did you "change" anything when you did that or did you just remove the hub and hope things worked as they had? You added UD ISY Portal for Alexa connection. That's when you started noticing problems. Right? If you made any changes when you unplugged the hub then you'd have issues when you plug the hub back in because you might have removed the link from the device to the hub. So, did you attempt to re-add any devices to the hub? Still, run a Topology (for yourself). Make sure the ISY/PLM see all the devices you have. Check specifically any "relationships" for devices you seem to have direct linked. If they don't show up in the ISY as a "relationship" then the ISY doesn't know that relationship exists. As I said the other day I never owned the hub so haven't personally tried to have ISY/PLM + HUB to have Alexa support. My devices directly added to ISY/PLM + UD Portal + Alexa Skill (v3) devices work 100% of the time. If you're confident that they're correctly added to the ISY then perhaps it is a PLM issue and repair would be best option (currently). Good luck with a support ticket. I'll be interested in seeing how this turns out. Keep us posted!

THERE'S YOUR ISSUE! Bingo! You've got devices that the ISY/PLM don't know are connected/related. Even if the device is somehow connected to the PLM correctly it's still got direct links in there that don't feed back to the ISY/PLM. These are the half links people often mention. It's worked "fine" for the last 9 years because the Insteon Hub didn't care about it and you used the system with a hub and direct links and it worked as you designed it. When you went 100% ISY/PLM you need to set your system up as a NEW system. This means removing any direct links and links to the hub. You should run a Network Topology report and see what devices are actually connected to ISY/PLM and if there are some odd issues in there. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Generate_Topology No, that's only UI driven. It wouldn't impact any operations of the ISY (mostly anyway). It would just mean you wouldn't see options/programs/scenes correctly if you were running FW 5.x and UI 4.x. As soon as you match FW/UI it should all be better. Especially increasing the Java (as you said you did). Make sure it's still set that way. Sometimes in Java updates it can clear that setting out. It's a little strange as it doesn't always happens, but I know I've set it up on my primary computer I access ISY and every now and then that setting seems to be gone. Not major issue, but I notice a little lag here and there. Yes, repair might be suggested. Do you happen to have a spare PLM at present or just the one? I know @gadgetfreak sent in two PLM to this person and reported one came back fine. Hadn't heard about the other one, but would have to assume it works. I'm sure if you open a ticket with support they can help direct you to troubleshoot the PLM to get a better idea of if it's bad or dying. It's possible, but not your issue so I wouldn't advise it. You're up to 5.x now. Just fix going forward. I think the only fix for this will be to start fresh, or at least factory reset the trouble devices.

How are things running? Did you attempt any other settings adjustment since Monday? Hadn't seen any other posts so figured you had given up or gone a different route for help. The above portion of an earlier posts gives me some concern...I'm hoping that it's just how you're trying to describe things, but wondered if it's also the setup of your system too. Did you eve direct link devices? device specific scenes rather than setup through ISY? I think this was done a lot by Insteon Hub users "back in the day". And I think somehow the Hub could manage that or it just worked for them. When you're in the ISY/PLM method that's not advised. So when you said "device-to-device" it made me think that you've got device based links. If you haven't done anything I think it's time for you to open a support ticket and see if they can help you out. One final advise I would give is to check you Java settings and see if you have it set for higher memory usage. The 512 can also be changed to 1024 if you're on a system that has a lot of system memory. That "might" help some, but not sure. It's another tool in troubleshooting to attempt to resolve admin console issues. However, you can start a ticket either way below: Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com Good luck! Post back what fixes this so it can possibly help others that might run into this issue.

@tedolsen thanks for clarifying. Just seemed really strange. If you're still having issues then I'd suggest opening a support ticket with UDI. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com It seems you've tried almost everything. I think if you're having connection issues just changing the microSD card might not really be the fix for you since you have to have it make a connection to the network for you to be able to telnet into the unit to install the firmware on the new microSD card. When you submit your ticket make sure you mention you have 2 different networks and it will not connect to either and be sure to have a clear explanation of the light pattern. It might even be good to take a short video of it and attach that to your ticket. Good luck! Please post back once you get back online what the solution is so it might help others that might have this issue.

just to confirm...you're using a wire to connect the ISY994 to some network device. Right? The ISY994 DOES NOT HAVE WIRELESS...you say you can't get it to connect to a wireless network...how would it? Have you attempted to plug the ISY994 into the AT&T gateway and it still won't connect? And you put it in DHCP status recently?

Why do you have 2 devices handing out IPs on your internal network? Have you always done that or are you setting up new routers? Do you mean to have two different wireless networks? They can't talk to each other since two different devices are handling the connections. Usually this is not an ideal situation. Either the AT&T gateway should handle everything or it should be put in bridge mode and let the eero device handle everything. Since ISY994 is hardwire only and not wireless which device are you connecting it to? I still think this is Network related. Especially since you said you let eero handle one set of IPs and AT&T Gateway handing out a different set of IPs. Sounds like you're connected to the eero and it's not actually sending anything out to the internet. Connect the ISY to the AT&T gateway and see what happens. I think @Techman and @MrBill might be onto something too about the SD card, but my thought is that it's still network related. I think what @Techman pasted above (from the Wiki) just doesn't clearly say the RX light would also be on. If it's always trying to make an internet connection then I think the RX would be on because it's trying to communicate. The flashing memory and error are what are indicating network issues.

@GFuller01 moved your post to a new topic since you seem to have multiple issues and not really related to prior post you tagged on to. It's possible the ISY was setup for Static IP on the device and when you connect it to the current router the DHCP table is different. Therefore the ISY is unable to connect to the router. Have you ever used this ISY? Even though you say it's "NEW". Is it "new to you", or was it still in the box new and never been powered on? What does this mean? You mentioned scan link (from this post), but does it show up on your network? Make sure you've connected all the cables to the correct ports: Be sure you plug the PLM in first and allow it to power on (about 15-30 seconds) then power on your ISY. Please refer to the ISY Wiki for additional setup and troubleshooting steps: https://wiki.universal-devices.com/index.php?title=Main_Page

I don't think this has been covered anywhere. My suggestion would be to open a ticket with support to make sure any steps needed to be done are done in the correct order and the process. It might be different depending on package versions being run. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

@tedolsen Please refer to the wiki for what the lights mean: https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs.2FLights What brand router are you using? If you have auto DHCP set on the ISY then log into the router. Does the router show the MAC/UUID connected anywhere (new IP)? It does seem that you're having network issues. Do you have ISY Portal activated for this device? If so, log into my.isy.io and see if it is reporting the ISY online. That should at least give you the remote access URL that you can use to get Admin Console to load (remember to log in with ISY Portal user/pass). It's always best to set a DHCP reservation on your router rather than static IP on the ISY. For this case for sure. If you change the router and available networks it might not be able to connect if the ISY is set to get a a static IP that's no longer being offered from the device handling DHCP routing. If you have a PLM make sure that it is powered on and connected before you power on the ISY. It's possible that putting the network into the PLM port and the PLM into the network port (on a ISY994).

@EricBarish I've never had this experience. If you're setting it up in ISY Portal and then instruct Alexa to discover devices it's instant. I don't use variables, but for any device (ISY, Hue, Kasa, or Wireless Tags) I've never had to wait 24 hours for them to show up in Alexa. Setup the device through my.isy.io. "<echo wake word>, discover devices" couple of minutes later all devices are added to Alexa. Can confirm in Alexa app and on alexa.amazon.com -> Smart Home -> Devices If you're having to wait 24 hours for a device to "show up" on the Alexa app then you are having service issues. Hopefully @EMercado will let us know what fixes this. I think @Athlon identified the issue that the Alexa Skill wasn't enabled (and linked). Makes the most sense. Also an oddity that I've not experienced, and I have several devices that have ramp rate about 1-2 seconds at various times of day. Perhaps you should review that further. If you have issues, and it's troubling to your setup you should start a thread in the Echo area of the forums and tag @bmercier as he's been the primary one to review ISY & Echo issues.

@Bernman Glad you've got the launcher working and see the device. Try the default (admin/admin) first just to be sure that's not it. Then good luck hunting for that information!

Welcome back to the forums. Good luck with what you want to attempt. Just to be sure...make sure you do have an ISY994 and not a very old ISY99i. When was the last time you attempted to access the ISY994? Were you able to get admin console to load? If you can open admin console please go to "Help" -> "About" and post your screen shot of the firmware and user interface you are using. If you cannot (or have not) access admin console recently note: ISY Launcher - a new process for accessing the ISY Admin Console; released in 2018 in this post: https://forum.universal-devices.com/topic/24381-isy-launcher/#comments This method does not require a web browser to remain open as the old (now, very old) process used to. Since most browsers don't directly allow that java process to run. Firmware - If you are on Firmware 4.x then you can use the auto update process to get up to 4.9. This is the last version in the 4.x branch and the auto update to this level does not require much involvement. Release notes about changes in 4.9 are found here: https://forum.universal-devices.com/topic/31907-release-49-isy994-last-release-on-4x-branch/ Update - If you're feeling more adventuresome and wanted to venture into the 5.x world then get ready for some work. It's quite a process and requires that you follow the steps very closely. Make sure you read all the update process steps before attempting so you know what to expect! Since you say you have "simple" programs that are mostly just timers you might not have much to adjust, but if you use scenes and "adjust scenes" in programs then you will have more to adjust. Current release for 5.x branch is 5.3.4 and can be found here - https://forum.universal-devices.com/topic/33287-534-update-for-isy994-july-30-2021/ Ultimately, it's up to you to determine if you're good with how it's running just to make your minor adjustments and let it keep rocking & rolling. Otherwise, you can update to the version you're most comfortable with. I might suggest just going to 4.9 if you're already at 4.x just for some slight bug fixes and modifications through the years. Since you don't have a current need for node servers and aren't running a new Polisy then 5.x isn't really necessary. Finally, for review and tips and other help please review the ISY Wiki - https://wiki.universal-devices.com/index.php?title=Main_Page Let us know what firmware you're currently running and be sure you confirm you've got an ISY994

PLM -> wait a bit (I think light should be solid green?) -> ISY Make sure PLM is plugged into correct port on ISY994. Make sure your ISY is connected to your router via network cable (again using correct network port). Make sure your ISY is online. Go to my.isy.io and log in. Confirm there is a green dot for your ISY. If you hover over it then it should show "online since...". If not online then perhaps your ISY Portal has not converted over correctly (since you said you had Mobilinc previously, did you have/use their portal?). Make sure ISY Portal is active on the Admin Console. You should see this on the Configuration -> Portals tab in the admin console: Did you follow the steps to switch from MobiLinc to ISY Portal - https://wiki.universal-devices.com/index.php?title=Main_Page#Switch_from_MobiLinc_to_ISY_Portal I would try with your old PLM first. Using a different PLM is a little more complicated than just switching one out. There's a process you have to follow.

@EMercado Also, check the Alexa App for devices to see if they appear there. There's also a way to check from a website by going to https://alexa.amazon.com/ and the clicking on "Smart Home" -> "Devices". You should see the things you have setup in the Portal in this list and should show "ISY Device address" under the device name. If you don't have devices showing up on the Alexa app or on the website then @Athlon is probably correct that you haven't enabled the ISY skill for Alexa to fully complete the connection. Alexa skill information: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3

@tritip.films What MacOS are you running? Sometimes Mac users have quick success with ISY Launcher. Other times it's a struggle. I don't know why, and it's strange. Even some that it works great for months/years suddenly will have a time it doesn't want to pay well. To me it's just Mac+Java = issues. Make sure you've followed the steps mentioned in the wiki for MacOS users - https://wiki.universal-devices.com/index.php?title=Main_Page#MAC_Users What brand is your router? In your image above you say the *.36 IP is not for the Polisy, but does appear to be for your original ISY994 box since the UUID matches. Check your router IP table (connected devices/DHCP table). Make sure your IP for the UUID/MAC address is what you think it is/should be. Something is reporting the 192.168.1.36 address as an ISY. To me that means you don't have DHCP reservation for your ISY994 box and it's changed. Are you able to log into devices at both the 192.168.1.16 and .36 addresses? Or does only one connect? While logged into your Router look for the MAC address for your Polisy and make note of the IP address. Then in finder add the IP address as described in the Wiki Polisy User Guide (https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Can.27t_Find_Polisy)

@MNicholes Do you have 2 step authentication turned on for your Google account? If so, I think this might be a case where you would need an app specific password for Google and apply that to the node server. Using your Gmail address as the user name and the app specific password for the node server setting. Learn more about that from Google: https://support.google.com/accounts/answer/185833 I don't use this specific node server and haven't changed the MyQ app to use my Google account so can't help specifically, but knowing that Google no longer allows unsecure apps to sign in with just user/pass you have to have the app specific password option. So think this would apply in this case. Give it a try. Let us know if it works.

Don't pull that hail mary until necessary! You're not there yet... Log into your router to make sure you see the Polisy IP address from the router. It's possible that you didn't have DHCP reservation for the Polisy and it's changed. Some routers cannot handle the https://polisy:8443/desc routing and must use the IP address. Were you able to use the polisy:8443 url previously or relied on IP address? Also, since you said UD Mobile can access, the device is online and accessible. It's simply that the local IP might have changed. Can you surf to the PG3 web interface? (<polisy IP>:3000)

@Chris McKean glad you got them working! Probably didn't need to remove them, but perhaps could have restarted polyglot for it to force the connection to the IoP once the credentials were correct.

@Chris McKean It's possible that your password for the setup for the IoP is not correct and it's not able to make the connection to the IoP process. If you edit the IoP do you see the eye/show icon (seen in the link posted above). Review your password to IoP to confirm it's what you use when you open admin console for IoP. I'm not much help with reading logs, but review the main logs for PG3 and see if there are some errors trying to connect to IoP. Perhaps @bpwwer can help with an idea of what to look for if Polyglot is not able to sign into the IoP to setup the nodes. If nothing is being sent to the IoP then last attempt would be to remove the current IoP settings and set it up again. Being sure to add user/pass for the IoP specifcially. You'll get a warning that things will be removed. So if you've setup IoP make sure you make a backup so you can restore if you remove the IoP. Currently there several different areas you need to enter passwords and each one might be different.

Thanks to a little help from @bpwwer the trick is the IP has to be formatted in an "odd" way that I wasn't expecting. I fixed in my PG2 node server setup and then added in PG3 and it worked right away. So, I think it should also work in PG3, but check and confirm if you don't mind. Key = bridges Value = ["#.#.#.#"] (MUST have the square bracket AND the quotes) In PG2 see below: As soon as I set that and restarted the node server it told me to press the button on the hue. After doing that nodes filled in right away!

@k.root did you ever get this sorted out? I recently ran into this issue and finally got it resolved today... You need to add a custom configuration parameter with the bridge IP address. Otherwise the node server is always looking at the old IP address. The IP has to be added in a strange (unexpected) way with square bracket and quotes. See image for how I added bridge IP value and it worked. FINALLY! KEY = bridges Value = ["#.#.#.#"] (MUST include the square bracket AND the quotes!) (Honestly, the configuration help does state that, but I just took that to be what it's looking for, but it really is looking for the brackets and quotes. Very odd...IMO) Hope this helps!