Repository navigation
Conversation
Update Dev
update dev
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>
…-component-0.13.375
…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>
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>
|
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 The change only touches |
|
@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 |
|
@KJonline no problem, I was just doing some housekeeping. Will take a look at you suggestion, |
What does this change?
Home Assistant 2026.11 moved
hive.boost_heating_on,hive.boost_heating_offandhive.boost_hot_waterout of the coreclimate/water_heaterplatforms and intohomeassistant/components/hive/services.py. Core now registers them from its ownasync_setup(core 2026.11.0hive/__init__.py).This component replaces the
hivedomain, and itsclimate.py/water_heater.pyre-export core's platforms. Core'sasync_setuptherefore 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_setupthat calls core'sasync_setup_serviceswhen that function exists. The import is guarded, so on Home Assistant before 2026.11 (hacs.jsonminimum 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
script/testpasses. No new test: the existingtest_boost_heating_servicesandtest_boost_hot_water_servicecover this, and they will fail without the fix oncepytest-homeassistant-custom-componentpins HA 2026.11.script/testpasses (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 (httpxalias / removedlogger._clear_logger_overwrites). Instead it was checked on a live HA 2026.11.0 install: without the change onlyset/cancel_holiday_modewere registered (that install carries holiday mode from feat: add holiday mode services and sensors #222), and with itboost_heating_on,boost_heating_offandboost_hot_waterare back.script/lint --checkpassesversioninmanifest.json. Left for the maintainer.🤖 Generated with Claude Code