Geddy

Glad it was that "easy". There have been some issues along the way with the reboot button not fully forcing a power cycle and something about the UDX or MQTT (or something "technical") not starting up right causing such an error. So a power cycle is usually the best option to fix that so the system fully boots up and starts the systems needed to launch PG3x and IoX correctly. Glad you're on your way!

@jpoje Thanks for sharing. Have you performed a full power cycle of the eisy? Even though you might have updated and then pushed the "reboot" button in Admin Console sometimes a full power cycle is still needed to get things working correctly. You can either press the power button 5 times to reboot the device or you can press it 6 times to power it down (power led should turn red) then unplug (just out of habit this has been suggested) then plug in and allow it to fully boot (3-5 minutes). (Source for button press: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Multi_Function_Button) Then try PG3x again.

Can you share a screenshot of the error or link to the other posts you mention? Without seeing your error there's little that we can do to help. Most would just be suggesting what you said you've already attempted by reading the wiki and/or other posts. Also, let us know the following: Computer OS (Windows, macOS, other) Browser(s) you are using or tried using Are you running any antivirus/vpn/pop-up blocker? Do you have different V-Lan setup inside your network? Is the eisy connected via wi-fi or wired network? Lastly, since you said you've tried all that you have seen mentioned in the wiki/forums it might just be time to open a support ticket with UDI (https://www.universal-devices.com/my-tickets) to see if they have thoughts for how to get you into PG3x interface.

@GSutherland I'm not really sure where this fits so moved under the Notification node server for now. Perhaps a little more information would be helpful to get you moving toward a solution. What kind of phones are you using? What OS are they on? What version UD Mobile are you using? What PG3x version are you using? I don't use the Notification node server other than the basic that's offered so uncertain what you're meaning by the "GPS envelope", but I have an iPhone 15 (iOS 17.0.2) with UD Mobile 1.1.24 and my geofence works okay as long as the app is open. I've found that if I force close the app then geofence crossings are not being updated with UD Mobile. Without the additional information I'm not sure if @Javi or @Jimbo.Automates would be able to help narrow down the possible issue for why one phone works and one doesn't.

@MLozevski Welcome to the forums. What's the reason for looking for files in a compressed/archived backup? The restore process uses the zip file not individual files. So any attempt to alter/edit files within the backup could corrupt the backup and cause a future restore to fail.

