Geddy

@btreinders Very strange indeed. Glad you got them to work though! I'm not sure if UD has any logs they could check out but maybe see if @bmercier or @Michel Kohanim might have some insight as to what might have happened. I try to check out https://alexa.amazon.com/ if there are issues pending by it not operating my lights/programs as expected. But I don't tend to get too fancy with the setup so I don't normally have too many issues.

@btreinders Maybe reconnect the ISY skill in Alexa. It's a pain, but some issues I had a while back (about a year) got cleared up by disabling the skill then reconnecting. Is the Echo working otherwise? It could also be an AWS issue that would make the Echo miss a few things if it can't connect online. About two hours ago we had some issues with the Echo completing a request, but that was about 2pm Eastern today so not sure if that impacts your timeframe or not. If a onetime occurrence then it might be AWS...if ongoing (over several days) try resetting the skill.

@rwelke, sorry you've got this problem, and sorry nobody has been able to help. I'm guessing not many mac users are active here these days to try to help out. I'm not a mac user and based on most of your attempts I would say things should work well for you, but it might be a mac/java issue. Perhaps open a ticket with Universal Devices to see if they can specifically help your case. Open a ticket through email - support@universal-devices.com or through their web site - https://www.universal-devices.com/my-tickets I'm sure somebody on the helpdesk can get you running again. Since you are (or were) able to get the launcher to open and see an IP/URL it doesn't sound like a network issue. It sounds more computer/java related. Do you happen to have any other computers to try to connect with? Good luck!

Let's face it people...all the "big guys" like to talk about how important our privacy is, and they all tout that they do things better than the next guy, but at the end of the day so many of us blindly give information to so many companies that what's the point of privacy at this stage in the game? I mean UD has a box in our house that's connected to the internet that while we hope/assume that it's private and encrypted enough that nobody knows when our lights are being turned on or off or when the garage opens or closes that it's all just a big game. How many of us have iPhones with Google Maps on it with location tracking available? Sure, maybe many of us in this forum subset of a very subset of the general public might take things a little further and actually turn a lot of tracking settings off, but really? Do you really? I mean I know having a young kid I like to know where he is so I rely on Apple's "Find My" to keep up with my child's location. How many of us have elderly parents that you've setup their phone that you can track their position? Come on...I know many of you have done it, or maybe thought about it. Here's the issues I have with Amazon now being in this area...the others already occupy... My ISP charges me for my internet service and holds me accountable for the traffic across said network. Now, I've gone the extra step of buying my own modem and router so I feel as though I can control my network. If I didn't and had to rent an ISP owned modem/router then they leave an additional wifi SSID open to other customers/users of same said cable system. Sure, they say I'm not responsible for the traffic over THAT network, but whose to say I'm not? Now, Amazon wants to use 500MB of my monthly allotment to have a subnet open to smart devices that I might or might not already own sitting outside the range of my existing wireless network while also helping other Amazon customers as they are "near" my house. I don't know about you, but I haven't seen people walking around my neighborhood with their Echo devices in a wagon and a 1 mile extension cord laying around going back to their home so they'd be able to ask Alexa something while they walked by my beautify landscaped yard. No...the problem I have is that I'm PAYING for my ISP and if I did rent your modem why are you (EVIL ISP) benefiting from MY account by offering a hotspot for others to use? Amazon, why are you "stealing" my WIFI to give others access to the internet in front of MY HOUSE? Why can't I charge rent back to the ISP for them keeping an additional network open on my "home wires" that then connect back to their coax network? Why can't I charge Amazon rent on that 500MB/mo that they might use for others to access my network? I mean come on...I'm paying for the Amazon equipment (and paying an annual subscription for Ring video storage) and I'm paying for my ISP network connection. Why not think we shouldn't be able to charge it back to the companies that are piggybacking on what we're paying for? Sorry...have had this bottled up for a while and just had to blow some steam off in the face of F.U.D. to consider the other options that we're missing out on. It's kind of a moment of can't we all just get along? Why not share your network with your neighbor? Why not let somebody that might need to use that open hotspot to accomplish something? Well...it's because people can't be trusted. We all assume the worst in people and therefore people are bad and companies that try to make it better for others must also be bad because we don't want to help others. Well, I'm thankful for this forum in that so many people are helpful to those that need help to understand the ISY and Polisy. I'm glad people helped me when I was starting out that I'm still here to try to help those that might just be starting out or those that have been here a while and just stumble from time to time that ask for help. So I say if Amazon Sidewalk might help somebody that needs that extra little bit of wifi access while passing by my house let them have it. I just hope they're doing good things and not trying to hack my other neighbors wifi to make it look like I'm doing it! Now...flame away...I'm ready! I've got thick skin and have zero fox given. So yeah...let's have fun and smile about life because we can for this moment enjoy what we have to comment/complain about. Keep smilin'!

