Troubleshooting
Use this sequence before changing equipment settings. It preserves useful evidence and avoids making the problem harder to reproduce.
Device does not appear in a scan
- Confirm Bluetooth is enabled.
- Confirm the equipment is powered and visible in its manufacturer's application.
- Fully close the manufacturer's application and scan again.
- Move closer to the equipment.
- On Android, confirm the Bluetooth/nearby-device permissions requested by VoltSyncra are allowed.
- Restart Bluetooth or the phone/computer only after capturing the current error if the problem is repeatable.
Device appears but VoltSyncra cannot identify it
Run the protocol probe. If no supported protocol responds, open the technical probe details. You can copy the diagnostics, prepare an email to support, or save the device as Unknown so its fingerprint is retained for future versions.
A registered device shows Offline
- Use Retry to retry only that device.
- Use Refresh All to request a fresh pass across registered devices.
- Close other applications connected to the same BLE device.
- Use Details when available to copy or send the technical diagnostics.
- Do not repeatedly recreate the registration before capturing the failure details.
Readings look wrong
- Compare the same value with the manufacturer's app at nearly the same time.
- Check units and sign/direction. Charging and discharging current may use opposite signs.
- Compare voltage before SOC; voltage is usually the easiest sanity check.
- For batteries, compare individual BMS readings with a whole-bank shunt if available.
- Capture the values and diagnostics before power-cycling the equipment.
No internet connection
Bluetooth monitoring does not require continuous internet access. If VoltSyncra has successfully validated the account recently and the cached entitlement remains valid, it can continue offline for up to 30 days. Registration, sign-in, password recovery, device activation, and renewed server validation require connectivity.
VoltSyncra goes to sleep or closes
Active BLE work is stopped and connections are released when the application is backgrounded or closed through its normal lifecycle. If another application reports that a device remains busy afterward, record the platform, device type, and sequence that caused it.