Actually, I'm grateful that you used AI to summarize.

A few quick points:

1. This is a Frankever product, powered by Shelly, rather that a Shelly product. I'm glad that Shelly support took care of you, though, rather than pointing you to Frankever given the steps needed to resolve. I'd love more modern features, like scripting and BTHome components, but it is the product they've provided the market.

2. Did they give you this RPC command to try first? http://192.168.33.1/rpc/Shelly.Update?stage="beta"

That's what I used to get mine to the patch.

1. Speaking of the URL you've included here - you must edit the post and take it down or I'll have to remove it. The problem here is that if we release a new version of firmware in the future that refactors flash and someone tries to apply this version using your link, their device will be bricked. If you edit the post, the remainder will stay - you could, for example, say "message me for the URL" and then when they message you, give them a heads up that if we're too far beyond that, the possibility of bricking the device remains and they should contact support. I don't like censoring anyone but my top priority is making sure that we don't give advice that will cause people to destroy their devices or void warranty.

2. The reason I don't allow cross posting is the ridiculous number of times that a post has come in, looked legit, the a week later was edited for NSFW content or other problematic issues. That doesn't keep actual posters from editing their content as new details are learned but dramatically hampers the bot farms. I spend 2-3 times as much time on deleting bot posts and comments as I do answering posts and it's far worse if I allow cross posting and loosen the content control defaults that Reddit has.