BlueRange Gateway / Firmware

Fixed issue in the BlueRange gateway when loading corrupt update packages from the BlueRange server

Fixed an issue where some nodes mistakenly had an AutoSense compliance violation.

Increased BLE TX radio power from +4dBm to +8dBm for Modbus Adapters with nRF52840. Also fixes a bug where only +4dBm was allowed in FruityHalNrf.

Fixed an issue where component_act messages may have generate an error response while also returning a valid read response.

An extended system diagnosis can be generated as an action on the gateway.

Added a new LED state indicator for DFU_IN_PROGRESS. It blinks yellow-green.

Allow SensorData, marked with publish flow, to be published without time restriction

Added capability request to the beacon monitoring service for assets. Fixed an issue where the beacon monitoring service could not connect long enough to assets if a connection was already being established by the "interested in connection flag".

AutoSense configuration is now properly applied to nodes that are inactive during configuration change but active afterwards. Periodic checks are now performed every 5min.

Fix LED blink code after Gateway (un)enrollment when restarting the Meshgateway service.

Changed advertising behavior of AssetModule to behave like Eurotronic devices: when unenrolled, not connected once, or not connected for the last hour, advertise with a lower interval than usual to allow easier connection of other Nodes..

Reduced stack usage by ~2kB of prod_mod_nrf52832 by disabling Segger RTT.

Fix LED blink code after Gateway (un)enrollment when restarting the Meshgateway service.

Added Eurotronic Comet to device catalog.

Fixed an issue where the watchdog would trigger between and after restarts caused by Gateway enrollment and unenrollment.

Rewrite of the asset connection service that handles how assets are connected. This allows for more assets to be connected in parallel and adds a retry mechanism that is used in RWIO actions and other modules. The beacon monitoring service now handles assets differently than nodes. It tries to connect to assets every few minutes and queries status, device info, etc. like in nodes, but once every tag has been connected to once, it slows down to an interval of 6 hours. The connection time for RWIO actions is reduced to 5 seconds to save battery.

The Euro module uses an advertising interval of 2s to save battery. Whenever new data is present, it sets the interestedInConnection flag to 1 so the Gateway will connect. Valve position is only updated if the same position has been polled twice to avoid sending positions during motor movement. Valve position and flags are polled twice as often (every 2.5min). InterestedInConnection flags are rate limited to 5min. When no data has changed, the flag is still set again after 30min.

Added Eurotronic Comet to device catalog.

Added new Eurotronic iot package.

Fix exception on Gateway withdrawal via BlueRange Admin or Setup App

Decreased asset advertising interval while standing still from 8s to 2s to allow easier enrollment for non-moving assets. To make up for the higher power consumption, the interval of which a mesh access connection is requested is increased from 2min to 4min.

Fixed potential buffer overflow in virtual com port that might lead to the node not being correctly connected to the Mesh anymore.

In case while enrolling a device the requested node ID is already taken within a network, the Gateway will chose a different one to ensure the uniqueness of node IDs in a network

Nearby WiFis will no longer show networks without name

Fixed an issue where debug time report would spam component_sense messages.

Removed chip-based battery measurements from Modbus boards.

Fixed an issue where the BACnet library could produce an OutOfMemory Exception in very busy BACnet networks with lots of IAmRequests.

Increased AutoSense message retry count from 1 to 3.

Rewrite of the asset connection service that handles how assets are connected. This allows for more assets to be connected in parallel and adds a retry mechanism that is used in RWIO actions and other modules. The beacon monitoring service now handles assets differently than nodes. It tries to connect to assets every few minutes and queries status, device info, etc. like in nodes, but once every tag has been connected to once, it slows down to an interval of 6 hours. The connection time for RWIO actions is reduced to 5 seconds to save battery. Firmware: the Euro module uses an advertising interval of 2s to save battery. Whenever new data is present, it sets the interestedInConnection flag to 1 so the Gateway will connect. Valve position is only updated if the same position has been polled twice to avoid sending positions during motor movement. Valve position and flags are polled twice as often (every 2.5min). InterestedInConnection flags are rate limited to 5min. When no data has changed, the flag is still set again after 30min.

BACnet sensors are now force polled automatically every two hours

Rewrite of the asset connection service that handles how assets are connected. This allows for more assets to be connected in parallel and adds a retry mechanism that is used in RWIO actions and other modules. The beacon monitoring service now handles assets differently than nodes. It tries to connect to assets every few minutes and queries status, device info, etc. like in nodes, but once every tag has been connected to once, it slows down to an interval of 6 hours. The connection time for RWIO actions is reduced to 5 seconds to save battery. Firmware: the Euro module uses an advertising interval of 2s to save battery. Whenever new data is present, it sets the interestedInConnection flag to 1 so the Gateway will connect. Valve position is only updated if the same position has been polled twice to avoid sending positions during motor movement. Valve position and flags are polled twice as often (every 2.5min). InterestedInConnection flags are rate limited to 5min. When no data has changed, the flag is still set again after 30min.

Fix duplicated actuator/sensor compliance violations on wrong devices

Added get_gw_status and set_gw_status terminal commands and module messages to improve transparency of the Gateway status to other mesh participants (e.g. no mesh connection, no serial connection).

Extended RawData protocol "raw_data_start" and "raw_data_start_received" with an optional "metadata" field with up to 40 bytes.

