Jump to content

Support thread for: ISY on Polisy (IoP) v5.4.1 (March 8, 2022)


Recommended Posts

Posted (edited)

Is there an updated admin console available for 5.4.1?  After this update, I cannot get into the admin console - it says I need an updated version (my admin console is apparently 5.4.0)

UPDATE: nevermind - I cleared the java cache and re-clicked the admin console link on the Wiki and now I can get in - sorry for the false alarm

 

image.png

Edited by JTsao
update
Posted (edited)
42 minutes ago, Michel Kohanim said:

All, this is the support thread for 5.4.1:

With kind regards,
Michel

Successful upgrade with using Help-Upgrade option for the first time. After restarting Polyglot in PG3, it now also shows the correct version (5.4.1) of IoP.

I did not have the AC issue mentioned by @JTsao

Edited by asbril
Posted
1 hour ago, brians said:

I upgraded which success, but my PG3 web interface still shows 5.3.0 while PG2 shows 5.4.1

 

 

Based on my experience, you may want to restart Polyglot in PG3.

  • Like 1
Posted

@Michel Kohanim is there a way to confirm the flip to UEFI was successful?

I did not watch for lights and listen for beeps during the upgrade process.

But I'm on 5.4.1 and everything is working properly with left most light solid.

Thanks.

Posted (edited)
1 hour ago, asbril said:

Based on my experience, you may want to restart Polyglot in PG3.

I did and does not display correct version. I restarted entire Polisy also.

 

Edited by brians
  • Confused 1
Posted
3 minutes ago, lilyoyo1 said:

Everything with the update went smoothly. Launcher shows 5.4.1 and no lights are blinking (though I had already upgraded via SSH to stop that).

I think you can check the configuration page. There is a switch for it to turn on when time comes.

Posted (edited)
17 minutes ago, DennisC said:

I think you can check the configuration page. There is a switch for it to turn on when time comes.

???. Possibly for the wrong person. I'm not having issues with my upgrade

Edited by lilyoyo1
Posted

@mmb,

Currently, the only way to verify UEFI:

sudo vi /var/udx/logs/log ... scroll down to a few lines before the bottom and you should see somthing like:

Tue Mar  8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Tue Mar  8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Tue Mar  8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3
Tue Mar  8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version
 

With kind regards,
Michel

  • Thanks 1
Posted (edited)
35 minutes ago, Michel Kohanim said:

@mmb,

Currently, the only way to verify UEFI:

sudo vi /var/udx/logs/log ... scroll down to a few lines before the bottom and you should see somthing like:

Tue Mar  8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices
Tue Mar  8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy
Tue Mar  8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3
Tue Mar  8 15:28:22 PST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version
 

With kind regards,
Michel

@Michel KohanimLooks like I'm good...

Tue Mar  8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios mfr: Universal Devices  
Tue Mar  8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios product: Polisy  
Tue Mar  8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios ver: 1.1.3  
Tue Mar  8 16:50:14 MST 2022|/usr/local/etc/udx.d/static/udx_startup.sh: bios has the correct version  

It would be helpful to insert this bios info in the Help About (someday?)

Thanks!

 

Edited by mmb
Posted

I upgraded via the SSH sudo..... method.

Total crash. Currently I have no access to IoP. I can access polisy admin console page but it always just shows it cannot access ISY and creds should be updated from polisy. After attempting that a few times, it rejects connections completely.

Polisy has been power cycled a few times, polyglot has been rebooted about 7-8 times. ISY finder finds ISY at :8080 only but will not display falldown connection options.

I am stuck. After power cycling, polisy left green LED comes on immediately and then after about 60 seconds, polisy makes some grinding noises and then the two rightmost LEDs begin fast blinking. Single poke of reset doesn't change anything.

@Michel KohanimHelp!

Posted

I upgraded via SSH without apparent problem (both PG2 and PG3 dashboards show up)  but I  wasn't running IoP or any nodeservers on Polisy before or after so perhaps  not a very meaningful test...  

Posted
10 hours ago, JTsao said:

FYI you can also type "sudo cat /var/udx/logs/log | grep bios" to filter the logfile for the section of interest

Thanks!

"Version 100 is old and needs to be updated"

Posted

Just ran an update as I do whenever a new PG3 is released.  The follow packages were included:

Installed packages to be UPGRADED:
	isy: 5.4.0_5 -> 5.4.1_1 [udi]
	npm: 8.4.0 -> 8.5.2 [udi]
	pciids: 20220128 -> 20220225 [udi]
	pg3: 3.0.44 -> 3.0.45 [udi]
	py38-distro: 1.6.0 -> 1.7.0 [udi]
	py38-typing-extensions: 4.0.1 -> 4.1.1 [udi]
	udx: 2.6.0_2 -> 2.6.0_7 [udi]

After the install Polisy went into a reboot loop.  It would startup, I could login...few minutes and it would just reboot and give the lovely beep during boot.... annoying BEEP.

Powered off from console.

So far the only resolution I've seen is open a ticket and a remote session? 

Posted
2 minutes ago, simplextech said:

Just ran an update as I do whenever a new PG3 is released.  The follow packages were included:

Installed packages to be UPGRADED:
	isy: 5.4.0_5 -> 5.4.1_1 [udi]
	npm: 8.4.0 -> 8.5.2 [udi]
	pciids: 20220128 -> 20220225 [udi]
	pg3: 3.0.44 -> 3.0.45 [udi]
	py38-distro: 1.6.0 -> 1.7.0 [udi]
	py38-typing-extensions: 4.0.1 -> 4.1.1 [udi]
	udx: 2.6.0_2 -> 2.6.0_7 [udi]

After the install Polisy went into a reboot loop.  It would startup, I could login...few minutes and it would just reboot and give the lovely beep during boot.... annoying BEEP.

Powered off from console.

So far the only resolution I've seen is open a ticket and a remote session? 

Thanks!

Sounds exactly what I was seeing. Michel remote sessioned in, and found a bricked BIOS chip (old version 100). However I have a spare polisy and have flipped over to it (Michel did). Works fairly well but am currently trying to get PG3 working, and have given up with it refusing to add or find any ISY, and refusing to accept and new settings due to "no backend connection. Settings unchanged". I tried Edge browser and things seemed a little different, so I disabled firewall things for Firefox (GD MS!). Didn;t make any difference, so far.

I am currently deleting PG3 and attempting to return to PG2, where it worked well for a few years now. I wonder if IoP v5.4.1 will allow that at all.

Posted

I am only offering a datapoint.  

Looking at my (smooth) ssh update/upgrade I find that my packages match the targets in @simplextech's log with the exception that my machine does not have pciids installed.   So maybe that is the source of the problem people are experiencing?  Again I am only offering data. 

Guest
This topic is now closed to further replies.

×
×
  • Create New...