Geddy

If those are ALL the devices you have, and you want to get rid of them all hit the trash can at the top of that screen and it will give you the prompt to delete all spoken Otherwise, individually, click the red "x" on the left side. IT will say: Click "yes" Then on the Alexa side either delete from the app or go to alexa.amazon.com click on "Smart Home" then "Devices" and click "Remove" on the right side of the list.

@brians You didn’t do the restart command. At least doesn’t show above. sudo service pg3 restart

@smithlevenson so when did you upgrade to 5.0.16A? You say the programs were written in V4.x, "haven't been touched in years", but now you're on 5.0.16A. When did you upgrade? Did you update/save the programs since that upgrade? Have you since upgraded to 5.3.4 as @MrBill suggested? Just wondered if any of your programs (other then the one you posted) had scene issues that were messed up from the 4.x to 5.x upgrade that didn't get sorted out. Or perhaps programs haven't been saved since the update. There were some early 5.x releases that had big program bugs from upgrade that might have required a lot more interaction to get them working again. What do you seen on the summary page of the program tab? Any yellow text in any of your programs there? (I forget what the text would say) I'd lean more toward what @MrBill mentioned of PLM issues or Noise issues. Could come from simple new bulb installed, bulb going bad, or any little electrical change (known or unknown). Have any storms, power surges, or outages lately?

What process did you use to update? If SSH then log back in and try pkg version Check for PG3 version in the list. If still showing 3.0.45 then run the commands in the post @bpwwer made for PG3 announcements. sudo pkg update sudo pkg upgrade sudo service pg3 restart I think the other option would be to follow the wiki instructions of pressing the multi function button on the front once. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Update_and_Upgrade_All_the_Packages I did not reboot the device after updates. I figure if it needs to be rebooted somebody will say reboot. I don't know enough about FreeBSD stuff or *nix to know when to reboot or not, but always remember the computer geeks I know bragging about never having to reboot their *nix machines just stopping and restarting processes seemed to be the same as a Windows reboot. So I try not to reboot or power cycle the Polisy if I don't necessarily have to. That's just personal preference.

https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Default_Username_and_Password Additionally, while I like the thought that @kzboray has for using Windows built in SSH process I prefer Putty settings for Putty:

Then you should be upgraded to 5.4.3 on your 994. If you're on 5.0.16C you're on an old firmware that has many updates and upgrades since. That's step #1. Follow the steps outlined in the release post - https://forum.universal-devices.com/topic/33287-534-update-for-isy994-july-30-2021/ Then, as @lilyoyo1 suggests, read and understand the process. Read the wiki. It has commands you posted above. So, all the information is there to be consumed. You've just got to take the time to read it and understand what the steps do before you get too far down a path. Don't just read a line and do it. Know your plan for upgrading. Just in case you get interrupted in the middle of a step. The key is...always allow plenty of time to pass before proceeding. Sometimes the update can take a while to download and install. So don't expect each step to take 30 seconds and try to perform the next before the system is ready to proceed. There was a report that one of the updates took ~10 minutes before the Polisy was ready to move ahead. I forget when/what that was, but just be prepared to wait until you hear beeps and have steady lights on the Polisy. Post (in one place) when you have more questions. Bouncing back and forth aren't doing you any favors.

I do not know. Perhaps @Michel Kohanim can chime in to confirm. Otherwise, email support@universal-devices.com and ask about upgrading from 5.0.16.C. Support will get back to you fairly quick during the week. Do you have (and use) Z-wave and have the z-wave 300 series controller? If you don't use z-wave or have a z-wave 500 series controller in the ISY994 you should upgrade to 5.3.4 first. But, if limited to 5.0.16C because of your z-wave controller you need to check with support if the migration path is acceptable to attempt. I'm not sure where you see this mentioned or what you're referring to. If there's a file version referenced in early January odds are it has been updated as PG3 has been updated several times since that post was made. I did a search in that post for 1.21 and didn't find any mention of it. Where did you see that? How do you figure that? Follow the steps in this part of the Wiki - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Polisy_OS_Versions_Below_13 What version do you have when you run the "sudo uname -a" command? I just checked my system and have: Follow the steps in the Wiki to upgrade OS to 13. From there upgrades can be done using the multi function button on the front of the Polisy.

There is also the documentation in the Wiki for Polisy User Guide - https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide I think the post by @dbwarner5 helps fill in some tips/tricks found while doing the real life migration at that time. It was also started before the User Guide had been added to the Wiki.

