Sounds like a good time to try out esphome then and might stick with it when it fits
I’m really grateful for Theo bringing us Sonoff-Tasmota (now Tasmota) as it was clearly the beginning to open the whole esp ecosystem. Maybe without him Otto would have never invented esphome!
But for the same reason I choose Home Assistant over any other solution I also choose esphome over any other solution. Afaik there is simply nothing comparable out there which gives so much freedom but at the same time the maximum “output” with the minimum input possible.
And well, it’s not only down to the fact that with esphome you can avoid mqtt completely (which is just 100% win for me because I don’t waste any time here!) but also about the whole architecture.
Tasmota still tries (and somewhat still succeeds) with one (actually last time I looked there were over 100) pre-compiled binaries to “rule them all”. At the same time space is rare since always and so it comes that not all configurations are actually accessible in the menu but hidden in different corners. Some things nneed special commands in the command line or some stuff even needs to manually compiled upfront to get it working.
Actually I think this is also a “weak point” of tasmota. Many users stay on old (or very old) tasmota versions because it “ain’t broken”.
But the saying “never touch a running system” is actually dangerous for connected devices like esp’s.
Every now and then there is still users out there running a ota exploitable tasmota versions like 6 or 7 just because it “works” and they know (had) the pain of updates going south already.
Why is it bad to don’t give users the easiest way updating like we are used from computers or phone (known as ota update)? Because then they will not update and over time start to have vulnerable devices. It’s enough that manufactures often give a about updates but if someone takes control over a device (replacing the stock firmware) it is also the responsible to keep it up2date.
And well, here is esphome superior in probably every aspect and it’s down to a ota “one-click-update” (for all devices at once).
As I have also gained like 2 years experience with tasmota, espeasy, espurna (my favorite before esphome btw.) and more I can say that updates on this systems were often a hit and miss. Sometimes parts of the configuration got lost, some times the update was to big so two updates were needed, some times everything looked fine but the device behaved differently like before - I know all these pains and hours wasted just to get the working state from before! My last device I migrated over from tasmota to esphome were one I didn’t update with intention because I had so much pain with the update before and I was just so fed up wasting so much for a (in theory) simple update.
Since I moved to esphome I just had updates which went wrong and if there was a breaking change (which lies in the nature of actively developed systems) I actually get the information before it updates the esphome node. This year I think I had update which didn’t work because of a breaking change - and guess what, the error message actually just tells you what to do to make the update work, one line in the yaml edited, saved and update flys
I can imagen that on tasmota things would just fail silently, the sensor would stop working, need to do some research in the end a reset of the device and completely new configuration would have been the way… 1 hour wasted just to get what I had before!
I stay with esphome