I recently encountered an interesting challenge with my Shelly devices, which I thought might be worth sharing with the community. For those of you who are also using Shelly products, you might relate to this situation: managing firmware updates across multiple devices can become quite a task, especially when dealing with beta and released versions separately.
As a user with around 50 Shelly devices in my home, I found myself in a bit of a predicament. The binary_sensor entity provided by the Shelly integration does an excellent job of alerting me when an update is available. However, it doesn’t differentiate between beta and released updates, which can be a bit overwhelming. Imagine receiving notifications for beta updates that I wasn’t necessarily ready to install yet! This led me to wonder if there could be a way to have separate entities for beta and released updates, making the process more streamlined and user-friendly.
Another feature I would love to see is an entity that displays the currently installed firmware version. This would not only provide clarity but also make it easier to track updates across all devices. I can only imagine how much time this could save, especially for someone managing a large number of devices like myself.
In my journey to optimize this process, I’ve considered a few strategies. For instance, setting up a dedicated admin-only page where I can oversee all available updates and initiate them directly from there. This would consolidate the update management process and reduce the time spent navigating through individual device settings.
I’m curious to hear from other users who might have faced similar challenges or have innovative solutions to share. Have you found a way to efficiently manage firmware updates across multiple Shelly devices? Any insights or tips would be greatly appreciated!
Let’s continue to explore and share our experiences to make the most out of our Shelly devices and enhance our smart home setups.