This is a custom component for Home Assistant to integrate Philips Sonicare BLE toothbrushes.

The integration connects to your toothbrush via Bluetooth Low Energy (BLE) to provide battery status, brushing session data, brush head wear tracking, and more. All communication is fully local -- no cloud, no app required.

Three connection methods are supported:

1. Direct Bluetooth -- connects from the HA host's Bluetooth adapter (built-in or USB). Uses a persistent live connection with a poll fallback.
2. ESP32 BLE Bridge ★ -- an ESP32 running a custom ESPHome component acts as a wireless BLE relay. Recommended for out-of-range setups; supports multiple devices and notification throttling.
3. Bluetooth Proxy -- uses an existing ESPHome bluetooth_proxy. Works for a single Sonicare per proxy; not recommended due to stability issues.

See Configuration for setup instructions.

• Tested Models
• Dashboard Card
• Features
• Prerequisites
• Installation
• Configuration
  • Option A: Direct Bluetooth
  • Option B: ESP32 BLE Bridge
  • Option C: Bluetooth Proxy
• How It Works
• Troubleshooting & Caveats
• BLE Protocol
• Screenshots

Any BLE-enabled Philips Sonicare toothbrush using the standard protocol should work (Sonicare For Kids, ExpertClean, DiamondClean Smart, DiamondClean 9000, DiamondClean Prestige, and more). The Series 5300–7400 (HX74xx) use a newer BLE protocol that is not yet supported. The integration auto-discovers compatible devices via BLE. If you have a different model — happy to hear your test results!

For a visual brushing dashboard, use the Toothbrush Card -- a custom Lovelace card with live sector tracking, pressure display, and brush head wear indicator. Works with both Philips Sonicare and Oral-B toothbrushes.

This integration creates a new device for your toothbrush and provides the following entities based on your device's hardware:

These sensors are only available while actively brushing and stream live data from the toothbrush IMU.

• A compatible Philips Sonicare toothbrush (see Tested Models above).
• Either a Home Assistant instance with the Bluetooth integration enabled and a working Bluetooth adapter, or an ESP32 running the BLE Bridge component.
• Pairing depends on the model -- DiamondClean Smart (HX992X) uses open GATT without bonding. ExpertClean (HX962X), DiamondClean Prestige (HX999X), and HX991M require BLE pairing. The integration handles both cases automatically. Simply close any Sonicare phone app to free the BLE connection.

Don't have HACS yet? Follow the HACS installation guide first.

1. Go to HACS > Integrations in your Home Assistant UI.
2. Click the three-dot menu in the top right and select Custom repositories.
3. Add https://github.com/mtheli/philips_sonicare_ble and select the category Integration.
4. Find the "Philips Sonicare" integration and click Install.
5. Restart Home Assistant.

1. Copy the custom_components/philips_sonicare_ble directory from this repository into your Home Assistant config/custom_components/ folder.
2. Restart Home Assistant.

The integration supports three connection methods:

1. Wake up your toothbrush (pick it up from the charger or briefly turn it on).
2. Navigate to Settings > Devices & Services.
3. The toothbrush should appear under Discovered -- click Configure.
   • If not discovered automatically, click + Add Integration, search for "Philips Sonicare", and enter the MAC address manually.
4. The confirmation dialog shows the current brush status and detected services. Make sure the toothbrush is turned on (status shows "Active") before clicking Submit.

If your Home Assistant host is too far from the toothbrush for a direct Bluetooth connection, you can use an ESP32 as a wireless BLE bridge. The ESP32 connects to the toothbrush and relays data to HA over WiFi.

This is not a standard ESPHome Bluetooth Proxy -- it is a dedicated component that manages the BLE connection directly on the ESP32 and provides full read/write/subscribe access to all GATT characteristics.

For the complete setup guide, see ESP32 Bridge Setup Guide.

If you already operate an ESPHome Bluetooth Proxy, the integration can use it as a relay — no dedicated bridge firmware needed. Confirmed working on ESPHome 2026.2+ with io_capability: none.

Known caveats:

