Please see the release info here: 

 

This thread will be used to support/help with this version of ISY on Polisy. 
 

I updated to 5.4.0 and now the left Polisy led is rapidly flashing. I tried soft and hard reboot to no avail. I'm able to access the Polisy via the admin console and it appears to be working as it should. Any thoughts?

 

 

Updated no issues so far with ISY itself.

One thing I noticed is that UD Mobile on iPhone does not seem to update/show current status of devices, and is not consistent controlling devices. I will post more on appropriate forums regarding this after I test more.

Update - seems to work fine on my iPad when I checked last night  but not iPhone. I’ll check later what difference is eg. if I am going through portal or not on iPad. 

Edited March 1, 20223 yr by brians

Updated, no issues with the update. Testing to follow.

@Techman, My experience was slightly different

After the upgrade, I noticed that the center LED was flashing rapidly. After a Polisy power cycle, now the left LED is blinking rapidly. Also, after the power cycle and a trial reboot polisy, the musical tunes are now gone. Policy is silent.....BUT EVERYTHING seems to work normally.

I updated using ssh and rebooted Polisy after the update completed. Some PG3 node servers were not reporting properly after this reboot, but started working again after a PG3 restart. No issues with UD Mobile after the update.


Sent from my iPhone using Tapatalk

Updated using IoP Help menu link. IoP did update and is running okay. Polisy still showing ISY as version 5.3.0. 

I upgraded to 5.4 using SSH and have the rapidly blinking left LED. 

Gary

17 minutes ago, garybixler said:

I upgraded to 5.4 using SSH and have the rapidly blinking left LED. 

Gary

Polisy is in the garage near distribution panel for PLM concerns, so I didn't notice. But, yes, I have the blinking LED as well. I upgraded via the IoP Help menu link.

2 hours ago, mbking said:

I updated using ssh and rebooted Polisy after the update completed. Some PG3 node servers were not reporting properly after this reboot, but started working again after a PG3 restart. No issues with UD Mobile after the update.


Sent from my iPhone using Tapatalk

I have another topic for this last weekend.  Pg2 and Pg3 have this issue.  Some fields will come in and update.  Others will be blank.   Most commands like for valves and stuff wont work.   You can update there

 

Can someone please test this.   Run a program that exposes a variable to alexa as a motion sensor and have alexa run a routing and say something.

It was working just before 5.4 update.  Not working now.

I even created a new one.

Variable setup in ISY and expose to alexa as motion sensor and 1 is activation

Discover devices

In alexa routing put if motion sensor is activated then say something or do something

run program in ISY to set variable to 1

I watch the variable change to one but nothing happens in Alexa.

**Controlling alexa devices does work   Its just the variables

 

 

I updated to 5.4.0 using SSH and didn't reboot.  I don't see any leds except the ones on the Ethernet connector.  Still testing.

I too discovered that variables aren't triggering Alexa responses.

Just now, garybixler said:

I too discovered that variables aren't triggering Alexa responses.

THANK YOU   You saved me hours of testing.  Thinking it was on my end.   I have put a ticket in with UDI.   I will mention you in the ticket in case they need other logs.

Now there is a chance Amazon has the issue and it happened at the same time but if that was the case my controls would not work and they do.

My Polisy, front panel, left most LED is flashing like others have reported after the update.  But, operationally, everything seems to be working OK.  

Re, blinking light is because:
- UEFI image. Currently, Polisy uses BIOS which does not support TPM boot. If the 3rd light is blinking, it means that you still have BIOS and not UEFI. You can click the button on the front 6 times consecutively and UEFI will be installed. This said, at this juncture, this is NOT mandatory

Re, variables not triggering Alexa:

If the variables are updated in the Admin Console AND in the Alexa App, I cannot see how this would have anything to do with the upgrade. It's Alexa throttling things.

With kind regards,
Michel

@macjeff

With further testing I see the switch on Alexa turn on and off with the variable change. So the problem must be in the return response from Alexa.

Hi Guys,

UEFI vs. BIOS.

In short, you can ignore it for now. But, you'll eventually have to flash with UEFI. This way, we can make sure that TPM boot is working (i.e. will only boot UD signed OS).

With kind regards,
Michel

I've never found motion or door sensors a reliable way to trigger Alexa Routines. For this reason, I've relied on skills such as Voice Monkey or Virtual Buttons which use "doorbell" events to get Alexa to react.

5 minutes ago, randyth said:

I've never found motion or door sensors a reliable way to trigger Alexa Routines. For this reason, I've relied on skills such as Voice Monkey or Virtual Buttons which use "doorbell" events to get Alexa to react.

I use variables.  If garage door is closed set variable to 1.  When alexa sees variable one it announces the garage door was closed.  Seems to be issue on Alexa side but strange it started almost the exact time of upgrade.

15 minutes ago, garybixler said:

@macjeff

With further testing I see the switch on Alexa turn on and off with the variable change. So the problem must be in the return response from Alexa.

I am calling Amazon.  You should probably call too.  I confirmed it is seeing motion on its side but not responding to it.

@macjeff,

As I mentioned, Alexa has throttle procedures. After the upgrade, ISY publishes 1000s of events. Alexa sees them and decides that this is too much and thus throttles everything. So, by the time the variables are reported, Alexa ignores them. If you wait 15-30 minutes, they start working again.

With kind regards,
Michel

3 minutes ago, macjeff said:

I use variables.  If garage door is closed set variable to 1.  When alexa sees variable one it announces the garage door was closed.  Seems to be issue on Alexa side but strange it started almost the exact time of upgrade.

Those variables were set up as either Motion Sensors or Contact Sensors in the Portal. In any case, I'm sure Michel is correct that you just need to wait a while for the logjam to clear.

I did in Putty :

 

sudo pkg update
sudo pkg upgrade
sudo service pg3 restart

No error message but  Polisy still shows :

Version 3.0.41
Status: Connected
Frontend Version: 3.0.41
ISY Version: 5.3.0
Uptime: 13 Minute(s) 1 Second(s)
(c) 2022 UDI
Running on Polisy
Documentation

I haven't updated yet but don't you have to do "sudo service isy restart "?