Change Logs

Support for Component Replacements

• Added backwards compatible support for new flash memory chip
• Updated bootloader to support new flash chip

Bug Fixes

• Updated the wording around copying a calibration as part of user calibration
• Resolved a bug where the channels from an archived sensor were not retired correctly
• Resolved a bug where reports that hadn’t been started were showing in the results
• Resolved a bug with form submission when performing bulk updates
• Resolved a bug preventing locations from being dragged and dropped on the Manage > Locations page
• Resolved a bug where archived legacy loggers couldn’t be re-registered
• Resolved a bug where the email and chat links from the Support menu weren’t working
• Resolved a bug where the system was expiring passwords despite SSO being forced

REST API

Note: these changes do not affect the front-end application. If you validate the REST API as part of your processes, then there is a Low impact.

• Update warning and excursion naming conventions in the REST API to support differentiation between severity for alerts
• Updated the device route to include location information
• Added device count to locations relationship
• Added channel count to device’s relationships
• Rest API User routes now include locale info2

Bug Fixes

• Resolved a bug where recipients couldn’t be added to reports
• Resolved a bug where the graph wasn’t properly displaying values equal to 0
• Resolved a bug where the sensors page was displaying replaced loggers name instead of new logger
• Resolved a bug where the list of devices shown on the Locations view weren’t saving their order
• Resolved a bug where a swapped sensor was still shown as current sensor and updating last reported at time
• Resolved a bug where the background of some reports was red
• Resolved a bug where claimed RFLs wouldn’t appear as registered until after the page was refreshed
• Resolved a bug where flags for annotations and alarms on the graph were not displaying their contents when hovered over
• Resolved an issue where some reports were failing to generate
• Resolved an issue where data was loading on the graph but the the graph indicated it was still loading
• Resolved an issue where users who utilize SSO were only seeing raw HTML and not seeing styled pages
• Corrected the styling of the filter on Manage > Sensors
• Made graph generation more resilient when connecting to the database

Security Enhancements

• Increase version of UI component
• Increase version of backend monitoring component
• Increase version of component that aids in displaying information that had been previously sanitized

Bug Fixes

• Resolved a bug where RFG settings tabs were empty.
• Resolved a bug where the alarms tab on a device turns blank and freezes (note: this existed prior to the v1.5.0 release).

User Experience

• Improved performance on the Manage > Sensors page.
• Redefined the scope of the Calibration widget on the dashboard to only include sensors that are actively in use.

Bug Fixes

• Resolve a bug where RF LoRa Gateways (RFGs) do not respect the firmware update settings.
• Resolve a bug where Alarms on the Alerts page display the wrong time when first loaded.
• Resolve a bug where RFLs would not appear on the Unassigned Loggers screen if they had communicated through any gateway not owned/registered by the user or organization.

Accessibility

• Improved the visual components of the application to make them more accessible.
• Improved structure for screen readers.
• Improved keyboard navigation.

User Experience

• The Manage > Sensors page was added enabling users to see and filter all their current and historical sensors. 
• Refactored how sensor swaps are handled
• Updated the Calibration widget on the Overview Dashboard for clearer understanding of the information and improved readability/accessibility.
• Updated iconography throughout the application for consistency and recognizability setting the foundation for future features as well.
• Improve the date/time selection for the reporting suite to allow the reported timeframe for one-off reports to be customized down to the second!
• Update differential pressure audible alarms to support more than tenths as the related variables extend beyond tenths. 
• Improved handling of deleted roles related to templates and notification policies so that they would resolve cleanly.
• Code to support future User Calibration functionality has been released.  

Application Upgrades and Security

• Updated back-end server frameworks for improved stability, security, and features

New Sensors

• Released support for CO2 sensor
• Released support for universal 4-20mA sensor

Calibration Certificate Repository

NOTE: At this time please rely on hard copy certificates sent with your sensors for your calibration records as the source of truth while we continue to update this functionality.

• Released a new page, Calibration > Certificates, where users can view/download their calibration certificates.

Bug Fixes

