siloos-ble-debug

name: siloos-ble-debug description: "Troubleshooting TopBrewer BLE connection, GATT errors, and WebSocket relay issues."

SiloOS BLE Debug Skill

When to Use

• TopBrewer is not responding to commands
• BLE connection drops repeatedly
• Notifications are not being received
• GATT read/write operations timeout

Prerequisites

• SSH access to Raspberry Pi (ssh -i siloos_key siloos@10.0.124.90)
• TopBrewer machine is powered on and within BLE range
• ble_bridge.py service is running

Procedure

Step 1: Check Service Status

ssh -i siloos_key siloos@10.0.124.90 "sudo systemctl status scale_bridge"

Expected: Active: active (running)

Step 2: Check Recent Logs

ssh -i siloos_key siloos@10.0.124.90 "sudo journalctl -u scale_bridge -n 50 --no-pager"

Look for:

• BLE connected — TopBrewer connection established
• BLE disconnected — Connection lost (check range, power)
• GATT error — Protocol issue (check characteristic UUIDs)

Step 3: Verify BLE Adapter

ssh -i siloos_key siloos@10.0.124.90 "bluetoothctl show"

Expected: Powered: yes, Discovering: no (scan should be off when connected)

Step 4: Reset BLE Adapter (if stuck)

ssh -i siloos_key siloos@10.0.124.90 "bluetoothctl power off && sleep 2 && bluetoothctl power on"

Step 5: Scan for TopBrewer

ssh -i siloos_key siloos@10.0.124.90 "python3 find_machine.py"

Expected: Device with MAC 88:6B:0F:BC:00:A1 should appear

Step 6: Restart Bridge

ssh -i siloos_key siloos@10.0.124.90 "sudo systemctl restart scale_bridge"

Step 7: Verify WebSocket

From development machine, check if WebSocket is accepting connections:

curl -s -o /dev/null -w "%{http_code}" http://10.0.124.90:8765/

Expected: HTTP response (indicates aiohttp is listening)

Expected Outcomes

• BLE connection re-established
• WebSocket relay operational
• Notifications flowing from TopBrewer to dashboard

Troubleshooting