BatMON BLE → MQTT bridge

1. Service health

systemctl status batmon.service --no-pager -l

Good: active (running) and fresh sample lines. Bad: repeated Tracebacks, restart loops, or no fresh samples.

2. Clean live BatMON view

journalctl -u batmon.service -f -o short-iso \
| grep -aEi 'FailureBat-|BmsSampl|ERROR|WARNING|InProgress|not found|Service Discovery|timeout waiting|disconnected after'

This is the main operator view: samples, reconnects and useful failures without the full byte-buffer noise.

3. One-shot recent status

journalctl -u batmon.service -n 160 --no-pager -o short-iso \
| grep -aEi 'FailureBat-|BmsSampl|ERROR|WARNING|InProgress|not found|Service Discovery|timeout waiting|disconnected after'

Useful after opening an SSH session when you want the last few minutes without following the log.

4. Bluetooth adapter map

bluetoothctl list
for i in 0 1 2 3; do echo "===== hci$i ====="; btmgmt --index "$i" info 2>/dev/null || true; done

Confirms that the four adapters still exist and have not disappeared from USB/BlueZ.

5. MQTT discovery check

timeout 20 mosquitto_sub -h 192.168.42.99 -t 'homeassistant/sensor/#' -v -R \
| grep -aEi 'FailureBat|state_topic|json_attributes_topic|unique_id|name'

Shows Home Assistant discovery messages. Use this when HA entities look wrong even though BatMON samples are fresh.

6. Avoid noisy full MQTT grep

timeout 60 mosquitto_sub -h 192.168.42.99 -t '#' -v -R \
| grep -aEiv '^(zigbee2mqtt|homeassistant)/' \
| grep -aiE 'fail|bat|bms|jk|cell|soc|volt|curr'

Use -R and grep -a so retained Zigbee2MQTT payloads do not turn the output into binary-looking noise.

Restart only BatMON

sudo systemctl restart batmon.service

Use when BatMON itself looks stale but BlueZ adapters still look normal.

Reset one stuck adapter

sudo systemctl stop batmon.service
sudo btmgmt --index 2 power off
sleep 3
sudo btmgmt --index 2 power on
sleep 5
sudo systemctl start batmon.service

Example uses hci2. Change the index based on the adapter-to-pack map.

Reset all BatMON adapters

sudo systemctl stop batmon.service
for i in 0 1 2 3; do sudo btmgmt --index "$i" power off || true; done
sleep 3
for i in 0 1 2 3; do sudo btmgmt --index "$i" power on || true; done
sleep 5
sudo systemctl start batmon.service

This is the reboot replacement when several packs are stale or BlueZ is clearly wedged.

Full Bluetooth service reset

sudo systemctl stop batmon.service
sudo systemctl restart bluetooth.service
sleep 5
sudo systemctl start batmon.service

Use if adapter power cycling is not enough.

2. Create systemd service

sudo tee /etc/systemd/system/batmon-ble-watchdog.service >/dev/null <<'EOF'
[Unit]
Description=BatMON BLE watchdog resetter

[Service]
Type=oneshot
ExecStart=/home/failurep/batmon-ha/scripts/batmon-ble-watchdog.sh
EOF

3. Create systemd timer

sudo tee /etc/systemd/system/batmon-ble-watchdog.timer >/dev/null <<'EOF'
[Unit]
Description=Run BatMON BLE watchdog every minute

[Timer]
OnBootSec=2min
OnUnitActiveSec=1min
AccuracySec=10s
Persistent=true

[Install]
WantedBy=timers.target
EOF

4. Enable watchdog

sudo systemctl daemon-reload
sudo systemctl enable --now batmon-ble-watchdog.timer
systemctl status batmon-ble-watchdog.timer --no-pager

5. Watch watchdog actions

journalctl -t batmon-ble-watchdog -n 80 --no-pager
systemctl list-timers | grep batmon

Battery blocks

# Each pack has a dedicated adapter.
# Example structure only — keep private addresses in batmon.yaml.
- alias: "FailureBat-03"
  adapter: "hci0"
  keep_alive: false
- alias: "FailureBat-02"
  adapter: "hci1"
  keep_alive: false
- alias: "FailureBat-01"
  adapter: "hci2"
  keep_alive: false
- alias: "FailureBat-00"
  adapter: "hci3"
  keep_alive: false

Sampling and publishing

sample_period: 30          # seconds between reads
publish_period: 10         # seconds between MQTT publishes

sample_period: 2 was too aggressive for long-term BlueZ/Bleak stability. The slower cadence is still fast enough for pack telemetry.

Verify current config

grep -nEi 'keep_alive|sample_period|publish_period|FailureBat|adapter|hci' /home/failurep/batmon-ha/batmon.yaml

Backup before edits

cp /home/failurep/batmon-ha/batmon.yaml \
/home/failurep/batmon-ha/batmon.yaml.bak-$(date +%F-%H%M%S)

Confirm unit command

systemctl cat batmon.service

Expected runtime path: /home/failurep/batmon-ha/main.py -c /home/failurep/batmon-ha/batmon.yaml.

Confirm process

ps aux | grep -Ei 'batmon|main.py|python' | grep -v grep