A modernized temporary replacement for the native Home Assistant component.
Option 1: HACS
HACS
>Integrations
>⋮
>Custom Repositories
Repository
: paste the url of this repoCategory
: Integration- Click
Add
- Close
Custom Repositories
modal - Click
+ EXPLORE & DOWNLOAD REPOSITORIES
- Search for
dbuezas_eq3btsmart
- Click
Download
- Restart Home Assistant
- Copy the
dbuezas_eq3btsmart
folder insidecustom_components
of this repo to/config/custom_components
in your Home Assistant instance - Restart Home Assistant
- Go to
Settings
>Integrations
- Either wait for automatic discovery, or click
+ ADD INTEGRATION
and search fordbuezas_eq3btsmart
- Addition will succeed immediately, so give the entity some minutes to connect to the thermostat
See here https://github.com/rytilahti/python-eq3bt#pairing
- It works in HA version > 2022.7
[x] Supports ESP32 Bluetooth proxiesMaybe if you have EQ3 firmware v1.20 (doesn't require pairing)- Supports auto discovery
- Supports adding via config flow (UI)
- Fixes setting operation mode
- Allows to turn off by setting temp to 4.5°
- Retries (10 times) when you change a thermostat attribute.
[x] Push instead of Pull. It updates on bluetooth advertisement instead of polling every x minutes (seems to generate less unsuccessful tries)- Connections are persistent (this may or may not reduce the battery life, but it makes the thermostats more responsive)
- Fully uses asyncio (less resource intensive)
-
Current Temperature
updates immediately, regardless of when the bluetooth connection is made. The component will apply the change as soon as it can connect with the device. - Service to fetch heating schedules and serial inside the thermostat
- Only one concurrent request per thermostat
- Service to set the heating schedules (Work in progress)
- Removed support for installing via yaml
- Support pairing while adding entity
This is heavily based on https://github.com/rytilahti/python-eq3bt and https://github.com/home-assistant/core/tree/dev/homeassistant/components/eq3btsmart and it should ideally be two PRs instead. Unfortunately, the changes go too deep and remove support for the CLI and other backends. Therefore, here's a self contained custom component instead.