Added get_gw_status and set_gw_status terminal commands and module messages to improve transparency of the Gateway status to other mesh participants (e.g. no mesh connection, no serial connection).

Download syslog files via the WebUI

Changed the expiration times for republishing same sensor values. If a sensor reports the same value repeatedly, the Gateway will now republish the value every 10 minutes instead of every 4 hours. If the sensor data stays the same for 2 days, it will be marked as expired / invalid, instead of the previous 6 hours.

Fixed an issue that would not restart the BlueRange Connect USB initialization sequence if the USB disconnected during this sequence.

Added CPU temperatur, MQTT Broker status, BlueRange Connect staus and Internet status to device details

For Wi-Fi connected Gateways, the Wi-Fi name and Frequency is visible under device details.

Download syslog files via the WebUI

Replaced set/get Modbus module messages with component_act. This also uses a new, human readable format instead of enums.

Identify for Yara now lights up LEDs and light heads sequentially with the color order RGBW.

Added script to generate arbitrary amounts of node configurations for CherrySim.

When the USB blocks for some reason, the serial communication now properly retries to reestablish the connection.

Fix lookup of installed Mender client version on startup

Implement DIP switch settings for BlueRange Connect Modbus

Fix lookup of installed Mender client version on startup

Fixed an issue where a withdraw (or unenroll) action would not properly unenroll them from the Mesh. Now a "enroll remove" command is sent into the Mesh.

We now offer the option of copying all 3 elements at once when a gateway is enrolled via the Portal/WebUI

AutoSense configurations now throw compliance violations if entries could not be applied to nodes.

Fix MQTT connection in Gateway WebUI for WebSocket connections

AutoSense configurations now throw compliance violations if entries could not be applied to nodes.

Flags (e.g. child protection, heating mode, open window) are now polled in Euro module.

Optimize VS Gateway to increase the packet sending frequency over UART.

Fix lookup of installed Mender client version on startup

Watchdog triggers will be logged into syslog. They are also persisted across reboots and logged again after boot.

AutoSense configurations are now distributed into the BlueRange Mesh. This check is done when the configuration has changed and periodically every hour.

More robust DFU update in inconsistent states

OS Update via Gateway WebUI prepared for updates on kirkstone

AutoSense configurations are now distributed into the BlueRange Mesh. This check is done when the configuration has changed and periodically every hour.

Adds the ability to dynamically and persistently assign a BlueRange device to one or more dynamic groups.

Fixes an issue where the wrong RecordStorageEventHandler might have been called after data was saved.

Upgrade ApiClient to use proper fields of periodicResubscribeIvSec in BACnetEnvironmentProfile

Services now remove their persistent files when starting if the gateway is not enrolled.

Eurotronic fine tuning and external temperature sensor.

Updated Spring Boot from 2.4 to 2.7.

Added more internal docs for the OS to meta-bluerange. You can find them at Development → Gateway OS (internal).

Added gateway customizing key with ed25519 as OpenSSH 8.8 does not support rsa.

Removed duplicate debug health check logs.

Added mmc wear estimation to standard diagnose script. Will only work with eMMC with JEDEC standard 5.0 or later.

Devices will not be marked as unhealthy in enrollment phase. The Gateway’s MQTT status won’t be marked as unhealthy as initial value on startup.

Serial communication is now reinitialized if the serial port is disconnected in previously undetected scenarios.

The IP address is now properly read via BLE for unenrolled gateways.

Mender now tries to commit first with -commit and then with commit. This is necessary for Mender client v3 (new OS).

Add heartbeat to keep communication between Gateway software and bluetooth firmware active

Removed UseLargePagesInMetaspace start parameter since it is removed in Java 17.

Added helper to generate AutoSense configuration json files into table entries and vise versa.

Add indicator handling for battery info

Modifies the read behavior of the ModbusModule (also affects the BpModule) to be more consistent with the AutoSense functionality. All reads will need to specify the number of bytes instead of the number of registers from now on. The readResponse and writeResponse does not contain a prefixed byte with the number of registers anymore. For more information, see the errata in the documentation of the ModbusModule for this ticket number.

Added server and MQTT resolution, router pinging and improved lsof to diagnostic script.

The units LITER and LITER_PER_HOUR are now available in our platform.

Fix parsing of periodicResubscribeIvSec in BACnetEnvironmentProfile

Dedicated Gateway authorization added

Introduce SensorDataFlow attribute to SensorDefinition to configure how far a sensor value flows from its origin to the persistence

The gateway services KNX and BACNET can now be restarted via their package names or their service name

Add check for USB devices to diagnostics script (lsusb)

Compliance violations of failed configurations weren’t created anymore

Optimized stack usage of nRF52832 sink node.

Added capability entry for mesh firmware, softdevice and bootloader version.

Cached sensor values will be invalidated once the corresponding SensorDefinition is removed

Remove ComplianceViolations once its originating policy configuration is disabled or removed

The selected language in the WebUI is now displayed correctly even if it is not English or German.

Enabled CRC by default for nRF52840 sink node.

Added differentiation of individual YARA lamp heads by letting the generic LED blink with different frequencies and colors.

Added capability entry for current Modbus configuration.

Included Poll and Report module in sink nodes.

