v4.1.1 — Fix integration crash when HomeKit can't start

[hiall-fyi]

A small patch that stops a crash on startup. If you don't use HomeKit local control, nothing changes for you.

Bug fixes

Integration no longer fails to load when HomeKit can't start (#308 - @wisskid). If you had HomeKit local control switched on but your Home Assistant host has no zeroconf service running, the whole integration crashed at startup and the cloud side stopped working too. HomeKit local control is optional, so it now quietly falls back to cloud-only and the integration loads as normal. The same protection covers a bridge that drops out while HomeKit is connecting, either during startup or on a later refresh. If you want local control back, add default_config: (or zeroconf:) to your configuration.yaml and restart.

Clearer pairing error when zeroconf is missing (#308 - @wisskid). Trying to pair the HomeKit bridge on a host with no zeroconf service used to show a generic "pairing failed". It now names the actual cause and tells you to add default_config: (or zeroconf:) and restart.

How to Update

From v4.1.0: HACS → Tado CE → ⋮ → Redownload → select v4.1.1 → Restart HA.

Fresh install: See Quick Start in the README.

---

Thanks to everyone who supported the project through Buy Me a Coffee. It genuinely helps.

Full changelog: v4.1.0...v4.1.1

---

This discussion was created from the release Fix integration crash when HomeKit can't start.