Adding & Managing Devices

VoltSyncra discovers nearby BLE equipment, identifies supported protocols, and stores the information needed to monitor registered devices.

Scanning

Scanning listens for nearby Bluetooth Low Energy advertisements. A device does not necessarily need to be actively connected in order to appear. Keep the application near the equipment and avoid running another application that holds an exclusive connection to the same device while troubleshooting.

Tip: if a device is visible in the manufacturer's app but not VoltSyncra, fully close the manufacturer's app and scan again. Some BLE devices accept only one active connection.

Registered devices

Registration tells VoltSyncra which discovered devices belong to your system. It also stores the selected protocol/device type so VoltSyncra does not have to rediscover the protocol every time the application starts.

Use meaningful names. If you have multiple identical devices, include location or purpose in the name.

Device states

Connected / Reading: VoltSyncra received a current reading from the device.
Waiting / Stale: The last reading is retained temporarily while VoltSyncra waits for the next successful update.
Disconnected: No active connection is being held. Advertisement-based devices may still provide data without showing a conventional connection.
Unsupported / Unknown: VoltSyncra can see the BLE device but cannot yet decode meaningful telemetry from it.

PINs and credentials

A PIN is typically used to authenticate a Bluetooth connection. A PUK is normally a recovery mechanism and should not be treated as a routine PIN. Some manufacturers use additional keys for passive encrypted advertisements. VoltSyncra should label each credential by its actual purpose rather than asking users to guess.

Deleting a registered device

Deleting a registration removes VoltSyncra's saved association with that device. It does not erase or reconfigure the physical equipment. You can scan and register the device again later.

Read-only monitoring

VoltSyncra's monitoring design is intended to be passive/read-only wherever practical. Device integrations should request telemetry without changing charger, inverter, BMS, alarm, or protection settings. Where a protocol requires a request packet to obtain a reading, that request should be limited to explicitly supported telemetry operations.