Geddy

@ndorny perhaps before you get too far into it you might want to at the very least upgrade your Firmware to the latest 4.x level (4.9). It had some improvements along the way, and is the last automatic update process that should be fairly straight forward and "simple" to perform. Make sure you backup the ISY first! You can find what's updated in 4.9 in this post. Make sure you follow step 2 - This step tells you to clear your java cache and download the "Launcher" so that User Interface (UI) and Firmware (FW) match. If you don't upgrade make sure you're currently using 4.6.2 for both UI/FW or you might run into some problems if you go changing a bunch of things to get them into the Alexa system. Once you're up to 4.9 then follow the instructions @lilyoyo1 posted above to activate the Portal with Universal Devices. Then go here (https://wiki.universal-devices.com/index.php?title=ISY_Portal_Amazon_Echo_Integration_V3) to get directions how to setup the Alexa UDI skill. That should get you going the way you want...currently. If you really want to get creative you might look into upgrading to 5.x, but there are a lot of detailed steps to that so I might suggest you just stick with 4.9 for now. If it's been working the way you like it and all you really want to do is have Alexa help turn things on/off this is all you'll need. Good luck! Post back if you need more help or if you're successful.

@greazer I know you found it, but in case you needed more help maybe these videos will help...they're a little dated, but I guess the thought behind them should remain fairly constant. I've never done anything with a rpi so this is as close to help I can give. https://youtube.com/playlist?list=PL418LHgc2F6uttVUW4cSDlpuX4BewQk8Y Here's an early post about installation steps: https://forum.universal-devices.com/topic/18093-polyglot-installation-instructions/ There's also some documentation found here: https://www.universal-devices.com/developers/polyglot/docs/index.html PS: You've tried to tag us in some replies above. Make sure when you're doing that when you hit the @ sign you'll start to get a spinning wheel and then as you type the name the person you're trying to tag should show up. You need to select the name to make the tag stick. (Either down arrow & enter to select the name or mouse click the name you want to tag)

Quick, and maybe simple answer: Neither are "required" (currently) to run node servers. On ISY 5.x you can run node servers from Polyglot Cloud (https://polyglot.isy.io/). This seems to be what you've been doing... You appear to be running Nodeservers on the "cloud" (Polyglot Cloud). You can continue to do that without Polisy or rPI units, but the future path might alter (pure speculation) that would make them not work for your situation or not get updated. Polyglot 3 is in development and will replace current local usage of nodeservers. If what I've seen talked about elsewhere (and don't have all the links currently) Once Polyglot 3 is out it would be wise to have the Polisy to support those efforts. Otherwise, I see that Polyglot 2 would still be supported on the pi, but again, not certain all developers would update the existing nodeservers. Have you read all the setup steps on the cloud version? https://github.com/Einstein42/udi-ecobee-poly#readme It appears in a recent update a PIN is no longer required: Perhaps @Jimbo can chime in with additional steps to troubleshoot, but make sure you're going through the current setup process. I'd say when in doubt it might be best to remove and re-install the node server on the cloud settings. Careful though because I've also seen suggestions to reinstall it in the same slot that it was originally in. Hope that helps some. Please post back any other questions or steps you have taken to try to resolve so others can help. Of course, it's always good to share what Firmware (and UI) you're running to be sure you get the best assistance for your situation. (From ISY Admin Console menu -> Help -> About) Oh, and I know you said you didn't care about Darksky, but here's the information on that too in case you want to take steps to try to fix/repair that install: (Note: Darksky was purchased by Apple. Not sure if this still runs or is open for new updates. I've never run this one, but know that the Apple deal did impact something related to Darksky. I use Climacell and NOAA weather nodeservers.) https://github.com/bpaauwe/udi-darksky-poly

I'm with you there @asbril. We could all go in wearing @MrBill name tags though. And I'd be in for the trip. It's been a few years since I was in LA. Let's get past Covid a little more though. And hopefully not have 80+ ships anchored off the coast of LA. We can all go point at the ships and wonder if home automation parts (of any brand) are in any of the containers.

Glad it seems you got it working again. seems like your backup issue has been an issue a while. You posted the issue last year. Did you try what @Michel Kohanim suggested? If you still have issues it might be time to start a ticket with support at UDI.

Make sure that you are allowing location tracking "always" (if that's an option) for the app you are trying to have update your location. It's possible that iOS 15.1 (I think it's still "beta") might have some bugs or could have been that you didn't allow location tracking when you first used the app on the new phone. It's also possible that the app finally broke under iOS 15 since it hasn't been updated in 3 years. (4.17 was released 3 years ago). Sounds like it might be something you seek support from MobiLinc. Perhaps @InsteonNut can chime in to see if there's something you can do with existing app or if you need something else.

@dinostop In addition to letting us know what Firmware and UI you're using check if you have two factor authentication or Gmail 2-Step Verification turned on. You would need to have an app specific password assigned by Google. I have used Google since day 1 and not had any issues. Mine is a ISY dedicated account with 2 step verification turned on for added security even though it's just a "trash" account. If you're sending a bunch of notifications it could be that all the sent mail is stacking up in the sent mail. I added a filter to send alerts to the trash label/folder so it wouldn't stack up in storage in that account. Gmail tends to keep all the sent emails forever, but wipes out the deleted as time goes on. Even though it worked at one point make sure you're following the steps in the wiki to setup gmail service.

Glad you got it resolved! Seems like a neat function, and even more entertaining trigger word to show off to guests.

@TriLife I also don't have Google Home products so can't help further, but maybe others will come around and see your post to help. I did see @GaryK4 recently had an issue that he went to the Google Home app and unlinked Universal Devices and reconnected it and seemed to get it to work. I think what you're saying for removing from Google is just removing it on the Portal isn't the same as what I (we) can do with Alexa. We can remove the actual device/program/scene from alexa.amazon.com and then have Alexa rediscover smart home devices. In your case while some commands work it would be an option to unlink and re-link the skill (or whatever Google calls it) so that it might reset everything. I think others have commented on doing this in the past with Google as being the only way to really reset everything. I think others have said they used to have to do this often and that's why they ended up quit using the Google products. Another tip might be - Have you attempted to copy (recreate) the program and add it with a different spoken command to see if Google can control the program if you use a different spoken? It could be that it's not understanding the phrase. (Unlikely, but throwing everything into the mix of "what if?")

@UD2)17rrh It's important to share the FW/UI to try to help further. But, the key steps to try to ensure you're using the correct version of Admin Console is by using the launcher method found in this post. Before you go too far make sure you're clearing java cache before trying to reinstall the launcher. Also key - always download a fresh launcher (start.jnlp) or get a current admin.jnlp - DO NOT USE OLD DOWNLOADED FILES! This helps with the hope of getting an accurate UI for your firmware (specifically if you get the launcher (start.jnlp) from the instructions found in the latest update area of the forums. If you can confirmed that FW/UI match, cleared cache, and installed new launcher/finder there are other things we need to check. Have you changed your router lately? Is the ISY set on DHCP or Static IP? Have you added any other network devices that might be competing for the IP address? How is your Mobilinc connecting to the ISY (local or remote)? Are you using ISY Portal or Mobilinc Connect portal? Hopefully this helps sort it out, but any additional information you can give might help others with your troubleshooting.

@TriLife as lilyoyo1 points out it's always good to let us know what Firmware and UI you're using so those trying to help can troubleshoot efficiently. It also is a check for you (and those helping) to be sure that you're matching FW/UI versions so that you're not risking having other issues. I'm not 100% sure about the Google home options, but figure it would be this...using the refresh and send spoken to Google processes. On the ISY Portal -> Select Tool -> Connectivity -> Google Home In there you have "Send spokens to Google Home" and "refresh" (buttons below). 1 - Make change in Admin Console 2 - hit "refresh" on ISY Portal website 3 - hit "send spoken to Google Home" I would expect that if you make a change in Admin Console you then go to the ISY Portal (it's the web so you can be logged into both). One step I'm not sure about is how to get rid of old spoken commands already sent to Google Home. Perhaps somebody with Google Home experience has a way to delete from the cloud settings. I know on the Alexa side there's a way to delete smart home entries through the app and/or through a website. Not sure if Google offers same operation.

Did you, by chance, upgrade ISY to 5.x sometime 3-4 months ago (when the problem started)? I noticed when I went from 4.9 to 5.3.4 all my programs became enabled. Just wondering if there was any update during that time to the ISY that went un-noticed then to start the issues you were facing. Glad it's seeming normal again. Consumer grade routers can often cause lots of unexpected problems as we add more wifi connected devices. While they may be low cost and easy to setup troubleshooting router issues are very difficult for most general home users.

@jons7391 are you running polyglot cloud or locally? It's in there for polisy store. https://github.com/exking/udi-hue-poly Does not appear in the polyglot cloud store. That's why I was asking which location you're trying to run from. Your situation sounds like what I've been considering too. I'm trying not to add a bridge to my setup either. I don't really know if I need/want color options, but I do want to be able to dim the lights. Thanks @lilyoyo1 for the tip on the diffuser! Just might order me some parts of that to help keep individual LEDs from reflecting on the new countertop.

I don't think they have a PLM to sell. Noticed they said a while back the system got hit by lightening and knocked out the PLM. Since they can't find one for sale they're probably ditching the rest of the ISY/Polisy side of the system. Saw this post about the hit.

@60Driver, at this point I think it’s best if you open a ticket with support to get some one-on-one support. They may be able to help make sure you’re properly installing Java and the launcher app. Please submit a ticket via email to: support@universal-devices.com Good luck!

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.