Gateway requests error logs in a sequential manner avoiding throughput peaks in the mesh

Time/date synchronization status added to Gateway diagnosis script

Ensure the CronJobTrigger to trigger SoftwareUpdates is created

Mesh nodes will not be marked as failed in case of a "component not updatable" response during the DFU initialization

Debug logs can be automatically uploaded to the server after a specified time (sec)

Add functionality to create multiple actuators for the same component and register

Prevent requests to the server if the Gateway is unenrolled

Beacon scanning configuration is now applied after a node has recovered from an inactive state

Version mismatch in gateway enrollment now leads to deletion of the device on the server

Mesh nodes will not be marked as failed in case of a "component not updatable" response during the DFU initialization

Added identify for Waldmann ceiling sensors. The LED with a diamond symbol will blink blue.

Fix undefined RS485 bus state for nRF52840 Modbus adapters by sending RS485 reset mark.

Add docs and test for Modbus error logging.

Add functionality to create multiple actuators for the same component and register

Gateway requests error logs in a sequential manner avoiding throughput peaks in the mesh

The logging view of the Gateway WebUI has been extended by additional information of the error message.

Avoid duplicate entries of gateway licenses

Upload to server of the system diagnostics log works now in multi tenant environments

Gateway requests error logs in a sequential manner avoiding throughput peaks in the mesh

Mesh nodes that are slow (e.g. due to connectivity issues) are removed from the firmware update after some time.

Fix illegal removal of unresponsive devices from the update in synchronuous mode

SystemDiagnostics output reduced on default with option to retrieve all. Added max run time to 10 mintutes.

Don’t log the last MQTT exception on health check execution

Automatically triggered (scheduled) firmware updates are shown in the list of gateway actions

The Gateway monitors mesh read and write separately for the internal watchdog

The Gateway is able to send connection information via Bluetooth to the BlueRange Admin App.

In the enrollment process (WebUI) the primary button is highlighted better.

If the update is configured as a "gradual" update, an update failure of a single device will not abort the update of all remaining devices anymore.

Fix wrong handling of firmware update cancellation

The sink node is resetted (at most three times), if it permanently fails to connect to the mesh

Diagnosis logs for asset connection establishment has been reduced to log level "trace"

The gateway WebUI now displays the connection type (wlan/lan) correctly.

The Gateway is able to send connection information via Bluetooth to the BlueRange Admin App.

Fixed issue, where gateway got stuck during DFU in case of unresponsive mesh nodes

Add a maximum timeout of two hours for DFU updates

Fix update via policy, that executed only the last update URL

The Gateway sends now details about near by devices, too.

The status of the public DNS check has no impact to the overall connectivity status anymore.

A DFU fails no longer, if a MeshNode went offline right before an software update started, but rather is ignored for that update

Add error reporting for Modbus module.

Added modbusModuleConfig for setting uart parameters by mesh message

A new connection check has been added to the gateway, making it easier to detect connection problems to the BlueRange server

The Gateway Web UI shows the MQTT status of the Gateway backend

Fix enrollment in a different Organization

Fix constant Modbus reinitialization by setting a delay between retries (configurable with a macro).

Add support for more Sensor units: ampere, hertz, ohm, second, watt, watt-hour

The gatway now logs an error when detecting a non-matching sensor definition. The error details contains the sensor definition details.

Broken KNX health status is cleaned up, once the KNX configuration is removed

Changed EnOcean LEAF node behavior, so a vossloh node can be enrolled into a new mesh, when it has an active mesh connection and an EnOcean switch configured

Provided basic documentation on Matter / Thread.

Modbus now supports nRF52840 with configurable stopbits (1 or 2). Added board 43 for Rodsum RS485 adapter.

Changed enrollment behavior to doing a factory reset when enrolling and not only when unenrolling.

Fixed a bug where the power off button would sometimes boot into safe mode, causing a WATCHDOG_REBOOT. This disables the Waldmann SIG mesh functionality (which is not used at the moment)

Action related messages originating from the StatusReporterModule can be sent through MeshAccessConnections

Added PIR moduleId and others to fruity-api

Adds logrotate for watchdog.
All logrotations now use 1 rotation file with half the size instead of none. This ensures that half of the log is still present when the rotation just happened.

The Gateway doesn’t remove NodeDetails anymore

Persistent time reporting: Nodes with the status reporter module can now be configured to report their local device time with a certain reporting interval. Settings are kept after node reset.

Changed enrollment behavior to doing a factory reset when enrolling and not only when unenrolling.
This disables the Waldmann SIG mesh functionality (which is not used at the moment)

Adds the option to activate periodic re-subscriptions for BACnet devices which helps if remote BACnet devices forget the registered subscriptions.

A compliance violation with status "pending" is created by the gateway before each beacon scanning configuration check.

An error where the compliance violation "IOT_BEACON_SCANNING_NODE_FEATURE" occurred incorrectly has been fixed.

Trigger the watchdog when either the server or the mesh connection is stuck

For BR support there are scripts extensions to run and download the Gateway’s Diagnostic log.
For orga admins there is a Gateway Diagnosis action in the BR Portal (Gateway Device Overview page)

Reduce misleading warning in log, that an update package couldn’t be loaded via proxy

Sleep in realtime loop instead of busy waiting

