I was driven by frustration to replace my Z-Wave plugs with something reliable and easy to manage. In the end my solution with ESPHome plugs were cheaper, easier to manage, and more reliable. Now every smart plug on my network can be controlled reliably. The best part is that they actually work. That is all I ever wanted.
This is simple use what works for you. Both have advantages and disadvantages along with the fact both are evolving.
Esp for streamlined but it fails in the setup area rather badly with the setup since a newcomer is going to lose their mind trying to configure yaml.
Tas one size fits most things isnāt always the way to go.
The great thing is we have options and with the push to improve both things are only going to get better.
Just thinkingā¦ perhaps we would come reasonably close to āperfectionā if esphome would have similar approach as HA, where you can configure cards via UI (newcomer), but you can also do it (or improve) directly by typing a code (advanced user).
But, as i said: just (crazy) thinkingā¦ since massive amount of work would be needed on UI part of ESPHome addon.
Is there a guide anywhere describing how to convert tasmota templates into esphome code?
The guide i found on the esphome website seems to only describe the esphome to tasmota firmware upload process.
To meā¦tasmota is jibberishā¦
Pretty sue it is not convertable
Donāt think so. But you find ready made yamls for various devices under this link
All you need from Tasmota are the GPIO used and what they do. Then create a new device in ESPHome.
Thanks for the replies. Iāve managed to convert most of my devices now. A few power monitor plugs and bulbs are remaining.