Geddy

@X-10 while I'm sure it probably isn't exactly the same your titles for your new post and a prior post were identical so I've merged them to try to get you the best help here. If you're working with Universal Device Support team then you've already got the best support you can get and you should be back in business soon. There's nothing AT the location you're attempting to use "launcher.app" so that's just wrong, and don't know where you would have found or attempted any links like that. Furthermore, the "ISY" portion should be the IP address for your ISY not just the word "ISY". Additionally, since you're on macOS there's been some that get the ISY Launcher to work right and some that don't. So I'd be risking sending you down a possible wrong path by just suggesting using the ISY Launcher that is downloaded from this link, not whatever you're trying to download from what you say "https://isy%20 launcher.app". I think your basic problem goes back to the original January post and that @larryllix was right in that you might have an IP conflict somewhere.

@CPRail1 I'm not quite sure why you need Java 11, but I'm sure that Launcher/Admin Console probably is only written to work with the current supported release of JRE 8. Perhaps @Michel Kohanim can chime in to confirm or give other advise on the Java case. Since you still have issues then I suggest starting a ticket with UD Support to ask them directly how to achieve launching the Admin Console with other versions of Java.

@CPRail1 first question - why download any version of Java from a site other than Java/Oracle? My assumption would be that you need to clear java cache. Since you're still running JRE you might need to clear java cache and then download a new ISY Launcher (start.jnlp)file to add the ISY Launcher icon (to your desktop) and access to Admin Console.

@SHM Have you been able to get back into the Polisy? Just checking if you got this resolved through a ticket or on your own.

