Well… why learning another programming language (shelly scripting) if i already know esphome’s yaml?
Some examples why i change fw: shelly 2.5 with esphome allows current based cover operating, which means that shelly monitors cover motors and turns them off if something goes wrong (burned motor, jammed cover…i set max current in fw after measuring it). Also end positions are monitored with current measuring, so the moment when motor turns off (hits endswitch) shelly’s relay also turns off, so it”s not just time-based. Honestly i didn’t explore if original fw can do that, but i kinda doubt…
Some of my shelly’s are also btproxy’s.
I have shelly’s led programmed so that i can see if it’s connected to wifi and/or HA (or nothing of two) from the way it’s flashing.
Holding switch for more than 2s restarts shelly, so i don’t have to disconnect power if i need to reboot it.
With 2-relay module built-in button works this way: single push=relay1, double push=relay2.
And so on…
yes, if you don’t need all these extra functions original fw is quite ok. But i love to “tinker” and add my 5 cents to all my things. And i’m too old to remember gazillion different programming languages…
But, i also do my own things “from scratch” with esp modules. I just like shelly’s because they are very small and quite powerfull. My start was with sonoff’s, but they are pretty clumsy comparing with shelly’s…