Geddy

@bcdavis75 interesting. Appears to be a Mac centered issue. Are you running any firewalls? Perhaps first I would make sure that you've got the latest version of Chrome installed. Just to be certain. Quick (Google) search lead me to this page for possible help options: https://support.google.com/chrome/thread/10551759/net-err-cert-invalid-website-sent-scrambled-credentials-self-signed-certificate?hl=en Specifically this post (many seem to reply that it worked for them) Some of the suggested solutions in the link appear to be Keychain related. Have you ever been able to access the Polisy in Chrome? Perhaps it saved something in the past that it's now having issues with. Beyond my help with Mac issues though. Sorry. Good luck. If still stumped after trying a few things mentioned in the link above perhaps open a ticket with UDI and see if they can offer some assistance for macOS specific issues. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

@bcdavis75 in Chrome are you using HTTPS or just HTTP? I'm not no MAC, but on Windows if you just type "http://<polisy IP>" I don't get the option to proceed. Only if I use HTTPS does it give me the choice to proceed (at least the first time...then it doesn't bug me for future visits). What does your screen look like in Chrome when it doesn't give you that option? Mine looks like this if I just type http://<polisy ip>

@JWBDolphins I did exactly the same thing this year. I don’t think it’s trying to write anything to the device. I disabled an outdoor plugin device and the ISY994 doesn’t squawk about not being able to reach it when I load admin console. So just disable them and you won’t get those notices anymore. Doesn’t seem to impact anything else. Remember to also disable any programs calling on those devices!

As @Techman says you just need the launcher and it will do all the "work" for you. (Read about its release here) The main thing if nothing is happening then it sounds like you don't have Java installed or are using a browser that isn't java "friendly". Since you just clean installed Win10 what browser are you using? Make sure you go to https://java.com/en/ and download/install Java. Then go back and download the launcher from the wiki you linked to. Most browsers will have a warning that the file might be harmful, but it's okay and save it. Then go where you downloaded it and double click the start.jnlp and allow it to run (you might get another Java warning) I just tried this in Edge and it does warn you... Click the "..." to get the following menu and select "KEEP" Then you should be good to go! The key is having Java installed before running the start.jnlp. Once it runs you should have an icon on the desktop like this: From there you'll get the "ISY Finder" window. As long as you're on your local network with the ISY994 it should auto find and put the UUID and other information there. Then anywhere on that line you can click and get this menu: Click on the Admin Console for either LAN or Cloud (depending on your location relative to the ISY994) and it will load the correct Admin Console relative to your firmware. Key from that point...always make sure you User Interface (UI) and Firmware (FW) match. (Admin console -> Help -> About). Good luck! Report back how you progress.

Yeah, sorry...can't help on that side. I'm sure it's something like Google doesn't allow you to see outdated apps if they aren't specifically rated for your OS. (Or the older versions have been removed and only Mobilinc X remains) Have fun using UD Mobile. @Javi has done a great job getting that up and running.

@ingeborgdot It's been a while since I went through the update process, but now looking at the notes for the 5.3.4 update find a few issues with how they're presented. Step 8 shouldn't be involved at all. Currently the most suggested way to launch the admin console is through the launcher process (found here and referenced in this post). What computer OS are you using? Windows or MacOS? In Windows once you've got the latest version of Java and have downloaded the launcher you should be able to get into the admin console with every click. The launcher puts this icon on your desktop: When you run the launcher it typically will open the "ISY Finder" window. That should automatically find the ISY as long as you're on the same local network as the ISY. If not, you will need to add it manually. When you see your ISY listed you should be able to click anywhere on that row and will get another pop up menu to launch the Admin Console (lan or cloud) or Dashboard) [see below] There is no difference for Admin Console here as long as you're local to your ISY. The "LAN" option lunches the admin portal directly from your local ISY. The "Cloud" option will download from the web to make sure UI/FW match (user interface and firmware). What you're trying to do in step 8 is what many will consider the "old" method of getting the admin console directly from the ISY994 firmware package. That's great, and the best way to make sure you match, but starting with 5.x UDI developed the launcher to help take that guesswork out of the process. It's somewhat a failsafe, but we have seen issues with it working for some people on MacOS (it sometimes works, but sometimes doesn't work). For most Windows users the launcher works 100% of the time. So if you've been able to upgrade the 994i to 5.3.4 and verified that firmware and UI match using the launcher...that's far enough. I wouldn't suggest the step 8 you mention of getting the admin console only directly from the ISY. I too have found it an issue after the first time launch is successful. The Launcher process works for me 100% of the time and the most simple way to access the admin console and assuring that UI/FW match.