Looks like PG3 was updated. Usually @bpwwer will make an update in the PG3 Release status thread. I had 115 packages to update when went through SSH update/upgrade process. PG3 is now version 3.0.46. Lots up the updates were to FreeBSD packages. PG3 web interface now shows:

What's the point? It's just meant to be a reference file. If you need it for use elsewhere you can click the "copy raw contents" on the top right and then paste that into Word (or other text/word processing program). Or you could print/save the page as PDF.

@DennisC, @Bumbershoot, @TUhl01, @lilyoyo1, @asbril and others... Seems this is a bug (UI only - according to support ticket reply). Should be fixed this week. Thanks @Michel Kohanim for the confirmation!

Same issues here as @DennisC, @Bumbershoot, @TUhl01, @lilyoyo1. and @asbril. I have Lat/Long set to specific area. My DST offset changes to -4. If I change it back to closest city (Atlanta) it changes back to DST offset -5, but after admin console restart it still shows sunset to be at 8:43pm (should be 7:43pm). Noticed also after closing and relaunching admin console that my custom lat/long are selected again, with the DST offset back to -4. So it's not correctly storing the location update. Seems since my "customs" location was setup during Standard Time (-4) that's what's stuck in the coding. Cannot change DST offset for custom location.

Watch out for those apps! That message (and somewhat the other one) is specific to apps that use just the Google User/Pass. I think with 2-step authorization they consider the app specific password safe enough alternative that they will allow it. I think it's more geared toward things like Scan to email (like some HP printers can do) since it typically uses your default user/pass combination. If you have it setup with app specific password or have "Sign in with Google" maybe you'll be alright. I haven't received any such notice, but I've had 2-step authorization setup for a very long time. So I'm hoping that it wouldn't impact the setup. We'll know April 1st (great day to get hosed!). I'd check more on this page from Google: https://support.google.com/accounts/answer/6010255 The fixes they list include specifically having an app specific password is allowed. HA! Just noticed that my "backup codes" are from 2011. That must have been when I first activated 2FA process for my primary account.

As @lilyoyo1 suggests give them links to the WIki and specifically the Cookbook. Make sure the ISY doesn't have static IP set on the device so when they setup new networking equipment it will get an IP address automatically. They will then find (in the cookbook) how to setup static IP reservation on their network gear. Also provide links to the forums and the ISY Launcher (referenced in the Wiki and on the forums). That's the best thing for them to have on their computer to access the ISY. Top 6 items to suggest: ISY Wiki - https://wiki.universal-devices.com/ ISY Auto DHCP - reset password to default [admin] (keep it simple!) Java - https://java.com/ (just "plain" Java 8 - no fancy java downloads!) ISY Launcher - https://isy.universal-devices.com/start.jnlp UD Forums - https://forum.universal-devices.com/ UD Mobile - App for Apple & Android - https://wiki.universal-devices.com/index.php?title=UD_Mobile

So when you say it's crashing it's crashing the (old) ISY994i device? Not the ISY on Polisy process? Hope you were able to clear it out and get the "proper" SMTP settings back in easier this time. Thanks for testing them again. I think I'll certainly steer clear if it's on the 994 device. Can't have that crashing on me! Just one reminder...if it's an extra Gmail account (only for sending ISY notifications) it is a good idea to log in at least once a quarter (every 3 months) so they don't deactivate it for inactivity. I forget what Google set their timeframe too, but I know they've been adjusting their requirements for such "dummy" accounts that just send the same messages over and over. The default mail process was fixed in 5.3.4 (or maybe just prior) for the 994 devices. I would expect it to work as intended in IoP. But, it does always have the potential for issues, so it's good to have a backup plan to switch to in case. Or to take some traffic off the UD servers depending on your notification load. I know @MrBill, and others, suggests the Notification node server and the Pushover app for mobile notifications rather than email alerts. It's all in personal preference.

