Geddy

Your update shows that you found the best way to get them back to IoX, but always remember that any change in PG3 will not "refresh" or show up in IoX until Admin Console is restarted. That's why it's always been suggested/recommended that best practices is never to have BOTH the PG3 and IoX windows open when editing one or the other. Anytime you change something in PG3 the Admin Console needs to re-launch to add any changes to nodes. NOTE: Rebooting the eisy had nothing to do with the re-adding. It was simply relaunching IoX that refreshed the available nodes.

What computer OS are you using? (Windows, Mac, Other) What version Java do you have? The current version should be: Version 8 Update 421 (based on java.com site) Portal connectivity shouldn't have any impact on what you're describing as UI issues.

Please open a support ticket with UD - https://www.universal-devices.com/my-tickets Seems that something might be corrupt on your settings. If you're trying to revoke from the Admin Console it should let you do that without issue. You might also need to delete the device on the portal site. But please let UD direct you in the best method to resolve this. Please post back what resolves this so that it might help others in the future.

Have you checked your spam/junk folder? Some test emails always ended up in junk for me. Not sure why. Also, make sure you select a recipient in the Groups area to send the test to. It should default to the first, but it might not always (looking at my eisy (remotely) it selected the first line and test ran fine). What SMTP servers were you using? I have had this happen ages ago using @outlook.com or @hotmail.com accounts. I couldn't use those to send. Additionally, Microsoft has turned off simple password use. I suspect even app passwords aren't working at this time. Have you tried with Gmail? The Gmail setup instructions in the wiki still apply and still work (as of testing just now). I don't use/rely on email notifications any more, but still have them setup to be able to test. Since you're on ISY994 the usual suggestion of using the Plugin on the Polisy or eisy would not help you in this instance. The only other option would be to setup network resources to send push alerts. Those setup instructions should also still be current in the wiki.

