Geddy

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.

@K-bert even though you opened a ticket have you performed a full power cycle of the eisy? Either by pressing the power button (Multi function button) 6 times to force it to shutdown or by pressing and holding or pulling the power supply. Also be sure that you cleared the Java cache and download a new start.jnlp from the UD site (https://isy.universal-devices.com/start.jnlp) Also, since you did open a ticket please be sure to post back what steps were performed to fix this so it might help others in the future. Finally, what IoX Firmware were you updating from? And what Firmware version did you upgrade to?

@JimTurner The ZMatter USB Enclosure was designed for those that had the original ZMatter board that went inside the Polisy. It is not intended for use with another Z-Wave product. If you have the ZMatter board it has to be modified to fit inside the dongle. (See this topic) If you have a different Z-Wave USB device it can be used with the eisy. I'm not entirely sure of the setup, but I have seen others mention they had a Zooz stick connected to their eisy. Just make sure you haven't enabled ZMatter on the eisy. You might search for "zooz eisy". I found this in a search:

@JSchumann I'm not sure if the appearance on android is similar to iOS, but on my phone if you're on the Notifications section hit the 3 dots in the top right for the menu. select "Mobile Devices/Groups" Click on the device you want to remove Top right should have a trash can to delete that device.

Review this portion of the wiki….might help with the Java install on your system. What computer OS do you run? If not Windows do you have access to a Windows machine? A lot less issues using a Windows system. https://wiki.universal-devices.com/Main_Page#Cannot_find_Valid_Java_Home Also…review this sections for the FRONT LEDs: https://wiki.universal-devices.com/Main_Page#Front_Panel_LEDs/Lights Is the blue light solid and super bright on the front of the device after powering on? If not real bright it could be a power supply issue. (This is also covered in the wiki)

If you access using the portal address then you have to use the portal credentials. Are you really using an ISY99i?

@JSchumann this topic is covered in the UD Wiki - https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:File_Menu#Restore_Modem_.28PLM.29 Yes, it's written for the older ISY devices, but the process remains the same with the modern devices. Be sure you've done a lot of troubleshooting to confirm it's a "bad" PLM. Lots of troubleshooting steps are also covered in the wiki.

No, don't keep attempting to restore the PLM. If it didn't help the first time it might cause issue in repeating. It's always been the suggestion of proper booting/powering up to have the PLM plugged in prior to any ISY/Polisy/eisy device. Plug in the PLM, wait "a little bit" (the light might flicker when first powered up). Once the light is green and steady then power up your controller device. Allow that to fully boot (for eisy could take 1-2 minutes+/-, possibly more if you have a very large system). Then log into admin console. If it's not in safe mode then the PLM should be connected correctly. From there you should troubleshoot any issues you still have. Troubleshooting steps for reference: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Troubleshooting_Flowchart# They're written for the ISY99/994 era, but still relate to Polisy/eisy for most items to check/confirm for troubleshooting with Insteon. If you're still having issues I would suggest opening a ticket with UD to get further assistance: https://www.universal-devices.com/my-tickets/ It's quite possible that something else changed in your installation that is causing poor communication with the PLM to devices in different areas and causing issues with connections to the device at your entry gate. Good luck. If you do open a support ticket please post back what resolves the issue to it might help others in the future.

The original instructions (from the wiki) were written for the older ISY devices (99/994). Those devices didn’t have a reboot process so pulling power was the only way to “reboot” them. Just know that the eisy can boot quickly so if the PLM isn’t settled as the eisy boots it could result in a “not connected” state and the eisy might need another reboot. Thus, when changing the modem it might still be advised to unplug the eisy and make sure the PLM is powered and stable before booting the eisy.

Did that resolve it? Wonder why it wasn't working/running? Wonder how this was happening if the plugin wasn't working. Do you mean outside of IoX things were functioning as expected? You mentioned that Alexa triggers were firing...do you have those setup outside of IoX/PG3 (i.e. Alexa direct Ring access - how however they call it..."works with Alexa")?

@andrew77 sorry the problem is back. Hopefully you can get some answers from the vendor as to if the product is defective or not. I'm not sure if your link would work, but might be worth trying if you can return easily if it doesn't work. Here are a few posts from 2022/2023 when the eisy came out about connecting the serial PLM to the eisy. Of course the best option is buying the "Serial PLM Kit" from UD, but shipping to Canada might not be an (easy) option. https://forum.universal-devices.com/topic/39206-roadblock-db9-to-rj-45-cables-are-unicorns/ https://forum.universal-devices.com/topic/40305-serial-plm-to-usb-adapter-alternative/ There was an extra cable in the Serial PLM packaging that had the DB-9 pin on the end. The first link above contains a link to an adaptor that a network cable could plug into. Then you could use a DB-9 to USB cable to connect to the eisy. I used this one: https://www.amazon.com/gp/product/B00IDSM6BW/

This seems to be normal. I have a Ring Doorbell Pro and also don't have a "ding" in the plugin. I have the same 4 items you have, but there's no battery in the Doorbell Pro (the version I have anyway). It's hardwired, but shows a "battery mV". My "ding" programs works as expected (just tested). If you check the program summary tab are the 2 programs you're calling on running? As @paulbates points out above it's possible they're running, but false. Therefore, not running the "then" you expect. Last thing I would suggest is to be sure the "Remote Connection" is Configured AND Active on the ISY/UD portal page. I recall it flipping off many months ago and was the last thing I checked to get mine working again. Thankfully hasn't been an issue since that time (for me).

Aside from what @Techman suggest I'd say get a "cheap" Windows 11 computer and use it for IoX. You're running macOS and seemingly have endless issues with IoX Launcher. This icon is for the JNLP file that would run and put the icon on the desktop. If you've run this file and it didn't put an icon on the desktop then it probably means the icon was deleted, but Java thinks it's still installed. Clearing the java cache (checking all 3 boxes) should clear this up. But, again...being on macOS not sure exactly what happens or if the directions to clear the java cache are the same as how they are for Windows machines. Glad you got it sorted out...again!

@CPrince depending on how old the topic/thread was it could have auto archived. It isn’t found in the normal forum search at that point. I would suggest trying Google Site Search to find the old thread you might be looking for.

@Me2 Glad that fixed it. Not sure why you added that in the folder conditions, but now you know another place to look. Once you posted the summary screenshot and I happened to see the "My Programs" (typically the root) was false I knew it was what needed to be fixed before anything worked. Should allow all other programs to work properly too. Still odd that you said the other one worked. Maybe the folder condition got added recently and/or the motion sensor is directly controlling the other device? Still a mystery there...sort of. But if they all work that's the winner!