@DennisC and @mmb - personally I would say the change shouldn't impact the operation of the Gmail account, but as @Michel Kohanim says it depends on the final change. I've been running with Gmail since I got the ISY. I haven't made the change to IoP yet so can't confirm there. But I have always had 2-Step Verification on and an app specific password. I didn't get a notice (probably because of that fact). When I go to look for the "Less Secure Apps" section in security I get this notice: So my guess would be if you use Gmail with 2-Step Verification and have an app-specific password you should be able to continue using. Now... @mmb for your question about Outlook.com...can't help on that. I've never tried using Outlook.com servers. And my current setup ain't broke so don't want to temp fate and make any changes. Maybe before I migrate to IoP I'll give the Outlook settings a try. I have 2FA setup there as well so that will need an app specific pass also (for me anyway). If you can't get by using the Gmail with app-specific pass and need to use Outlook perhaps open a support ticket for them to check the logs when the IoP is crashing.

Good to hear! Sucks to have to redo the favorites, but a chance to set it up a little different and adjust.

@dbwarner5 in the HTTPS line just use “my.isy.io”. Don’t use the full URL. does that change anything? That’s all I have in my profile and can get it to just update. I haven’t tried the “download all” option because I don’t want to risk having to redo the favorites. Depending on how large your system is it might take a while to sync.

Not sure the reason to want to go direct, but the portal account access is super easy, reliable, and cost effective! 2 years is a whopping $23 for the first two years then $20 for two years after that. For less than $1/mo you get all the great advantages of ISY Portal.

@dbwarner5 Take the extra "https" out of the URL. Just use "my.isy.io" (oops...just saw you edited the original post) Also remove the port on the local port just to be sure nothing is there. Not sure about the other issue. Might be best to post in the Mobilinc forum and tag Wes or email Mobilinc for support. OP was posting about a different app.

Have you tried all steps in the wiki for remote access? Read here: https://wiki.universal-devices.com/index.php?title=UD_Mobile#Remote_Connections Next question will be, what is your ISY Firmware version? What device are you running ISY on? (ISY994 or Polisy) Welcome to the forums.

It doesn't "bring" you to the Admin Console, that's just how you log into the console remotely. It should work for accessing in most apps since that's what they're accessing anyway. When you were using the IP address did you end it with "desc"? You will need to use the entire URL. It should start with "https://my.isy.io/isy". I don't know how that app works since I'm not an Android user. Although, it you were using the IP address then using the URL for Admin Console or even the "URL to ISY" should work for one of the options. As you mentioned you will need the portal credentials to access the ISY using this process. It also might only work if you are remote. I've never tried it in other apps while local. This URL aren't typically ones that you are using to surf to the ISY, but they're used for accessing through Admin Console or apps. I too get the "not found" if I try going to the "URL to ISY", but in an app to access my ISY it works without issue. When you use the IP address are you using any port forwarding on your router to point to the ISY? Using one of the "URL to ISY" or "Admin Console URL" paths should give the app the address directly to the ISY. You don't need to use port forwarding when accessing the ISY through the Portal through this method. If you've got it working again that's great. Just make note that if it stops working again you can log into the ISY Portal and get the current public IP address for the ISY. Perhaps there are other users of Simple Home Controller here that can give you more insight and help.

SSH to the Polisy and use this command: sudo uname -a This information is in the wiki Polisy User Guide (Troubleshooting). If the version is 13+ you should have the ability to one press the multi-function button to update the Polisy. If it doesn't update then @Michel Kohanim gives the SSH codes in the release post to update to IoP 5.4. Also, @kzboray has a great post with the SSH commands to find the version of UDX currently running and how to upgrade that, but @Michel Kohanim also added a follow-up post on the release thread and also here with the commands to get UDX up to 2.6.

@bhihifi according to the release it would be best option, but kind of depends on a few things. Also, since a later update said 2 files were left out the following SSH commands are necessary: it also depends on what version you are running…some older Polisy boxes didn’t update with the single press option, but the version 13 and beyond should have given the box that functionality on the button press. So try those two commands in SSH then try the single button update process.

@j.rieff you don’t need to keep up with the external IP if you’re using the portal to connect while remote from the ISY. You need to use the “URL to ISY” seen in screen shot attached. It’s a long URL and is updated by the ISY if is needed. This is a more secure way to remote to the ISY. No port forwarding is needed if accessing this method. You just use your UD Portal credentials to log into the ISY. What App are you using on the phone to connect to the ISY? Most of them might allow Portal integration access, but just not sure. if the only way is to use the IP address and port forwarding then there is no good way to know. I would suggest perhaps using some sort of free DDNS. Some routers even have that built in now that it updates if your IP changes so you don’t have to remember it. (You can Google how those work best for your setup) Good luck