@Edmund Lam be sure you clear your Java cache (selecting all three check boxes in the process). Download a new start.jnlp from the UD website (https://www.universal-devices.com/), clicking “MY ISY” on the top right of the image on the home page. This should fix the issue.

@MickBehr This could mean a couple of things. It could be a corrupt IoX upgrade (if you upgraded recently) or could mean the PLM has failed. More than likely it's PLM related. How old is the PLM? What style (serial or USB) is the PLM? How is it connected to the eisy (what cable(s) are you using)? Has this worked previously and this is suddenly new errors? Or has this always happened since you updated to 5.8.4? What computer OS are you running? (Windows, Mac, other) I would suggest: Check the PLM to see if the light on the side is on and green close Admin Console Shut down the eisy (https://wiki.universal-devices.com/Eisy:User_Guide#Multi_Function_Button) Unplug the eisy Unplug the PLM Wait 20-30 seconds Plug in the PLM (allow light to stabilize - about 30-60 seconds) Plug in the eisy (allow 2-3 minutes for it to fully boot) While waiting for the eisy to initialize clear your java cache (be sure to check all 3 boxes in the process) Download a fresh copy of start.jnlp from UD website (https://isy.universal-devices.com/start.jnlp) Run the file to put the IoX Launcher icon back on your desktop Open Admin Console and allow it to fully load Select random device Do you still get the issue? If so, check the status of the PLM: Admin Console -> Tools -> Diagnostics -> PLM Info/Status If you don't get a "Connected" status then you know the PLM (or the connection to the PLM) has failed. If the PLM is okay then it's possibly a corrupt update and you should run the "Upgrade Packages" process again and allow it to complete before being rebooted. This might require further troubleshooting with UD so you might want to open a support ticket: https://www.universal-devices.com/my-tickets But depending on the age of the PLM I would suspect it has issues. Be sure to keep the wiki handy if you end up having to replace the PLM as it has the steps to follow for PLM/Modem replacement.

@MARK R glad you got things sorted out. The only reason I suggested opening a ticket was because you had replies that seemed to answer the question, but you asked again or differently. Meaning that you didn't really get the answers you were looking for. This is the best place to get support for issues as the user-to-user assistance is top notch. But sometimes when product specific questions are being asked we (the users) don't know a definite answer for some unique questions. That's when a support ticket is typically best option for getting the information to exactly answer the question/concern. Since you mentioned wanting to get help here before you opened a ticket, but asked the question again (just different) made it feel as though you didn't trust the answers given. As UD has said many times in the past..."They are developers and programmers. They are not documentation writers". Sometimes what's on the website might not always match up with what you observe in the wild. So sure, checking out here and asking here is preferred and typically answered quickly.

With your doubt it's always better to open a support ticket and ask UD directly rather than getting speculation in the user-to-user forums. While many here (myself included) operate the ZMatter dongle without issue your hesitation is warranted based on what you read online and what you experienced when installing. To best get things sorted out for you and answered to your satisfaction I would suggest opening a support ticket directly with UD and get the answers to your questions straight from them. https://www.universal-devices.com/my-tickets This tells us nothing. In the future please state the actual firmware version you are running. Many might think they're on the "latest", but have often times found they aren't. Also, if somebody comes back in 3-6 months to see this post and the "latest firmware" is a few versions later they might think it's "still" an issue. (Yes, this has happened many times in the past.) As of today the current firmware for eisy/Polisy is 5.8.4. You can always confirm the "current" available version by visiting the Current Release Announcements area of the forums. I would suggest following that area to get notifications about when future releases are made available to keep your device up to date.

eisy (it’s in his reply! Bold added for attention.)

What does this mean? Pulled it where? The ISY994 can’t run without the SD card in it! Review this part of the wiki: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Errors_And_Error_Messages When you say it “went offline”, what does that mean? Have you changed any network equipment? Is the network cable damaged? Are you able to access the admin console using a computer? Since the ISY994 is no longer supported there isn’t much to try other than what has been suggested and outlined in the wiki. The upgrade from 4.x to 5.x needed a fair amount of adjusting. It has been so long since that update was pushed out that it is hard to determine what could have gone wrong. It could be as simple as clearing the Java cache or rebuilding the programs.

You didn’t use COPY to clipboard. You used export. Please try again. As @paulbates and @MrBill say, leave it be. At least you have it running daily (as it seems). If a few min off of your offset makes it an issue maybe it will sort out.

@SimonK will you please post your program as you currently have it? Please RIGHT CLICK on the program. Select the bottom option "Copy to Clipboard" then paste as text in your reply. Then post a screenshot of your location window (this is to confirm the location you entered is correct and near you). Note that you should not have a negative "Long" figure. To find your coordinates find your address on Google Maps then right click and it will give you the Lat/Long (the "Long" will be negative). Enter both in the Configuration -> Clock window for your location. Otherwise, if you've selected a general location it will use the Lat/Long you see listed with that time zone selection. Based on your program screenshot above your program is only set to run on Sundays. If you want it to run daily you need to click on the block in the "IF" and then in the bottom portion click "ALL" and then "Update". Be sure to save your program. This is why the next "TIME" the program would run isn't matching what's in the top of the screen because by Sunday that would be the next sunset time. However, you may have adjusted your program based on the advise @MrBill gave you; that is why I'm asking for the current program you are having issues with.

@tlightne have you seen this thread @Goose66 started today:

@nowandthen I had been on the beta for ios18 for a few weeks and didn’t notice any problems, but I’m not a “power” user for the mobile app like some here. I just added a dimmer as a favorite and if I click below the icon it brings up the settings that allows it to dim. I’m not sure how you have it set up to allow dim, but I’d say it worked as I would expect it to. You might want to make a screen recording of what you’re seeing and submit it as a support ticket for a possible issue with the new iOS. https://www.universal-devices.com/my-tickets/

I would revoke the UAID and Secret Key and generate a new one and use that in the Polisy. Everything else looks okay from the screenshots you’ve posted. Just the log is having issues with the token. If you do that and still have issues then I would suggest opening a support ticket with UD and maybe they can review. Submit a downloaded log package with your ticket. https://www.universal-devices.com/my-tickets/ Please update with any info you get if you have to open a ticket so that it might help others in the future.

@Marc Thauvette welcome to the UD forums. Since Moblinc hasn't been updated in a few years (looks like 5 years for Pro and 2 years for X) I'm guessing that iOS 18 might have broken something that isn't allowing the app to be used to add widgets to the phone. You might be better off contacting Mobilinc directly through their site - https://mobilinc.com/ - to see if they support iOS 18. I know I use(d) Moblinc and it still (somewhat) works with the eisy (well enough for my system needs). I never used widgets though so no help there. But I checked my install for MoblincHD and it still works in iOS18. Can confirm that widgets cannot be added though.

Looks like something might be wrong with the token or the process to connect with the yolink system. Interesting that at least you have the hub showing. I don't remember the process when I set mine up. Maybe @Panda88 can chime in with some assistance from the bit of the log you posted. It seems that it's not correctly accessing the account. I checked my log from a recent restart and it does have a "Refreshing Token" line, but it is followed with a line that contains: "yoLink_init_V3:__init__: Retrieving YoLink API info" Be sure you've added both the UAID and SECRET_KEY (and maybe add the "TEMP_UNIT" = F (for fahrenheit). @drprm1 I'm not sure what pressing the set button will achieve. Are you thinking it will "wake up" and be found? I didn't have to do that with any sensors, but I don't have leak sensors...just temp/humidity and vibration. @david-4 On the "more info" from the plugin page it provides this information: Credentials needs to be added to configuration in YoLink node server under PG3. In YoLink app goto Settings->Account->Advanced Settings -> User Access Credentials and copy UAID and SecretKey (alternaltive path in app is Profile->Advanced Settings -> User Access Credentials ) It is possible to get credentials for each home that is defined but the nodes server can only handle one of them currently Enter both UAID and SecretKey under configuration in the node in PG#'s browser page (scroll down if you do not see the fields to enter) - then restart - some times it seems to require 2 restarts to fully get all devices synchronized (I have looked but cannot find pattern) Sometimes a reboot of the ISY is required to make the node server show up correctly. If you've restarted the plugin a few times, and rebooted the eisy/Polisy then do a full power cycle (shutting down the device with the multi function button presses as outlined in the wiki. Lastly...are the YoLink Hub and eisy/Polisy on the same network? (They probably are since the hub is seen, but just wanted to make sure there wasn't some strange network setup happening.)

You don't do anything. If you've set things up correctly they should auto populate in the PG3x dashboard portion for YoLink in the "Nodes" section. It might require a webpage refresh to populate a number. You might also need to restart the plugin for it to correctly connect and import the nodes. You might want to change the log level to "debug" and restart the plugin and look for any possible errors it might have trying to connect. Allow a few minutes for the log to settle and you can turn off auto scroll and then look back what has populated, or you can download the log and open it and view in a text editor. Finally, be sure that you've closed and restarted Admin Console (as @drprm1 suggests). It's always best to have admin console closed when altering anything in Polyglot (PG3x) as the admin console only updates (PG3x changes) on start. Once you have the devices showing in the PG3x Nodes screen they will be visible on the next launch of admin console.

I think you should attempt further troubleshooting before you go back to 4.9. Many have run 5.3.4 without issue. It's likely a power supply issue or corrupt SD card. I would suggest you review the wiki for troubleshooting tips. Looking specifically at the lights on front of the ISY: https://wiki.universal-devices.com/Main_Page#Front_Panel_LEDs/Lights General troubleshooting: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Troubleshooting_Flowchart I never ran the ISY994 with UD Mobile so can't help with those specifics, but you should be fine with the ISY994 and 5.3.4 and think you've got other issues that could possibly continue if you simply try to roll back to 4.9.

Still stuck on 5.4? It's 5.3.4 What LED light? Something on the ISY994 or something on the device? It's possible it might not be compatible, but not sure. I would be sure if you delete it from the ISY994 that you're performing an exclude before including. Have you attempted to factory reset the device and attempt inclusion again? Others that used Z-wave in the ISY994 days (or even now) would certainly be better suited to help. My experience with z-wave has been limited and honestly I don't like the system all that much so only have 4 or 5 z-wave devices -- they aren't even currently active in my system. (For specific issues that you're experiencing - unreliable!) How many Z-wave devices do you have in your system? If just this one how close is it to your ISY994? It's possible your z-wave network isn't strong enough for this battery operated devices to reach the ISY994 card and you would need to have it closer to the door or build out a larger z-wave mesh network.

