Geddy

@johnstewart what firmware are you running? And are you running any z-wave currently? If what you're running is working then I'd stay with it for the ISY994 since it's no longer supported by UDI without paid support. The primary warning is from 4.x to 5.x firmware on the ISY994. It's been out so long and I did the upgrade so long ago that I can't remember all the pitfalls, but the main ones are any programs that used "adjust scene". Due to a major overhaul of how scenes were handled in 5.x (due mostly to the introduction of Z-wave..IIRC) the programs need to be updated. Sometimes that's as simple as just selecting the program confirming the scenes and saving all programs again. If you're on a firmware pre-4.9 then you should at least update to 4.9. Going up to 5.3.4 is advised as long as you don't have/use z-wave or have a z-wave 500 series board. There's a post in the z-wave area for the 994 that describes how to tell the difference between the 300 and 500 series. In all, the key steps to going to the 5.3.4 firmware would be make sure you make a good backup. Save programs to a text file (right click on the root program folder, last option is "copy folder to clipboard" then paste in a plain text editor (i.e. notepad in Windows - DO NOT USE WORD or other word processing type file as it might auto correct/format and you don't want that!). After you run the update clear java cache, download a new start.jnlp (IoX Launcher) file from UDI and you should be up and running. If you do update and run into problems please start a new thread for help with that issue as many might not read this post if you start posting about firmware upgrade issues. Good luck! PS: Note that if you wanted to upgrade to the eisy and wanted to migrate from the ISY994 to the eisy you would need to get to Firmware 5.3.4 as that is the only migration path option.

Correct. There aren't any speakers on the eisy so no beeps. Flying blind on updates most of the time! I think a recent change in admin console does somehow alert you that updates completed if you leave the window open during updates. I haven't really worried about it as I usually run updates late at night when I'm the only one active and come back to it a while later and check that things are running as expected. I'm not sure about that. Since I don't have a Polisy I'm not sure if that would go away or not. What version IoX are you on? I'm not sure if UDI has something in the IoX Launcher code to know it it's connecting to a Polisy or not. For my eisy I just have the following: Have you cleared our java cache and downloaded a new start.jnlp to see if it went away?

@mmb Great! Glad it's working. Make sure you reinstall all node servers! While I kind of miss the beeps of the Polisy I also saw it as troublesome because I was always on the other side of the house so couldn't hear the beeps when I would reboot the device.

Marched right into PG3x! Have you pulled the power supply? Or just using the reboot button in admin console and ssh commands? Make sure you're forcing a refresh of the webpage. Sometimes cache will get stuck and report incorrectly. Odd that your IoX is showing disconnected. I've never made the jump from PG3 to PG3x on the Polisy so not sure what all is going on. You might need to run Upgrade Packages again from admin console to get things to run correctly. Make sure once you get things matching in this that you go through the "re-install nodeserver" step. That is often times something people have been missing. It's not broken out as a step to focus on, but certainly something that needs to be done following the PG3x update. But shouldn't be causing the issues you're at currently. That seems more like a power cycle will fix it or a forced web refresh.

If you're on 3.1.21 are you on Polisy and still on PG3 (not PG3x)? Based on current release area 3.1.21 was the last mentioned release for Polisy PG3 - https://forum.universal-devices.com/topic/41246-pg3-version-3121-polisy-may-22nd-2023/ To get beyond that you would need to update to PG3x (please note that doing so will remove PG2 from the Polisy. To move to PG3x on the Polisy the process is in the wiki - Polisy User Guide.

@whslec welcome to the forums! While @bmercier is great and helping you out already I want to ask something specifically just to make sure you're both going the right direction... You originally said... This would indicate that you can't get into Admin Console, but then you said... So, what do you mean by it "does not recognize your network"? The ISY/UDI Portal is: https://my.isy.io/index.htm Once you're logged in there it should list your device and will have the UUID with the status next to it (like this): If you mean that you don't have a device showing on your portal account then you need to set that up. Read this page of the wiki for the process (last section applies to adding the device to your portal account): https://wiki.universal-devices.com/index.php?title=ISY_Portal_Installation_Instructions Otherwise, since you're able to access the device with Admin Console you should be all set. From here check out the Polisy User Guide on the wiki and skim the forums for burning topics you might have questions about. Good luck! Welcome to the crowd of UDI users and enthusiasts!