A compliance violation with status "pending" is created by the gateway before each beacon scanning configuration check.

The occupancy data service is removed from the gateway code.

The link in the device list in the Gateway WebUI now refers to the device page in the new BlueRange Portal.

All health components are published now periodically regardless if something changed or not

Fixed issue where CherrySim would return CLC capabilities for prod_sink_nrf52 featureset.

Adds the option to activate periodic re-subscriptions for BACnet devices which helps if remote BACnet devices forget the registered subscriptions.

Add optional setting on BACnet device or properties to poll a sensor value instead of a subscription

A compliance violation with status "pending" is created by the gateway before each beacon scanning configuration check.

An error where network connections between devices were not displayed has been fixed

Set default configuration for Occupancy management for all devices

Don’t create falsely evaluated ComplianceViolation of BeaconScanning

Occupancy management can be configured via the portal

License handling for BeaconScanning for gateways and mesh nodes added

Optimize throughput of beacon scanning and reporting in gateway

Gateway does not overwrite server device attributes if it has not properly received them e.g. after a reboot

Receiver could not edit the workflow states of facility management incidents reported to the BlueRange Maintenance app. This was due to a too restrictive permission check fixed in this release. Also, the messages may be archived now.

Add MQTT load test to gateway

Optimize MQTT message batching for "beacon scanning and reporting" to improve the throughput limits on the gateway side.

Create compliance violation in case BACnet sensors can’t be subscribed

Change topic structure for batched beacon report messages

Gateway does not overwrite server device attributes if it has not properly received them e.g. after a reboot

Create compliance violation in case BACnet sensors can’t be subscribed

The Record Storage now supports so called "Immortal Records" that persist on the Flash Storage even when a factory reset is triggered.

Beacon scanning configurations will not be persisted on the mesh node anymore

Live reports triggered by Gatt disconnect events send a part of the other nodes mac address instead of the node id because the mac address is available more often which helps with investigating issues in the mesh.

Removed unused debug functionality from productive featuresets.

Add MQTT message batching of beacon reports to gateway

The gateway waits now for end of updateData() before a pending Gateway restart is executed.

For Device with a MOTION sensor, the OCCUPANCY sensor is calculated and published

The Gateway creates a compliance violation if the time difference between the gateway time and server times is bigger than 5s.

Added new units PPB and DBA to device catalog and respective to server and gateway

Compliance violations on asset tags which was set by a gateway are now removed if the tag is not tracked anymore by this gateway.

Added new units PPB and DBA to device catalog and respective to server and gateway

System diagnostics prints the networkcacerts.pem file storing CA certificates now so that the content can be checked in case of communication issues.

Fix missing component name in MQTT health topic and timestamp in payload

Fixes an issue in dev_vslog where the UART communication was broken.

Integrated validation and application of beacon scanning policy configurations in the gateway.

For Device with a MOTION sensor, the OCCUPANCY sensor is calculated and published.

The firmware version information displayed in the server UI was not updated in all cases.

Most Asset tags and Mesh nodes can be unenrolled by pressing the button for 10-14 seconds. LED’s will start flashing for about 7 seconds to indicate this

Added prod_mesh_*_sdk17 featuresets which are now included in our SystemTest

Integrated validation and application of beacon scanning policy configurations in the gateway.

Fixes an issue where the firmware of some gateways reported an invalid license while the license should have been valid.

Fixes an issue where the chipId was incorrectly being reported with wrong data.

Gateway periodically calculates and reports mesh specific metrics

Rapidly restarted Asset Tracking Calibrations don’t block each other anymore
Long running Actions aren’t blocking the MQTT client anymore

Adds the Beacon Scanning configurations to the Gateway and the Mesh Nodes so that the user can configure beacon scanning according to his use-case.

Add beacon scanning and reporting to firmware

Publish beacon report messages via MQTT in gateway

Indicator events are triggerable based on a boolean formula that is based on the last value of a sensor

Solves an issue where the license state was not correctly displayed in the gateway UI.

[VS]: Implemented and enhanced the time synchronization to support time zones for prod_vs_nrf52

Adds the ability to query the current time of every node in the mesh network.

Migrates all necessary changes to SDK17 that had to be done based on previous migrations. Includes migration that was determined based on the migration guides and release notes for all intermediate SDK and SoftDevice versions.

Integrated GCC9 into fruitymesh-buildbox-mini which allows SDK17 targets to be compiled and added two targets for nrf52832 and nrf52840 to our automated build pipeline.

Add beacon scanning and reporting to firmware

It’s possible to enable/disable one or more detail gateway loggers in the System Logging configuration (BlueRange portal).

The rltn-iot/{organizationUuid}/{siteUuid}/{deviceUuid}/assets///infoRequest will now report all Asset Tags with an RSSI up to -85 instead of -75 as previously.

The gateway stores the compliance violations locally.

cleanup of idle asset connections in internal data structures so that outgoing connections are freed up for reuse. This fixes the mesh running out of connections in environments where there are more assets than connecting mesh nodes.

In case, there is no floorplan length set, the Gateway falls back to a default of one meter

The System Monitoring configuration will be applied as it is selected.

Fix issue of older Gateways not being able to be enrolled to newer Servers, due to alleged denied access.

Tags that disappeared during a gateway reboot will be transitioned to the state "lost", after the gateway has recovered.

