v0.10.0

Highlights

• Scheduled-thermostat temperature changes work again (#99, thanks @mune360). When a schedule was enabled, single-setpoint changes in HEAT and COOL modes silently dropped because the override_schedule flag was missing from the API call. Setpoint changes from HA now override the active schedule as expected. Fixes #35, #98.
• Sentinel values from the Daikin API are sanitized per-field (#111, building on @gcamp's prototype in #94). When a thermostat restarts or drops connectivity, the cloud returns 255 / 65535 / 32767 / 4294967295 for individual telemetry fields. Those now become None so only the affected sensor goes unavailable — the rest of the device keeps updating instead of the whole entity going stale. Fixes #22, #77, #79, #97, #103, #105.
• Equipment with garbled identity strings no longer churn HA's entity registry (#111). When a model or serial comes back with \ufffd sentinel characters, the equipment is omitted for that refresh instead of splicing garbage into its eid. Entities go briefly unavailable and recover on the next good refresh, rather than being orphaned and re-registered under a shifting unique_id.

What's Changed

• Modernize deps and dev tooling by @zlangbert in #110
• fix: skip offline devices with empty data during refresh by @hansdg1 in #109
• fix: add missing override_schedule parameter for single temperature c… by @mune360 in #99
• fix: sanitize sentinel values in Daikin API responses by @zlangbert in #111
• fix: sanitize max-RPS and enum-wrapped fields by @zlangbert in #112
• release: prepare 0.10.0 by @zlangbert in #113

New Contributors

• @hansdg1 made their first contribution in #109
• @mune360 made their first contribution in #99

Full Changelog: v0.9.6...v0.10.0