O3 Firmware 2.5 Release Notes

Welcome

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

Note: Proviso 2.8 is required to work with an O3 Edge or Sense running firmware 2.5 or newer. 

New Features in 2.5

Delta BLE V3 Support

Firmware 2.5 adds support for the Delta BLE V3 protocol. Delta BLE is the Delta Controls’ implementation of the BLE GATT. Version 3 of the protocol includes new characteristics and services designed to improve the protocol’s data handling efficiency.

Note: Custom BLE GATT applications will need to be changed to use Delta BLE V3 services and characteristics to support O3 Edge and Sense devices running firmware 2.5 or newer. Please see the Delta BLE V3 GATT Services and Characteristics document for details.

Seymour Connect Support

Firmware 2.5 adds initial 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.

System Requirements

Proviso

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

Seymour Connect

N/A - Seymour Connect is not yet released.

enteliWEB

enteliWEB 4.23 or newer is required for O3 firmware 2.5. 

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.5 from firmware 1.6.16 or newer.

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. 

Cloud Engineering 4 Virtual Image Information

There are some notable differences between firmware running on Cloud Engineering 4 and firmware running on a controller. Please note the following for 2.5 firmware running in Cloud Engineering 4:

• Network Objects: NP4, NP5, NP6 are not present
• IO Faults: IO objects will appear in fault
• MQTT: The internal broker is not available
• Node Red: DLM files can be uploaded but Node Red execution is disabled

Resolved Issues

The following notable issues are fixed in version 2.5:

• • General

    • Time adjustment loop when DST ends (SHFW-2782)

    • IP static IP communication issue with non-standard subnet mask (SHFW-2789)

    • Loading database clears temperature calibration (SHFW-2783)

    • Set NTP to “Disabled” after factory reset (SHFW-2770)

  • Cloud Image

    • Virtual database corrupted when saved out to file (SHFW-2764)