Release Date: April 2026

This release hardens the internal message handling pathway to prevent hanging processes during receiver restarts, adds proper acknowledgement handling for OTA battery-low responses, and introduces new failure acknowledgement message types for improved error classification.

Message Reliability: The internal message pathway now handles receiver restarts gracefully. Previously, if the receiver restarted while a device was sending data, the protocol process could hang indefinitely. This is now resolved with a 5-second timeout and clean error recovery.

OTA Battery Low: When an OTA firmware update is attempted on a device with battery below 40%, the system now correctly identifies this as a battery-low rejection rather than a generic failure. This means clearer status messages in the dashboard and fewer misleading AFAIL indicators.

No Action Required: These are transparent protocol improvements. No configuration changes or device resets needed.

Release Date: April 2026

This release delivers internal message resilience improvements, new OTA failure acknowledgement types, standardised language settings with descriptive labels, and foundational accessory data extraction for peripheral battery monitoring.

Language Settings: Language options now display with clear descriptive labels (e.g. “en-US (English)”) and use a consistent format across all Eview protocols. If you configure language settings on ROAM devices, the options are now easier to understand and consistent with other device types.

Accessory Monitoring: ROAM devices paired with accessories (such as Flic buttons) will now forward accessory battery data to the platform. This is the foundation for the upcoming peripheral battery monitoring feature — no action required now, but accessory data will begin appearing in the system.

Error Handling: New acknowledgement types mean the dashboard will show more specific failure reasons during OTA and device operations, replacing generic failure indicators with meaningful status messages.

Release Date: April 2026

This release delivers the same reliability and error handling improvements as ROAM, adds standardised language settings with descriptive labels, and introduces accessory data extraction for peripheral monitoring.

Battery Low Alarms: When an OTA update is blocked due to low battery, the Sentry protocol now generates a properly classified Battery Power Low warning. This appears as a meaningful alarm in the dashboard rather than a generic failure, making it easier for monitoring teams to understand what happened.

Language Settings: Same standardisation as ROAM — descriptive labels and consistent locale format across all Eview devices.

Accessory Monitoring: Same as ROAM — accessory data from paired peripherals now flows into the platform, preparing for peripheral battery monitoring.

Release Date: April 2026

This release adds OTA failure acknowledgement types, a comprehensive language configuration overhaul with expanded locale support, and accessory data extraction.

Expanded Language Support: CareWatch now supports 9 languages: English, Spanish (ES), Spanish (US), Portuguese, French, Dutch, German, Italian, and Chinese. Each option displays with a clear descriptive label. This is particularly relevant for international deployments and the DV Spain programme.

Error Handling: Same OTA and failure acknowledgement improvements as other protocols — clearer error messages in the dashboard.

No Action Required: Language options will appear automatically in the protocol settings. No device resets or firmware updates needed.