Geddy

@Rex Gruenwald a 503 error makes it sound like you're not even able to see the login page. Is that the case? If so then PG3 might not be running correctly. Did you run an update process recently that might have failed to complete? When you power cycled the device did you allow a while for it to fully boot before trying? I would suggest you open a support ticket with UD to get proper support for resolving. https://www.universal-devices.com/my-tickets Please be sure to post here what is done to resolve your issue.

Actually I moved it to the YoLink plugin area for discussion and help there. Don't get too into the details until you have the eisy and have migrated your current system to it. Be sure to read, and maybe print, the migration steps from the wiki. There's a lot to be aware of in the process.

@Illusion a very random and probably insignificant option. Have you tried using a different network cable connecting the Polisy to the router? Maybe one of different length or manufacturer. I would go as far as suggesting it be a "new to you" cable and not one that's being used elsewhere or been used in the past. Another suggestion would be do you have any way to connect the Polisy to the network through another device other than directly to the main router? Not sure of the fiber modem options (I have cable not fiber), but does it have multiple ports that you're able to use? Do you have another network hub somewhere you can remove the direct connection from the router to the Polisy?

@Illusion I don't run/use macOS so I was just sharing what I found from a Google search and not even sure what browser it was for when I did it. Glad you found whatever runs a browser refresh and glad that worked.

@btreinders glad it was that "easy" to fix. Guess something got stuck in the initial install.

Worked as received. Open package. Connect PLM Serial cable to it. Connect to eisy. WORKED! Note: that it's specifically the SERIAL cable (with the DB9 connector) and not the cat 5 (RJ45 connector) that's used from the PLM to ISY994. I went from ISY994 (cat5) to Polisy (serial cable) to eisy with the same PLM.

@johnstonf you'd need something like this: https://www.amazon.com/gp/product/B00IDSM6BW/ I've used that to connect the old serial cord to the eisy since I got the eisy. Works really well. UD sells a different cable now if you don't have the original serial cable that came with the PLM.

@Rex Gruenwald additional information needed.... What device are you using? What's the error it's giving you? Have you tried the default admin/admin login? Did you update the system recently that it could be stuck or not loaded? Have you attempted a power cycle? Please let us know the error and what troubleshooting you've attempted then maybe more tips can be attempted.

@lilyoyo1 thanks for posting that link. I knew there was a thread with the information somewhere. However, reading through that seems one user had an issue and a different command was needed (never posted that information). I still think a support ticket might be the best way to get it done "correctly"/accurately since IoX (and other underlying information) might have changed in the last 2 years.

This is an interesting point. What if you keep the portal connected, but turn off any system and ud communications notifications in UD Mobile? (In the notifications tab tap the 3 dots then "Mobile Devices/Groups" and turn off for "System Notifications", "UD Communications", and "Plugin Notifications" to all groups/devices). I might also stop the notification plugin. Then test the internet drop. I would think they would target the connection to the portal since that seems to be a big data point for if it's not connected to your account then IoX isn't restarting. Also, do you have "Query at Restart" set on the IoX Config tab? Lastly, along the lines of what @Guy Lavoie suggested, do you have any programs that are stuck in a loop if you lose internet? Perhaps a random program checking a status of a wifi device or a plugin that requires internet and is suddenly in a fast loop if the internet drops that's causing the IoX system to fail? (though I would expect something like that to be in a log that would be seen by now.) Very interesting situation.

@CJVann I think there is a way to override that and allow other Z-Wave controllers. You should open a support ticket to get assistance (if it is still possible). https://www.universal-devices.com/my-tickets

The “rest” of the story:

@flsenior The preferred method for posting programs to the forums is to right click on the program. Select the bottom option of "Copy to Clipboard" (be sure you use COPY). Then paste the program to your post. This makes the program editable by any that are trying to help you rather than having to re-type something or refer to something in an image. Additionally, does this relate to the post you made yesterday?

@lalang looks like @Guy Lavoie and @paulbates are giving great options and information. One question I have is how's the power service out to the pavilion location? Is it on a different power supply or is it a branch off the main power supply from the house? Since Insteon uses power line communication in addition to the RF signal it's possible you need a powerline booster (of some sort) to attempt to increase the signal going out to the pavilion. If the power is from a separate feed there would need to be a way to bridge to that feed or keep it as second eisy. It's kind of overkill if you're only going to have a few devices in that area so it might be better to look at how power and range can be improved to get the Insteon signal out to the pavilion or look for an alternate option (if just for a few devices). Others know a lot more about how the signals work. I'm just asking the question about how power gets out to the area. If you're running Insteon devices out there now and it's hit & miss then you just need to get a better path for the Insteon signal to get out there. If it's completely unavailable then it's probably a different power supply and fewer options.

probably shouldn't, but if you leave it open I'd close it. Again, the question is does the plugin node on the web indicate the proper percentage? If not then the plugin is not talking to the outside system correctly. From my understanding the plugin is only capturing the data from the 3rd party API then feeding that to IoX. If the PG3x node is not showing the battery percentage correctly then indeed the information being pushed to IoX would be incorrect. Perhaps @Panda88 has more info/insight as to what's happening. If you confirm PG3x doesn't have the correct data then you'll need to troubleshoot the plugin more.

