I recently encountered a peculiar issue with my Shelly Motion sensor, and I wanted to share my experience in case it resonates with anyone else or if someone has additional insights.
After updating to firmware version v1.1.3-rc12, I noticed that the device was not responding as expected. Attempts to update to the newer v1.1.3-rc16 firmware consistently failed, and the device reverted to the older version. I tried various troubleshooting steps, including isolating the device on a separate Wi-Fi network, manually downloading firmware archives, and even hosting the firmware file on a local web server. Despite these efforts, the issue persisted, leaving me a bit puzzled.
After some research and reaching out to the community, I discovered that others had encountered similar issues. It seems that certain firmware versions can be particularly stubborn, especially when dealing with beta or release candidate builds. One helpful tip I came across was to ensure that the device is fully powered off before attempting any firmware changes. This involved unplugging the device and waiting a few minutes before reconnecting it. Surprisingly, this simple step seemed to resolve the issue for some users.
I decided to give it a try and was relieved to see that the update process finally completed successfully. It was a bit of a learning curve, but it taught me the importance of patience and thorough troubleshooting when dealing with firmware updates. If anyone else is facing similar challenges, I’d recommend trying a full power cycle before exploring more complex solutions.
Thank you to the community for your collective wisdom and support! 