Geddy

Sounds like going the admin.jnlp route might be working better for you. Please let us know specifically. Since you're on 4.9 and you're working fine...STAY THERE! (personal suggestion right now...especially being a mac user with an "outdated" version of macOS.) Since you're still on ISY994 and it's working for what you have currently...STAY WITH WHAT YOU HAVE. UDI has new products out that are the current and future for controllers. Save your money and get an eisy when it comes out (time still TBD, but could be by EOY). Or you could wait for a Polisy to be available. But I would not spend money to update the ISY994 at this point. It's still a workhorse, but the equipment is not getting any planned updates at the moment so Polisy or the newer eisy will be the controllers you want to look for. Do NOT update to 5.x. It's a pain at this point (IMO). As I mentioned above...you're on an outdated macOS. There are a lot of fixing steps required for most 4.x to 5.x updates so I wouldn't want you to get messed up in the middle of an update if the OS messed up something. If you have access to a windows computer then I might suggest it be done, but at this point I'm more on the side of "ain't broke, don't fix it" for your situation. So, if you're able to access admin console regularly that's great! Let's call this a win and start saving a few bucks for a new controller when they're available. Just going through the process of updating the firmware won't update the UI. You have to download a new version of admin.jnlp following each Firmware update to keep UI/FW matching. This is why the ISY Launcher process was developed. Whenever the FW changes you have to get a new admin.jnlp file from the ISY994 itself. Too many users forgot this step during the 5.x beta/update processes that UDI needed a way to develop a more streamlined (i.e. idiot proof) process. Sadly, even that has been met with ridicule...mostly from macOS users because mac is not very "friendly" at this stage of interaction (IMO). So I think you're best where you are now. As long as you're able to login directly with the admin.jnlp process.

@caknowles Are you sure that your portal license is current? When you're logged into my.isy.io go the ISY Portal Access License under "Select Tools" -> Information If should say: "License Active: Yes" If not then you need to renew the license. It's possible it's just expired and simply renewing the license will help. They're usually only good for 2 years. It's simple to forget to log back in and renew it and sometimes I'm not sure if reminder emails get overlooked or end up in spam/junk because they're infrequent. Either way...if you've got a support ticket open then I'm sure you'll get taken care of, but wanted to be sure to offer help and suggestion to look at the portal license status. Make sure to post back the solution just so it might help others if they have similar situation and find your post in a search.

Don't go too far on this yet. What is your current firmware version? Please post a screen shot of your help -> about screen (can black out any personal info) Mine is this: If you're on 4.x then at least update to 4.9.If you're on 5.x then depending on if you use z-wave or not will determine your update path. If you don't use z-wave then yes, update all the way to 5.3.4. If you use z-wave please post what version z-wave is showing and if you know let us know what board you have. z-wave 300 controller you can only go to 5.0.16c. If you have z-wave 500 you can go all the way to 5.3.4. The reason I say don't jump into the update if you're in 4.x is that there was A LOT of effort to update to 5.x. And I'd say let's "fix"/resolve one issue at a time. So post your about and let's go from there. I don't think updating the ISY firmware would change your results on macOS. I think your version is old and something's blocking the process. If you can have more reliable success with directly using admin.jnlp let's call that a victory for now. I don't think you'd have much difference if you update the ISY to the "latest" version trying to fix your issue. Afterall, the ISY Launcher process was released in 2018. Best I can tell it hasn't changed...perhaps something in the background has changed, but there's no better "mouse trap" at this point. So don't update the ISY just yet!

@Dub I'm not sure on a mac, but on Windows start.jnlp never launches an admin console process. So my guess is macOS just handles the jnlp different. Sorry...can't help on MAC. I think the other thing I would suggest is to dowload the admin.jnlp from the ISY and just use that to login each time and forget the start.jnlp. But again, I'm not sure why Mac is handling it differently. The "OLD" method was to download admin.jnlp directly from the ISY (http://##.##.##.##/admin.jnlp) (replace #s with actual ISY IP address). Save that admin.jnlp file somewhere easy to access (if the desktop that's fine). Double clicking that should open the admin console directly to the ISY and be prompted to log in (I just tested on my windows computer and it works each time I tried to log in). The reason UDI went with the "ISY Launcher" method was during the 4.x to 5.x update there were a lot of beta releases. When you download the file directly from the ISY it is getting the UI for THAT SPECIFIC Firmware that you are running. When you update the firmware you MUST remember to remove/delete any old admin.jnlp files you have been using. THEN download a fresh one from the updated ISY994. Ultimately...the most important thing to check once anybody has had issues with admin console is once logged into the ISY is goto Help -> About and confirm that User Interface and Firmware versions match EXACTLY (down to the date/time code). You should never have a mismatch on UI/FW or you're just asking for more problems. @CPeterson Unfortunately I'm not much more help on MAC other than saying make sure you've tried everything mention in the wiki (https://wiki.universal-devices.com/index.php?title=Main_Page#MAC_OSX). They might be a little outdated, but with this and the help above by @Bumbershoot, @Hoosier Daddy, and @Dub seem to get you (and maybe others) going the right direction. See above...you're not really "missing" anything, and there's no such thing as a "fancier console" (wishful thinking from a mac user...I love it!) Since you're having problems then I would skip the start.jnlp setup and just download the admin.jnlp from the ISY and use it. Hopefully that would work easier for you. I don't know why they (Apple/macOS) would block you from opening admin console. I mean it's not like it's super new or something that it would be blocking it. I think perhaps the safety settings in Mac are blocking it and you need to review the posts above. I think @Bumbershoot once said the process had to be completed within minutes of the request or it didn't show in security settings. Either minutes or within an hour....anyway...not like you can just go looking in security a day or so after attempting to launch the admin console. If you're still having issues after going direct file from ISY route please post back and try to include some screen shots of any errors you run up against. It might help others that area familiar with the mac process and get you instant success. @PatPend same for you...I would download the admin.jnlp directly from the ISY994 using the information above. This should go around the issue you're having with start.jnlp. Good luck all! Please post back if you have further issues and I think somebody will help guide you the rest of the way. Great help here!

