v9.0.4 🛠️ Fix spurious startup triggers

👋 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.4

A small bugfix release that stops Multiscrape from firing spurious state-change triggers right after a Home Assistant restart.

🖼️ Restore the icon on startup

When restoring an entity on startup, Multiscrape restored the state and attributes but not the icon rendered by an icon / icon_template. The entity was briefly written with no icon, and the coordinator's first update set it a few seconds later — an attribute-only change that a bare platform: state automation trigger (no to/from) would fire on.

Multiscrape now restores the icon alongside the state, so the first real update no longer produces a phantom change. Entities without an icon template are unaffected. (#605, closes #437)

Thanks to @proscar87 for the fix, and to @parautenbach and @Broekman for the detailed reports.

⬆️ Dependencies & Tooling

• Update pytest-homeassistant-custom-component to v0.13.355 (#600, #595)
• Update ruff to v0.16.2 (#601, #596)
• Update colorlog to v6.12.0 (#597)
• Update actions/setup-python to v7 (#598)
• Update actions/checkout to v7.0.1 (#599)

---

Full Changelog: v9.0.3...v9.0.4