@willieneal, As @DennisC says the DHCP being set to auto in the admin console is key, but if you can't get into the admin console that's difficult to update. You might need to do a factory reset to have it reconnect to the network correctly. You started off with saying you were able to upgrade to 5.0.16, but then recently you changed routers and that's when problems started. It's possible that the ISY isn't actually on the network or is having IP conflicts as devices jump on/off the network or from if you have a mesh router type devices can jump from satellite to satellite as they get signal interference or move around the house. That's one issue with mesh routers that devices can jump, but some aren't as seamless as they might think they should be and IP changes could suddenly conflict with something that's trying to be static controlled by the device rather than by the router. Since you mention you're running the launcher I would assume then that your UI/FW would match, but are you sure that your upgrade completed properly when you did that or did you just run it and leave it alone after the fact? Do you have a ISY portal subscription? Maybe use the remote access URL to login with the launcher/finder from that direction. Finally, make sure that the Google router is setup to allow wireless and wired devices to talk back and forth. I'm sure there's help on Google products to help direct the settings for those things. I know if you search there was an issue with the Google routers not finding/supporting the ISY, but it was a simple thing of the IP not working right to be in the net network. Ideal setup is always IP Reservation by the router so it hands out the same IP to the MAC address reserved for that IP. Rather than the device (in this case the ISY) "asking" to be put on a specific IP address when it finds the router. 1 - Power cycle ISY and PLM (be sure to plug PLM in first and allow it to stabilize before powering up ISY) 2 - Clear java cache 3 - download launcher - https://forum.universal-devices.com/topic/24381-isy-launcher/ 4 - disable antivirus/firewall (other than Windows defender/firewall) - https://wiki.universal-devices.com/index.php?title=Configure_Firewall_Software 5 - try launcher with local IP, but other option is through ISY Portal URL information If successful to get to Admin Console quickly go to configuration and make sure IP is set to automatic DHCP. Good luck!

@jaycanter If the above doesn't help make sure that you power cycle everything in order. Sometimes things come back online or power up differently when returning from a power outage so they might not be correctly linked. Turn off ISY - unplug PLM - turn off router - unplug modem (wait 20-30 seconds) plug in modem - allow it to completely power cycle plug in router - allow it to connect to internet plug in PLM - wait for light to be on (maybe 5-10 seconds) plug in ISY - check the light pattern (as described above) There's also the IP address conflict depending on how you have it setup in the ISY and on the router. Once the lights are settled on the ISY if they appear to be normal then check your router IP table to make sure the ISY is connected and that it's at the IP you expected it to be at. If you still cannot connect from a computer then run through the java cache clearing process and download a fresh instance of the launcher to try to make the connection to the ISY and log in. If still having issues maybe start a support ticket with UD (support@universal-devices.com) to get their assistance. Do you know what caused the power outage? If a storm could you have been struck by lightning? Could there have been a surge to the house when the power came back on? Good luck! Post back if you're able to get back up and running or have more issues.

