Geddy

I will assume you have ISY Portal since you are tying to control through Amazon (Echo) so will ask if you’ve logged in and added them to the Alexa interface so you can then control them with the UDI skill on the Echo? it sounds like you haven’t properly followed the directions to upgrade firmware and having MAC issues with Java and admin console, but also haven’t added new devices to the Alexa connection through the ISY portal. Good luck fixing the issues. Try to focus on fixing one issue at a time so you don’t mess too much up.

@Michaelv Did you only adjust the java runtime memory? What's your current Firmware and UI version screen shot? If still 5.3.4 (FW) and 4.9.0 (UI) you didn't clear Java cache correctly. You've got to follow the directions. Post a screen shot of your about to verify FW/UI match. The communication issue is often not matching FW/UI or could be more involved with the powerline signal from the PLM. Do you have any battery devices?

@Michaelv read my post above and follow the directions for Launcher. Make sure you clear java cache first (you shouldn't have to do it every time if you're doing it correctly).

Glad you got it working the way you want it! (even if it did take some time) Don't give up on the motion sensors just yet. I'm not sure how old they are, but something seems to make me think that some would work better in the 5.x firmware. Other's can support this, but let us know more about what motion detector you have and maybe somebody that has experience setting them up can get you into using them (again?). As another note make sure all your programs loaded correctly in the new firmware. Check out the summary page and make sure none are yellow. If you had any "adjust scene" settings in old programs they probably didn't convert properly and will need to be updated. Finally, you'll have a hard time finding a backup PLM right now. They're currently out of stock at Smarthome and very limited (and expensive) in aftermarket. If what you have is working hold tight. They might come back around once the supplier is able to source all the parts again. (I know many on here might think/feel differently, but there's always hope!) There's usually not much need for a "backup" ISY as the fail rate on those is very low. (@Michel Kohanim recently shared some information about that in another post.)

If you're able to get the about screen then you should be in the admin console and you solved your first issue. Are you still having java issues? If you don't have Z-Wave then you can upgrade all the way to the latest build 5.3.4 (even if it's a "test" build, it's very stable and the most up to date). You don't have to go to 5.0.9 first you just need to be sure you read the directions of the upgrade to know what admin console to load. Loading from the launcher referenced in this post is the best way to always have Firmware and UI match. It will put an icon on your desktop (I assume you're running Windows(10?)) (see below) Then next time you can just double click that icon and it will load the ISY Finder and if you're on your local network with the ISY it will find it. Then click the row for your ISY and then "Admin Console" (cloud or lan are fairly interchangeable at this point). So first - Did you resolve your initial issue of having "unable to launch application"? Are you currently using the launcher to access admin console? If you're ready to move ahead and update/upgrade then go to the 5.3.4 release thread and READ (and take notes) of the steps to upgrade. The most important being to backup and to make notes of your programs (it's often suggested to select the entire program root folder (usually "My Programs") and "copy folder to clipboard then paste them in notepad (or any text editor that doesn't auto format text). Good luck! Report back any issues you're still having.

@SMiller I'm sure others will have options to try and hope you can get this solved, but with the switch installed have you run a Topology (In admin console menu Tools -> Generate Topology). That should spit out all devices and scenes the ISY knows about. Look in the scene portion for that keypad and remove it from that scene. Otherwise, I would think if you factory reset it and then made sure to clear links when adding back into the ISY it should do the job, but again others have more experience with that than I. Here's even an old post on how to change from 8 button to 6 button in case you want to try that even though you said you don't think you converted it to an 8 button, but just as another step in the process. That post links to the owners manual to give you other resetting steps to try. https://forum.universal-devices.com/topic/16971-converting-8-button-to-6-button-kpl/ In fact maybe try this (from the manual): Good luck! Let us know how you progress.

Not sure what's causing this, but a few questions to try to give others additional information so they can maybe help: What's your current firmware/UI versions? If you're using MobilincX do you have a Mobilinc Connect account? Has it possibly been canceled or expired? Or it might now allow you to use an ISY Portal account. Make sure it's still current/active. Are you running Polygot locally? Have you power cycled the ISY since "removing" Polygot and MobilincX? If it's a Mobilinc issue maybe @InsteonNut can help with support from there. There are a few other forum posts that reference AutoPin CSL55, but doesn't seem to be a root cause to point to just what to try to fix.

@brockp can you create scenes in the device you have? I've got the Somfy shades, but went with the mylink wifi controller. I don't have it integrated with the ISY (never wanted to go that far), but in there I can create scenes that lower/raise the shades to the "my" setting. I can then add that setting to Alexa and tell Alexa to turn the scene on. Not sure how the z-wave device works so if you can't set specific scenes in there it might not be possible for you (as Techman states).

