Troubleshooting
Use this sequence before deleting devices or 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 no readings are shown
This usually means discovery worked but the telemetry protocol was not successfully decoded. Open the device details and capture the detected device type, protocol/schema, services, characteristics, and error details.
For Victron equipment, also record the product/firmware information from VictronConnect.
Connection times out
- Close other applications connected to the same BLE device.
- Wait a few seconds and retry; BLE stacks sometimes need time to release a previous connection.
- Do not repeatedly delete/re-add the device until diagnostics have been captured.
- If several devices are being monitored, note whether the failure happens to one specific device or only when many are active.
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.
VoltSyncra goes to sleep or closes
Active BLE work should be stopped and connections released when the application is backgrounded or closed normally. If another application reports that a device remains busy afterward, record the platform, device type, and sequence that caused it.
When to stop testing
Stop and investigate if testing coincides with unexpected equipment configuration changes, protection-state changes, unusual battery behavior, or other behavior that could affect the electrical system. Monitoring software should not require changing equipment settings merely to obtain ordinary telemetry.