BMS Connection Issues
If no JK-BMS data appears:
- Confirm the BMS is a JK-BMS.
- Confirm the JK-BMS is powered on and awake (a sleeping pack does not advertise over Bluetooth).
- Confirm the BMS is within Bluetooth range of the gateway.
- Check the gateway's BLE state and discovered-address diagnostics in the dashboard.
- If several packs are nearby, set an explicit BMS Bluetooth address so the gateway does not connect to the wrong unit.
- Confirm the ESP32 is not being powered from battery pack voltage.
The gateway is online but there is no battery data
These are two different states, and the dashboard shows them separately:
- Gateway offline: the gateway itself has not checked in. Check its power and WiFi.
- Gateway online, no BMS data: the gateway is reporting, but the Bluetooth link to the pack is down. The device page shows the last error and the RSSI it saw.
While the link is down the gateway keeps sending a heartbeat, so the gateway stays visible and the missing piece is named rather than looking like a dead device.
"Online" means the gateway is talking to us, not that it has data. A gateway polling for settings is alive even when it has never uploaded a reading, so it reads as online within a minute of boot; hasTelemetry and the BMS link state carry the separate question of whether the pack link is working.
From firmware 0.9.12 the recovery path is bounded:
- a dropped link is retried after 30 seconds, then at most every 60 seconds;
- a link that connects but sends no data for 30 seconds is dropped and re-established, instead of staying attached and silent.
What to check when this happens repeatedly:
- Signal strength. An RSSI weaker than about -85 dBm is marginal. Move the gateway closer, get it out of a metal enclosure, or reorient the antenna.
- Power. A gateway on a weak supply browns out during a WiFi transmit and looks like a Bluetooth fault.
- One pack at a time. Two nearby packs with the same name confuse discovery; set an explicit BMS Bluetooth address.