Skip to content

fix: register boost services on Home Assistant 2026.11 - #234

Closed
nsleigh wants to merge 15 commits into
Pyhass:masterfrom
nsleigh:fix/register-boost-services-2026-11
Closed

nsleigh wants to merge 15 commits into
Pyhass:masterfrom
nsleigh:fix/register-boost-services-2026-11

Conversation

@nsleigh

@nsleigh nsleigh commented Nov 4, 2026 •

Copy link
Copy Markdown

What does this change?

Home Assistant 2026.11 moved hive.boost_heating_on, hive.boost_heating_off and hive.boost_hot_water out of the core climate / water_heater platforms and into homeassistant/components/hive/services.py. Core now registers them from its own async_setup (core 2026.11.0 hive/__init__.py).

This component replaces the hive domain, and its climate.py / water_heater.py re-export core's platforms. Core's async_setup therefore never runs, and on 2026.11 the three boost services are missing. Scripts and automations that call them fail, and Spook raises "unknown action" repairs for them.

The fix adds an async_setup that calls core's async_setup_services when that function exists. The import is guarded, so on Home Assistant before 2026.11 (hacs.json minimum is 2025.6.0) it does nothing and the platforms keep registering the services as before. CONFIG_SCHEMA = cv.config_entry_only_config_schema(DOMAIN) is added alongside it, matching core.

Related issues

Fixes #235

Checklist

  • Tests added or updated, and script/test passes. No new test: the existing test_boost_heating_services and test_boost_hot_water_service cover this, and they will fail without the fix once pytest-homeassistant-custom-component pins HA 2026.11. script/test passes (82/82) on the current pin (HA 2026.10.4). The suite can't run on 2026.11 yet because the latest plugin (0.13.375) doesn't load against core 2026.11.0 (httpx alias / removed logger._clear_logger_overwrites). Instead it was checked on a live HA 2026.11.0 install: without the change only set/cancel_holiday_mode were registered (that install carries holiday mode from feat: add holiday mode services and sensors #222), and with it boost_heating_on, boost_heating_off and boost_hot_water are back.
  • script/lint --check passes
  • If this is going into a release: bumped version in manifest.json. Left for the maintainer.

🤖 Generated with Claude Code

Khole and others added 15 commits July 8, 2022 19:13
Bumps the github-actions group with 1 update in the / directory: [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv).


Updates `astral-sh/setup-uv` from 10.2.0 to 10.3.2
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@v10.2.0...v10.3.2)