The System Monitoring compliance violations are removed if the dependent configuration is removed.

When the specified Graphite hostname contains any blanks at beginning or at end these are removed before the config is applied.

Resolved compliance violations are syned properly from the Gateway to the server.

The mesh nodes are now listed as compliant if they are compliant.

The software update process now starts without waiting for all devices to be reachable.

Existing compliance violations will be shown in the device configuration view

Avoid adding UUIDs of deleted assets to MQTT geofence events

New Compliance Violations have been added

Compliance violations now also occur in case of errors in the device configuration.

Adding rooms and zones now causes the device tracking service to be reinitialized.

Asset tags will stay active as long as tracked-asset advertisements are received. If an asset tag cannot be connected to for some time a compliance violation will be created and shown in the portal.

Fix considering asset tag on all gateways of a building after its enrollment

Floorplan image file names containing unusual characters can no longer cause gateway software malfunction.

Add detection of contradictive signals received from mesh nodes placed at wrong position, to make the asset tracking system more robust

Increments version to 1.1.x which enables the LicenseModule so that all nodes can now report their license state. This does not affect any existing nodes and does not impose any restrictions.

Adds documentation for the sink routing.

SDK17 integration (alpha): Refactored the CMake build so that we can now build against SDK14/15/17. All builds do not support GCC 9.3.1 as well. The user is now able to specify SDK/Chipset and BLE Stack (SoftDevice) as part of the featureset.

Fixes an issue where under rare circumstances mesh access connections used for enrollment were never disconnected. Also fixes an issue where DFU packets received out of order could abort an ongoing update, which was triggered due to an extraneous mesh access connection caused by the other issue.

Improve the movement detection of asset tags for asset tracking by increasing the sample rate of the accelerometer.

Adds the SoftDevice S132 and S140 headers to the simulator for better DFU Simulation. Includes FruityLoader simulation in CherrySim. Adds License migration during DFU Updates.

Improve position stability after reboot and standstill position changes

The rltn-iot/{organizationUuid}/{siteUuid}/{deviceUuid}/assets///infoRequest will now report all Asset Tags with an RSSI up to -85 instead of -75 as previously.

Corrected an error reported in the logs when the gateway attempts reporting battery levels of recently unenrolled nodes. The issue arised only if receiving a status message while the node is in the process of being unenrolled.

Increments version to 1.1.x which enables the LicenseModule so that all nodes can now report their license state. This does not affect any existing nodes and does not impose any restrictions.

Adds the SoftDevice S132 and S140 headers to the simulator for better DFU Simulation. Includes FruityLoader simulation in CherrySim. Adds License migration during DFU Updates.

Improve position stability after reboot and standstill position changes

BRS-199: Implements PT_CMD sending for vs_converter and PT_RSP reception for vs_converter.

The rltn-iot/{organizationUuid}/{siteUuid}/{deviceUuid}/assets///infoRequest will now report all Asset Tags with an RSSI up to -85 instead of -75 as previously.

cleanup of idle asset connections in internal data structures so that outgoing connections are freed up for reuse. This fixes the mesh running out of connections in environments where there are more assets than connecting mesh nodes.

Add an option to serial connect which enables better connection parameters if the BLE address is specified.

The MQTT health indicator no longer fails by reporting a NullPointerException in case the MQTT client is not up and running yet. Notice, the indicated health status was fine previously, but the additional detail information was not accurately reported.

Add an option to serial connect which enables better connection parameters if the BLE address is specified.

Adds some final preparation before the LicenseModule can be used with the upcoming version 1.1.0. Updates the public key in the firmware to its final version.

Improve asset tracking scalability and stability at standstill by improving the processing of incoming signal measurements.

Enhanced reporting of compliance violations to BlueRange server. This supports error reporting in future versions of the software.

Fixes an issue where the Gateway could have missed a reboot of its Mesh Bridge under certain conditions.

Less fluctuations after standstill position changes, since position suppression is reenabled after every position chnage now

Adds an indicator for the Mesh Bridge to the gateway Web-UI and a health indicator which tracks the health of the mesh bridge and is shown in the BlueRange Portal.

The gateway Graphite metrics are structured now hierarchical.

Gateway waits until asset position has stabilized after reboot, if real-time tracking mode is enabled

Fixed an issue where switching log levels caused an error in the Gateway WebUI.

Fix missing component name in MQTT health topic and timestamp in payload

Enable stack overflow detector in hard fault handler. Also disable logging for prod_vs_nrf52 featurset

Cleaned up LicenseModule and fixed some bugs. Can be used beginning with version 1.1.0.

Fixed a small bug where the wrong error code was returned for prod_sink_usb_nrf52840 if set_serial was used.

Fixed an issue where the reported ABSOLUTE_UPTIME for a BlueRange node was not properly reported through the error_log.

Upgrade Log4j library to 2.15.0 due to security issue CVE-2021-44228

Fixes an issue where the gateway would connect to a Tag running on critically low battery for a very long time. After this fix, the gateway will now continue updating the status of other tags first before re-trying the failing tag. This could have caused all Tags to be reported as INACTIVE while they were still being tracked.

Reverse SSH Tunnel actions are properly set to error, if the feature has been disabled by the user

Fix the reverse SSH option toggle in the Gateway WebUI

