⚠️ This release contains some important changes! ⚠️
🎉 I'm super excited about this new release! It's containing some changes that are not breaking but do make Multiscrape work slightly different than before. 🚀 Read on!
⚡ Performance Boosts!
This release brings huge improvements to startup performance. While it’s a big leap forward, you might not feel the impact as much because of the great improvements in Home Assistant over the past few months. But trust me, it’s fast! ⚡
On my production system:
🔄 Restoring Previous Values
Both sensor states and attribute values are now restored after a reboot, meaning you’ll be right back where you left off! No more waiting for new scrapes to kick in to get your data back after restarting. 🔄 (It is also restored when you set 'last' in 'on-error')
⏸️ No More Scrapes with scan_interval: 0
Here’s a subtle but important change: if you set scan_interval to 0, Multiscrape will no longer scrape on startup. Previously, it would still initiate a scrape on startup, but now it stays idle just like you’d expect. 🛑
As always, thanks for using Multiscrape! Let me know how it’s working for you. Happy scraping! 🕷️💻
Other notes
- I want to dedicate this one to @Madelena as she (unknowingly) was one of the main triggers for this release. Seeing Multiscrape pop up here was painful 😅: Release party 2024.4
- Happy with Multiscrape? Consider to buy me a coffee or sponsor me on Github!
- Check out my other custom integration: MeasureIt!
Changes
- Fix scrape on startup when interval = 0 @danieldotnl (#425)
- Update dependency ruff to v0.6.7 @renovate (#424)
- Update dependency pytest-homeassistant-custom-component to v0.13.163 @renovate (#423)
- Restore entity's last state on startup @danieldotnl (#417)
- Update dependency ruff to v0.6.5 @renovate (#422)
- Update dependency ruff to v0.6.4 @renovate (#419)
- Update dependency pytest-homeassistant-custom-component to v0.13.162 @renovate (#420)
- Update dependency pytest-homeassistant-custom-component to v0.13.161 @renovate (#415)