When I go to run the upgrade, I get the following message, which seems good . . .

Within a few seconds of that, my Polisy reboots, and comes up running again within a minute or so, running the same old version.

I did check the sysConfig.txt ahead of time, which produced the following output, showing that I am running at least the minimum version necessary for the upgrade, but the last line is interesting in that it says, "UDX_UPGRADE_STATUS="inactive". What does that mean?

*** OS ***
FreeBSD polisy 13.2-RELEASE-p11 FreeBSD 13.2-RELEASE-p11 releng/13.2-n254665-f5ac4e174fdd POLISY amd64
*** Package Information ***
************ UDX ************
************ IoX ************
************ libwebsockets ************
************ tpm2-tools ************
************ eisyui ************
************ iox_matter_bridge ************
************ mosquitto ************
************ pg3x ************
*** Networking Information ***
igb0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=4e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
	ether 00:0d:b9:55:24:74
	inet6 fe80::20d:b9ff:fe55:2474%igb0 prefixlen 64 scopeid 0x1
	inet 192.168.1.14 netmask 0xffffff00 broadcast 192.168.1.255
	media: Ethernet autoselect (1000baseT <full-duplex>)
	status: active
	nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
igb1: flags=8822<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=4e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
	ether 00:0d:b9:55:24:75
	media: Ethernet autoselect
	status: no carrier
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
igb2: flags=8822<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
	options=4e527bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP>
	ether 00:0d:b9:55:24:76
	media: Ethernet autoselect
	status: no carrier
	nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> metric 0 mtu 16384
	options=680003<RXCSUM,TXCSUM,LINKSTATE,RXCSUM_IPV6,TXCSUM_IPV6>
	inet6 ::1 prefixlen 128
	inet6 fe80::1%lo0 prefixlen 64 scopeid 0x4
	inet 127.0.0.1 netmask 0xff000000
	groups: lo
	nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
pflog0: flags=0<> metric 0 mtu 33160
	groups: pflog
pfsync0: flags=0<> metric 0 mtu 1500
	syncpeer: 0.0.0.0 maxupd: 128 defer: off
	syncok: 1
	groups: pfsync
*** USB Devices ***
ugen0.1: <AMD XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
ugen1.1: <AMD EHCI root HUB> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (0mA)
ugen1.2: <vendor 0x0438 product 0x7900> at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=SAVE (100mA)
*** Upgrade Status ****
UDX_UPGRADE_STATUS="inactive"

For what it's worth, my ISY Portal license is active. Is there anything else that would cause the upgrade status to be "inactive"?

I downloaded the pg3 and System messages. When the polisy reboots, I do see these lines which seem like they might be relevant to the failed (or no-op) upgrade:

2025-10-04 14:45:18.490 [pg3] error: stderr: ld-elf.so.1: Shared object "libssl.so.30" not found, required by "pkg"

2025-10-04 14:45:18.515 [pg3] info: *****************************************
2025-10-04 14:45:18.516 [pg3] info: Latest PG3x version available is undefined
2025-10-04 14:45:18.517 [pg3] info: *****************************************

In the system messasges.txt, I see a few errors immediately after the reboot, including one "REPORT THIS!" line:

Oct  4 16:35:03 polisy daemon[4088]: 2025-10-04 14:35:03.454 [pg3] ^[[32minfo^[[39m: Auto Reinstalling completed
Oct  4 16:35:03 polisy daemon[4088]: 2025-10-04 14:35:03.458 [pg3] ^[[33mwarn^[[39m: Logging to console is disabled. Log file is in /var/polyglot/pg3/logs/pg3-current.log
Oct  4 16:43:49 polisy daemon[4088]: 2025-10-04 14:43:49.973 [pg3] ^[[31merror^[[39m: unhandledRejection REPORT THIS!: [object Promise], reason: Error: ENOENT: no such file or directory, access '/var/polyglot/pg3/logs/pg3-current.log'
Oct  4 16:43:49 polisy daemon[4088]: 2025-10-04 14:43:49.977 [pg3] ^[[32minfo^[[39m: Failed to unwatch stream, this should be OK.
Oct  4 16:43:49 polisy daemon[4088]: 2025-10-04 14:43:49.980 [pg3] ^[[31merror^[[39m: unhandledRejection REPORT THIS!: [object Promise], reason: Error: ENOENT: no such file or directory, access '/var/polyglot/pg3/logs/pg3-current.log'
Oct  4 16:43:58 polisy shutdown[11505]: reboot by root: 
Oct  4 16:43:58 polisy daemon[4088]: 2025-10-04 14:43:58.200 [pg3] ^[[32minfo^[[39m: Caught SIGTERM/SIGINT Shutting down.
Oct  4 16:43:58 polisy daemon[4088]: 2025-10-04 14:43:58.207 [pg3] ^[[32minfo^[[39m: Pushing notification {"title":"PG3 is stopping","body":"From PG3 (00:0d:b9:55:24:74)"} to UD Mobile
Oct  4 16:43:58 polisy daemon[4088]: 2025-10-04 14:43:58.559 [pg3] ^[[32minfo^[[39m: Stopping running NodeServers...
Oct  4 16:43:58 polisy daemon[4088]: 2025-10-04 14:43:58.574 [pg3] ^[[31merror^[[39m: stopNs: SqliteError: attempt to write a readonly database
Oct  4 16:43:58 polisy daemon[4088]:     at Object.update (/var/polyglot/node_modules/@universaldevices/pg3x/lib/models/nodeserver.js:322:6)
Oct  4 16:43:58 polisy daemon[4088]:     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
Oct  4 16:43:58 polisy daemon[4088]:     at async stopNs (/var/polyglot/node_modules/@universaldevices/pg3x/lib/services/nodeservers.js:823:7)
Oct  4 16:43:58 polisy daemon[4088]:     at async Promise.allSettled (index 0)

Everything seems to run fine after this, but the upgrade simply never happens, and never appears to really get started. All this happens in about a minute (or two), rather than the 30 minutes warned by the dialog when starting the process.

 

Are you upgrading from the IoX Launcher?

Try removing power from the polisy for about 30 seconds then try "upgrade packages" again

Your config.sys file is missing a lot of information, not sure why.

I'm not entirely sure what you mean by "launcher", though that sounds like the IoX "Finder" as I know it. I'm not directly doing it from that, but I use the launcher/finder to open the admin console, then go to the config tab, then click "Upgrade Packages". This screenshot shows that sequence, from top to bottom.

I did just remove the power entirely and don't see anything substantially different. I'll include the sysconfig.txt in the screenshot as well (after reboot). Sounds like a support ticket and just waiting for help may be my only alternative at this point since you say I'm missing a lot of information.

One last thing you can try. Clear your java cache, be sure to check all 3  boxes, then download the IoX Launcher from here:  https://isy.universal-devices.com/start.jnlp  (this will install the IoX Launcher icon on your desktop)

then try running update packages again. If you don't get positive results then it's best to open a support ticket.

I just cleared the cache, downloaded the latest start.jnlp from the link you provided, tried again, and still got the same result. Despite the confirmation dialog saying the upgrade will happen, it seems my polisy simply doesn't see it (or get the message to see it) and so it simply reboots to the same version. I put in a support ticket, but THANK YOU @Techman for taking your time to help!

You could also attempt to upgrade from the multifunction button.