• A bug that caused billing problems for monthly credit card subscriptions when a replacement credit card had been re-issued by a bank has been resolved.

Software Version Updates

• We have implemented non-functional version upgrades for our supporting software packages to address minor bugs and ensure ongoing compatibility

Bug Fixes

• A bug that caused manual data uploaded to not be properly processed on the device’s graph page was fixed.
• A bug regarding RFL data loggers only that caused incorrect sensor serial mappings on the sensors page of a device was fixed.
• A bug regarding PDF reports including additional characters in the report date range was fixed.
• A bug that caused the timestamp to not respect the timestamp account format in PDF reports for excursion events was fixed.
• A bug that caused pressure units to not be programmed on the devices when updates are made was fixed.
• A bug that caused the notifications, custom alarms, and alarm template pages to become inaccessible when user roles are deleted was fixed.
• A bug that causes email addressed to not properly be removed from the DicksonOne emailing lists was fixed.
• A bug that prevented OTA updates for RFG gateways when the account default option was selected has been resolved.

• Updated the LoRa server to point at TTN V3 infrastructure
• Update SDK to latest RAK version
• Resolved a bug where static IPs for the WiFi and Ethernet controllers couldn’t be edited in the admin UI
• Resolved a bug where gateways were unable to connect to hidden SSIDs

Bugs

• A bug that caused inconsistent sampling of data points was fixed.
• A bug regarding audible alarms not triggering when a sensor pod is swapped was fixed.
• A bug regarding log files not containing the correct times or serial numbers was fixed.
• A bug regarding readings above 999.9 not being displayed on the logger’s screen was fixed.
• A bug regarding settings not being changed properly when device settings are changed was fixed.
• A bug regarding the exported LOJ files not containing channel thread IDs was fixed.
• A bug regarding incorrect Epoch/date timestamps in log files was fixed.
• A bug regarding server errors being caused when data loggers are re-registered to DicksonOne was fixed.
• A bug that caused intermittent issues regarding data exports not containing data was fixed.

Enhancements

• A factory reset functionality was introduced.
• Logged events on the data logger now utilize the RTC timestamp.
• Data loggers now support exporting data using exFAT formatted USB drives.
• Data logger screen display error messages were updated to provide better context.

Networking

This firmware includes a required update to migrate RFL data logger traffic from The Things Network version 2 to version 3.

Bug Fixes

• A bug regarding the chat and email support modals within the interface was fixed.
• A bug regarding alarm information not being rendered on the interface when translating to French or Spanish was fixed.
• A bug regarding a lag in time for the timestamp displayed in the alert logs was fixed.
• A bug regarding graphs in reports not rendering properly when reviewing a report in DicksonOne was fixed.
• A bug regarding calibration reports having the wrong factory calibration date for very fringe cases was fixed.
• A bug regarding the Twilio integration throwing an error page when having to re-verify the connection was fixed.
• A bug regarding audible alarms only sending an alarm value to the tenth place for differential pressure sensors was fixed.
• A bug regarding SSO URL redirects on the DicksonOne sign-in page was fixed.

New Sensors

Backend work was completed to support the development of new sensors such as CO2 and 4-20 milliamp.

Follett Integration

An integration for Follett equipment was released.

This is not applicable to DicksonOne devices and only applies to customers that use third-party equipment from Follett.

Helmer Integration

An integration for Helmer equipment was released.

This is not applicable to DicksonOne devices and only applies to customers that use third-party equipment from Helmer.

Performance and Security

Authentication is now required to view reports in DicksonOne when accessing a report from emailed reports.

User Experience

• A new alerts report was released that allows users to run reports for alerts.
• A new daily temperature report was released focused on vaccine monitoring where daily AM and PM temperature logs will be reported as well as the daily min and max.
• The Manage Devices table was updated to include a column for Last Reading to indicate a timestamp for the most recent data point that was reported by a device.
• Helper text was added to alarm schedules when building custom alarms and alarm templates.
• Updates to the REST API were made to support a new mobile app development project as well as make improvements to the REST API. The REST API is optional to use and it is not applicable to the general use of DicksonOne and validated customers.