Use the configured scanning window and interval for reception probability computation in advertisement delivery and introduce a parameter to skip blocks of nodes when considering advertisement delivery.

Unified and documented the LED blink codes for powering on/off our tracking and sensor tags. Take a look at https://www.bluerange.io/docs-internal/bluerange-manual/AssetTracking/AssetTrackingTags.html for more information.

Optimize the power requirements of assets during movement.

Add some documentation on how to use pre compiled binaries in github source relase distribution

An integrated watchdog now automatically restarts malfunctioning gateway devices. The feature is opt-in and can be controlled using a policy configuration. Before enabling it please read the instructions carefully and make sure to have the latest BlueRange OS, Gateway and Server software installed as these components tightly work together in monitoring the devices.

Option to opt-out of M-Way Support Access using reversed SSH tunnel. Notice, deactivating this feature severely restricts the options for online support staff! It is recommended to leave the setting active.

Allow to connect to a server via SSH on another port than 22.

Corrects an issue where the gateway permanently fails connecting tracked tags for (sensor) data retrievals until it gets restartet. The issue happened in rare cases when certain firmware messages that are part of the connection establishment handshake and teardown procedures get lost in transmission.

Optimise power when asset is connected using serial_connect using slave latency

Fix the multiple Gateway restart after applying configuration, that requires a restart

The gateway now checks server version compatibility more strictly. Also, the server version is checked at enrollment time ensuring the device is capable talking to the infrastructure.

Increase the NodeId range for Tags to 25000 starting at 33000

Minor bug fixes and improvements in the Gateway WebUI

If an MQTT connection does not exists or is lost the health data is sent to the BlueRange server with REST call.

subscription is done even if unsubscription shows errors

Include a pre-load library to set the KEEPALIVE flag on outgoing socket connections

The gateway version information was not present in the user-agent header when talking to the server. The user-agent header is fixed now.

Adds the ability to configure regularly distributed ceilings in the simulator. These attenuate the (simulated) signal strength between receivers and transmitters.

Increase the NodeId range for Tags to 25000 starting at 33000

Adds WIP support for nRF52840 asset tags and the acnBuzz tag. Buzzer and Vibration motor are supported through the identify action but gateway support to execute this action is not yet ready. Featureset was not added to release artifacts for now and must be flashed from a master branch.

Asset only refreshes advertisement job when the packet is modified

Add possibility to track assets that do not advertise in movement by supporting the motion state "standstill-init".

The gateway has a new web UI for several versions by now. So far the former legacy UI was deployed at a separate location, still. With this version, the legacy UI was removed entirely as it is no longer needed.

Boardid for acn52832 is added and should work now with fruitymesh

Adds a position counter field to the proprietary AssetModule and the AssetScanningModule. This field counts changes in the movement state of a asset tag and allows a positioning system to notice missing state-changes (e.g. due to lost advertisements).

Support for acconoFind beacon with accelerometer

Add documentation on the proprietary AssetScanningModule. Also adds the movement modifier field to the (experimental) tracked INS-asset JSON message.

Fixes a bug that generate double autoPoll messages

The fix will allow to query sensor value from Barometer when the sensor is initialized

The nearby_nodes message now only contains nodes from networks with the same network id, not any nearby node.

Refactors the AssetScanningModule to fix an issue about wrong RSSI averaging and some other bugs.

The OpenAPI specification of the BlueRange server now defines security schemes properly. Also the tag grouping is enhanced so that the user experience of the Web API page is greatly improved.

Improve the scalability of asset tracking in case of a huge number of mesh nodes

Improve startup time of tracking system for non-moving assets

BlueRange Gateway can now query standstill packet from the mesh in order to increase stability when BlueRange Gateway restarts

Boardid for acn52832 is added and should work now with fruitymesh

Improve startup time of tracking system for non-moving assets

GitHub PR 180: Add an example module which allows sending and receiving terminal commands and output on a smartphone.
GitHub PR 183: Fix undefined behaviour in the hardware abstraction layer.

Accelerometer now will detect motion in 6D

Fix build on MSVC / Visual Studio due to the pi-constant not being defined in the cmath standard header.

Suppression of position estimate publication after gateway reboot

Fix wrong tracking state transition after gateway reboot

Increase configurable default value of max-inflight for the MQTT library to increase message throughput send by the Gateway

The Gateway will check for new MeshNodes to ask for their device capabilities, even if a Node isn’t responding to the request anymore.

The asset tracking advertisement now contains a organization identifier under certain conditions. It is used to filter the received advertisements on the scanning side.

Add a command line flag to set tester verbosity to true by default.

The simulator now utilizes Gaussian RSSI noise. Functions concerning RSSI computations are refactored into their own compilation unit.

Fix undefined behaviour in the hardware abstraction layer.

CherrySim with gateway uses terminalId instead of hardcoded value to select sink node

The current voltage of battery supplied assets and node devices are provided as sensor data and are made persistent.

Improve the scalability of asset tracking in case of a huge number of mesh nodes

Most recent values are now shown in the asset details view of the Gateway WebUI.

Makes the Serial Number of the Node available for 3rd Party Applications which allows the user to easily identify the nodes.

Adds the ability to CherrySim to specify the working directory (Normalized Path) using an environment variable (CHERRYSIM_WORKDIR)