I don't see there being a problem. I explained that you're doing two different things to achieve the same result. Your original question... The answer (to "what did I do wrong") would be for both of you to download the exact same link (https://isy.universal-devices.com/start.jnlp). I pointed out that your brother downloaded a launcher link and you downloaded the admin link specific to 5.3.3. Those are in-fact different ways to access the admin console of the ISY994i. Once you both use the same process your observations should be identical. That process is suggested to be the ISY Launcher link (the one you had your brother download). Here is a visual for you to consider: The left is what you get when you use the suggested ISY Launcher link. The right is what you downloaded for the direct admin.jnlp file for your 5.3.3 firmware. They look and behave exactly as you're describing. So, there's no issue here. You didn't do anything wrong and nothing is in error. If both of you downloaded the same link (the launcher) then you would have the icon on the left and it should look and operate the same for both of you. That's entirely your prerogative, but should you need other troubleshooting the first step would be to update your system to the current release and attempt to replicate any issue. So that's why both replies above suggested going ahead and updating now. It takes maybe 20 seconds for the download and probably less than 15 minutes to update (depending on your system).

I agree with @DennisC, you should upgrade to 5.3.4. It's the most recent supported firmware for ISY994i. While there might be very few changes from 5.3.3 to 5.3.4 it's enough that it would be the first step in further troubleshooting any other issues you have. As do your exact experience - your brother has the "Launcher" which loads the finder and allows the computer to download the UI to properly match the firmware with every launch. (Thus, "Launcher") You downloaded the admin console for the direct version you installed. It would be just as though you downloaded admin.jnlp from the ISY994i directly. These two routes to access the Admin Console act differently, but they are in fact the same once you access the ISY994i. Since the Launcher was introduced in 2018 that is the most often suggested and the recommended process for accessing the ISY994i admin console. It was designed with 5.x in mind as beta builds were being released so users would always have firmware/user interface matching. So nothing is "wrong" in your setup. You're just taking different routes to get to the same destination. There have been a lot of reports of the font/display to be different as we moved into 5.x. You can change those settings, but odds are they won't stay for long as they tend to be dropped and need to be reset. But, be sure to go ahead and upgrade to 5.3.4 (since you're so close it should be very quick and not require any additional effort, but be sure to follow the steps as outlined on the release post.

What version z-wave controller do you have? (I'm sorry...I forget how to tell the difference, but maybe @lilyoyo1 can help with the identification part, if you are unsure. I didn't specifically see it mentioned in his z-wave tips and tricks post. If you're on a 500 series board in the ISY994i then you would be best supported by upgrading to 5.3.4. The default will work. If you have a 300 series board you cannot go above 5.0.16C as that is the last firmware to support the older z-wave controller. Over a year ago the "Default" mail server was getting hammered by spammers and UD made changes to the authentication used in the firmware. That was updated in version 4.9 for the 4.x branch and I believe 5.2 in the 5.x branch. So if you meet the criteria to upgrade please upgrade to 5.3.4 as this is the current release and supported firmware. If you're "stuck" on 5.0.16C you can open a support ticket with UD and get information about setting up the default email service if needed. However... This is good to know. But you should still consider upgrading if you meet the requirements to go beyond 5.0.16C. Since you're already on the 5.x branch the upgrade should be straightforward and painless.

If you've tried all the above then you should open a ticket with support and have them assist with the process. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com

I did remove the app, but did that early on in troubleshooting so can’t say if it’s a must, but if still having issues I’d try that. I didn’t do it after updating to 15.3.

Perhaps this: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide# See the part near the end about the multifunction button on the front Note the comment about updating if doesn’t work as described Reset Credentials Press and hold the button till the first LED (from the left) starts blinking then release. This action resets Polyglot as well as SSH credentials back to the default admin/admin.

Interesting. I guess I don't really ever have issue maxing out Java. I know I've set the parameter in the past, but haven't checked after each update. Since it's normally not a problem for me I assumed it stayed in place, but just checked after a recent update and it is, in fact, gone. Shame. Glad I don't have to alter it for my system so one less thing to have to keep up with. The parameter setting is certainly something users that experience a laggy or sluggish admin console should update. Hopefully for @EVictory the setting and the new SD card keep the system running as expected.

@tbuchber Welcome to the Forums. First, please let us know what Firmware and User Interface you're using. That is found in the Admin Console under Help -> About. It should look similar to this: Make sure first of all that they match! If they don't then make sure you're getting the ISY Launcher. It will take the guess work out of matching UI/FW for you. We have seen other posts about this being an issue and typically a factory reset and restore in the ISY will resolve the issue. Since the "factory default" is to NOT beep then somewhere either the ISY set it to beep or something just went a little wonky in setup. While some have not been cursed with phantom links from the factory it's always key to remove existing links when adding to the ISY, and ultimately if something isn't working as expected the factory reset typically helps. CLOSE ADMIN CONSOLE before you attempt a factory reset (just as a safe step to not be active in the system) KEY POINT - If the device is in a folder right click on it and select "Remove from Folder". Do NOT delete the device from the ISY. Leave it in the ISY, but make sure it is not nested in a folder. Make sure to follow the directions exactly. It's typical for some users to not HOLD the set button until the long beep stops. From the manual the process for factory reset is below: After device was factory reset open the Admin Console. Right click on the device (should be in the root of the device tree) and select "Restore Device". Try the reset again and report back.

@EVictory interesting observation and hopeful solution for this. As an additional note if your system has a lot of memory you can change that parameter up to 1024. -Xmx specifies the maximum memory size. I haven't specifically heard of (or experienced) this setting being removed from regular Java upgrade. It might have been removed if you uninstalled Java. Glad you seem to be back in business though. Post back if you run into more issues.

@Roman I too had removed the geofence area as part of the troubleshooting since @MrBill had success in doing that with Locative. So hopefully that helps on your wife's phone. I'm the only one running geofence triggers on the phone or else I'd probably have to do the same on wife's and son's phones. As another note my geofence for our alarm system is also working more reliably. That is outside of ISY/Moblinc, but was also wonky since ios15 upgrade. The only "reliable" geofence settings that I had seen was with Alexa, but I rarely use those. However, had changed to those for some casual triggers while I waited for the iOS updates to fix prior location trigger apps.

@Roman Hopefully you've had continued success. I can report that mine has been working well since upgrading to 15.3. Glad this seems resolved by Apple!

First, I agree with @lilyoyo1 that if you don't have a z-wave 300 series board you should upgrade to 5.3.4 (latest build). At the very least if you DO have a z-wave 300 board is upgrade to 5.0.16C (the last build for 5.x supported the 300 series board) Yes, in 2020 there were issues with the default server option (mentioned in this post). That has later been fixed and if you upgrade to 5.3.4 you can use the default server again. Although, looking at how you've setup the server it should work unless you have added additional security to the Outlook.com account and need to make an app specific password (like @jec6613 suggests). Strange that your tests aren't popping errors, or being received anywhere. Are you trying to send to the same email that you're sending from? Sometimes these free mail providers shut that down after period of time of auto generated emails. So this could have also caused you issues if it wasn't an active account or if you were sending emails in a loop from/to same address too often. I've used Gmail since 2017 without issue, but make sure to have it on my phone to be an actual checking and sometimes send non-automated emails.

Yes, the "Use Default" option had gone down back in 2020 (see this post) and it was suggested to use Gmail so not to tax the UD servers. Then, they updated the default settings and changed the method of sending. That was resolved in an update later than 5.3. So your updating to 5.3.4 corrected the "use default" settings. Although, I would still suggest using an alternate server to possibly avoid such issues in the future. Was the Gmail account you were using an inactive account? Sometimes Gmail will close access to accounts that just send messages (like ISY notices) if there is no actual logging in done by a user from a device. It's possible the account had been deactivated and just needed to be logged back in and updated the password/security settings to get it working again. Not sure where you got that the SMTP should be "googlemail.com", but I have it set as "smtp.gmail.com", port 587, TLS = checked and have zero problems sending tests or actual alerts.

Thanks. I had intermittent working with Mobilinc HD if I opened the app shortly before starting out. But if I hadn't opened the app in a day (or several days) then it would never alter the location variable and wouldn't notify on the phone. I also updated to 15.3 last night and did the "update only" for Mobilinc and also reset the location settings for Mobilinc. I did NOT open it this morning before departing and received notification of exiting the geofence area. So that's a plus. Fingers crossed here too!

@Roman, did you do anything to Mobilink to get it to work for you? Like delete the existing geofence area or remove the app and download again? I haven’t installed 15.3 yet, but will tonight and see if I get alerts crossing the geofence tomorrow. Glad your initial testing appears to work better. Fingers crossed it keeps working.

@DarkCanuck If you want to get back on the 5.x branch with the 300 series z-wave the highest version you can go to is 5.0.16C. Just a side note if you use the default email server to send notifications you need to start a support ticket with UD to get email server credentials as they were updated in 4.9 and a later version of 5.3.x. So you're not stuck with 4.9 if you wanted to get into the mix of the 5.x goodness. Just realize that you can't go any higher than 5.0.16C without upgrading the z-wave controller.

@MHB Welcome to the forums. Let's get you running with this program, but also would suggest you upgrade to 5.3.4 firmware just to be on the most recent build. You're already on 5.3.3 so it's a fairly straight forward upgrade to the next version. You can find it and the directions to update in this post. Here is how I have my program to run what you're trying to do (turn on at sunset and turn off at sunrise): ----------- Front Light - Night - If From Sunset - 30 minutes To Sunrise + 20 minutes (next day) Then Set 'Front Door' On Else Set 'Front Door' Off ----------------- The important part is to have the "NEXT DAY" for the Sunrise time. This should also handle turning the light off at sunrise if it's manually turned on prior to my on timer, but I don't turn that light on manually so can't confirm. Also, as @DennisC points out the "copy to clipboard" then pasting here makes the program easier to read (like mine above). Please share the current program you have to turn if off in the morning. If looks like you're trying to turn on about 6 devices.

@EVictory Do you happen to be running any firewall or antivirus software on the computer? Disable both and try again. It's odd because you were able to get a version of the firmware installed, but having the issues when you're trying to upgrade. Though I can see firewall or antivirus being the cause to that. Make sure both are off. Also, make sure that you're using the ZIP file that you downloaded of the firmware. Do not extract the files from the firmware and try to update that way. Did you clear java cache along the way then download a new launcher start.jnlp? Make sure you're selecting all 3 boxes in the clear cache process! (this should remove prior ISY Launcher icons) What type of computer are you using to try this? (Win/Mac/Linux?) The only other thing I can think of is perhaps the replacement SD card you are using was corrupt. Was it new from the package (even though you said it was a few years old) or had it been used for something else previously? It might be easiest to open a ticket with UD to get specific help.

@WetCoastWillie I would suggest opening a ticket with UD to get help directly to the issue. I'd only be guessing at this point as I don't have z-wave and don't run this lock. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com @brians To your email issue - what firmware are you on? What are your email settings? If the default email server and old firmware please note some changes were made and you'll need to upgrade (to 4.9 if on 4.x or 5.3.4 if on 5.x (with 500 series z-wave board)) or open a ticket to get user specific mail settings. I would suggest starting a new thread so you can get specific help for that issue (if you want/need help).

@WetCoastWillie I agree with @lilyoyo1 that you should upgrade to 5.3.4. Is appears that there were some z-wave lock fixes along the way above 5.3. So getting up to the current build of Firmware might get you to a working status. Once upgraded if you're still having problems further troubleshooting can be performed. Since you're already at 5.3 the upgrade process should be "simple". Find the release info here: https://forum.universal-devices.com/topic/33287-release-534-test-build-is-now-available/

MAC strikes again! Another oddity in the world of macOS and ISY/Polisy access. Good to know both options seemed to work. @dwengrovitz neat tip on the "thisisunsafe" process. I saw that mentioned elsewhere, but seemed to only be a temporary solution (next time Chrome launched it might have been a problem again) so thought the keychain issue was the best long-term corrective action. @bcdavis75 glad you're back in action w/ Chrome. Hopefully it's not a reoccurring issue, but at least you know the steps to resolve. (I assume you mean "And noW I have my proceed link back in the Chrome", rather than "not".)