• Proxy firmware needs the Bluedroid workaround until ESP-IDF v5.5.5 is released.
• First connect after reboot takes ~5 s longer than Direct BLE. Bond keys live on the proxy's NVS, so service discovery and re-encryption race briefly; the integration retries reads automatically during this window.
• Notify Throttle option has no effect on Proxy — throttling is only implemented in the ESP32 BLE Bridge firmware.
• RSSI shown in the Connection device reflects the scanner actually carrying the link (since v0.9.x), not the strongest advertisement.

Setup is the same as Option A — Home Assistant's Bluetooth stack picks the proxy automatically when it has a better or equal connection score to the host adapter.

The Sonicare toothbrush has unique BLE behavior compared to other Philips devices:

• Slow advertising -- the toothbrush sends BLE advertisements only every 10-30 seconds (most BLE devices: every 100-500ms).
• Short wake window -- after turning off, the toothbrush stays connectable for only ~20 seconds before entering deep sleep.
• Pairing varies by model -- DiamondClean Smart (HX992X) uses open GATT without bonding. ExpertClean (HX962X), DiamondClean Prestige (HX999X), and HX991M require BLE pairing. The integration handles both cases automatically.

The integration handles this with:

1. Advertisement-triggered reconnect -- a BLE advertisement callback immediately wakes the connection thread, eliminating unnecessary backoff delays.
2. Subscribe-first pattern -- after connecting, BLE notification subscriptions are established immediately (before reading data). This keeps the connection alive because the toothbrush stays awake as long as active subscriptions exist.
3. Smart lock management -- the polling fallback yields to the live monitoring thread when an advertisement is detected, preventing connection contention.

Toothbrush wakes up
    --> BLE Advertisement detected by HA
    --> Integration connects (~6s BLE stack overhead)
    --> Subscribe to 13 notification characteristics (~1s)
    --> Read all characteristics (~3s)
    --> Live updates flow until toothbrush sleeps
    --> Disconnect detected --> wait for next advertisement

• Toothbrush not discovered: Wake it up by picking it up from the charger or briefly turning it on. The toothbrush is not reachable via BLE while on the charging stand.
• Slow connection: The toothbrush advertises every 10-30 seconds. The integration connects as soon as the first advertisement is received, but the BLE stack adds ~6 seconds overhead.
• Connection drops quickly: This is normal when the toothbrush is idle. It sleeps after ~20 seconds. The integration will reconnect automatically on the next wake.
• Phone app conflict: The toothbrush supports only one BLE connection. Close or uninstall the Sonicare phone app if you experience connection issues.
• Pairing issues: If a model that requires bonding won't connect, remove the toothbrush from your phone's Bluetooth settings first (Settings → Bluetooth → Philips Sonicare → Forget/Unpair). The integration handles stale bonds automatically, but the phone's bond may block the connection.
• ESPHome Bluetooth Proxy: Works with the Bluedroid NULL-check patch until ESP-IDF v5.5.5 ships. See Option C for scope and the dedicated ESP32 BLE Bridge as the recommended alternative for multi-device setups.
• Unsure if your model is compatible? Run the GATT scan script to check which BLE protocol your toothbrush uses. It only needs Python 3 and bleak (pip install bleak).

• Direct BLE reconnect may be delayed: Home Assistant's Bluetooth stack filters duplicate advertisements. Since the Sonicare sends identical advertisement data on every broadcast, wake-ups can be missed. The integration uses a D-Bus RSSI listener as a workaround, but reconnects may still take longer than expected. See habluetooth#397 for the upstream discussion.

The integration communicates directly via BLE -- no cloud, no app required. All communication is fully local.

The toothbrush exposes multiple GATT services with individual characteristics for each data point (battery, brushing state, pressure, brush head, etc.). Data is read directly from these characteristics and live updates are received via GATT notifications.

For a detailed technical description of the BLE protocol including service UUIDs, characteristic reference, data formats, and enum values, see PROTOCOL.md.

Sensors & Controls	Diagnostics	Dashboard Card

Device Overview	Brush Head

This is an independent community project and is not affiliated with, endorsed by, or sponsored by Philips. All product names, trademarks, and registered trademarks are property of their respective owners.

MIT