Skip to content

CloudBoxx⚓︎

Fleet managers and developers integrating CloudBoxx devices often need clarity on long-term support, data integration, and hardware capabilities. Use this FAQ to plan deployments and troubleshoot common inquiries.

Product Lifecycle⚓︎

How Long Can I Use INVERS Technology?⚓︎

Use case: “Plan long-term hardware investments for your fleet.”

INVERS guarantees 6 years of support post-production, including firmware updates and component supply.

  • Many customers use CloudBoxx devices beyond 10 years due to proven durability.

Integration⚓︎

Which Software Do Customers Use With CloudBoxx?⚓︎

Use case: “Build custom integrations using INVERS APIs.”

Our APIs are platform-agnostic, allowing full flexibility for booking software development.

Identification⚓︎

What Is the CloudBoxx Unique ID?⚓︎

Use case: “Identify units in API responses and logs.”

The telematics_unit_id (formerly QNR) is the primary unique identifier.

  • Appears as telematics_unit_id in API outputs.

What’s the Difference Between Telematics Unit ID and Serial Number?⚓︎

Use case: “Match physical units to digital records accurately.”

  • Telematics_unit_id: Primary identifier for API communication.
  • Serial number: Alternate hardware identifier used in some contexts.

Hardware⚓︎

Can I Use My Own SIM Card in a CloudBoxx?⚓︎

Use case: “Evaluate hardware customization options.”

No. CloudBoxx requires integrated SIM cards to ensure full functionality.

  • Third-party SIMs are incompatible.

Is the SIM Card Secure Without Soldering?⚓︎

Use case: “Trust hardware reliability in harsh vehicle environments.”

Yes. SIM cards pass rigorous shake tests and field-proven in tens of thousands of vehicles.

Vehicle Data⚓︎

What Vehicle Information Can CloudBoxx Retrieve?⚓︎

Use case: “Access manufacturer-specific CAN bus data.”

Data availability depends on:

  • Presence of a CAN bus in the vehicle.
  • Manufacturer/model/year-specific data transmission protocols.

Decommissioning⚓︎

What Happens If I Cancel My Contract?⚓︎

Use case: “Decommission hardware while preserving vehicle operation.”

When deactivating a CloudBoxx:

  1. It’s removed from your FleetControl account.
  2. The internal SIM is terminated, disabling connectivity.
  3. The unit retains its last configuration but becomes inaccessible.
  4. Devices remain physically operational in vehicles but cease transmitting data.