@bpwwer not sure what you and @Michel Kohanim might have done in the last hour, but I was just able to log in and get it to display the dashboard within 10-15 seconds of logging in so that's much better and seems to work now. Since I went there before seeing this post I'm not able to get logged back in and have the issue again to try to collect any data. Fingers crossed it's "fixed" or at least working better. Well...it was short lived...errors now. Back to spinning "loading". Sending log through message.

@bpwwer I just let mine sit for about 10 minutes and never populated anything just keep getting "loading" spinning non-stop. Maybe it will work come Monday!

@bpwwer seems to still be having issues. When trying to get to https://polyglot.isy.io/dashboard it just shows "loading" for ages and never stops. If I take off the dashboard and just get to https://polyglot.isy.io/ it will load, but doesn't show my ISY in the ISY list on the top right. I finally upgraded to 5.3.3 and was trying to get some node servers, but doesn't appear to be loading right. Not sure who else to tag on these to see if there's other issues or not. Maybe @Michel Kohanim can check in and see what's up.

WOW! Insteon strikes again. Kind of like changing the on/off switch LED pattern to just the two LED "on/off" visible rather than looking identical to the dimmer with LEDs running up and down the side of the switch. Really kind of a design bummer for those that expand their system over time to have what we think would be identical switches, but have different appearances. Either really smart (for the company to make more money by selling replacement switches to the OCD types that like everything to look that same) or a huge oversight by part assembler and no QC from developer level. Great job troubleshooting the physical appearance difference! A picture truly said it all.

Watch out @MrBill you've started Chapter 1 again!

@KenUD2 Q1 - What is your Firmware and UI for the admin console? (can you get "help" to work?) Q2 - Have you recently updated Java? You might want/need to clear java cache (https://www.youtube.com/watch?v=5I_w4VUR9bA|) and download the launcher again to run admin console to be sure UI/FW match. Since you can log in it could just be that the java client is sluggish and you need to make the adjustment mentioned in the 5.x release notes (https://forum.universal-devices.com/topic/30939-release-530-is-now-available/) It's not likely an ISY issue, but a computer/Java issue and simply clearing cache and redownloading and running launcher will be the solution.

@jpoje, "back in the day" I would send you to the dslreports.com site, but it's not what it used to be for help. Now I might suggest starting at https://portforward.com/ for generic help/discussion type pages. When in doubt just Google port forwarding and start reading. I think even Tom's Guide might be a place to read up more, but it's too commercial for me (sometimes). If you're not needing to access the ISY from outside the network then you don't need port forwarding. While most will say it's not risky it does open up a hole to the network. You rely on the hope that ISY is protected by a password a little more difficult to guess (at least make it harder than the default). I second @lilyoyo1about getting a portal subscription so you don't have to port forward (if you're not comfortable with setting it up). For the cost ($20 for 2 years) it's a low cost option and gives full function with Alexa (yes, with minimal setup, but it's straight forward if you read the steps outlined in the Alexa (or Google Home) forum), as well as giving you remote access without port forward, and abilities associated with the old Network Module. I'm in the same boat as you though with the "ain't broke, don't fix" (just as @MrBill). Just glad you're operational again! Take care and good luck on the research for port information.

@jpoje Glad you're back in business! Sucks when it's a simple thing like the cable being bad/damaged. But that's a simple fix and glad you got it back online! Always glad to be able to help in the process. Take care!

@jpoje, If you can access the ISY through Mobilinc then it's on the network. If the lights are still flashing, but you can reach it with an app then you've got other issues and should open a ticket with UD Support. Are you able to access the ISY through a computer and admin console? Maybe check that everything is loading up right in there. It just seems odd to be able to access the ISY via an app and have blinking lights that might indicate a network issue. Maybe others have further steps to take, but I'd send off an email to UD Support and let them walk you through some troubleshooting.

