v8.0.2

Release notes

Caution

With the v8.0.0 release onward, the settings structure migrated from a 1 byte model to a 2 byte model where the first setting is the
respected setting family and the second byte is the setting ID
This affects all aspects of settings usage when the device communicates (BT, Satellite, LoRa)
More about this can be found here:

• settings scripts README.md
• settings app README.md

Legacy IDs 0x38 and 0x60 were reused for unrelated settings in older firmware. Whenever either legacy entry is present, migration writes the compiled default for ublox_min_satellites_timer or external_switch_detection_gpio_pin_power_enabled, respectively, regardless of the stored value or length. This also replaces an existing destination value. Once the legacy entry has been deleted, later boots preserve any subsequent changes to the destination setting.

Note

If you're using the SmartParks Connect App (available here) it needs to be at least v2.13.0 to support the new settings model

Fixed

• Fix device_eui being overwritten with zeros after restoring a LoRaWAN session by reading the chip EUI and preserving the stored value on invalid reads.
• Fix settings migration failing on legacy settings with incompatible lengths by deleting those entries and continuing migration, preventing repeated failures on subsequent boots.
• Validate legacy numeric and boolean settings against current min/max limits during migration and replace out-of-range values with compiled defaults.
• Reset the GPS minimum-satellites timer and external-switch power setting to compiled defaults when migrating reused legacy IDs 0x38 and 0x60, even when stored values appear valid.

v8.0.1

Release notes

Caution

With the v8.0.0 release onward, the settings structure migrated from a 1 byte model to a 2 byte model where the first setting is the
respected setting family and the second byte is the setting ID
This affects all aspects of settings usage when the device communicates (BT, Satellite, LoRa)
More about this can be found here:

• settings scripts README.md
• settings app README.md

Note

If you're using the SmartParks Connect App (available here) it needs to be at least v2.13.0 to support the new settings model

Fixed

• Validate GPS time from a single fresh NAV-PVT epoch and confirm large corrections with consecutive readings.
• Allow the application clock to recover from future timestamps and serialize clock reference updates and reads.

v8.0.0

Release notes

Caution

With this release, the settings structure migrated from a 1 byte model to a 2 byte model where the first setting is the respected setting
family and the second byte is the setting ID
This affects all aspects of settings usage when the device communicates (BT, Satellite, LoRa)
More about this can be found here:

• settings scripts README.md
• settings app README.md

Note

If you're using the SmartParks Connect App (available here) it needs to be at least v2.13.0 to support the new settings model

Added

• Add Bluetooth scan filters for including or excluding devices by manufacturer ID.
• Add family byte to user settings, expanding the user settings structure.
• Add reboot-persistent LoRa join session support.
• Add deletion exception for LICENSE file to public release workflow.
• Add support for freeedge v1.7.0 hardware.

Fixed

• Fix GPS reset handling by cold-resetting the ublox module. GPS fix retries now mean actual retries (instead of retries-1).
• Fix provisioning rx tx tests reading inconsistent RSSI values due to lora chip de-initialization.

v7.3.0

Release notes

Added

• Add workflows for publishing releases to the public SmartParks repository.
• Add support for firmware type of elephantedge and wisentedge to rangeredge hardware version 1.8.0.
• Add user controllable configuration for the ublox minimum satellite check timeout. (The time after which we check if there are sufficient satellites detected to continue the ublox fix acquisition)

Fixed

• Fix codechecker and pre-commit (now prek) detected code errors and typos.