@Ray What phone OS are you using? iOS or Android? If in iOS you should be able to still find it in the app store. If not then look at your purchases (in the app store click your icon in top right then purchased then my purchases. You should be able to find it in there. Sorry...don't know about the Android app store. At least to be able to get it installed on the phone again. (for iOS anyway) Since you were using the Mobilinc Pro version you could use the UDI Portal for remote access. Otherwise, the "old" method of port forwarding would be an option. Probably the reason you would suddenly have issues connecting was if your IP changed if you weren't using a DDNS options. Other situation could have been local IP changed if you didn't have DHCP reserved for the ISY or didn't have ISY setup as static on the LAN. (sorry...weeds...don't get lost in the weeds of the technical side) However, I think you're going the right direction of going with UD Mobile. The ISY Portal is a deal at less than $1/mo to give you so many additional features (remote access, network resources, and Alexa/Google Home).

Thanks @Bumbershoot for pointing that one out. Just added that to the forum list.

@stevehoyt the PG3 forums have been made available for posting now. The list should have all the PG3 nodeservers that were available as of a month ago. If more are developed/released and don't have a dedicated forum yet please let me know.

@dbwarner5 That's "only" 15.2" that's been out for a few weeks at this point. You said 15.2.2 and might have gotten a few of us excited. I can confirm this is NOT fixed in 15.2. At least not with Mobilinc Pro. It appears that other geofence systems are running more accurately, but I haven't made the switch to using those hoping that Mobilinc will work as iOS updates. But I don't use them for mission critical automations so I'm not worried about it...unlike some that seem to have more dependencies on location services.

I've not seen any such release or any comments online about an update. Perhaps you're seeing some beta releases. @dbwarner5Where are you seeing 15.2.2?

I am NOT one that knows what to look for in error logs, but based on other replies on these the -170001 aren't really errors, but informational. Unless there's an error following the line it's probably nothing to worry about. Here's a recent post about the -170001 in the log. I ran my error log just to see and I too had lots of the -170001 entries, but no errors were being thrown. That's troubling. Indeed...open a ticket. Let them help you through UDI Support. Good luck.

I've got the same setup as you for wifi. I have the Deco 9+. My ISY is connected to a switch connected to the primary satellite several rooms away from my laptop running admin console. I just ran a backup on my system and it took about 90 seconds to run. Do you have an approximate idea of how many devices, scenes, and programs you have setup? I'm wondering why your device takes so long to backup. It could be network, but more likely the amount of information you're backing up and/or MAC related. Since you're on 5.x (5.3.3 from original post) are you running any nodeservers on the Polisy? You might want to try the ISY-Inventory nodeserver to get a count of your devices... That's key too. Are you running a firewall on the MAC? Ultimately, I think support ticket is the best option. They can help you and check the logs if there are any errors showing up on the ISY that might point to PLM, SD card, or even power supply issues. Since you say your 994i is "fairly old" it could be several things. Good luck! Post back any updates or resolution.

@dbwarner5 If that doesn't work it could be an issue with the PLM. I found a very old thread that says it could be PLM related. How old are the ISY and PLM? Best bet if changing to 1024 doesn't work is to open a ticket with support. https://www.universal-devices.com/contact-us/ https://www.universal-devices.com/my-tickets/ Email: support@universal-devices.com

@dbwarner5 Have you ever adjusted the Java runtime parameter? I'm not a MAC user so can't tell you specifically if this might be causing your issue or not, but could certainly be an issue if Java on Mac is like on Windows to any degree. You might be running out of memory allocated to the Java process during the backup. If you're taking that long to backup you've either got a slow computer (not typical for macs) or a large backup. It's probably capping out the Java process. Here's steps to do this on Mac: https://apple.stackexchange.com/questions/63314/how-to-i-change-the-default-jvm-heap-size-on-os-x From the UDI forums in release notes there are these instructions (geared mostly toward windows users): See if this helps you any. There might be other issues causing this so if it doesn't solve it perhaps others can chime in for things to try or you should open a support ticket with UDI to get specific MAC help. as a side note...you say you're on 5.3.3. Why not upgrade to 5.3.4 on the 994i? That's the latest firmware build. Not that it should make a difference based on the errors you're getting, but wouldn't hurt to be on the latest for the 994i when going to the latest for the Polisy.

@someguy while I won't say this is "normal"/usual it is somewhat common. I ran into this about a year ago. It has to do with Java updates. Sometimes the updates will wipe out everything and you've got to just download and run the launcher again. (https://isy.universal-devices.com/start.jnlp) I think it goes away (sometimes) if you say yes to the option to reset warnings during a Java update. That's usually a good thing (IMO) so it just takes 30 seconds to download the launcher again and run it to get the icon back on the desktop. So, while not always happening it isn't uncommon for it to happen. It's a very simple fix to just download and run again. I always suggest downloading a fresh version just out of habit of always getting the most current version of admin console. Yes, the launcher "fixes" that, but it's still easy (and somewhat better) to just download a fresh copy to reinstall the launcher. Also, if you made any adjustments to the java runtime memory limit make sure that is still set or it will need to be reset. (NOTE: you can also set this to "-Xmx1024m", but NOT both. If your system has more memory to dedicate to java as it's running the admin console.)

No, as @gzahar points out it's plain text. That's why I suggested pasting in notepad. If you paste into Word or other word processing program it could auto format the layout and that would be cumbersome. But as I suggested it's just plain text and mega easy. That's typically a step suggested in Firmware update too so you have a logical and readable version of all your programs should something go wrong with the firmware upgrade (i.e. from 4.x to 5.x a lot of adjusting might have been necessary. Having a text record of all programs saves the day!). Great advise! Always keep it simple. Too much will inundate people that might not know what they're doing and they'll just leave it alone. The best thing is to point them in the direction for help and they can seek the help they need and/or learn at their own pace and get help as needed.

@Old Surfer Dude Do you use any cloud storage (i.e. Google Drive, OneDrive, iCloud)? My first suggestion is to start a folder in a cloud drive and keep everything in that. This way you and anybody that comes after you would have an electronic version of what you're trying to do. As soon as something is printed it's outdated. As @Techman suggests a Topology and a copy of programs is good starting point. But that's just for the "guts" of the system. "Generate Topology" is in the tools menu of the admin console. For programs go to the programs tab and click the root folder ("my programs"). Then right click and select "copy folder to clipboard". Then open a text app (if windows I suggest Notepad) -- something that allows you to paste plain text and not auto correct or auto format. Then PASTE into that text document. SAVE said document. This is now all of your programs stored in a safe place. (note...repeat this process every time you make a backup as part of your documentation set). I suggest using date file names so you know how recent file are without having to look at the details (yyyymmdd-filename). The real start of it all will be general information about the hardware and how to access it. And this is where it gets tricky because people that don't know what they're getting into might not follow all the directions (even if provided and clearly written). So the most important thing would be how to contact UDI support. If somebody walks in without knowing anything and wants to do everything the phone number to support should be first thing they see. This way they can call and say "please help, I know nothing". Important links to include are as you mentioned manufacturer and wiki, but also the forums. Ultimately, they can come to these forums and many can help them find there way of accessing the system and maintaining it. I wouldn't stress too much on "rebuilding from scratch". Not many would want to take the time to do that. And can get very "wordy". Just keep it basic (so you don't have to always make sure it's "up to date") and keep a current backup and program file in the folder. My family has the "what if" shared folder in OneDrive. In there is the "Home Automation Info". I keep the last 3 ISY/Polisy backups and current program text file. Good luck as you progress. Good thinking about it as a just in case.

@SJC85284 no issues for me, and I did the same upgrade path. Perhaps the settings didn't transfer exactly. Have you attempted to just enter the IP address again? You can find it in the old phone. Make sure you have the local http as just the ip address then "local port" set to 80. If you're able to access the ISY from a web browser (http://isy_ip-address:80 -- put your actual IP address in there) then Mobilinc should work just fine. Tagging @InsteonNut to this to help further if necessary. Note - one other oddity that has been discussed in other areas (of this forum and on line in general) is that iOS 15 broke geofence services for most location based automation. Mobilinc is included. So far I'm on iOS15.2 and it still isn't working as expected. So if you have any geofence events setup with Moblinc they more than likely won't work every time.

There's been numerous other posts like this over the years. This last year has probably been one of the biggest questions on everybody's minds if not openly posting here. There's just too much uncertainty to say. It's more in what does your budget allow and what do you want/need to accomplish in the system? Here are a couple to read through: https://forum.universal-devices.com/topic/31786-future-in-insteon/ https://forum.universal-devices.com/topic/34022-is-radiora3-the-ultimate-replacement-for-insteon/ Since Smarthome/Insteon is trying to launch their new Nokia line it's causing the tried & true Insteon camp to wonder what the future holds. Nobody (really) knows or certainly aren't able to say in an open forum until the company officially does/announces something. There are options that would work in the future of the Polisy. So if you're looking for the reliability of the controller that you've had in the ISY you should consider the Polisy as the new controller to handle the future system you go with. The Polisy can use the USB PLM (and some have mentioned success with a USB Stick that Insteon makes/made), or go the z-wave route, or use one of the many Polyglot Nodeserver options that have been developed to incorporate other platforms. There are pros and cons for every system. Just have to dig and figure out what you want them to do and then hopefully find one that can do that and make you happy at the same time.

Great! Glad to hear it was resolved. Yes, UDI offers great support for their devices. The forums are good for general troubleshooting and trying to get answers for common issues. The Polisy has variables that Michel and the rest of UDI are just better suited to handle through their ticket and support methods. Enjoy the options Polisy brings!

@wayneph When you’re in the Alexa app what do the fans look like? I just checked mine and they appear as fan icons then in the type they read fan. Make sure that’s how it appears to you. Since you have so many and none seem to be working right I’d open a ticket with UDI and get some help that way.

@wayneph You probably need to delete any old references in Alexa. Login on the Alexa website - https://alexa.amazon.com/ (you can remove old devices in the Alexa app too, but I find it easier and quicker on the website) Click on "Smart Home" and find the old device names that you've used. Since you said that you're sure you're selecting the device/fan in the Portal to link it back to Alexa you should be able to remove the old entries and have Alexa rediscover your devices. It should then find anything NEW and you should be able to use it as expected. I'm with you on here. I saw the post @Javi made and ultimate update to the wiki and am leaning that direction. I haven't tried it yet to know if it keeps the buttons in sync, but would expect it to since that's the point of the scenes.

WOOHOO! Thank you @Javi for updating the Wiki on this for 5.x instructions. It will be VERY helpful for new users to set it up with the way scenes are handled in 5.x. Mine were setup in the old 4.x world and really causing me problems. 100% THIS @lilyoyo1! This was 100% of an issue I was having with each keypad I setup years ago. The instructions included altering the grouping and that was recently causing me issues. I went back and factory reset each keypad and set them up in the 5.x scene process (as @Javi outlines above). Much better ( more reliable) control of the devices! (Thanks also to @MrBill for a suggestion of changing how they were originally setup.) @Gunn Happy Dance! You finally reset everything. I think you'll find that very helpful for the entire system.

Looking at your about screen you have already purchased ISY Portal. Make sure you go to my.isy.io and setup your account. Instructions for activating ISY Portal: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions KEY: You've got to APPROVE the portal request from the Admin Console Then to access your ISY remotely through ISY portal follow these directions: https://wiki.universal-devices.com/index.php?title=ISY_Portal_Admin_Console Were you just trying to make sure your portal was active or were you trying to do something else that lead you down the path to try to "Enable Internet Access"? You might need to restart the process from the portal side. You could have entered an incorrect UUID so it isn't contacting your ISY to get the approval to link the Portal.