@jpoje, Have you been able to get into the admin console since you updated to 5.x? If so then it very well could be the new camera or anything on your network if you're not using IP Reservations in the router. Of you have a lot of devices and the router just cannot give out enough addresses (this is typically a problem when people have computers, smart TVs, mobile devices, and switches or plugs that don't require a hub - some internet provider supplied equipment are arriving with limited number of devices able to connect so the available IP range is very low.) Are you using the Launcher to try to access the admin console? Does the finder not find anything if you're local to the ISY? (i.e. you're on the same network the finder should search and find it if the ISY has a valid IP on the same subnet). Check your Router if you see the ISY listed in the IP table. Now, what kind of router do you have? If you're good with tech you know how to log in and check the IP table (attached devices). You should be able to find the ISY MAC address and associated IP address. Then try to connect the finder directly to that IP and see if you can access it. My next suggestion would be to try to turn off as many network devices as you can and reboot the PLM and ISY to see if it's able to reattach to the network correctly. If that helps then you know you've got an IP conflict somewhere. If still unable to get things to work out then open a case with UD Support (support@universal-devices.com) and see if they can troubleshoot a little more detailed.

Have you replaced any network equipment lately? It's possibly a network issue. (but looks like the link on the reply in that thread doesn't exist so go here - https://wiki.universal-devices.com/index.php?title=Main_Page#Front_Panel_LEDs.2FLights) Other steps will require additional information: What Firmware are you using? What's your UI (launcher)? Have you checked that your SD card is properly seated? When you say "fairly new" for latest PLM how "fairly" do you mean? Weeks, Months, Years? Has it been working since the last PLM replacement? Do you have ISY Portal subscription? If so, is it showing the ISY online? You could attempt to reach the AC through the portal URL and reset any network settings on the ISY that way (in case you have the ISY set to static IP and there's suddenly a new router or new network gear that's trying to take the same IP address). Make sure you set the ISY to Automatic DHCP and then handle the static IP address from the router just in case you change routers in the future this will allow you to plug and play the ISY into a new network setup. Report back if not a network issue with answers to questions above. Good luck!

@Larry Lovering - While the process above will get you there if you don't want to factory reset the ISY and you have an ISY Portal subscription you could access it via the ISY Portal URL using the ISY Launcher and access the admin console to make the change on the setup tab to a new static IP in the new network or allow it to se to automatically get IP (DHCP) and then handle it with DHCP reservation in the router. It never fails that more often than not you might not have a "good backup" or "recent" backup and you might miss something. Make sure you clear java cache and get the ISY Launcher (found here) then find your "Admin Console URL" on the ISY portal site and log in with your ISY portal credentials. Then go to the configuration tab and change network settings to "Automatic (DHCP)" and hit SAVE. Then restart the ISY and it should connect to your new network with the new 10.0.x.x. Keep the ISY Portal URL handy if you don't setup port forwarding in the new router so you can access the ISY remotely with any apps or devices you might use to connect to the ISY while away from home. Good luck!

@pmoles how old is the switch you're using? And is it managed or unmanaged? Are you sure you haven't plugged one into a dedicated up link port? I wonder if perhaps the switch has gone bad and not allowing traffic between ports. I'm not familiar with the eero products enough to suggest it might be that. But you said both computer and ISY are plugged into an 8 port switch. Have you attempted to remove the switch and plug the ISY directly into an eero device and use the computer on wifi? Since you can get to something through a web browser/URL have you attempted to telnet into the ISY (https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Telnet_To_Your_ISY)? That might give you help accessing the device differently to check if the switch (or eero) is blocking some traffic or not. Last suggestions is to clear java cache, remove/reinstall java, download new ISY Launcher (https://forum.universal-devices.com/topic/24381-isy-launcher/, and attempt that way. You specifically mentioned that there's no PLM installed yet. Why? Not sure if this would cause problems, but wouldn't this cause the ISY to start in safe mode? Should still be able to get into the ISY though, but would think you'd want to have the PLM active unless what you're doing is setting up a new ISY and using an old PLM. Finally...time to open a support ticket with UDI and see if they can help walk you through some other troubleshooting steps. Email - support@universal-devices.com Good luck!

