Skip to content

First steps⚓︎

Installation⚓︎

Before installing the CloudBoxx, ensure that the vehicle you want to install into has already been analyzed and is listed in our list of available vehicle models. You can find this list in FleetControl and in our SmartControl app.

Make sure that the installers receive the API key and QR code for the installation in advance, so that they can access the CloudBoxxes. Ensure that the correct vehicle configuration has been selected in SmartControl during the installation. Verify that the following hardware components are working as expected:

  • Central lock
  • Immobilizer
  • CAN-Bus information, e.g., fuel level and total mileage
  • Key fobs
  • RFID tags

Make sure that your software and/or your reservation app are working as expected:

  • Perform an internal test with a small fleet
  • Test new vehicles with a user group before introducing them to the entire fleet
  • Test setups internally before deploying them to your live operation

Operation⚓︎

Before moving CloudBoxxes from your testing environment to live operations, make sure that the CloudBoxx firmware is up to date. If they are outdated, run a firmware update in FleetControl with bulk jobs.

Ensure that the vehicle’s configuration is correct. If it is misconfigured, correct it in FleetControl on its inspect page.

Make sure that the vehicle is not locked with its remote key. For further information, see troubleshooting.

Verify that user actions on the vehicle match the events in FleetControl.

Troubleshooting⚓︎

You can find explanations and solutions to common issues in the troubleshooting section. If you encounter a problem, we recommend you take the following steps:

  • Check, if the issue is already documented in the troubleshooting section.

  • Open FleetControl and check the following:

    • SIM status on the inspect page
    • 24h monitor, specifically heartbeats, on the inspect page
    • Fleet log entries for the vehicle
    • The CloudBoxx’s configuration on its inspect page

  • Document any indicators that point towards a probable source of the issue and provide them to our support when you contact them.

INVERS responsibility⚓︎

As outlined in your contract, INVERS is mainly, but not exclusively, responsible for any issues with the following:

  • API
  • Connectivity
  • Servers
  • CloudBoxx outages without an identifiable cause
  • Malfunctions of CloudBoxxes which are not caused by improper configuration, installation, or usage