[SeanathanVT]

Summary

Bleak 3.x takes the disconnect callback only as a BleakClient constructor argument, and ph4-walkingpad's Controller.connect() passes none. The old set_disconn_callback/set_disconnected_callback branches never ran on Bleak 3.x, so a drop was only noticed by the staleness watchdogs (~15 s active, ~45 s idle/paused). The test fake had set_disconn_callback, which hid this.

• app.Controller subclasses the library's Controller and overrides connect() to pass disconnected_callback=_handle_disconnect.
• Removed the dead old-API branches and their tests.
• _graceful_shutdown() clears connected before its own disconnect, so the now-live callback doesn't log it as a drop or record an auto-pause.

Testing

• New test checks the arguments against the real BleakClient signature, not the fake.
• New test: shutdown's own disconnect isn't treated as a drop (fails without the fix).
• pytest on 3.10, 3.12, 3.13 (557 passed each); ruff check . clean.
• Manual on macOS: power off the pad mid-session; the session should pause and reconnect start immediately, not after ~15 s.

Notes

The connect() override mirrors the library's code, so upstream changes to it won't be picked up; ph4-walkingpad is pinned <2.

🤖 Generated with Claude Code