@vmastros, Thanks for the info. Looks like that's a fairly locked down router and one site I found says only able to set wifi password and port forwarding through a phone app. Are you able to log in through a web browser or is it true to only be phone controlled? If anything I'm guessing that if Spectrum is doing this to their customers then they are probably also blocking most common ports to try to "protect" the users since they seem to think customers are not tech savvy. My suggestion would be to get away from ISP supplied equipment and handle your own gear and setup. That is if you're able to handle it and you've got an ISY so you're already ahead of the curve for most people. Since the router is mostly locked down by the ISP your best bet is probably not to use port forwarding, but to go the ISY portal method. Steps found above or through wiki of how to access the ISY while remote with the ISY portal. Also, thanks @Michel Kohanim for clarifying that UD Mobile does NOT need the isy portal subscription. But, I'm sure it would be helpful for those that are unable to port forward due to hardware or ISP limits. Good luck @vmastros!

@vmastros, I second @MrBill's comment about the ISY Portal. For $20 for 2 years it's a steal (~83 cents a month!) for what you get with it and removes the need to port forward for remote access. Plus looks like the new UDI mobile apps (iOS and Android) will need ISY Portal subscription (or at least work better with one). (I mentioned this option in my reply above.) You still never let us know what brand/model router you're using. Or if you're using a Modem/Router combo that is supplied by Spectrum. Lots of people here have experience with a lot of different brands of routers so might be able to help troubleshoot your settings. @MrBill brought up a good point about the external IP being rout-able so that could be an issue as well. Since you don't use remote access often then it might not a big issue, but still wanted to try to help get it to work for those few times you do need it.

@vmastros Any luck getting things sorted out to be able to access the ISY while away from the site?

The Alexa app won't let you create the same group names, but you would be able to use them as room triggers. Make a group for living room and put the reading lamp and the echo in that group and should be able to say "Alexa, turn lamp/light on". Do the same for the office. Depends if you have other lights setup in the group already. You could possibly change the type to a plug and control it differently or give it a custom group name to help you finetune what trigger you can use. Maybe @bmercier can help confirm if this is possible or steps to do it differently with ISY and Alexa App setup. Trial and error never hurts though.

@vmastros what is your brand of router? Or are you using a Spectrum supplied Modem/Router product? Sometimes it is difficult to manipulate the devices you rent from the ISP. Additionally, while Spectrum might "confirm" that it's forwarded to 443 they might actually be blocking inbound to their customers at common ports. Try a different port on the WAN side to try it that way. Do you have a UDI Portal subscription? If so then you can use the information from there for the ISY address and bypass port forwarding (sometimes seen as more secure because you're not leaving an open door on your local router). From the Portal page go to Select Tools -> Information -> ISY Information the copy "Admin Console URL" and use that and use your portal login/pass rather than the local ISY direct connection admin/pass. But once you give us some more info about the router you're using perhaps there are some here that have experience with the same router to help correct forwarding rules. Good luck! PS: And go ahead and update to 4.9. I am/was like you in that if it ain't broke don't fix it and was on 4.75 and made the upgrade to 4.8 and then 4.9 without any issues. It won't help your problem, but it will keep you up to date on the current 4.x branch so I would suggest doing at least those updates.

@larryllix I haven't had issues on a regular basis, but I don't use the Alexa commands often. I know there have been some issues if Amazon's cloud service is down and have had some issues with Alexa reporting itself offline randomly with other instructions (i.e. turning a FireTV on or changing inputs on primary TV). I can't say it's specific between Alexa and ISY, but perhaps you're unlucky and having the issues when they (Amazon) are having AWS problems.