I agree, but I'm sure 994 had its growing pains too. I was "late" to the party with the 994 just before they went into 5.x beta versions. I can recall a lot of issues during that development. Thankfully many take for granted how reliable systems were, but more so how "basic" they were (even though advanced for what they could/can do). With an almost limitless expansion in the Polisy/eisy era with Polyglot the variables to cause issues are just as limitless. While my eisy does seem to run just as stable as my trusty 994 many appear not to be as lucky. However, I'm not trying to run a bunch of different systems either. I know it's the desire of UDI to have a device as stable and reliable as the 994 (based on posts made elsewhere over time). It's just a lot harder to hit a moving target these days than it was in the past.

@thedishking what PG3x version are you running? I think random disconnects was something fixed recently. Current release area shows: PG3x 3.1.36 There's a beta post for PG3x 3.1.37 if you wanted to try that. Somewhere in the past I had a time where node servers would drop connection and not re-start. I have not had that problem recently so not sure if you're running an older version of PG3x or not. If you are at 3.1.36 or 3.1.37 make sure you fully power cycle the device (by pulling the plug). If still experiencing the issue please submit a support ticket so UDI can properly document your issues and attempt to fix for you, but also improve PG3x moving forward. https://www.universal-devices.com/my-tickets

Are you using the same computer for when you're home and when you're remote? This happens a lot to me when I'm trying to connect from a different computer to a remote device. The address is just gone. Best ,"simple", solution is to save the current addresses in the IoX Finder window by clicking "SAVE" on the bottom of that window. It will save it to a file like this "ISY-Finder.Thu 2023.07.27 05.37.20 PM.state" You can rename it to something like "Property A ISY Address.state" and/or "Property B ISY Address.state". Then load the appropriate file if it blanks out depending on your location. Saves you the effort of logging into the router to get the IP address each time you move locations. But...be sure you setup IP reservation with the routers at each location so the device is always at the same IP! Another solution is if you have portal subscriptions for both locations you can add the Portal URL then save the file (as above). You then have one file with both locations listed. Just log in using the Portal URL/Address (and credentials) each time. It's not location specific that way.

Do you have the Hue hub set with an IP reservation in the router? Do you have the IP referenced in the node server setup? Are you running this on Polisy or eisy? If on Polisy is this PG3 or have you migrated to PG3x (this is not a suggestion to go to PG3x if you haven't only a question...don't blindly go to PG3x without reading more about it - note the process removes PG2 from the Polisy) As I said, I'm running this node server. I'm on eisy so PG3x. I have the same udi happening, but not queuing. I put the log into debug and restarted the node server and did get this QUEUING line, but it went right though. (snip of my log below) 2023-07-27 00:00:08,551 MQTT udi_interface.interface INFO interface:_message: Successfully set 88010958c2dd0b :: GV5 to 24 UOM 100 2023-07-27 00:00:08,679 MQTT udi_interface.interface INFO interface:_message: Successfully set 88010958c2dd0b :: ST to 9.4488 UOM 51 2023-07-27 00:00:08,784 MQTT udi_interface.interface INFO interface:_message: Successfully set 88010954beaa0b :: GV5 to 64 UOM 100 2023-07-27 00:30:24,003 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message longPoll 2023-07-27 00:30:24,004 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING longPoll If your router has the hub at a static IP then the node server should find it. And it wouldn't work if it's not finding the hub at other times of the day so that's probably far fetched for troubleshooting, but worth checking. Maybe it's reloading something at midnight and can't find the hub so causes a drop. When it drops does it reconnect and stay running? How long before it reconnects? (on the UD Mobile notifications) At this point I would suggest you open a support ticket and supply a full log for the node server and possibly a PG3/PG3x log package with your ticket so it can be reviewed. https://www.universal-devices.com/my-tickets

Not sure. I don't have any Zigbee devices so haven't done any testing yet. As @xlurkr points out he knows of one that doesn't work. If you've got some try them out. If they don't work open a support ticket letting UDI know what brand/model/function doesn't work. Maybe they've got to fine-tune/target specific brands. As with Z-Wave it appears that Zigbee, while a standard, allows each manufacturer to handle things differently. It's got to be a crap shoot for UDI to figure out what does or doesn't work. This is where the user base trying what they've got and letting them know first hand really helps UDI and the rest of the userbase.

@pkauf it happens. But to get on the list of included devices be sure you put the device with the brand (and other info) into the request thread:

@pkauf As @lilyoyo1 pointed out these devices aren’t supported yet. The release post is found here: What you need to focus one is:

Could be Hue device (hub) issue. I run same node server and don’t have any disconnect issues. Perhaps the network connection to the Hue hub is going out or the device (Hue hub) is having other issues. Download the log file from the node server and see if you see anything happening at midnight. Not sure if the Hue app has any history or logs.

@saclarkdoc plug in network cable and reboot (might not be needed, but good idea). The eisy will disable wifi automatically. Note, since using a different network connection the IP address might change, and if you’ve setup DHCP reservation for the wifi MAC addresses you’ll need to alter it for the wired MAC addresses. But as @DennisC suggests…please read the wiki for the eisy User Guide. It has a lot of good information that helps.

@xlurkr What firmware are you running? And have you power cycled the Polisy since any recent firmware update? There were reports by others that Z-Wave quit working with recent Zigbee firmware release that I think is being worked on. I haven't noticed any other comments about the Zigbee portion not working now. You might want to open a support ticket if a simple power cycle doesn't fix it. Either use the multi-function button to reboot the Polisy or remove the power supply, wait 30-60 seconds and plug it back in. Wait several minutes before attempting to open admin console.

I always prefer and suggest wired. Less chance of something blocking/interfering with a wired signal Support ticket - https://www.universal-devices.com/my-tickets/ If you don't want to open a support ticket then use Google Site Search for this forum and enter the errors with quotes around them and you'll find several posts and options of solutions.

So what you’re saying is “works as written in the User Guide”? https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide

Yes, works exactly like it did for my ISY994. Cannot handle node server devices, but perfect for Insteon devices. However, I would suggest looking at setting up UD Mobile for full feature access with the eisy.

Looks like you started a new thread about this that has you going down a path to solution. Locking this one so you’re not getting help on the same issue in two places.

Yes, Moblinc (Pro) works with the eisy (at least as of current attempted use) but only for basic Insteon and Z-wave devices. It does not allow any node server or Zigbee devices to be found. You might want to begin looking at UD Mobile as an optional replacement. Information for that can be found here on the forums and in the UDI Wiki. Especially since Mobilinc hasn't been updated in ages.

@Spencer welcome to the forums! How are you connecting while remote? If using the ISY Portal then you don’t need a local setting. See the wiki for setup using ISY/UD Portal https://wiki.universal-devices.com/index.php?title=ISY_Portal_MobiLinc_Configuration The connection only uses one user/password. If you’re using a portal to access while remote you cannot use a local setup as well because that will use the admin/pass for local connection. Leaving the local server and ports blank will allow connection through the portal to work no matter where you are.

Probably because not many people use such programs these days. That wiki page hasn't been edited since 2018, and before that 2016 so I'm sure all the programs have changed a lot through the years. Glad you got it working though! Good luck finding the setting in the latest version of the firewall software. I'm sure it will move to a different spot next version. Gives them a reason to charge for "updated" software.

No, those are just clock entries. Not sure why they're happening, but they remain out of sync. That's been an issue some commented on when the eisy was released. The only traffic is are the events at 12:46:16 mentioning "Restore". I just opened my event viewer for a few minutes and get this: Wed 07/19/2023 02:06:24 PM : [ Time] 14:06:25 1(0) Wed 07/19/2023 02:06:54 PM : [ Time] 14:06:55 1(0) Wed 07/19/2023 02:07:24 PM : [ Time] 14:07:25 1(0) Wed 07/19/2023 02:07:54 PM : [ Time] 14:07:55 1(0) Wed 07/19/2023 02:08:23 PM : [ Time] 14:08:25 1(0) Wed 07/19/2023 02:08:53 PM : [ Time] 14:08:55 1(0) I don't have any motion sensors and had no other Insteon traffic during this time.

Unsure if there's a "simple" way to wipe out IoX so I'd suggest opening a support ticket and see if that's even best course of action. There might be other "tricks" they can suggest given the current state of your system. Since the front power button is the multi function button used to reset the function it's best just to use a finger to press it. Paper clip isn't needed. I'm not sure if there's another button to push that would need a paper clip to access (It's been a while since I examined the eisy case). I think this will be part of what support needs to help with. If you've got the new PLM connected to the eisy and Insteon support box checked (on configuration tab) and you've linked the devices again then you shouldn't have issues. Also make sure that your Firmware and UI match (Help -> About). More than likely your devices aren't linked properly. I think you made a comment earlier that devices were added from the restore attempt, but you weren't able to control them. That's because the eisy and PLM are probably unable to communicate because of broken link tables from a (probable) failed migration attempt.