I tried updating packages but get nothing past 6.0.3 ?

Based on the release notes, no, this would not apply to the Polisy. I believe I read others saying they tried to update their Polisy and nothing changed for them.

https://forum.universal-devices.com/topic/46914-os-144-release-is-now-available/

It does work, but the update must be done manually, by accessing the Polisy by ssh. Then you do:

sudo pkg upgrade udx isy eisyui pg3x

This method was suggested by Michel at UDI. I've successfully upgraded two Polisys this way.

Remember the release announcement warning:

If your FreeBSD OS is below 13.2p11 (check via https://eisy.local:8443/WEB/sysconfig.txt), do not attempt this upgrade; it will brick your system.

Edited August 20Aug 20 by Guy Lavoie

@Guy Lavoie thanks for clarifying and info.

Do you know if this will be enabled/allowed from the Jave console in the future. I'm not that familiar with ssh control of Policy. I get this error when trying that upgrade command. No repositories are enabled. (My OS is 14.3)

Edited August 20Aug 20 by EJones01

Have a look here, on the 4th page of the thread. there is a command to do first:

That was it. Updated fine. Thank you!

This contradicts this statement. Do not use SSH to perform the upgrade; this will brick your system.

Just now, brians said:

This contradicts this statement. Do not use SSH to perform the upgrade; this will brick your system.

That's for the Polisy only.

3 minutes ago, Guy Lavoie said:

for the Polisy only.

4 minutes ago, Guy Lavoie said:

That's for the Polisy only.

Ok so I have a polisy do I use ssh to upgrade or not. The instructions are kinda ambiguous I think I see now that is a warning for older kernels

Edited August 22Aug 22 by brians

Yes, heed the warning about the freebsd version. This upgrade method was suggested by Michel at UDI. I've personally upgraded all three of my Polisys successfully this way. Page 4 on the following thread has discussion, including instructions on enabling the repositories if needed.

19 hours ago, Guy Lavoie said:

Yes, heed the warning about the freebsd version. This upgrade method was suggested by Michel at UDI. I've personally upgraded all three of my Polisys successfully this way. Page 4 on the following thread has discussion, including instructions on enabling the repositories if needed.

I ran the command, been a while but I get this when connecting to the web...

Should I just be patient now?

Uploading Attachment...

That might be normal, I saw something similar during the command line update, probably because the Polisy cannot be fully upgraded to freebsd 14.4. I'd reboot it and then check out that everything is ok.

ok so that system busy went away.. I removed java cache and reinstalled and IoX seems to be on lastest version..

Gonna restart now hoping for the best ;)

Ok well that was nerve-wracking.. reboot didn't work from gui, so I did from ssh but was running a continous ping and didnt see drop so presumed crashed.. after a while I hard rebooted Polisy by removing power and it eventually all came back up.

I did not have to use the command to set the repo when I upgraded unlike others.

I got the impression that we will have to ssh upgrade polisy each time and possibly require to run command to set repo in future ?

31 minutes ago, brians said:

I got the impression that we will have to ssh upgrade polisy each time and possibly require to run command to set repo in future ?

Very likely. I updated 3 Polisys this way and didn't need to set the repository on any of them. Not sure why it happens for some cases.

On 8/19/2026 at 6:43 PM, Guy Lavoie said:

If your FreeBSD OS is below 13.2p11 (check via https://eisy.local:8443/WEB/sysconfig.txt), do not attempt this upgrade; it will brick your system.

Hiya Guy,

I tried that url a couple of times, but it does not work for me. (Server Not Found.) https://eisy.local:8443/WEB/sysconfig.txt

Do you know of another way to check the FreeBSD version?

EDIT: I think I just woke up - that link is for Eisy's only? (eisy.local)

Edited yesterday at 09:32 PM1 day by Athlon
Update my post

8 minutes ago, Athlon said:

Hiya Guy,

I tried that url a couple of times, but it does not work for me. (Server Not Found.) https://eisy.local:8443/WEB/sysconfig.txt

Do you know of another way to check the FreeBSD version?

Yes, hardcode the ip address of your controller instead. For example:

https://192.168.0.123:8443/WEB/sysconfig.txt

1 minute ago, Guy Lavoie said:

Yes, hardcode the ip address of your controller instead. For example:

https://192.168.0.123:8443/WEB/sysconfig.txt

I just ran https://polisy.local:8443/WEB/

and got this - looks like I'm good to go?

FreeBSD polisy 14.3-RELEASE-p3 FreeBSD 14.3-RELEASE-p3 releng/14.3-n271444-30ad842dd970 POLISY amd64

6 minutes ago, Athlon said:

I just ran https://polisy.local:8443/WEB/

and got this - looks like I'm good to go?

FreeBSD polisy 14.3-RELEASE-p3 FreeBSD 14.3-RELEASE-p3 releng/14.3-n271444-30ad842dd970 POLISY amd64

Yes. So go ahead and do the update, from the comnand line as explained earlier.

1 minute ago, Guy Lavoie said:

Yes. So go ahead and do the update, from the comnand line as explained earlier.

Thank you!

I'm trying to find my user name and password - been using my portal login for so long I may have forgotten it....

2 minutes ago, Athlon said:

Thank you!

I'm trying to find my user name and password - been using my portal login for so long I may have forgotten it....

You only really need the admin password.

2 minutes ago, Guy Lavoie said:

You only really need the admin password.

That did it - thank you again!

2 hours ago, Athlon said:

That did it - thank you again!

were you meaning admin for ssh? Mine is admin and password is admin so not the same as the IoX password.. not sure if that is normal or not... I don't remember ever changing it.. sure not the most secure LOL

9 hours ago, brians said:

were you meaning admin for ssh? Mine is admin and password is admin so not the same as the IoX password.. not sure if that is normal or not... I don't remember ever changing it.. sure not the most secure LOL

Yes, for ssh.