When you look at Help -> About in Admin Console it should give UI version. You're issue sounds like UI doesn't match firmware. (Old screen shot for reference - make sure Firmware/UI match exactly) If you're using the "Local" method to connect try the "Cloud" option once and see if that works. If that does then you're FW/UI aren't matching and you need to completely clear the Java cache as @DennisC suggested (checking all three boxes - even though you said you did that). Remove any start.jnlp or admin.jnlp you have on the computer and download a fresh copy from UD's site and clicking on "My ISY" (https://isy.universal-devices.com/start.jnlp)

Got this, and first use it did NOT crash. So that’s hopeful. Thanks for the update. Any luck getting geofence crossings to work with the app not running (or in background). Running iOS 17.0.2.

This has been fixed…you need to clear Java cache, download a new “start.jnlp” file from UDI site (click on “My ISY”) and it should be fixed. This was reported several weeks ago and downloading a new IoX launcher seemed to fix it. Make sure you delete any existing start.jnlp or admin.jnlp files before proceeding. You mention Polyglot, but posted in ISY994 area…moving to IoX since it’s not really clear you’re using the 994. But agreed, with @Javi it’s not really a firmware issue, but you are behind. Many bugs have been fixed and enhancements made since 5.5.9 so you should try to stay current. You need to clear Java cache and download a new start.jnlp file. Make sure you delete any existing copies on your system before proceeding.

@tibbar check this list out: https://polyglot.universal-devices.com/ You can read what each does and consider if works for your system(s).

Yes, that should be it. I think it’s the root folder name in the tree of devices. Or first folder under it that things are nested in. Not looking at it at the moment to know which folder name it is using.

How are you accessing it if not via admin console? What computer OS are you running? (Windows, macOS, other) what firmware is your device? You’re posting in the ISY994 area so do you really have a 994 or other device? Make sure you’re using the IoX launcher (start.jnlp) from UD’s site….download a fresh version from the UD site and clicking on “My ISY”. (Clear Java cache again before attempting this again just to be sure.)

@jkraus depends on the name of your device, but the program would be like this: 00-Query All - KEEP If Time is 3:10:10AM Then Set 'eisy' Query Else - No Actions - (To add one, press 'Action') Look for your device name near the bottom of the list of devices maybe after scenes or near them.

That's not the way UDI is pushing updates these days. There's not a way to cherry pick which OS you want to go to. You press the upgrade packages button and you get the current version that is available.

@TheWabit this seems to be an issue that happened in updating to 5.7.0, but appears there is a fix. Please review posts from today in this thread: Locking thread as discussion can continue in support thread linked above.

@EWhite just unlocked the old topic. Not sure who the developer is (Showing TangoWhiskey1 on the store, but no user here with that name). Might be better to raise an issue on the github - https://github.com/UniversalDevicesInc-PG3/udi-shelly-poly/issues. Developer might not be active on the forums or might have abandoned the node server. This might be another one that @bpwwer migrated from PG2 to PG3, but doesn't appear to have any updates since 2022.

If you made a backup before you updated you can restore the backup and it seems to restore programs to enabled/disabled status prior to backup. At least it did for mine.

@RRalston gotcha! I haven't looked at that section in ages to know if it ever showed the current IP or not. I thought since it wasn't an editable option that it just defaulted to 0.0.0.0. I looked at an older OS running on an old Polisy and it reads 0.0.0.0. So thought that's always been the case and never occurred that it needed to be "fixed".

@Kentinada Did you attempt to restore the PLM? It's possible it was wiped as part of the repair process so the ISY994 might find it as a new PLM. Review the Wiki for PLM Replacement steps: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:File_Menu#Replace_Modem_(PLM)

Hasn't this always been the case since 5.x (something) on Polisy and eisy? It's been defaulted to "Automatic DHCP" since the eisy was released and if not from release of the Polisy a very early IoP update probably set it to where this was unavailable. UDI does not want the devices to be set to static IP on the device anymore (too many support tickets with old ISY99/ISY994) that it was removed from Polisy/eisy settings, but the boxes are still there. Just never populated.

@raydoc aside from the comments above to update the firmware you should review the "replace device" instructions in the wiki: https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Replacing_a_Device It's possible you've got devices in folders and they need to be moved out to be replaced. 5 button? Thought they only had 6 and 8. On the main entry for the device right click and see if you have a "group devices" or "ungroup devices". Did you happen to factory reset the (any) device before adding to the ISY994? When you're adding new devices it's good rule of thumb to factory reset the new device as part of the linking process. This should force out any internal links or programming that you don't want introduced into your system. If you don't see the other buttons after you ungroup or group the devices then you should perform a factory reset and re-link it to the ISY994. Since you've probably been running just fine with 4.0.0 firmware I think it's possible to try to fix your issue before updating, but do understand that 4.0 is extremely outdated. Any help/support in the forums would probably be very limited as most have moved into 5.x and even onto the Polisy and eisy product lines. Further, UDI is no longer supporting the ISY994 so only paid support is available with UDI for the next few months. Instances like this with replacing devices or using newer Insteon devices it would be wise to consider further upgrade options moving forward.

@barrygordon do you want it to run the program only if the switch is physically turned on? You might want “control” rather than “status”. If using “status” then anytime the switch is “on” (by any means) the program would be true and run. https://wiki.universal-devices.com/index.php?title=ISY-99i/ISY-26_INSTEON:Program_Commands#Control_vs_Status

If you read the link I posted there are specific directions to go from Polisy to eisy. https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Preparing_for_Migration_from_Eisy_/_Polisy I haven’t attempted such a move so only going off what is written in the wiki and lots of posts in the past that the directions worked when they followed them. Again, the PG3x might change things. As I think the node server migration process was only intended for PG3 on Polisy, but now that many have PG3x on Polisy I don’t know if the portal migration will still transfer the license. You might want to open a support ticket to ask that specific question if not answered here by others over the weekend.

@BrianN324 thanks for the update and glad changing the DHCP to what the old router was worked. I'm the same way with the 994 in the past and fixed it the same way. Now, before you go too much further...turn off static IP on the ISY994 and setup a DHCP reservation in your router. As you mentioned it was just "easier" in the past especially if you were connecting while remote. You probably used port forwarding. That's also a security risk to leave a port open on the router. If you do setup UD Portal you have remote access using that Admin Console URL I mentioned. Just put that into the IoX Finder window while remote and use our UD Portal credentials to access the Admin Console while you're remote.

@tlightne I think @bpwwer mentioned in the past there was a migration for Polyglot only to go from PG3 to PG3x "back in the day" when people were moving from Polisy to eisy. I don't think there's a method to migrate Polisy PG3x to eisy PG3x currently. Since the node servers are assigned to the UUID it might require UDI Support to move the license(s) to the new device. Perhaps Bob or @bmercier can chime in with if there's a process. Otherwise open a support ticket: https://www.universal-devices.com/my-tickets As for moving from the IoX and ZMatter portions I think the migration steps in the wiki still apply: https://wiki.universal-devices.com/index.php?title=Eisy:User_Guide#Migration

@scrutch if you click the "more info" button on the node server page in the store it takes you to the Readme file for the node server. Sometimes that gives you additional setup/use information. https://github.com/UniversalDevicesInc-PG3/Virtual/blob/master/README.md Otherwise, others that use this node server would need to chime in to give assistance. Is there something specific you're trying to do? Maybe that would help others help you. I don't use this node server so cannot help beyond pointing to the "more info" button for assistance and further information/documentation.