@Tony Naquin welcome to the Universal Devices forms. These are forms for products supplied by Universal Devices such as the ISY or the Polisy. What device are you trying work with? Perhaps you would be better served in support for the product you’re using. Otherwise, please let us know what UD device you’re using and what firmware you’re on. Thanks!

@Javi thanks…wasn’t sure if the link was still active for new beta testers.

@GTench got it. Perhaps posting about you issue specifically in this thread that is for YoLink. It might help the developer resolve your issue. Perhaps @bpwwer can’t add insight if it’s possible to issue a restart command somehow from IoP side.

Looks like 0.8.4 is indeed the latest “official” release for the iOS App Store. So it is accurate. I’m not sure if beta testing is still open for new users. Maybe send a PM to @Javi to check. Include the email address you use with Apple App Store. I’m on the beta build and TestFlight is showing 0.8.8 as current even though 0.8.9 was mentioned in the current release thread. I think there is usually a delay from when the app is released to Apple for review and when it really goes public. To prepare to run beta versions read more about TestFlight here: https://testflight.apple.com/

@GTench not sure if it can be done from IoP, but if you’re local you can use the web access to restart the node server by clicking on the details from the dashboard. Is there a reason you’re trying to restart from IoP?

@jkraus @landolfi Make sure you hit the “refresh store” while on the non-production store. the version referenced above appears in the store…then restart the node server and it should update.

@EDilks Make sure you follow these directions from the Wiki Polisy User Guide: https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide#Setup_ISY_Portal_for_Remote_Access/Alexa/GoogleHome/IFTTT Polisy and IoP no longer use modules as the old ISY994 platform did. Node Servers have replaced modules. The portal is just a little different though. If unable to add from the directions above, then open a support ticket and include your portal email and the UUID for your IoP.

Another option would be that you could buy this adaptor and make the cable yourself if your so inclined… https://www.amazon.com/StarTech-com-Serial-adapter-DB-9-RJ-45/dp/B00006IRQA I know this product has been linked in other posts and is what @MrBill references in a post above with the link to another cable option. In the other posts there was discussion about how to wire it correctly. You would need to search the forums to find those posts.

Why not just upgrade and find out yourself? I’m not local to my Polisy so can’t for a while. You should just upgrade your device so you have access. Doesn’t cost you anything to bring the device up to current supported system level….might even be better that you do it sooner rather than later. Think of all the fun things you can “play” with and learn about!

Just part of the system that hasn’t been updated. Kind of like why does the Wiki still have the steps if it doesn’t work? Because there are just too many moving parts sometime. Getting the correct processes for new development is priority for the wiki. Just as I figure it is for portal coding.

Yep, I know what it is from prior posts about it and from the wiki. My point is that the app isn’t supported anymore, and not available to install, according to other android users posting here in the past. So, if you’re on Android it might not work. Again, I’ve not heard of it “crashing” an ISY or IoP before so that’s why I suggested downloading logs and starting a support ticket in case it did cause the crash perhaps support can find something in the logs. There are other posts around about setting up geofence with Android. I’m on the iOS side of the fence so don’t know what to suggest for other options if an old app is not compatible with the new phone. I was just suggesting that a support ticket is the only way to better trigger a review of the system or track a bug or find if you stumbled into a way that crashes Polyglot. Wasn’t sure if you posted as “info” for others or really needed help with an issue. So suggested that you go the ticket route in addition to what you posted. Hopefully you’ve got your issue sorted out. 👍

Please read the wiki for the steps you need to perform: https://wiki.universal-devices.com/index.php?title=Main_Page#Installing_the_Admin_Console_Icon_on_Your_Desktop In 2018 the process changed to use what is called ISY launcher so it is not dependent on any browser being needed to launch admin Consol. All you need is a standard version of Java that you download directly from java.com. Make sure that you clear Java cash before proceeding on any steps in the above wiki.

