Geddy

Once you're up to 5.3.4 then fix any issues you have. There's no since to go up to a random build once later builds come out. Even if you thought 5.2 (or, again, even 5.3.2 because that's what you linked to in your first post) was the latest version, the first "official build" to support the z-wave 500 series controller was 5.3.0. But even that's been superseded by updates that have fixed some issues along the way. While UDI cannot call the 5.3.4 an official build because it has not been certified by z-wave (that costs a lot of money to go through certification) the certified build of 5.3.0 has minor bug fixes to reach the current supported build of 5.3.4. Additionally, 5.3.4 was released in July 2021 so has over 6 months of life under its belt with very little issue from most users. True...good that you're fixing things that aren't integral to your system so hope that you can resolve any issues that remain. Also, @lilyoyo1 made some great notes in this z-wave tips and tricks post that you might want to familiarize yourself with in case it will help resolve any issues that result from the upgrade. One final question and a couple of suggestions... What kind of computer are you using to access the Admin Console? If Windows please make sure you clear the java cache and use the ISY Launcher to put the ISY Launcher icon on your desktop to access your ISY994i. When you run the ISY Launcher you should see the ISY Finder window and if on the same local network should find the ISY. Click anywhere on the row of your ISY to get a menu to access the admin console. It should look similar to this: LAN will download the admin console UI directly from your ISY (so it is sometimes a little slow). Cloud downloads from the UD server the proper UI for your firmware. (sometimes this is quicker) This new process makes it easier to always match the UI and Firmware. A key point to be aware of when updating firmware and starting to make changes. Following your upgrade and the first time you enter the Admin Console please go to "Help" -> "About" and CONFIRM that your Firmware and UI match. They should look like this: Good luck!

@SirParadox May I ask why you (only) went to v 5.2.3 (I think you mean 5.3.2)? If you're upgrading past the 5.0.16C because you have a Series 500 board you should upgrade all the way to the current release of 5.3.4. Perhaps some "bugs" might have been fixed in later updates. I cannot answer to your specific question as I don't use z-wave, but my first, and foremost suggestion would be to fully upgrade to 5.3.4 first before fixing what you've done to this point. I wouldn't want you to have to do this again. I mean you even linked to a post that is in the "PREVIOUS BUILD" area. You should upgrade to the pinned firmware in the CURRENT RELEASE section.

@JTsao Not entirely sure as I can't test currently for not being at home, but you can look at the UD Mobile wiki section. Local IP should be the IP of the ISY - can be found from your router (if not known). Be sure to include the HTTP:// before the IP address. (not "https" and no "/" at the end of the IP address) Local port should be 80 - unless you changed settings on the ISY itself (perhaps with ISY on Polisy it might be 8080 - I don't run IoP yet so can't tell you 100% certain, but I've seen some mention the 8080 port for other items.) If you are able to access the ISY via admin console look at the configuration page and see if you have the HTTP port showing there. If you've set static IP on the IoP you might have the local IP shown there as well. Last thing to check...make sure "Only Use Local Connection" is turned OFF. This way if you have a remote connection it is still being used when not connected to your home network. The local then is only used when you're on the home network that you setup already.

Agreed. Thankfully it's not something that has to be done often. What's worse is through the years the same devices had different methods of being reset. So what might work for one might not work for the same type of device bought several years later. That's a wonderful pain to get into. Nope...just have to buy different products to avoid the wacky design of a feature not often used.

Ahhh...the ways important "SAVE" step! Glad it's working. I've been a t-mobile customer many years, but never send notifications to text through them. I attempted that, but was never happy with the speed of notifications. Of course, I wasn't really doing anything mission critical, but sometimes the texts came in quick and other times it would be hours later. Glad you got it working, and hope T-Mobile works out well for you. Their service is good and customer service had been great...it's starting to decline (as with most these days), but it's still miles better than other providers I've had experience with over the years.