@wmcneil Since you have a ticket open you would need to reply to the existing ticket to possibly make it active again or to bring it to the queue again. It's been stated many times in the last couple of years that the forums are user-to-user support. Yes, UD might monitor the forums and answer questions that are easily answered, but for more involved support it's best to run through the support ticket process.

Do you leave admin console open 24/7? Typically the data does not refresh if Admin Console is open. If you close and relaunch admin console it might update. Are the correct percentages shown on the PG3x node levels? If so then it's working as expected. Admin Console refreshes nodes and data on launch or manual refresh (as you seem to indicate). It's not a "live" system. At least not that I've experienced. Also note that admin console is not designed to be left open 24/7. It's meant to only run when actively changing/programing IoX. Make your changes...close admin console.

It doesn't appear this plugin is supported any more. There have been other posts in this area of issues getting through discovery or updating nodes and status. I think most have either moved away from this alarm panel type or not linking it to IoX.

F5 is a browser refresh (for Windows). For the Mac use Command + R. Might even need to try a "hard refresh" - for the Mac that's Command + Shift + R.

@abrayshaw (split your post out of a resolved topic that had no activity for 4 months so you might get more attention to your situation.) First off, please confirm you're running ISY994. Let us know (if you can) what Firmware and UI you are running. I realize that if you can't get into admin console (to get the UI), but if you're seeing the ISY on launcher it should say what Firmware the device is running. Did you select all three boxes in this process? The 3rd box clears the installed IoX Launcher icon from the Windows desktop. You'll need to download a new start.jnlp from the UD website to put the icon back on the desktop. Alternate method would be to download the admin.jnlp file directly from the ISY (web browser go to: http://ip.address.of.isy/admin.jnlp). Last question: What computer OS are you using? Windows, MacOS, other Make sure you've got "plain" java downloaded directly from java.com and not a special version or higher version than just downloading from java.com (showing current as of today: Version 8 Update 441).

@PapaBear just out of curiosity, what firmware are you on now (after running the "upgrade packages")? Glad they got you sorted out.

As @paulbates indicated I had heard that the i3 were smaller switches making it easier to install in multi-gang locations. The switch you're talking about might be different than the single paddle/outlet design. Glad it seems you were able to get the device renamed in IoX with a restart. But that's still tricky. You might want to open a ticket with UD to get that clarified for if it's a "known" (or unknown) bug with the i3 line. I recall @Michel Kohanim commenting that the "new" Insteon was willing to work with UD and they were working with them to support the i3 line better and fully. Don't recall other issues mentioned in the past so might be a new bug or perhaps something with that device family.

Thanks for the warning. Hopefully there's a "fix" in the works for this. With your ticket are you just sending the eisy back or are they helping sort things out to get it operational and able to setup Z-wave again?

@flsenior the eisy is just like the former ISY994 (or older) devices. If you've set them up before they would work nearly identical with the eisy. Since you've been registered here since 2011 I'll assume you're coming from another ISY device. If an existing install probably very little should need setting up. However, if this is a new install then you will be starting from scratch and you'll be able to setup what works best for your situation. You can always download and review the (old) ISY Cookbook (found in the wiki: https://wiki.universal-devices.com/Main_Page#ISY_Cookbook). I'll just caution you that the cookbook was written a while back pre ISY 5.x firmware so some things have changed (scenes mostly). I'm not sure if the wiki scene portion has been updated to 5.x setup, but review the wiki and then program and adjust as best fits your needs. Personal preference. Are you controlling the devices at the same time or various times of the day? If at the same time then make a scene. Are you trying to brighten or dim devices (use programs to adjust the scene) I'm not 100% sure on this one. All my 3-way are using the same type of device. I would need to have somebody else chime in for actual use case on this. I think the question might be do you want to be able to dim the devices? If so I'd say put a dimmer on each side of this. If you're just doing on/off then maybe either would work, but again, not 100% so don't risk it. I'd just make them the same type of device. 3-way will be a scene. There is a way you could control with a program, but the suggested way would be scene. (the Cookbook might help answer some of your questions) Review the cookbook. Make both controllers so they would both show "on" when the other was flipped on. I'm not sure I understand what you mean by "main eisy scene". One difference from ISY 4.x to 5.x was the loss of "copy scene attributes" (or whatever it was called). This was due to the inclusion of Z-Wave certification. If you mean for the scene properties when you click on the scene name in the device tree you should set the device properties there, but I think it also needs to be applied at the device level. I don't use scenes much beyond 3-way handling for halls and stairs so a more experienced user with scene skills would need to chime in to help. But through reading the cookbook and setting things up I'm sure you'll get the hang of it after adding a scene or two. Just remember if you turn the scene on using admin console it might be different than physically operating a switch so test at both levels as you setup. Be sure to review the wiki for a lot of details: https://wiki.universal-devices.com/Main_Page#

@Illusion have you tried refreshing the page? Just hit F5 and see if that refreshes it to show a more accurate time. Otherwise, I'd not worry about it too much. Not that impactful (IMO).