---
updated-dependencies:
- dependency-name: astral-sh/setup-uv
  dependency-version: 10.3.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Bumps [pytest-homeassistant-custom-component](https://github.com/MatthewFlamm/pytest-homeassistant-custom-component) from 0.13.370 to 0.13.375.
- [Release notes](https://github.com/MatthewFlamm/pytest-homeassistant-custom-component/releases)
- [Changelog](https://github.com/MatthewFlamm/pytest-homeassistant-custom-component/blob/master/CHANGELOG.md)
- [Commits](MatthewFlamm/pytest-homeassistant-custom-component@0.13.370...0.13.375)

---
updated-dependencies:
- dependency-name: pytest-homeassistant-custom-component
  dependency-version: 0.13.375
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
…ithub-actions-a055b02c66

chore(deps): bump astral-sh/setup-uv from 10.2.0 to 10.3.2 in the github-actions group across 1 directory
…ssistant-custom-component-0.13.375

chore(deps): bump pytest-homeassistant-custom-component from 0.13.370 to 0.13.375
Bumps the github-actions group with 1 update: [astral-sh/setup-uv](https://github.com/astral-sh/setup-uv).


Updates `astral-sh/setup-uv` from 10.3.2 to 10.3.3
- [Release notes](https://github.com/astral-sh/setup-uv/releases)
- [Commits](astral-sh/setup-uv@v10.3.2...v10.3.3)

---
updated-dependencies:
- dependency-name: astral-sh/setup-uv
  dependency-version: 10.3.3
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: github-actions
...

Signed-off-by: dependabot[bot] <support@github.com>
Pin pyhive-integration 2.0.0b5, ahead of core's 1.0.10, and set the
version to 2026.11.0b1 for the next beta.

Restore what 5e63418 reverted, which broke CI and Compatibility:
- Map HiveConnectionError to ConfigEntryNotReady, and
  HiveUnknownConfiguration to ConfigEntryAuthFailed. The tests already
  expected this and failed to import HiveConnectionError on 1.0.10.
- Restore en.json, which had a trailing space hassfest rejects and no
  options or services strings, and the files the revert reformatted, so
  ruff passes again.

custom_components/ now matches 2026.10.1b2 apart from the manifest.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
dev is now the default branch, and PRs and releases go through it.

- ci.yml runs on pushes to dev instead of master, so merges to dev get
  a CI run and still re-enable scheduled workflows.
- CLAUDE.md, CONTRIBUTING.md, MAINTAINING.md, README.md, CODEOWNERS and
  the release and repo-health skills now say dev, including the
  --target for gh release create and the branch whose protection to check.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
chore: make dev the main branch in CI, docs and skills
….0b5

deps: bump pyhive-integration to 2.0.0b5 and release 2026.11.0b1
…ithub-actions-7313d4f700

chore(deps): bump astral-sh/setup-uv from 10.3.2 to 10.3.3 in the github-actions group
Home Assistant 2026.11 moved boost_heating_on, boost_heating_off and
boost_hot_water out of the hive climate/water_heater platforms into
hive/services.py, registered from core's async_setup. This component
replaces the hive domain, so core's async_setup never runs and the
services are missing. Add async_setup that calls core's
async_setup_services when it exists (no-op on older versions, where the
platforms still register them), plus the matching CONFIG_SCHEMA.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nsleigh
nsleigh requested a review from KJonline as a code owner November 4, 2026 19:53
nsleigh added a commit to nsleigh/Hive-Custom-Component that referenced this pull request Nov 4, 2026
Holiday mode sensors are added with update_before_add, so a Hive cloud
timeout during startup raised out of async_update and HA never added
sensor.hive_holiday_mode / holiday_date_start until the next restart.
Catch TimeoutError, aiohttp ClientError and HiveApiError and go
unavailable instead; the 30-minute poll and dispatcher refreshes
recover them.

Also guard the homeassistant.components.hive.services import from
2a4b641 so the component still loads on Home Assistant < 2026.11, where
the climate/water_heater platforms register the boost services (same
form as upstream PR Pyhass#234).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@nsleigh

nsleigh commented Nov 8, 2026

Copy link
Copy Markdown
Author

Hi, gentle nudge on this one. Users are hitting the missing boost actions on HA 2026.11 (see #235: one has downgraded HA because of it, another patched __init__.py by hand). The CI run is waiting on workflow approval for a fork PR, so it hasn't run yet.

The change only touches __init__.py, and the import is guarded, so nothing changes on HA < 2026.11. It's been running on a live 2026.11.0 install since 4 Nov with the boost actions working. I'm happy to retarget it or adjust it if you'd rather it went out with a different release (e.g. a 2026.11.1B2).

@KJonline
KJonline changed the base branch from dev to master November 8, 2026 13:04
@KJonline

KJonline commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

@nsleigh apologies I’m out of the country at the minute and not looking at my phone much.

I’ve approved the workflow as part of this PR can you also bump the version to drop the beta tag to 2026.11.0 and revert the pyhive integration library to 1.0.10

it might be easier to base your PR off master instead of dev and do a new PR

apologies the beta is in dev and I want to avoid this change getting mixed in with that

@nsleigh

nsleigh commented Nov 8, 2026

Copy link
Copy Markdown
Author

@KJonline no problem, I was just doing some housekeeping. Will take a look at you suggestion,

@nsleigh

nsleigh commented Nov 8, 2026

Copy link
Copy Markdown
Author

Thanks @KJonline, no problem at all, and thanks for approving the workflow. I've reopened this against master as #239, with the version bumped to 2026.11.0 and pyhive-integration left at 1.0.10. Closing this one in favour of it.

@nsleigh nsleigh closed this Nov 8, 2026
@nsleigh
nsleigh deleted the fix/register-boost-services-2026-11 branch November 9, 2026 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG] Boost actions missing on Home Assistant 2026.11

2 participants