You need to make a program that sends the notification in the "THEN" portion. Similar to this (very generic and your trigger might be different): ----------------------------- Email-Front-ON - [ID 0005][Parent 0010] If 'MISC Light' Status is On Then Send Notification to 'Email1' content 'Light On' Else - No Actions - (To add one, press 'Action') ----------------------------- Then in your configuration tab you have to go to Emails/Notifications and make an entry in the Customizations for the email/text/notification that you're calling for in the "THEN" above. This wiki page has a wealth of information for how to generate the subject and body of the notification. In my sample program above when the "MISC Light" changes the status to on it emails me a notification. The notification I have is generic and I used the wiki page to figure out how to have the notification tell me which light came so the notification could be used for various objects that the status changes to "On" For mine it is: At ${sys.time12} ${sys.node.#.name} turned ${alert.control} What I receive is: "At x-time light-y turned z-status" (where "x-time" is in 12 hour format, the "light-y" = name of device that changed status and the "z-status" is if it turned on or off. Hope that helps. Post a new thread if you need more programming as this thread was originally about sending messages to T-Mobile.

@X-10 Is the 58:fb device still an active ISY or was that replaced? And you're saying that 5b:8a is new. I would start over with the activation process. Make sure you have the correct UUID (in Help -> About or on your order confirmation). Since the device is showing that it's "online" it's possible you have a typo on the UUID online. I'm not sure if requests ever expire, but you also could have waited too long and it did expire (I don't have any direct experience with that so it's just a guess). If the 58:fb device is no longer in service you need to click the red X to the left of it to delete it from your account. Make sure the admin console window is closed (exit/end admin console) before attempting the following steps! Restart the portal registration process. To begin the registration process again also click the red X next to the 5b:8a device to remove that from the existing account. Then go through the "Add ISY" steps again (make sure to type the UUID exactly as seen in the Help -> About window. (NOTE: I like to take a screen shot of that about window so I can zoom in the image and make sure that numbers or letters are entered correctly.) Log off the ISY Portal site. Once you have added the ISY back to the portal site then relaunch the Admin Console (again, here you're on MAC so sometimes the launcher doesn't always work, but you've shown the screenshot of the admin console above so you're able to access that currently...that shouldn't change in this process). Now in Admin Console do you see the new request to authorize the Portal? If so then go back and log into the ISY Portal and you should see a green icon and it should be reporting "online"! If not...close/exit the Admin Console again. Go back to the Portal site and then next to the one you're trying to register click "Select Tool" -> "Information" -> "ISY Portal Access Troubleshooting" and see if it gives you any tips. (NOTE: I've never tried this so I cannot tell you what to expect using this.) If, after you've tried these steps you still cannot get it to connect you need to open a ticket with support and have them give further instructions of how to get the portal connected. Submit a Ticket: https://www.universal-devices.com/my-tickets Email: support@universal-devices.com Let us know how it goes. Hopefully it's a success!

@X-10 Read the WIKI for how to activate the portal using the Admin console. https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions Again, no clue why you reference some "https://isy%20launcher.app" that's nothing that will work. In admin console follow these steps: 3. Giving permission to ISY to communicate with ISY Portal Login to the Admin Console Click Configuration | Portals tab You will see a request for access from your account in ISY Portal Approve it You are done!

You're too confusing. You say you can't get it online and you post that you can't get launcher to run, but now you say "local console works fine". What the heck are you talking about? Can you, or can you NOT get admin console to work? If you can then you can approve from admin console and be rocking and rolling with ISY Portal and get your Alexa setup.

@Roman I always deleted/added the geofence on the phone (in the app) then made sure the variable on the ISY matched what's in Mobilinc. As @MrBill stated, just removing the variable on the ISY wouldn't solve anything. It's the phone that is having issues. The ISY is being triggered by the phone so just doing something on the ISY would never fix the problem. According to the old Mobilinc instructions the app makes the variable on the ISY. So I guess it also deletes it if you remove the geofence, but always safe to check. Make sure to pay attention to the note on that page: Perhaps you had admin console open when you were messing with the geofence in the app and you should have closed admin console for the app to make the changes then gone in and checked that the variable was made and correct. Hope it does. Mine is still working as it did in iOS14.x so I'm happy again.

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