First of all, don't panic. Errors can have a variety of causes. They can be due to an underlying hardware problem, some can be caused by a dropped Bluetooth connection and will resolve themselves, and some just may require an update.
What to do
1. Wait for 2 minutes
Some errors are temporary. For example, Bluetooth communication might have been interfered with, and the device didn't know how to deal with it.
As a first step, wait 2 minutes. This will allow the device to restart and try again. If the error goes away, great, you can use it as normal! It will have been a temporary communications issue in that case.
If the error reappears, try the below:
2. Update your device
Hold down the power button (down on Velo 2/ Moto II devices) permanently while the error is showing. The device will then go into "update mode", showing the cloud. From there, update it using your Beeline app.
If you still get errors after the update, please contact us here. Select "I have a Beeline device that isn't working as it should" then "Error message on device screen" and if possible, add a picture of the screen. We will help you as soon as we can.
Types of Errors
You can look up the code and possible solutions here. In most cases, these errors will resolve themselves after the device restarts.
Otherwise, this error message screen has a lot of information which will help our engineers figure out what went wrong. Please take a picture if your error persists and contact us here.
Error type
Explains what part of the code caused the error
"Dev" : The main firmware had an issue. Try to update the device (see above)
"Boot": The bootloader had an issue. Usually during a firmware update. It should be possible to recover from this by updating (see above)
Error location
Explains where in the code this error arose from. This won't mean much to you. You'll commonly see text containing:
"beeline" or error codes starting with "B-#": Likely a Bluetooth-related issue. If it resolves itself, then don't worry but do let us know that you saw it, please.
"imu" or "i2c": Likely a hardware run-in. Please contact us here and we can help you out!
Software (aka Firmware) version (starting with v)
This tells us the device's firmware version. It might help to update the device. To do this, hold the power (bottom) button for many minutes. This ensures that the button is held when the Velo 2 reboots. It will then reboot into the update mode from where it can be updated via the Beeline App.
Hardware version (starting with p)
This tells us exactly what type of device we are dealing with here
Error number (starting with ec)
This tells us about the type of Error. The numbers are meaningful to our Engineers.
WDT Error
This error is very rare but occurs when the device has to restart after it gets stuck and freezes. Once it shows this error, the device will try to reboot, and 9 times out of 10 resolves the issue and error message itself. However, if it has not, the following steps should resolve the issue.
Ideally, you could provide us with information about what screen it was on when it stuck or what you did to cause it. Please do contact us here.
To troubleshoot the issue, if the error persists, please try these steps:
1 - Unpair your Beeline device from your phone. You can do this within the Beeline app > Settings > Unpair. The device should then be in the following screen:
If it is not, please unpair the device from the device itself as well. You can do this by using the device buttons to navigate to Settings > Unpair.
2 - Clear any pairing information from your phone's Settings. Go to the phone's (not Beeline app) Bluetooth settings and remove/delete/forget the device there:
3 - Press and hold the bottom power button whilst the device is in the pairing screen until the device turns off.
4 - Wait a few seconds, then press and hold the power button to turn the device back on. This will wipe all remaining device details to give the device a totally clean slate to re-pair from.
5 - Pair the device to the Beeline app. Go to the Beeline app > Settings > Devices > Connect a device > Pair from here.
From here, your device should pair to your app and return to working as usual, without the error message.
Please let us know how you get on with these steps and if this has resolved the error message.
If the error message comes back, please send a description of any actions you took on the device in the lead up to the error message - ie did you turn the device off then on? Did you start a ride then receive the error message? Did you do nothing at all? All of these details are really useful for helping us figure out and fix whatever is causing the issue here.
Please contact us here.


