Rio Protocol (v4.1 → v4.6)
Release Date: March 2026
Overview
This release delivers improvements to data accuracy, a new device conversion workflow, timestamp corrections across all Eview models, and a safety guard preventing accidental conversions on unsupported device types.
Requirements
Requirement | Details |
Platform Version | IntelliCare v3.8.x or higher with protocol import enabled |
Custom ID Conversion | Requires devices to be online and connected via long connection |
Firmware Validation | Conversion blocked if device firmware is below minimum supported version |
What’s New
Change | Area |
Step counter data corrected — previously missing or displaying errors on Rio and Watch dashboards | Data Accuracy |
New Custom ID-based device conversion workflow with firmware validation | Device Conversion |
Conversion automatically blocked on Care Watch (EV05) devices with user-facing message | Safety |
Timestamp accuracy corrected across all Eview models — resolves time discrepancies on production | Timestamp |
Legacy conversion controls removed from protocol | Cleanup |
What This Means for You
• Step Counter Data: Step count data that was previously missing or showing errors should now display correctly for Rio and Watch devices. Historical gaps predate the fix — new data will be accurate.
• Device Conversion: A new conversion workflow is available via Custom ID. Conversion is not supported on Care Watch (EV05) devices — the system now blocks this automatically with a clear on-screen message.
• Conversion Failures: If conversion fails, check: (1) device firmware meets minimum version, (2) device is online with active long connection, (3) device is not a Care Watch. The system provides specific error messages for each scenario.
• Timestamp Accuracy: EV06 devices were receiving incorrect time responses in certain conditions. This is now resolved. Historical time discrepancies predate the fix.
ROAM Protocol (v1.8)
Release Date: February 2026
Overview
This release resolves a critical issue where system settings were not applying on certain hardware revisions, and removes obsolete controls from the protocol.
Requirements
Requirement | Details |
Platform Version | IntelliCare v3.8.x or higher |
Hardware | Applies to ROAM P2 and Sentry P1 units |
What’s New
Change | Area |
System settings now apply correctly on ROAM P2 and Sentry P1 devices | Critical Fix |
Factory Defaults option removed — no longer part of the supported workflow | Cleanup |
Legacy Rio → ROAM conversion option removed from production | Cleanup |
What This Means for You
• Settings Not Applying: If you have experienced settings not taking effect on ROAM P2 or Sentry P1 devices, this fix resolves the root cause. Previously affected devices may need settings re-sent after the update.
• Factory Defaults: The Factory Defaults option is no longer available. This is an intentional removal and is no longer part of the supported workflow.
• Conversion Options: The Rio → ROAM conversion option has been removed. Any references to this in existing documentation should be disregarded.
Sentry Protocol (v2.0 → v2.2)
Release Date: March 2026
Overview
This release resolves the same critical settings issue as ROAM v1.8, introduces Silent Call Mode for discreet welfare checks, stabilises device feature toggling, and removes deprecated Factory Defaults.
Requirements
Requirement | Details |
Platform Version | IntelliCare v3.8.x or higher |
Hardware | Applies to Sentry P1 and ROAM P2 units |
Silent Mode | No firmware update required — configured via system settings |
What’s New
Change | Area |
System settings now apply correctly on Sentry P1 and ROAM P2 devices | Critical Fix |
Silent Call Mode — monitoring centres can call the device without audible indicators for discreet welfare checks | New Feature |
Device feature toggling stabilised — previously unreliable in some configurations | Stabilisation |
Factory Defaults removed from protocol | Cleanup |
What This Means for You
• Settings Not Applying: Same fix as ROAM v1.8. Sentry P1 devices where settings were not taking effect are now resolved. Settings may need to be re-sent to previously affected devices.
• Silent Call Mode (New): Monitoring centres can now establish a call to the device without audible indicators, supporting discreet welfare check scenarios. Configured via system settings in the protocol — no firmware update required.
• Feature Toggling: Enabling or disabling specific device functions was previously unreliable in some configurations. This has been stabilised.
• Factory Defaults: No longer available in the protocol — same as ROAM. Intentional removal.
Access TEC Care Watch (v1.9 → v2.0)
Release Date: March 2026
Overview
This release improves GPS reliability during signal loss and hardens internal message handling to reduce the risk of messages being lost or delayed under load.
Requirements
Requirement | Details |
Platform Version | IntelliCare v3.8.x or higher |
Firmware | No firmware update required |
What’s New
Change | Area |
GPS behaviour stabilised during temporary signal loss (indoors, tunnels, poor weather) | GPS Reliability |
Internal message handling hardened — reduces risk of messages lost or delayed under high load | Reliability |
What This Means for You
• GPS Signal Loss: Care Watch devices previously could behave unpredictably when GPS signal was temporarily lost. The device now maintains stable behaviour and recovers gracefully. If you have reported intermittent GPS issues, this should resolve them going forward.
• Message Delivery: A behind-the-scenes reliability improvement. The risk of messages being lost or delayed under high load is significantly reduced. No visible change to end users.
• No Action Required: These are transparent improvements. No configuration changes, device resets, or customer communication needed.
Contacts
Product Owner: Lex Smith
Tech Lead: John Wesley
QA Lead: Michael Rodrigues Da Cova