O3 Firmware 2.6 Release Notes

Welcome

Delta Controls is pleased to release O3 firmware 2.6 for the O3 Sense and O3 Edge products. These release notes communicate important technical information about release 2.6.4.

New Features in 2.6

Sound Level Rollup

For firmware 2.6 we have added a new sound level object to the default database. AV41 presents a 10 second averaged audio signal value. Averaging the sound level over the last 10 seconds provides for a more realistic representation of the sustained sound levels in a space, making AV41 an ideal choice for use in graphics. Learn more about the Sound Level Rollup feature.

Seymour Connect Support

Firmware 2.6 adds support for the upcoming Seymour Connect occupant app to the O3 Edge and Sense. Seymour Connect will allow occupants to control and monitor environmental variables in their space. Learn more about Seymour Connect.

System Requirements

Proviso

Proviso (formerly the O3 Setup App) version 2.9 or newer is required to use all the features of O3 firmware 2.6. 

Seymour Connect

Seymour Connect 0.6 or newer is required for O3 firmware 2.6.

enteliWEB

enteliWEB 4.25 or newer is required for O3 firmware 2.6. 

Installing an O3

To install the O3, follow the Installation Instructions. You can also watch the O3 Installation Tutorial. 

Once installed, devices should be secured, following the O3 Edge Hardening Guide. 

Upgrading an O3

You can upgrade to firmware 2.6 from firmware 1.6.16 or newer.

In firmware 2.6 and newer, FIL200 has been adopted as a default object used to store the Seymour Connect configuration. On upgrade, if FIL200 does not exist, it will be created. If FIL200 already exists on upgrade, the operator will need to delete it post-upgrade and reset the O3. FL200 will be re-created on reset.

If you have a build older than 1.6.16 in the device, you must follow a specific upgrade path. Refer to the O3 1.6 Release Notes for upgrade instructions. 

Do not unplug or reboot an O3 during a firmware upgrade. Once an upgrade begins, allow at least 5 minutes for it to complete without interruption. 

To perform the upgrade, follow the Firmware Upgrade Guide.

MQTT Write Priority Level

Firmware 2.2 changed the priority array level used for writes to BACnet objects through MQTT. Previously, MQTT writes would occur at priority 16 (the lowest priority). In firmware 2.2 and beyond, MQTT writes occur at priority 13.

This allows MQTT to have a higher write level than controller algorithms at priority 15, such as EnOcean, allowing MQTT to be used to configure these objects and override them. Existing applications, such as those created in Node-RED, may need to be updated.

Downgrading an O3

If you need to revert to a previous release (e.g. downgrade from release 2.1 to 2.0), you should first enable BACnet/Ethernet. In some cases, the O3 may encounter issues being assigned an IP address after the downgrade. Having BACnet/Ethernet enabled will ensure you can continue to communicate with the O3 should this issue occur. 

Starting in version 2.2, downgrading an O3 will clear its database. 

Resolved Issues

The following notable issues are fixed in version 2.6:

• General

  • Some O3 property fields in Proviso may periodically return an error.

  • Single Port O3-Edge does not accept a static IP.

  • BNserver crashes after creating a MI object and assigned with a MIC.

• Seymour Connect

  • Seymour name and beacon signal not updated after O3-Edge is re-provisioned to another Seymour device.

  • Implement recovery if the device is reset during Seymour Connect provisioning.