In one instance, I also saw it actually try to run the udx startup script, /usr/local/etc/rc.d/udx. I guess the attempt is so short that I just have to be lucky to catch the process on the fly. I'm not getting beeps, so it must always be failing the startup because udx is already running, though those beeps I heard means it must succeed every few days. I was thinking that maybe this is normal, to restart it in case udx failed for whatever reason. Just to be sure, I ran the same loop on the other two Polisys and on my eisy. Yes, they seem to be attempting regular restarts like that.

So it means that I might be getting periodic udx dying events. The udx log file doesn't show anything unusual for the time when I heard the beeps this morning. Has anyone else noticed this kind of thing on their Polisy?

It's not a problem or an operation issue for me, so I'm only asking casually, in the name of science! 😄

Thanks

ISY Error Log.v5.8.4__Mon 2026.09.07 07.03.12 PM.txt

I'm seeing lots of posts about 6.x.x versions, and that they're primarily meant for eisy products, but also that a Polisy update is "possible".

I'm wondering if it's worth it to update.

Honestly my system is running fine, but it would be nice to get rid of the Java interface. Aside from that, I'm wondering what other benefits 6.x.x would give me -- and, what other possible hiccups I could encounter with a newer version.

So, like the good user I am, I do them. Now my Polisy is offline, and I can't get the pg3 node server to start.

It seems to be functioning manually, no Alexa. no automation.

Current firmware version 6.0.5

Current PG3x Vsersion 3.4.18

And the portal says I'm offline

Any pointers on where/how to start troubleshooting this?

Thanks in advance for any assistance

Pete

Also, I've tried to force-reinstall the firmware, with the same result

No matter how many times I try, the Polisy Pro does not react to the "Multi Function Button" as described in the online user manual. I can hold the button in for minutes. Even just double-clicking the button to safely reboot the device does nothing (though I've had this work in the distant past). I also took the cover off to ensure I was truly pressing the button in . This did not work any better.

Is their any other way (via SSH, perhaps?) to clean my Polisy Pro of my credentials so it is "safe" to hand off to a stranger?

Thanks,

-Randy

I had logged into the isy through the portal and selected the update option. I think it said I was on 5.5.6 (or something close) and would update to 5.9.x. It told me it could take up to 30 minutes so I just let it go. Prior to the update, I could see the polisy on the IoX Launcher as well.

About 45 minutes later, I went back to the portal to confirm everything went well and it said the ISY was offline. I attempted connecting through the mobile phone app and tried to find it on the IoX Launcher, but nothing showed up, I attempted to ssh into the device, but it said there was no route. I have checked my DHCP logs and after restarting the device twice (by pulling the power cord since the multifunction button doesn't appear to be doing anything) don't see the IP request ever getting to DHCP.

Each time I power it on, it the device briefly shows 3 lights on the front, but quickly goes to just a single solid first light on the left. From everything I can find, that's a good sign, but nothing else seems to be able to get to it.

I'm still scouring the forum and wiki, but am quickly running out of ideas. I've also sent this to support, but trying to come up with ideas to get back online...

[admin@polisy ~]$ sudo chmod 622 /dev/speaker

Then let 'er rip: (highlight the line below, starting with "echo", do ctrl-C to copy it, then go to your ssh window and do ctrl-V)

[admin@polisy ~]$ echo "t165l8epepl4epl8epepl4epegcdl1e l4fffl8pfl4feepeddel2dg l8epepl4epl8epepl4epegcdl1e l4fffl8pfl4feeeggfdl2c." >/dev/speaker

Of course, for the best sound, you need to be using Monster network cables!

Sorry eisy owners, you're out of luck this time!

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.

UI ioX V.6.0.0. (2025-09-19)

File --> Restore ioX

Exit Malware Bytes

Turn off Windows Defender

YES to proceed

Select backup .zip file

Error Failed uploading configuration file [see Restore ioX error message .pdf file]

Attempted a backup file created today with same error message.

Rebooted Windows - same result

Any thoughts are welcomed.

Thanks

Stew

Restore iox error message 20251101.pdf Samuels Restore ioX problem20251101.pdf

Create Tiles From Nodes

Error: Request failed with status code 404

---

If I click on the Main Menu, then Nodes, a list of (I think) nodes shows briefly, then this:

1. Home

3. Nodes

I just seems bothersome for accessing your programs and such to require you portal login....

I don't know what to do next.  I can't launch the AC to start the upgrade on the backup Polisy.  When I ssh into it, it says it's still on FreeBSD 14.1, and the isy service isn't running.  So I guess that's why the Launcher can't find it, but how do I upgrade if I can't launch the AC?

-Tom