Unsure how you have this on an ISY994. The last firmware for the ISY994 is as @Techman says 5.3.4. Also according to the release of that firmware: Additionally, in the topic above you can find links to z-wave assistance that might help you. I believe the ISY994 with 5.3.4 was only z-wave certified up to series 500 modules. I didn't run z-wave in the ISY994 so never attempted anything in that line. I seem to recall that z-wave series 700 came out after Polisy was introduced so 500 might have been the last series UD supported on the ISY994. But I didn't pay much attention to z-wave previously so never kept up with what modules were offered in the ISY994.

@twired Glad you got them setup. Also take a look at what @Kentinada put together for some pointers if you want to get a little more advanced. There is a lot of information in the wiki about notifications as well: https://wiki.universal-devices.com/UD_Mobile#Notifications_Tab Lastly, the "free" version does have a limit to the number of notifications per day. I think it's 8. Buying the full version gives you a lot of additional resources. But you've found out what a lot of others have posted over the last few years is that email to SMS/Text is not as reliable as it used to be. Nearly all wireless providers treat it as junk/bulk mail and randomly delay or don't deliver. It's been the constant suggestion of getting the UD Mobile+Notifications system running. Another option was setting up network resources to push messages, but that is a huge learning curve.

I might still suggest the steps above to troubleshoot when you're home. At least check by controlling devices through admin locally first. If it seems that everything is good then that's a good thing, but it could be a flaky PLM that's misbehaving before it dies. It is odd that you say no z-wave devices are working wither. Are you running any firewalls on computers or routers? Do you have any non-default DNS servers loaded into your router? (sometimes alternate DNS entries could potentially block random sites without people knowing)

@woodfieldp did you ever get this sorted out? You might be best served with a support ticket with UD. https://www.universal-devices.com/my-tickets I don't use the wifi connection, but I seem to recall when I first setup the eisy that once it's connected to the router you can reserve it based on that connection and it did seem to work. My eisy is in the same location as my primary router so I have a short ethernet cable making the connection. One less "technology" to worry about being flaky. If you've got the ability to run it wired why not just keep using that?

Yep! Glad it helped. 👍 Guess you were meaning the z-wave board in the ISY994. Wasn't in the text of the post, but in the title. Didn't read them together.