Repository navigation
๐ 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.2.1
A bugfix release that makes multiscrape.reload clean up properly and lets sensors recover by themselves when a select_list suddenly matches nothing, for example when a session expires and the site returns its login page.
One fix changes how an empty select_list is handled. Please read the
๐ Bug fixes
- Sensors froze when a
select_listmatched nothing. An emptyselect_listreturned''and counted as a successful scrape. In #639 the site's session expired and it served the login page instead.on_errornever applied, and the form was never re-submitted withsubmit_once: true. Numeric sensors also failed when Home Assistant rejected the''state. The sensors stayed stuck until a restart. An emptyselect_listis now a scrape error, likeselectalready was, soon_errorand re-authentication kick in. (#640, closes #639) multiscrape.reloadraisedKeyErrorafter removing themultiscrape:section. Reloading with no Multiscrape config left now shuts down the old scrapers and finishes cleanly. (#642, closes #641)- Reload left stale
multiscrape.trigger_<name>services behind. Their scrapers were already shut down, so the services pointed at a closed HTTP session. Reload now removes the trigger service of every scraper it discards. (#643) - Reload set up a broken scraper for a services-only entry. A lone
multiscrape:entry withoutresourceorresource_templateonly enables theget_contentandscrapeservices. Setup already handled that, but reload created ascraper_unnamed_0that failed on every update. Reload now uses the same check as setup. (#643)
โ ๏ธ Breaking changes
- An empty
select_listis now a scrape error. If your config relied on aselect_listthat matches nothing returning'', it now goes throughon_error. That also means it logs at the configured level unless you setlog: false.
Thanks to @tridev-tej for the reload fix, and to @mdp716 and @pallemannen for reporting #639 and #641!
โฌ๏ธ Dependencies & Tooling
- Migrate the tests from
pytest-homeassistant-custom-componentto the Core-maintainedpytest-homeassistant(#645, #647). Thanks @balloobbot! - Move the development environment to Python 3.14 (#647)
- Update
ruffto v0.17.4 (#644)
Full Changelog: v9.2.0...v9.2.1