Diagnostics & Support
The fastest way to fix a device problem is to capture enough information to reproduce it without guessing.
What to collect
- VoltSyncra application version/build.
- Platform: Windows, Android, or iOS, plus OS version.
- Device manufacturer, exact model/part number, and firmware if available.
- What VoltSyncra called the device and which protocol/schema it selected.
- The exact error message and the text from any Details view.
- Relevant VoltSyncra error log entries.
- What the manufacturer's application showed at the same time.
For Bluetooth problems
Useful BLE diagnostics include the advertised device name, address/identifier, RSSI, advertised service UUIDs, discovered GATT services, discovered characteristic UUIDs, and the stage that failed: scan, connect, service discovery, notification setup, request, response, decode, or disconnect.
Describe the sequence
A short reproducible sequence is more useful than a general description. Example:
1. Launch VoltSyncra 2. Open Registered Devices 3. Device shows Connected for ~5 seconds 4. Open device details 5. Reading changes to Failed 6. VictronConnect can still read the device after VoltSyncra is closed
Protect sensitive information
Before posting logs publicly, remove account tokens, passwords, API secrets, signing keys, private server connection strings, Bluetooth recovery codes, or other credentials. Device UUIDs and model numbers are generally useful for troubleshooting; authentication secrets are not.