Yeah, I've had issues with Chrome just blinking on PDF downloads sometimes. It's not all the time and it's been the last several builds of Chrome. Usually have to open link as a new window and refresh and it will download properly. Then if I reboot the system usually it works. Just most days it's never a good time to reboot the computer. I've just started using Firefox again and have enjoyed it some. I can't bring myself to using Edge since it's based on Chromium. Glad it was browser issue. Simple solution!

@SGoldband odd that UD support has "gone dark" they're usually very supportive for all tickets. I can't offer much help with the PGC side as I've just started using them myself, but know they've been a little temperamental to use since a few weeks ago they seemed to have lots of problems. I thought I saw those problems were resolved, but as part of it some cloud nodeservers were removed. Look for a post from @Michel Kohanim elsewhere in the forums about that maybe 2 weeks ago now. On the Alexa side try logging into the Alexa web page (https://alexa.amazon.com/) to see that you have devices in the smarthome list to see if the UD skill is properly connected and getting information from ISY Portal. Then be sure to go back to the ISY portal and check that the license is still active: Tools -> Information -> ISY Portal Access License Finally, even if everything appears to be correct I would say go back to the Alexa site and go to Smarthome -> Devices and remove the ISY devices. If you have lots I would "remove all". Open the app on a mobile device (do you usually use phone or tablet?) and disable the ISY skill. CLOSE/kill/stop the Alexa app - just for the sake of killing/stopping the app reopen the Alexa app Enable the "ISY Optimized for Smart Home V3" skill. Link your ISY Portal account. Tell Alexa to discover devices and let it run to completion. It should tell you how many devices it found. Go back to the Alexa website and make sure it's added back the ISY items. Then try to use them through voice commands to Alexa/Echo. If still having issues make sure you're emailing UD Support (support@universal-devices.com) or using the ticket system on their site. The PGC issue might be lingering effects of the issues they had a while back. Support from UD is the best way to get those issues looked into. Good luck! Post back any updates.

@Roman make sure you aren't sending to many emails in close timing as that can also trigger SPAM filters and cause negative impact from the sending server (if you're sending from the default server that could possibly impact other users down the road). I would suggest sending/receiving from free email services and make sure you're setting up a new account for the send side just to keep it off your primary if you have one (i.e. gmail, yahoo, or hotmail/outlook). When I first setup notifications I was using my isp email to receive and would have some times that I wouldn't get messages I expected. Then I switched to sending from gmail and receiving at outlook and seemed not to have as many issues. Another thing is to be sure that your program to send the notification is indeed setup properly. If you're getting some notifications about the specific state variable you are monitoring then it sounds like it would be setup correctly, but perhaps you're getting notifications from another program and the state variable one isn't setup exactly right. I think somebody above had also suggested pushover for phone notifications as an option for notices if you want redundancy so you might not miss any notifications. I don't use that so cannot help with the setup, but there are many posts on the forum about it and how to set it up that I'm sure you'd be able to find it through searching or Google Site Search.

@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!

@ssherwood Glad you got it sorted out. Sometimes the 8 and B can look a lot alike. I think 5 and S also sometimes appear close to the same. You can also link devices without typing in the code by putting the ISY into linking mode and quick click of the "SET" button (3-5 seconds maybe - I think it beeps at you). Then be sure to always select "Remove existing links" before hitting finish. This clears out any prior links and gives you a clean start to setting up the device. Make sure you've got the ISY Cookbook to help you along the way - https://wiki.universal-devices.com/index.php?title=Main_Page#ISY_Cookbook

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.

@Roman Did you change your port to 465? From a search: Outgoing Mail Server Account Type: SMTP Username: Your email address is your username Server hostname: smtp.cogeco.ca Server port: 465 Authentication: Password SSL/TLS: Yes Perhaps that will help. (Otherwise, it looks like port 587 might also work, but I find mentions for both ports working for that ISP) I'm not sure on this one. Perhaps @MrBill can chime in and help out on this aspect. I would expect that if the emails can send anything you had setup (and working in the past) would start working again as soon as the email server can send out emails. If you just upgraded to 5.3.3 from something 4.x make sure that your programs are active and there aren't any errors or inactive programs that you think should be sending you messages. (I can't help so much as I haven't upgraded to 5.x yet, but I keep thinking about it.) Maybe check in the email customizations that you leave the "from" blank so it uses the default settings of sending email. I've never used a different address in that line so I'm not sure if you have your @cogeco.ca address in that "from" line and maybe the default web server isn't allowing that setting. Just a hunch, but again, never tried using a different "from" address in the individual notification so a shot in the dark for me.

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.