Geddy

@JWBDolphins split your post out to it's own topic since the old topic was a little stale (OP hadn't updated the issue since early April) and your situation is different coming from a migration. Please update after reviewing the tips @Techman and @paulbates have suggested.

When you log into my.isy.io there should be a green dot/circle next to the device. Just hover over that and it will show when it connected. If it isn’t green then it means disconnected and hovering over it will show when it disconnected. Disconnections don’t always indicate portal issues. It could be ISP/local network issues. If you get login errors when trying to log into my.isy.io might indicate a portal issue.

No issues here. Portal page shows my device has been online since Thursday evening (6/12).

All Insteon devices have set buttons. That's how they begin the linking process. While wiki the information is old it still somewhat applies to the current day controllers. Here's the information about linking devices: https://wiki.universal-devices.com/ISY-99i/ISY-26_INSTEON:Link_Management_Menu#Start_Linking You can also review in the ISY Cookbook that can be downloaded from the wiki. It too was written for older controllers, but still applies for most general Insteon setups.

@Ray95xxx your best bet is to open a support ticket with UD to get help to see if they can get things working again. https://www.universal-devices.com/my-tickets Do you have the Z-Matter board installed internally or via the USB dongle? If it's via USB try a different USB port and power cycle the device again (by pulling the power supply - waiting 60+ seconds before plugging back in). Since you said you ran the "upgrade packages" process please share your Firmware you're running. Don't just say "it's current", please give specific version number. Should be able to find it in admin console, but it would also help to get the full number/build info. Please go to this page when local to your device: https://polisy.local:8443/WEB/sysconfig.txt (NOTE: You might need to replace "polisy.local" with the IP address for your polisy. If you get a warning about security please press advanced and "continue to site". Since this is an internal device it's fine to proceed.) If you do open a support ticket please post an update for what is done to get this working again so it might help others in the future.

Even though the test is going through check our "Timeout (ms)" setting. Make it higher. I have mine at 5,000, but it's been suggested to set it to 10,000. What is your setting at before you change? You're correct to be using the app password. Again, if you are getting the test then it is successfully sending. If changing the timeout doesn't resolve the error then maybe reset the app password, but doubt that's an issue.

@msingold yes - see post in the UD Portal area: This was the initial issue. Apparently there was another brief drop in the evening of 6/12 (eastern time), but that only lasted a few minutes. Then the time to reconnect all devices meant some were offline longer than others.

@msingold if this has mostly been in the last 24 hours there have been a couple of portal down time that seem to have recovered. If this has been going on a long time you might be best helped by opening a support ticket to see if there are underlying issues. https://www.universal-devices.com/my-tickets The eisy does sometimes run warm, but it is designed that way. If you keep it in an enclosed area this could make it run warmer due to low air circulation.

@midrar from my personal use of the plugin it works fine. Others have had issues getting it to work or other issues, but for my simple setup this works fine. I haven't attempted to "cascade" lights, but having lights activate when other triggers occur has worked well since setting this up when I got my eisy. Be sure you set an IP reservation for the Hue hub in your router so it is always at the same IP address. The plugin doesn't like if/when the hub IP changes.

Was a portal outtage overnight - shoudl be back to normal. @bmercier posted an update -

@sdcrane @khag7 there was a portal outage. @bmercier posted an update. Should be back to normal.

@larryllix I tried the CAO Wireless tags, and still have several in place, but the battery life was worse than 8-10 months in some places and that's with very minimal updates. I think my freezer tag needed to be replaced every 3 months...at least recently it seemed that way. There are some quirks with those tags and every now and then the whole system goes haywire. I've just found the range and reliability of the YoLink worked out better for me. Also, the YoLink sensors have a display. If I am just grabbing something out of the freezer I can glance at the temp. I've had the YoLink in the freezer almost 18 months on the original batteries. Sure, it's 2 x AAA size (35 cents per battery), but to get that life is better than 5-6 (with my experience at 50-60 cents per CR2032 battery) the cost works out better with the YoLink. Just from my own use experience. Both have good options and fit for most.

Since these are "Ring" branded items it might only work (well) with the Ring Alarm system. It might be connecting to the Polisy Z-wave controller, but the Polisy doesn't know how to handle the sensors. From the product page you linked to: You would probably want/need something generically branded for z-wave to possibly work. Otherwise, I think @paulbates has a good idea of moving something closer to the Insteon sensors. It is possible you are beyond range (or very limits) even though the box they're in is "thin". The signal still has to go through walls/boxes and "stuff" that can really kill the RF signal. I'm not sure how others have handled gate setups, but know several have talked about it in the past. Perhaps a Google Site Search might help find some older threads.

@JimTurner the specific .state file you need to delete is: "udi_launcher.state" That will remove all "found" and added devices. Then the next time you launch IoX Launcher any listed devices will be what are found automatically. Since you said it's "grayed out" it's automatically being added when IoX Launcher loads the IoX Finder window. Another option might to clear the java cache (be sure to select all 3 boxes). Delete any "start.jnlp" or "admin.jnlp" files on your system. Download a new "start.jnlp" from the UD website (click "My ISY" on the top right). Then run the new start.jnlp to re-add the IoX Launcher to your desktop. But deleting the .state file should get it cleared up. If it returns again and is unable to be deleted then it must still be on without your system and connected to your network (even though you say it's "offline").

@JimTurner this should be in some of the ud*.state files. If using Windows look in the user - appdata - local - temp folder. Usually they aren’t hidden, but if you don’t see them maybe adjust to see hidden files. More from the wiki: https://wiki.universal-devices.com/Main_Page#Admin_Console_Minimized/Invisible_and_Cannot_be_Restored