Is you Polisy updated an current? If so you can find this yourself by logging into the Polyglot 3 web front then looking at the store yourself. https://wiki.universal-devices.com/index.php?title=Polisy:User_Guide Since prices might adjust it’s better to find the info yourself rather than posting for you and risk it be inaccurate down the road. You don’t have to use/run node servers in PG3, but if you have been updating your Polisy and possibly running IoP then you already have access to Polyglot v3. Find out how to access it in the wiki link above.

@apostolakisl Interesting, I’d download a full Polisy log from PG3 and PG2 (since you use both). Then I’d start a support ticket with UDI including the logs. Are you sure that you are using UDI mobile app? That is a very old app that has not been updated recently. I believe it’s only available on android and has even been removed from the android store so it’s no longer available to download. But I am not sure going from memory of other posts about “UDI Mobile”. It is NOT the same as the current UD Mobile (https://wiki.universal-devices.com/index.php?title=UD_Mobile) being developed by Universal Devices. It is a known “issue” that IoP and node servers do not load simultaneously in polyglot. The note servers should try to reestablish connection to IoP over the next few minutes following a reboot. I believe it is said that it could take as long as five minutes for everything to resynchronize.

This is somewhat “normal” lately….I’ve also had this issue when using the admin download direct from the ISY994. I don’t use that method now, but when I tested a while back also had issues launching it multiple times. Since you were able to get it to work once then the ISY Launcher method should work just fine, and would work EACH time you tried to open the admin console. Let’s look at network and computer issues…do you use VLANs? (Perhaps your ISY and Win10 machine aren’t on same local domain. Does the “Cloud” option ever load admin console when you tried the ISY Launcher icon? Win10 and Java 32 bit? Have you tried to remove Java (also using the Java remove tool to be sure ALL old versions of Java are removed)? When you reinstall what browser are you using to install Java? Maybe specifically install the 64 bit version. I’ve not personally seen much difference as I know I have 32 bit installed on one machine and 64 bit on another and both can access ISY without issues, but you might just consider this change. I would suggest these steps: Clear Java cache (be sure to select all three boxes in this option dialogue) remove Java (through windows AND the Java remove all version tools) DELETE any *.jnlp file you might have been using….look EVERYWHERE! Get rid of any old copies of start.jnlp, admin.jnlp, or any other ISY related .jnlp file) Install 64bit Java (might be a download process rather than simple click of “get Java” From the Java site. Be sure it installs in the “program files” directory…NOT the “Program Files (x86) directory) Download fresh “start.jnlp” from the wiki link you have above run start.jnlp and accept any Java warnings. Make sure it adds the “ISY Launcher” icon to your desktop. run ISY Launcher from your desktop icon try LAN option first. If doesn’t work, close and try Cloud option. Report back your status after trying all above steps. Include any necessary network information (be sure you can log into your router and see the ISY is an attached device. Make sure your ISY and computer are on the same subnetwork (192.168.1.x or something that the first 3 digits match!). Icon added to desktop should look like this: (probably without the green check mark though….mine is on desktop and being backed up to OneDrive)

Correct….they were not specifically fixed in that update…they were between the version you were running and the latest release. So I suggested to go all the way to the current release for ISY994. Since you were already at 5.3.0 then it’s a simple and safe update to 5.3.4. I think the mail servers were in an update or two before the latest. I’m sure in the past some users didn’t want to run beta or test versions, but due to the z-wave certifications each minor update is showing as simply an update. And since this version hasn’t had an update in over a year it’s fairly sure to be steady….as are most prior builds for the ISY994. Hopefully @MrBill got you the info needed for z-wave info. I don’t use them so couldn’t help ID them. I know there are a lots of posts here saying what makes one a 300 or 500. My suggestion would have been to ask the vendor you bought them from. Surely there is a serial number or other identification on the chip that could be referenced with the supplier as to which model they are. But I think the answer above should head you in the right direction.

@bgrubb1 you need to update. 5.3 is an outdated version. An update resolved the default email setting issue. Please update to 5.3.4 for ISY994 found here:

@bgrubb1 what are you attempting? And what firmware (and Ui) are you actually running? You mention”latest”, but please state what version you indeed are using. Usually just checking “use default” means nothing needs to be entered. What is your error? If you’re sending tests be sure to check your spam folder for receiving account (for me nearly all test sent from default servers went to spam folder). The more details you can provide here might get you help. From what you’ve said not really sure what you’re attempting to do. Not sure what your issues are. So not sure what you need “fixed”.

It’s very possible that your backup is corrupt. If you were having SD card issues or other issues prior to failure of last ISY. And, yes, I think network settings are stored in the back up file so it might be causing you issues when you restore and try to put it on your new network. It has always been commonly suggested that the ISY be in DHCP mode and handle IP reservation at the router level. But you seem network savvy enough to do it however best fits your system.

@JMC were you by chance using PGC? That was shut off earlier this year please see this post. If you have Polisy or Polygloy availability you can run a local version if available in the node server store.

@MGustin glad you got it solved, and thanks for sharing steps to resolve! @Hoosier Daddy originally was posted to another thread. But doesn’t really matter…split it out and OP got answer from support and updated. Thx all!