During the handshake for MeshAccessConnection, the Center which is the node that initiates the connection now waits for MessageType::ENCRYPT_CUSTOM_DONE before changing to handshake state to to set HANDSHAKE_DONE

Fixes an issue where our "BlueRange Connect" USB Dongle would not properly report the completion of its firmware update which makes it necessary to reboot the gateway manually.

The MQTT broker connection now is checked for malfunction. In case connection establishments hangs for more than 5min. in the MQTT library, the client gets reset so that the software heals itself. This fixes some rare connectivity issues.

The LED on/off action can now be executed from the server portal for assets just as is available for stationary nodes. This functionality is useful for diagnostics and testing purposes. Care must be taken to turn off the LED for battery powered devices!

When updating, the changes are written synchronously to the SD card explicitly. This protects against potentially high memory pressure caused by load of the write-back cache of the kernel and improves robustness against memory card issues.

The parameter fwrev is now allowed to have an arbitrary revision value.

The Gateway initializes itself with the data loaded from the server with mostly one request, instead of making multiple requests to retrieve the different needed entities.

Use the Gateway UI to update itself even if it is unenrolled

Adds guided instructions on how to implement sensors, actuators and capabilities in the firmware. Also adds steps on how to test and configure everything

Adds support for a new PCB (YJ-17120-USB) to be used for BlueRange Connect.

Refactors CMD and CMD_RSP so that CMD is now deprecated and WRITE/_ACK should be used instead and CMD_RSP was renamed to RESULT_RSP.

Document all the json file used in cherrysim

Vossloh: Only skip the firmware compatibility check on certain devices before a certain firmware version. This fixes a bug which caused the LiNA Connect app to hang.

The BlueRange Gateway WebUI has been redesigned from scratch. In addition to various design adjustments, there are also new options for managing and monitoring the BlueRange Gateway and Mesh network.

The connection to a configured KNX-IP-Gateway is now part of the BlueRange Gateways health status

The LED on/off action can now be executed from the server portal for assets just as is available for stationary nodes. This functionality is useful for diagnostics and testing purposes. Care must be taken to turn off the LED for battery powered devices!

Add discovered state to the asset tracking system

The error that the status of the Communication Beacon was not updated was fixed.

Ensure node id for BlueRange Tags to be always in the bounds of the valid node id range

AssetTag PowerOff functionality was implemented. AssetTag will be switched off if not enrolled for considerable amount of time

Board Id and BoardName will be part of capabilities now

Gateway will now accept component_sense messages with VendorModuleIds from the firmware.

Enhance SimulateBroadcast method to scale better

Optimized the connection to Asset Tags (serial_connect) by passing the BLE address of Asset Tags if known, therefore reducing the connecting time and making it more stable in case of low advertising or low scanning intervals.

Improve network transition latency for multi-network asset tracking

[Gampper] Implements additional registers for our prod_bp_nrf52840 featureset. These are necessary for the FM package.

Gateway will now accept component_sense messages with VendorModuleIds from the firmware.

Fixes a small bug in the state indicator supplier service which caused the state to be detected erroneously.

Reset the communication state of the serial connection when the serial port is closed (e.g. when the mesh bridge is unplugged).

Optimized the connection to Asset Tags (serial_connect) by passing the BLE address of Asset Tags if known, therefore reducing the connecting time and making it more stable in case of low advertising or low scanning intervals.

Refactors some code used in the unit tests and the socket terminal implementation to use the (unique) node index instead of the potentially ambiguous node id. This allows simulating multiple networks simultaneously. Fixes a bug in the simulator resulting in irrelevant logs due to a mock being always instantiated regardless of being used. Fixes a bug in the simulators socket terminal which resulted in an unusable replay log. Ensures that z-coordinates are actually used by the simulator.

[Gampper] Implements additional registers for our prod_bp_nrf52840 featureset. These are necessary for the FM package.

Adds the ability to CherrySim to specify the working directory (Normalized Path) using an environment variable (CHERRYSIM_WORKDIR)

Gateway will now accept component_sense messages with VendorModuleIds from the firmware.

Fixes an issue in the virtual com port implementation which provides a serial port via the USB CDC ACM implementation provided by the Nordic SDK. The ability to write to the port from a computer was sporadically lost.

Backwards compatibility of build-in module identifiers use for building automation so that existing policies take effect as is.

Fix the issue of constant static power consumption when lis2dh12 is connected to TWI interface. Anomaly89 from nordic was adapted

Backwards compatibility of build-in module identifiers use for building automation so that existing policies take effect as is.

Reduce memory consumption of the asset tracking system

Activated Asset Tracking can be configured to run in 'standstill positioning' or 'real-time tracking (experimental)'

The BlueRange OS can now be updated directly from within the settings menu of the new gateway web interface. The download URL is prefilled automatically. The OS is updatable without requiring access to an update server and may be trigger even when unenrolled as a preparatory step prior installation.

Allow use of long vendor-specific module identifiers in configurations of sensors and actuators as described in firmware specification.

The gateway software can now be attached to a running simulator. When doing so, the simulated mesh bridge node can be selected by setting meshgw.processInit to e.g. sim term 1.

Reduce memory consumption of the asset tracking system

The LED on/off action can now be executed from the server portal for assets just as is available for stationary nodes. This functionality is useful for diagnostics and testing purposes. Care must be taken to turn off the LED for battery powered devices!

