This custom Home Assistant component controls your Ooler Sleep System over a Bluetooth connection. It is fully compatible with ESPHome Bluetooth Proxies, so if your server is not in range of your Ooler, you can set up an ESP32 in your bedroom to relay the connection.

This component will set up the following platforms.

The integration automatically syncs the Ooler's temperature unit to match your Home Assistant unit system (metric = C, imperial = F). This ensures temperatures are displayed correctly in both HA and on the Ooler's physical display. If you need a different unit on the device, please open an issue.

• Ooler Sleep System (all models with BLE GATT interface)

The Dock Pro (Ooler's successor) uses a cloud API and is not supported by this integration. See sleepme_thermostat for Dock Pro support.

The integration reads and writes sleep schedules directly on the Ooler device. Schedules define per-night temperature programs with bedtime, off-time, and optional mid-night temperature changes and warm wake ramps. If you are only using Home Assistant with your Ooler, then it may be easier to implement your schedule as an automation in HA rather than use the built-in sleep schedule functionality, but if you want to keep using the functionality like in the Ooler app or care about it being built in to the device, then here you go.

The easiest way to get started is to create a schedule in the Ooler app first, then use ooler.save_schedule in HA to save it with a name (e.g., "weekday"). The app only supports applying the same schedule to every day it covers, but once the schedule is on the device, HA can read and save it for later use. You can also use ooler.get_schedule to read the device schedule, edit it manually (e.g., to add per-night variation or warm wake ramps), and write it back with ooler.set_schedule.

App compatibility note: The Ooler app does not read schedule state; it assumes that it is the sole arbiter of truth and will thus be out of sync with the device's loaded schedule until it overwrites with one of its own. (e.g. If you create a schedule in the app and enable it, then turn it off in HA, the Ooler app will think it is still enabled. Or if you create a new schedule in HA and then open the app and click the refresh button, your schedule will never appear since the app doesn't read from schedules from the device).

You can manage schedules through services:

Saved schedules persist across HA restarts. The device only holds one active schedule at a time; saved schedules are stored by the integration and loaded onto the device when selected.

The Schedule Tonight sensor shows a glance view of tonight's program, with full details (temps list, warm wake settings) available as entity attributes. The Sleep Schedule switch toggles the active schedule on/off — disabling it caches the schedule so it can be re-enabled without recreating it.

The device clock is synced to your Home Assistant timezone on connect and every 4 hours to keep schedule timing accurate.

Simple weeknight schedule — cool to 68F from 10pm to 7am, Monday through Friday:

service: ooler.set_schedule
target:
  entity_id: climate.ooler_XXXX
data:
  nights:
    - days: [0, 1, 2, 3, 4]
      bedtime: "22:00"
      off_time: "07:00"
      temperature: 68

Weekend schedule with warm wake — cool to 65F, then warm to 72F over 30 minutes before off-time:

service: ooler.set_schedule
target:
  entity_id: climate.ooler_XXXX
data:
  nights:
    - days: [5, 6]
      bedtime: "23:00"
      off_time: "09:00"
      temperature: 65
      warm_wake:
        temperature: 72
        duration: 30

Mid-night temperature changes — start cool, warm up overnight:

service: ooler.set_schedule
target:
  entity_id: climate.ooler_XXXX
data:
  nights:
    - days: [0, 1, 2, 3, 4]
      bedtime: "22:00"
      off_time: "07:00"
      temps:
        - time: "22:00"
          temperature: 66
        - time: "02:00"
          temperature: 72

Combined weekday + weekend — different schedules in one call:

service: ooler.set_schedule
target:
  entity_id: climate.ooler_XXXX
data:
  nights:
    - days: [0, 1, 2, 3, 4]
      bedtime: "22:00"
      off_time: "06:30"
      temperature: 68
      warm_wake:
        temperature: 74
        duration: 20
    - days: [5, 6]
      bedtime: "23:30"
      off_time: "09:00"
      temperature: 65

Read, edit, and re-apply — use get_schedule in Developer Tools > Services (with "Return response" enabled) to see the current schedule in the exact format set_schedule accepts, then copy and modify it:

service: ooler.get_schedule
target:
  entity_id: climate.ooler_XXXX

Save and manage named schedules:

# Save the current device schedule
service: ooler.save_schedule
target:
  entity_id: climate.ooler_XXXX
data:
  name: "weekday"

# Load it back later
service: ooler.load_schedule
target:
  entity_id: climate.ooler_XXXX
data:
  name: "weekday"

# Delete when no longer needed
service: ooler.delete_schedule
target:
  entity_id: climate.ooler_XXXX
data:
  name: "weekday"

