Skip to content

v2.1.0

Choose a tag to compare

@qlerup qlerup released this 10 Dec 22:16
ed32ca7

🚀 Release Notes - v2.1.0

☕ New: Donation / “Buy Me a Coffee” Button

A donation / Buy Me a Coffee button has been added! 🥳

It’s completely optional, but if you enjoy this project and want to support it, a small donation helps me:

  • 🧪 Spend more time debugging and improving stability
  • 🧩 Build even more cards and integrations
  • ✨ Develop lots of new features

The donation button is now also added at the very top of the README for quick access. ⬆️☕

Buy me some debugging time on Ko-fi

Thank you so much for any support – it really means a lot and keeps the motivation high! 💙


💾 New: Data Handling & Backup System - v2.1.0

This release introduces a completely new way of handling data and backups. 🔧

✅ JSON-based storage (no more 16KB limit)

  • All data is now stored in JSON files instead of sensors.
  • This removes the 16KB size limitation that sensors had.
  • You can now store much larger amounts of data without hitting that maximum size error.

📂 Unlimited backups

  • Backups are now stored in separate files, giving you practically unlimited backup capacity. 🎉
  • You’re no longer restricted by sensor size for backup data either.

🔁 Important: Older backups from previous versions will be removed during the update.

🛟 Action required: After updating, please create a new backup as soon as possible, so you always have at least one fresh backup available.

🗑️ Delete backups from the card editor

  • It’s now possible to delete backups directly in the card editor. 🧹
  • This makes it easier to manage old or unneeded backups without leaving the UI.

⚠️ Breaking Change / Important Notice

Because data has been migrated from sensors to JSON files, this update might break existing schedules/schemes. 😬

🧹 Note: As part of this migration, all old sensors used for storing data will be removed during the update. Data is now fully handled via JSON files instead.

This change was necessary to avoid the “maximum 16KB data” error and to make the system more robust and future-proof. However, it does mean:

  • 🧨 Existing configurations may no longer work exactly as before
  • 🔁 You may need to re-check and adjust your current setups after updating
  • 🔄 This update also requires you to update the sync integration to the latest version for everything to work correctly again

✅ Recommended steps after updating

  1. 🔄 Verify that your existing cards/schedules are still working as expected.
  2. 🛟 Create a new backup immediately after confirming everything works.
  3. 📝 If something looks off, review your configuration and adjust where needed.

Thanks for your understanding and for sticking with the project through these bigger changes. Your feedback, bug reports, and support (and coffees ☕) help this project grow! 💛