Skip to content

v9.0.2 πŸ› οΈ Home Assistant 2026.7 compatibility

Choose a tag to compare

@danieldotnl danieldotnl released this 02 Jul 10:03

πŸ‘‹ A quick note

I run The Smart Home Newsletter β€” a weekly curated digest for smart home enthusiasts.

Each issue highlights the most relevant and interesting smart home articles, news, and projects from the past week.

Since you're here, you're clearly into home automation β€” so you might genuinely enjoy the newsletter.

πŸ‘‰ Subscribe at smarthomenewsletter.com


πŸ”§ What's new in v9.0.2

A small maintenance release keeping Multiscrape in lockstep with the latest Home Assistant core.

🏠 Home Assistant 2026.7 compatibility

Home Assistant core 2026.7 removed the private Template._parse_result() method that Multiscrape used when applying a value_template on its own (without a selector). This caused an AttributeError and broke value-template-only sensors on the new core.

Multiscrape now uses the public parse_result=True parameter of async_render_with_possible_json_value() instead β€” equivalent behavior, and compatible across HA versions. (#588)

⬆️ Dependencies & Tooling

  • Update pytest-homeassistant-custom-component to v0.13.343 β€” now testing against HA core 2026.7 (#588, #585, #583)
  • Update ruff to v0.15.20 (#589, #586, #584)
  • Update actions/checkout to v7 (#590, #582)
  • Update actions/setup-python to v6.3.0 (#591)

Full Changelog: v9.0.1...v9.0.2