Schedule services target any Ooler entity (e.g., the climate entity). Device and area targeting also work through the HA UI. Days are numbered 0=Monday through 6=Sunday. Temperatures are in Fahrenheit (the device's internal format). Valid temperatures are 54-116F, plus the special values 45 (LO) and 120 (HI).

The integration maintains a persistent BLE GATT connection to each Ooler device. State updates (power, temperature, mode) are pushed in real-time via GATT notifications. Water level and cleaning status are polled every 5 minutes. The sleep schedule is read once on connect (since only one BLE client can be connected at a time, it can't change while HA is connected).

If the connection drops, the integration reconnects automatically -- both immediately on disconnect and via a 60-second periodic fallback. When multiple devices reconnect simultaneously (e.g., after a proxy restart), attempts are staggered to avoid overwhelming the proxy's connection slots.

ESPHome Bluetooth proxies can occasionally drop BLE notification subscriptions without disconnecting. The integration detects these missed notifications by comparing polled state against the last notified state. When a mismatch is found, it automatically re-subscribes or forces a full reconnect if needed. These events are logged and tracked in device diagnostics for troubleshooting.

1. Open HACS in your Home Assistant instance.
2. Click the three-dot menu in the top right and select "Custom repositories".
3. Add https://github.com/PostLogical/ooler with category "Integration".
4. Find the integration as Ooler and click install.
5. Restart Home Assistant.

1. Copy the custom_components/ooler/ folder to your HA custom_components/ directory.
2. Restart Home Assistant.

1. In the HA UI go to "Settings" -> "Devices & Services" -> "Integrations".
2. Your Ooler should appear in the discovered integrations automatically. You can also click the + sign and search for "Ooler".
3. If your Ooler is not discovered, make sure it is powered on and not connected to the Ooler app (only one Bluetooth connection is allowed at a time). You may need to hold the power button for a few seconds to make it discoverable.
4. Confirm the device and the integration will verify the connection.

If the BLE connection needs to be re-verified later, use the Reconfigure option in the integration's settings (Settings -> Devices & Services -> Ooler -> Configure).

• One Bluetooth connection at a time. The Ooler only supports a single BLE connection. If the Ooler app is connected, HA cannot connect (and vice versa). Use the Bluetooth Connection switch to disconnect from HA when you need the app.
• ESP32 proxy connection slots. Each Ooler uses 4 BLE notification slots. ESPHome proxies provide 12 slots (vs 9 for raw ESP-IDF). If you have multiple BLE devices on one proxy, you may run into slot limits.
• No Wi-Fi or cloud support. The Ooler communicates only via Bluetooth. The device must be within BLE range of your HA server or an ESPHome Bluetooth proxy.

• Device not discovered: Ensure the Ooler is powered on and not connected to the mobile app. Hold the power button for ~5 seconds to enter pairing/discoverable mode.
• Frequent disconnects: Check your ESP32 proxy's BLE slot usage. Reduce the number of active BLE connections if needed. Ensure the proxy is running ESPHome (not raw ESP-IDF) for maximum notification slots.
• Temperature displays incorrectly: The integration auto-syncs the Ooler's display unit to your HA unit system. If you recently changed your HA unit system, restart the integration.
• "Device unavailable" after HA restart: The integration seeds the BLE device from HA's cache on startup. If the proxy hasn't reported the device yet, it may take up to 60 seconds for the periodic reconnect to establish the connection.
• Missed notifications (proxy flakiness): If you see "poll detected missed notifications" in logs, the integration is handling it automatically. Check device diagnostics for subscription mismatch and forced reconnect counts. Consider dedicating a proxy to BLE-heavy devices if this happens frequently.
• Diagnostics: Download device diagnostics from Settings -> Devices -> Ooler -> Download diagnostics. This includes connection state, device settings, sensor values, and proxy reliability metrics for debugging.

Turn on the Ooler at bedtime:

automation:
  - alias: "Ooler bedtime cooling"
    trigger:
      - platform: time
        at: "22:00:00"
    action:
      - service: climate.set_temperature
        target:
          entity_id: climate.ooler_92106080601
        data:
          temperature: 68
      - service: climate.turn_on
        target:
          entity_id: climate.ooler_92106080601

Turn off in the morning:

automation:
  - alias: "Ooler morning off"
    trigger:
      - platform: time
        at: "07:00:00"
    action:
      - service: climate.turn_off
        target:
          entity_id: climate.ooler_92106080601

Disconnect for Ooler app access:

automation:
  - alias: "Ooler disconnect for app"
    trigger:
      - platform: state
        entity_id: input_boolean.ooler_app_mode
        to: "on"
    action:
      - service: switch.turn_off
        target:
          entity_id: switch.ooler_92106080601_bluetooth_connection

Boost mode during hot nights:

automation:
  - alias: "Ooler boost when hot"
    trigger:
      - platform: numeric_state
        entity_id: sensor.bedroom_temperature
        above: 78
    action:
      - service: climate.set_fan_mode
        target:
          entity_id: climate.ooler_92106080601
        data:
          fan_mode: "Boost"

If you want to contribute to this please read the Contribution guidelines

The code for this integration was primarily based on the official EufyLife integration and then adjusted using other components like Snooz and Philips Hue as guides.

This readme and some supporting HACS elements were generated from @oncleben31's Home Assistant Custom Component Cookiecutter template.

Development of this integration is assisted by Claude Code (Anthropic). Claude is used as a development tool for code generation, testing, and analysis. All code changes are reviewed, tested, and approved by the maintainer before being merged.