I upgraded an OPII to the 3.2 firmware about a week ago and started experiencing several strange issues. There are several UPB lights ("standard" UPB, not HLC) that use the BRIGHT X FOR Y MINUTES command. For example, exterior lights normally come on at 50%, but will ramp to 100% for five minutes with motion, and then return to their previous level. The BRIGHTEN FOR countdown is visible in the PC Access status when these routines are triggered. After the upgrade, these routines trigger an ON FOR, and the light turns off after the countdown period. This behavior is consistent and repeatable.
A similar anomaly occurs with some of the interior night time scenes as well. There is code that will turn on a bathroom light with motion at night if the light was already off. The Omni used to see any dim level other than 0% as ON so the event only triggered once, however that isn't the case with 3.2 so the command keeps re-firing with motion, creating a light that brightens 10% with every movement.
I had skipped a couple of generations during the firmware upgrade, so I went back and retested every version in between (3.0a, 3.1, and 3.1a) and can verify that it was a change from 3.1a to 3.2 that introduced the bugs. The unit is currently running 3.1a and works as it should, however the issues with 3.2 definitely need to be addressed.
A similar anomaly occurs with some of the interior night time scenes as well. There is code that will turn on a bathroom light with motion at night if the light was already off. The Omni used to see any dim level other than 0% as ON so the event only triggered once, however that isn't the case with 3.2 so the command keeps re-firing with motion, creating a light that brightens 10% with every movement.
I had skipped a couple of generations during the firmware upgrade, so I went back and retested every version in between (3.0a, 3.1, and 3.1a) and can verify that it was a change from 3.1a to 3.2 that introduced the bugs. The unit is currently running 3.1a and works as it should, however the issues with 3.2 definitely need to be addressed.