Add adaptive timeout to region estimation

Improved multi-floor coordination of asset tracking so that decision of tag responsibility selects a single gateway.

Allow use of long vendor-specific module identifiers in configurations of sensors and actuators as described in firmware specification.

[Gampper] Implements additional registers for our prod_bp_nrf52840 featureset. These are necessary for the FM package.

The gateway software can now be attached to a running simulator. When doing so, the simulated mesh bridge node can be selected by setting meshgw.processInit to e.g. sim term 1.

[CherrySim]: Implements an accelerometer mock that will report movement while an animation is executed in the simulator. Once the movement stops, the accelerometer will stop reporting movement.

Improves the USB read stability for BlueRange Connect (prod_sink_usb_nrf52840).

Activated Asset Tracking can be configured to run in 'standstill positioning' or 'real-time tracking (experimental)'

Enable postprocessing steps in region estimator master

Fixes the problem of missing overview of Wifi networks. The accessible Wifi networks of the BlueRange Gateway are now displayed in the BlueRange Portal.

The bug that the total number of log messages was not displayed correctly after applying a log level filter was fixed.

Adds temporary enrollments and meshBridgeMode for our USB mesh bridge. This greatly enhances security and usability as the enrollment will be lost as soon as the mesh bridge dongle is removed from the gateway. As soon as it is inserted again it will be automatically enrolled and ready. Also, advertisements are only enabled as soon as the serial number of the gateway is known after bootup.

Adds SocketTerm to CherrySim which allows multiple clients to connect to different terminals using TCP sockets e.g. by using Telnet or a gateway process. Also fixes a number of scalability issues so that the simulator will now support up to 1500 nodes. Improves the simulation performance so that (depending on your CPU) around 400+ nodes can be simulated in real time.

Fixes use of uninitialized memory under exceptional conditions. The firmware now triggers a reset under these circumstances.

The deprecated sensors 'power' and 'taskTuningPower' are removed – instead 'POWER' and 'TASK_TUNING_POWER' should be used

The Gateway Web UI showed outdated tracked asset positions in connections view. The software was changed such that the positions shown reflect a snapshot of the local state of tracking at the time the screen loaded now.

Custom Gateway tmp directory isn’t removed anymore in the background while the software is running

Fix issue making black pixels transparent, when loading and converting the wallmap image in the gateway.

ErrorLogEntries will now be logged with either the relative time since node start in seconds or in the absolute UTC time if the time was synchronized.

Support for several IoT things in device catalog incl. latest luminaire and valve definitions and the tag barometric sensor.

Update of timeouts in persistent configuration when existing defaults change in newer versions of the Mender OS updater.

Blockages caused by firewalls when resolving external IPs have been fixed

A high frequency of incoming numeric sensor values will now be throttled to one second or a deviation of more than 1% of the average

Support for several IoT things in device catalog incl. latest luminaire and valve definitions and the tag barometric sensor.

The error log is now sent over time instead of in one block. This reduces the number of dropped packets.

Due to a race condition upon startup or in the event of server connectivity loss action processing may have failed because of the target device data not yet being loaded from the BlueRange server. This is fixed by waiting up to 5 minutes for the server data load before accepting actions for processing.

Fixes deserialization of SensorDefinition-DataType HALF fetched via API client

Asset tracking might not be enabled in case of the mesh gateway software starting while the BlueRange server is not available so that required information fails to load. The information is stored locally on the device now so that the state is restored properly even in case of network or server outage.

This release supports updating the mesh gateway software of iot-gate-imx8 devices. Also it dropped support for discontinued Raspbian and Ubuntu OS devices that were used as PoC prototypes several years ago.

Add support for hybrid BLE/INS tracked asset messages

The installation now checks versions across server, gateway software and OS, mesh bridge and nodes ensuring compatibility prior to applying updates.

Device details have been extended with memory card information

Indicate the state of the meshgateway using (e.g.) a LED built into the meshgateway hardware.

BlueRange supports now half precision floating point actuators/sensors – e.g. in KNX terms, it is the 16-bit float.

Reduce memory consumption of wallmap in wayfinding interpolator

Upload of pure white wallmaps doesn’t disable the asset tracking

The new metric counter.dmesg.overcurrent allows monitoring USB overcurrent conditions. The value is exposed e.g. by the Prometheus endpoint at /actuator/prometheus.

Provided it is enrolled, the mesh gateway waits up to a minute for NTP time synchronization before starting up the controlling software. This is for robustness and correct reporting of the gateway uptime.

When enrolling wait for up to a minute for the network configuration to be applied so that there is enough time for joining the WLAN, for example.

Fixed the issue, that the software update process skipped a component, if the previous one failed

Add standstill detection for INS assets

Make it possible to not compile enum-to-string conversions into the firmware using a separate macro. The default does not change existing behaviour.

Add prod_sink_usb_nrf52840 featureset to our fruitymesh build package

Proactively fix potential buffer overflow while copying the event buffer.

Fixes a bug where messages over mesh access connections were not correctly relayed between nodes.

Disconnect a mesh access connection during the handshake if a invalid node key is used, instead of progressing with the handshake and leading to a unusable connection which times out.

Fix CI script checking the firmware size compared to the last master build.