My rule of thumb is mostly using esp home for custom sensors and then tasmota for prebuilt/store-bought sensors. but as always there are a million different ways of doing stuff in HA and as long as what you are doing is working for you then there is no issue.
Great comparison. I switched from Tasmota to ESPhome last year. I like the "create a dedicated binary" over the "configure a generic binary", as it allows for smaller binaries. Also ESPhome allows me more flexibility when adding non-standard scripts and functions to run locally. But I recommend Tasmota for beginners who do not often write code.
This is the video I have been waiting for. I have wanted to flash all my Tuya devices for some time but was lost as to what to flash to ESPHome orTasmota. Thanks for clearing this up for me. I am sure I will still have many questions but this is great information and inspiration to get me going. Very much appreciated.
That answered every question i had about those two, and i learned two new things. I do really like mqtt in that whenever i screw up HA, all the mqtt devices still work.
Travis, Your the man. Thank you so much for your videos, especially this one. You answered my last question as to which one to use Tasmota or ESPHome. I finally got around to flashing my first smart plug successfully and am on my way to being totally out of the cloud. I used at least 3 of your videos to make it all happen but now I can say I have been Tasmotized. Now on to flashing the rest of my IOT's
Perfect timing for this video! I recently started using tasmota and was planning to check the differences with esphome. Sounds like I’ll stick to Tasmota for now. Thanks again!
Very interesting. I Will be searching your videos for one that hopefully covers from start to finish how to set up a Tasmota device for use with Home Assistant. NOTE: more and more folks are learning about HA and ESPhome unfortunately most instructions are not written for the uninitiated. My search for instructions for those just beginning to learn HA/ESPhome and now Tasmota is still in progress. (been at it for months) There are many videos out there but there are missing steps and I can understand why. I mean after something is done for so long details tend to be forgotten and even a seasoned user falls into this crack. Thank you for the video and off I go to research your videos for examples I can follow, fingers crossed.
Thanks! Check out one of my recent videos, the extended version, it's pure step by step in depth from start to finish on doing a smart plug with power monitoring and doing automations based on it. ruclips.net/video/Tjg4tioZzbs/видео.html
I use both tasmota and esphome. For light switches, dimmers and plugs I use tasmota. ESPhome is used for my custom projects that requires multiple sensors using i2c. ESPhome works really well on ESP32. Also Tasmota does not support ESP32 yet. I did not know about the MQTT auto discovery. Thanks for the video!
That is something I wanted to mention but was a little early in development but if you look on the latest commits on Tasmota you will see a lot of them with the ESP32 work.
Great comparison--Tasmota fanboi here, but I do have a single ESPHome switch in the HA setup just to stay current. I did NOT know about TDM, so I downloaded it. Great piece of software--thanks for sharing!
I use ESPHome when when I've soldered up some sensors to an ESP8266 or ESP32 device to do some function such as monitoring moisture levels for plants, etc. Here I've got great flexibility for sensors and even code how to interact with the sensors. I've used it on a few projects and it's pretty great.
Yep. Exactly my use case for it on oddball builds. I did have to stop using esp8266 on those sensors due to stability issues introduced in recent versions.
Great comparison and info . Currently I use both . I was struggling for weeks to get a tasmota garage sensor to keep states after reboots . The MQTT retain options were a nightmare for me as a beginner and the sensor was so unstable I almost ditched the project. If you totally understand MQTT you can probably figure it out , but after loading ESPhome on a NodeMCU without any changes my sensors were super stable . Even after reboots I didnt have issues . So pick your weapon wisely . Both are great products .
i use tasmota for lights, and esphome for sensors. main reason is that esphome better refreshes the state of sensors after power failure which happens often where i live
That's pretty much where I'm at with things, switches/lights/plugs get Tasmota since it is quick and easy to deploy. Multisensors and other oddballs get ESPHome where the extra work to deploy it is needed and worth it.
The main reason for the to ditch the MQTT protocol over the ESPHome API was the speed, and it is very notable. You may not see it when you press a button on HA, but lets say you have a PIR or a switch to turn on the lights, the communication goes to the MQTT broker, HA, Node-Red, after that goes back to the HA, MQTT broker and to another wifi node! You can see the delay with MQTT and with the ESPhome API you can not. With MQTT we have the the problem related with the last msg sent from the node that is still on the broker, and problems when you need to delete a node, with the ESPHome API you have no problems, everything works fine.
I have also tested this with a PIR and light bulb in my bathroom. Both separate esp based devices. The automation was done via NodeRed. It was about the same again. One big plus I find using MQTT even with Esphome devices is it removes the dependency of Homeassistant running, upgrades, breaking changes etc.
In my system, I only use homeassistant as a monitoring system. The flow goes like this, Device -> MQTT -> Node-Red -> MQTT -> Device. For some devices, like a remote switch, I use tasmota rules. It flows like this. Device -> MQTT -> Device. HomeAssistant again can work as a monitoring device and node-red can still do automation on the sequence but can not interupt it.
I've been using Tasmota for a while (albeit only on one device in anger at present) and I'd heard of ESPHome recently, so I thought I'd check it out. Every other article I read was largely inconclusive, but made me think ESPHome might be a winner. However, watching your video has convinced me otherwise. I don't have anything fancy, just plugs and bulbs, so I don't need the configurability that ESPHome offers, plus the options for cocking up the config and bricking a device seems just a bit too high a risk. Since there's no real speed difference and I've been happy with Tasmota and MQTT till now, I think I'll be sticking with what I know. So thanks for helping me make up my mind and save me some time, much appreciated 👍
Things have definitely gotten easier even since this video especially with all the fixes on both the Tasmota and HA side for MQTT auto discovery. I'm still rolling the same here with Tasmota for my simple plugs, bulbs, switches and ESPHome for those oddball sensor devices. I do run a little different style of home automations where I use NodeRed a lot and interact with devices via MQTT and skip going through HA.
@@digiblurDIY I've got NodeRED installed, but I've not given it much thought as an automation tool as the automations engine in HA works for me - or at least it has done so far. Maybe in the near future I'll give it a try, and I'll either discover it's no better or I can't live without it. I guess the take away is, if it works for you, then it's the right solution for you. Maybe I should stop over thinking the options!
MQTT is the center of my home automation stuff, HA is more of a states machine for me. NodeRed does the automations. I love it. I learned it first a few years ago. I feel it allows me focus more time on the business rules as I'm not googling commands and YAML syntax. Dragging lines and bubbles.
The fact that ESPHome doesn't require an MQTT broker is why, as a beginner in all things Home Assistant, I chose it over Tasmota. I love that I could just Tuyaconvert it with my generic ESPHome firmware file, then modify it to what I want in the dashboard and then HA just automatically detects it and pops up a notification. I haven't used Tasmota at all, haven't needed to, but now that I'm pretty well initiated into the whole home automation world, I could have a play. I think, for beginners running just HA, ESPHome has the edge over Tasmota purely for ease of integration.
Interesting video, I like Tasmota and like the web front end on it for configuration. One thing, could you explain how I can calibrate a SHT30 plugged into a D1 Mini flashed with Tasmota? (The humidity value is very skewed)
I've been using mostly Tasmota for flashing Sonoff and Shelly devices. Once I learned how to do the first one, the following devices were consistent and fairly easy to do (minus when needed to solder :-( ). Regarding MQTT, I think that has been pretty much transparent once I used the Mosquitto broker integration in HA. From there, it is very simple to configure Tasmota with the broker's details and that's it. For backup, I use Tasmo Backup. I found TasmoAdmin not usable at all, but your mileage might vary. I also wanted to experiment with ESHome, so I've got a Wemo device connected to a water pressure sensor. There was a learning curve for that process, but once done, it is not too bad. HA also improved since this video was made with adding the flashing part built into the integration, which is very slick. That sensor has been rock solid and working like a swiss clock. Thanks for the video!
It made it a little easier but only in some setups. It actually added a step in the case of doing OTA updates. I agree on the Tasmoadmin as Tasmobackup is what I use.
It's getting close to winter in Australia and I'd love to do a heat recovery system in my roof to blow the hot air from the roof back into the house. What is best for a project like this if I want to set up a rule that if the roof is hotter than the house it will turn on but work independently from home assistant if I need it to?
Thanks for this great video. The trick of SetOption13 does help a lot. There are couple of instances ESPHome is faster still. When I'm switching sonoff after some time of inactivity, like we do in most house lights, there is a delay, but if you keep flipping the switch then it is instant fast, not sure if related to device waking up, sleep mode or whatever, but ESPHome is def faster there. Second instance, when I integrate to Home Assistant service, ESPHome perform better than Tasmota + Node Red. Last, when I use for blinking light or beep a buzzer, Tasmota not consistent and have a noticeable delay vs ESPHome that works sharp.
That said, after changing all my devices to ESPHome I start having tons of quick 1-2 seconds disconnect in every device. Tried everything I could find online to fix, but nothing did. So, I started moving back to Tasmota which was always reliable. After switching half of devices, I noted the disconnects improved significantly. Not sure what the problem was, maybe HA handling that many devices on api. Now I'm back to Tasmota with only few ESPHome. If was not the disconnects I would def have stayed with ESPHome.
I had my test HA down and the plug I had connected kept rebooting. I later thought about it and it was due to HA being off. I'm glad I didn't have more attached to it and seeing things power cycle.
A magor difference with Tasmota over ESPhome is the Hue Bridge option, I find for my lights Home assistant Hue Bridge option for Alexa gets the colours mixed up where the native Tasmota doesn't. One thing both can't seem to do in Home Assistant as good as the native firmware of WRGB bulbs is to combining the white colours so when you are on the white section of the colour wheel it produces RGB white and not true white, this is a different slider.
@@Jax2342 Thats interesting I entered in RGBWWTable 255,255,255,255,0 which gave good results then also saw this page which removed the white slider community.home-assistant.io/t/rgbw-lights-with-tasmota-and-mqtt/54916/12 (without the RGBWWTable command google home didn't like any white)
YES!! Home Assistant needs this feature on many levels from ESPHome MQTT devices and Tasmota devices, those pesky auto discovery retained packets should be simple to remove with a simple delete of the device.
If you want to operate switches and relays, i.e. these plug-in sockets, then Tasmota is easy. Even if the sensor is supported. But if you want to make complicated changes in the .bin then ESPhome is more suitable.
I have used ESPEasy and Tasmota. For general switches and basic sensors, I prefer Tasmota. I do prefer ESPEasy on devices with LED's and Displays though. I believe Tasmota still integrates better with Discovery and is easier to setup for the SonOff devices it was designed for.
Please tell me more about the third party tasmota managing softwares that you mentioned. I didn't know such software exists. And they sound really useful. Do any of them let you send commands to the tasmota console without having to go to the individual device's page?
Travis, I have discovery turned off because I hated having devices disappear when I had a power outage. Is there a way to keep devices adopted through MQTT discovery when they aren't available when the system doesn't see them? Thanks.
@@digiblurDIY Yep, they were. Drove me nuts! I switched to yaml definitions and left it alone. I should also note that this behavior is several versions of HA old. I haven't used discovery for about 9 months.
Is it true that ESPhome will soon have a music sync option for RGB bulbs? If not, what's the best firmware for an E27 style RGB bulb? Tasmota or ESPHome and which one will work better with Hassio?
No, Tuya Convert is to exploit the Tuya software off. Once you have Tasmota on it, you'll need to flash your own ESPHome bin to it, then once you have ESPHome on it you'll have to flash Tasmota to it from ESPHome to go back and forth.
I've been wanting to do the comparison in in/out speeds for quite some time as I've been curious since I've never had issues with speed on either project.
I'm new to HA so come from the perspective of what was easy for a newbie to get going. I was trying to configure a 5 led strip of individually addressable RGB leds (WS2812B). I was creating an indicator panel (for who is home and what's the weather etc each state would be represented by a different colour led). Tasmota was fine to control to control the colour of the whole strip but controlling each led didn't seem possible. ESPHome was relatively easy by comparison. So once I got the led strip going I converted my Sonoff TH16's to ESPHome as well. So I'm now an ESPHome fanboy.
You dont mention how hard it is to find the exact setoption-config of a unit on Tasmota where you have to go into console & check each option, like so with any other console-config command, Thats why i replaced Tasmota with ESPHome...Beside that when using autodiscovery the entities made are stuck in Home assistant/MQTT if either the unit breaks or you use it for another purpose & forget to Setoption19 0 before you flash the unit again....Also on ESPHome you just make a switch AND a light-output for the relay & then you can choose in HA which entity serves the purpose best...Tasmota..Setoption bla forgotten & so on :-)
If you have a really crazy setoption device then that's probably where I would switch it to ESPHome, never had to dig into them deeply and check each one myself. And as mentioned before, yes HA needs an option to remove both auto discovered ESPHome MQTT and Tasmota devices.
@@digiblurDIY This little free program takes care of all the crap auto-discovery van make by allowing you to remove non-valid persistent stuff hanging around in MQTT & hence curing the "19 1"-issues :-) mqtt-explorer.com/?fbclid=IwAR0HczPavWHfQeZPv6tOVcIkOk34a-LEU1dfZjAVj1HvvUd6GDBJchVns0s
i did it with a raspberry pi www.digiblur.com/2019/11/tuya-convert-2-flash-tuya-smartlife.html follow this guide you will need a phone or tablet to connect to the wifi spot the pi will create also you will need to be connected thru ethernet to the pi, if it doesnt work the first time use ctrl + c or x dont really remember and try again thats how it worked for me i succesfully updated like 4 plugs
CRIKEY!!! I did this with my Pi 4, on virgin plugs, it never loads the firmware. I get vtrust-recovery, if I hold the button for 5 secs I get vtrust-flash, but can not load any firmware. :(
One advantage I see with MQTT versus API is that with the prior you don't need any single computer at home, and you can control and monitor the system without opening any port on your firewall. The ESPs are only clients on MQTT. Mosquitto may sit anywhere. I am not a friend of RP and even NUCs and the like. I rather rent a virtual server for 5 bucks a month and run mosquitto, nodered, possibly home assitant on there . A pity that Home Assistant does not support containers as well and pretends a separete machine with a separate operating system. I don't have to worry about electricity. For alarm systems I can use a charged through old phone as a hotspot gateway to my virtual server, and somebody cutting electricty before breaking in cannot compromise the alarm system. The phone will continue to maintain connectivity for a couple of hous. No need for a UPS on ethernet switches, the RP, a nuc or anything. A phone is its own UPS. No messing with SD cards. And backups can be totally automised and stepping back is trivial. In particular when you want to control and monitor several distant residences it is easy to integrate them into a single system. Reassuring to always know that you holiday hut is warm enough to not freeze the pipes and well above dewpoint without havining to give it a separate raspberry. In Europe internet also mobile is dirt cheap and coverage is very good. Many people have switched from Pies to NUC, because really noone anylonger use the GPIO pins on the server. I don't want to burn the 60 Dollar Pie short circuiting the wrong pins. An ESP is just a couple of dollars and can talk directly to the remote virtual server through the phone. Burning it hurts much less in terms of money and set-up effort. If you want to connect to weird but at times usefull radio standards, there are hubs for Bluetooth you cann connect to any USB connector without a computer but just power behind it e.g. for bluetooth. RPI to NUC was the first step, NUC to Virtual server in the cloud the next logical step. Your explanation are really enlightning. I like the unpretencious format and openness. For me personally HA is an overkill. I much prefer nodered. I have no need to monitor the powerlevel and location of my phone in my home control software. Flipping switches, getting alarm notification on IR and door sensors is good enough for me.
I run all my stuff on separate containers on my NAS I already have, so it doesn't have much of an in impact to begin with as the machine would already be running.
Hate yaml, but when i need to do something with servos or sensors I will go with ESPHome, Tasmota is too buggy and messy, only suitable for well known devices. But its always better to have an arduino project with wifi and json rest setup as a a template for any new IoT device, always works like a charm.
good informative video, thanks again. Recently notices under template for a power monitoring plug HLWBL CF1, HLWBL SEL assigned to GPIO pins . whats these? Did i miss something?
Awsome video! I got a lot of insight from it! Can I ask you a question as you seem very familiar with IoT and home automation. I am using Home Assistant at home as well and I have a couple of wireless switches running Tasmota. A couple of days ago there was a power outage in the building and after the power returned those switches lost their entire configurations and were in the default Access Point mode where I had to connect to their wireless network in order to connect them to my home network's router. Do you know any way to automatically handle this situation? Thanks and all the best to you!
Yep, covered that once or twice in a live stream. :) That's a feature for during setup in case you mess up something badly you can toggle the power 4-5 times in 10 seconds and it goes back to default configuration. Once I have them in production and how I want them I do a "setoption65 1" without the quotes on the console of each device to turn off that feature.
@@digiblurDIY Oh, wow! Thanks a lot!!! This is awsome!!! I guess I should checkout your other videos for more useful options that I could set! Thanks again and have a great one :))))
I worked for 2 days trying to configure a static IP using ESPHome on a Milfra MA05 because of 2 sensors and a button. I never got it working. ESPHome thinks setting a static IP is a bad "user experience". I had a real bad experience not being able to. They have documented a way to manually set an IP, but it breaks other things so it is useless. I'm tired of Nabu Casa trying to make things super simple for newbs at the expense of taking things away from those that know how. Want an idea for a video? There you go, set a static IP using ESPHome.
@@digiblurDIY I'll search some more. I slowed this video down to see what you did and it's different now. I think maybe recent updates may have broken something. Time will tell. A few weeks ago I used static on a different device, easy peasy.
Using MQTT you don't need to know the IP of the device most times. When you really do, send your present IP address to a known topic on Mosquitto as a retained message. Actually Tasmota does this by default. I have no experience with ESPHome, but MQTT has many advantages over API. not the least that you don't need static ip addresses.
Hi, I don't have a nas or hardware laying around to run HA or mqtt. Is tasmota enough for me? I just want to monitor my power usage using (PZEM 004T) and maybe control 2-4 bulb.
Thank you very much for the amazing information you put out there. Your method of training is great and I've watch most of your videos. I've recently managed to finally integrate a Tasmota device into HA using the Mosquito broker, but not before a lot of struggle. I finally realized the device had to be on the same subnet for it to work. This is not the case for my ESPHome devices. I have a Vlan for my IoT stuff that only lets mDNS, Bonjour, Avahi, etc. through. Is it possible to let my Tasmota devices get discovered in my configuration or does it need a firewall rule letting all traffic between networks? Thanks for your help and keep up the amazing work!
How is the API connecting? It has to get across somehow. You only need to allow MQTT across but honestly home assistant should be blocked as well so stick it with those devices as there is far more risk out of an HA install than a little single core ESP chip.
@@digiblurDIY you are absolutely correct. I suspect it's because the api calls are found through mDNS or something like that. I have my HA setup on a Proxmox VM on my LAN, so now I have to figure out how to bridge that over to a Vlan... Thank you I will keep trying.
@@digiblurDIY I will definitely try just punching a few holes to see if it works. Ultimately I will add a NIC to my Proxmox node and get that VM on my isolated network. Thanks for that. I have a PFSense firewall/router with multiple NICs to route out my networks so it should work quite easily. This is an awesome new world after years of home automation in the cloud with Smatthings. I look forward to your next videos.
@digiblurDIY It was easier than I thought. Enabled Proxmox bridge to be Vlans aware. Created a Vlans on the network that the Proxmox node is on. Assigned that Vlans directly to the VM running HA through the bridge. No extra NIC required. Fixed all my rules, NAT's, and DHCP settings in PFSense and bingo! Now HA sees all thing IoT on various IoT Vlans and they see it, but none of these can get on my LAN and WLAN.
Any one knows how to mount an external drive and use it as a NAS in home assistant? (running on Pi4). Since the computer is always on and mapping a drive don't require a lot of processing power I wonder how this add-on does not exist yet.
Thanks for the videos. I am trying to get into home automation with a purpose of toggling my ISP modem off and on when I loose connectivity to the Internet using a round plug like a Gosund. I believe this needs to be controlled by logic local to the switch since I may need to do the same with my access point. I have never programmed an Arduino or ESP but I do know how to program and figure there are examples out there to connect/disconnect WiFi and to ping a public IP. The question that I have is how do I go from code developed using something like a NodeMCU to flashing a sealed round plug. I am assuming I need a base framework like ESPHome or Tasmota to allow me to continue updating my custom firmware over the air. Any thoughts on what direction I should head? Thanks.
@@digiblurDIY I have seen an esp8266-ping library on line. I am hoping to be able to use it to limit the number of hops since all I need to know is if I can get past my modem to my ISP so a response from any routable IP address would work..
@@digiblurDIY So do you suggest using Tasmota? How do I run custom code with Tasmota? Do I need to download the Tasmota source code and compile it with my code? Thanks for all the help.
Great video. Do you think it is safe to use ESPHome devices on main network? I like the simplicity of using device_name.local to add to HA. And seeing whether or not the device is online/offline in ESPHome dashboard which unfortunately I am unable to do if I separate them into Guest and main wifi.
Found this video after watching your other "extremely informative and easy to follow" video for Tuya Convert and converting my plugs which works great by the way, I was just wondering if it was possible to convert from Tasmota to EspHome?, and if it's even worth it.
Yes, you can use Esphome on devices if you want to go that route. I would highly recommend testing a conversion on a Wemos D1 mini or Nodemcu though in case something messes up. Create your bin with ESPHome, go to the Tasmota console and do a "setoption78 1" to disable the bin file checking. Then go to Firmware Upgrade and upload your bin file.
@@digiblurDIY How do you determine the board type to use in Esphome on sealed smart plugs like these smile.amazon.com/gp/product/B078SRSFD7/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
Hi, great video!. Just a question, do you know any way to us an ESP8266 directly connected to a MQTT broker? I mean, do you have a script to do that? The idea is to use a ESP8266 with some additional sensors connected to a MQTT broker. Do you have something like this? Any advice for that? Thanks!
After seeing how easy it is to manage a Tasmota Device and the MQTT side of things I'm definitely giving it a go. After having 25+ ESPHome flashed devices and constantly struggling with API dropouts clogging up my logbooks for nearly a year I'm happy to try the 'dark side' :D Thanks for the well-informed tutorial! Keep up the good work with TasMOTO
Tasmoto for life YO! :) I don't think I mentioned it in the video, but I also use ESPHome with MQTT too. I do it more to remove the dependency of HA on things.
Ouch. What is MQTT running on? That protocol is pretty solid as it has been tweaked and refined for the last day 20 years. It is the bread and butter center of my home automation. I would give up Homeassistant before I gave up MQTT.
Hey, I had 2 sonoff flashed with esphome, so I recently updated them, after the update, they stopped connecting to homeassistance. even though their led are flashing but no sign of them on my wifi {using Fing App} Please help, I do not want to reinstall them because I have installed the sonoffs inside the cable extension plug and ceiling light.
I watch every one of your videos but I still can't switch from Smartthings to HA. For the 4th time over 2 years I installed a HA update and I am unable to see my HA raspberry pi install. Very frustrating and unreliable, now I have to start over again
Thanks, Travis great comparison...I have currently 103 IoT flashed with Tasmota...I have now gone back and set option for auto-discover and speed... thank you...I have 25 K36 Kuled switches and I need to leave the "module type" at Sonoff Basic (1) for it to work properly..the KULED (0) messes up the switch at the wall...any ideas?
@@digiblurDIY so why after you "setoption19 1" can you no longer connect switch thru google home... it does not work thru google commands...by the way, it is really easy to have the switch go in Lovelace...:)
digiblurDIY sorry not making myself clear. Awesome comparison is up here. I meant as not so experienced one I expected the final phrase “use this over the other” : )
You are such an excellent instructor on some rather complex home automation setups. I sincerely thank you for your excellent videos.
Wow, thanks!
Thanks for this. A video topic long overdue.
Andrew L Hoover agreed
@@hamhumtube me too
Thumbed up as soon as I saw your music intro!
The beat is definitely catchy isn't it! :)
My rule of thumb is mostly using esp home for custom sensors and then tasmota for prebuilt/store-bought sensors. but as always there are a million different ways of doing stuff in HA and as long as what you are doing is working for you then there is no issue.
Great comparison. I switched from Tasmota to ESPhome last year. I like the "create a dedicated binary" over the "configure a generic binary", as it allows for smaller binaries. Also ESPhome allows me more flexibility when adding non-standard scripts and functions to run locally.
But I recommend Tasmota for beginners who do not often write code.
Thanks! Using both myself and probably will stay like that. Not really a switch between each other, just depends on the project.
This is the video I have been waiting for. I have wanted to flash all my Tuya devices for some time but was lost as to what to flash to ESPHome orTasmota. Thanks for clearing this up for me. I am sure I will still have many questions but this is great information and inspiration to get me going. Very much appreciated.
Good deal! Definitely jump into discord if you have questions, there quite a few of us to help and all with different opinions and ways to do things.
That answered every question i had about those two, and i learned two new things. I do really like mqtt in that whenever i screw up HA, all the mqtt devices still work.
Travis, Your the man. Thank you so much for your videos, especially this one. You answered my last question as to which one to use Tasmota or ESPHome. I finally got around to flashing my first smart plug successfully and am on my way to being totally out of the cloud. I used at least 3 of your videos to make it all happen but now I can say I have been Tasmotized. Now on to flashing the rest of my IOT's
Awesome! The more scchhtuff out of the cloud the better!
Perfect timing for this video! I recently started using tasmota and was planning to check the differences with esphome. Sounds like I’ll stick to Tasmota for now.
Thanks again!
Glad it was helpful!
Very interesting. I Will be searching your videos for one that hopefully covers from start to finish how to set up a Tasmota device for use with Home Assistant. NOTE: more and more folks are learning about HA and ESPhome unfortunately most instructions are not written for the uninitiated. My search for instructions for those just beginning to learn HA/ESPhome and now Tasmota is still in progress. (been at it for months) There are many videos out there but there are missing steps and I can understand why. I mean after something is done for so long details tend to be forgotten and even a seasoned user falls into this crack. Thank you for the video and off I go to research your videos for examples I can follow, fingers crossed.
Thanks! Check out one of my recent videos, the extended version, it's pure step by step in depth from start to finish on doing a smart plug with power monitoring and doing automations based on it.
ruclips.net/video/Tjg4tioZzbs/видео.html
I use both tasmota and esphome. For light switches, dimmers and plugs I use tasmota. ESPhome is used for my custom projects that requires multiple sensors using i2c. ESPhome works really well on ESP32. Also Tasmota does not support ESP32 yet. I did not know about the MQTT auto discovery. Thanks for the video!
That is something I wanted to mention but was a little early in development but if you look on the latest commits on Tasmota you will see a lot of them with the ESP32 work.
@@digiblurDIY that is awesome! I will check it out.
Great comparison--Tasmota fanboi here, but I do have a single ESPHome switch in the HA setup just to stay current. I did NOT know about TDM, so I downloaded it. Great piece of software--thanks for sharing!
Great piece of software!
Learned so very much through your videos. Thanks a lot for you work and keep up with it!
Great to hear!
I use ESPHome when when I've soldered up some sensors to an ESP8266 or ESP32 device to do some function such as monitoring moisture levels for plants, etc. Here I've got great flexibility for sensors and even code how to interact with the sensors. I've used it on a few projects and it's pretty great.
Yep. Exactly my use case for it on oddball builds. I did have to stop using esp8266 on those sensors due to stability issues introduced in recent versions.
Travis,
Great, informative video (as usual). Thanks!
P.S., LOL on the "couple of views" on that bulb video. ;-)
Still one of my favorite videos but I'm weird and like comparison data and doing it visual was just icing on the cake.
Great comparison and info . Currently I use both . I was struggling for weeks to get a tasmota garage sensor to keep states after reboots . The MQTT retain options were a nightmare for me as a beginner and the sensor was so unstable I almost ditched the project. If you totally understand MQTT you can probably figure it out , but after loading ESPhome on a NodeMCU without any changes my sensors were super stable . Even after reboots I didnt have issues . So pick your weapon wisely . Both are great products .
MQTT can totally be a love hate relationship indeed!
Great video! For me what I like about esphome is that it reduces complexity if you don't have an MQTT server running anywhere.
i use tasmota for lights, and esphome for sensors. main reason is that esphome better refreshes the state of sensors after power failure which happens often where i live
That's pretty much where I'm at with things, switches/lights/plugs get Tasmota since it is quick and easy to deploy. Multisensors and other oddballs get ESPHome where the extra work to deploy it is needed and worth it.
Sweet Video, great information. I learn something on every video you do. Keep up the good work.
Glad to hear it!
Nice comparison. Thanks!
thats exactly what i needed, THX!
The main reason for the to ditch the MQTT protocol over the ESPHome API was the speed, and it is very notable. You may not see it when you press a button on HA, but lets say you have a PIR or a switch to turn on the lights, the communication goes to the MQTT broker, HA, Node-Red, after that goes back to the HA, MQTT broker and to another wifi node! You can see the delay with MQTT and with the ESPhome API you can not. With MQTT we have the the problem related with the last msg sent from the node that is still on the broker, and problems when you need to delete a node, with the ESPHome API you have no problems, everything works fine.
I have also tested this with a PIR and light bulb in my bathroom. Both separate esp based devices. The automation was done via NodeRed. It was about the same again. One big plus I find using MQTT even with Esphome devices is it removes the dependency of Homeassistant running, upgrades, breaking changes etc.
In my system, I only use homeassistant as a monitoring system. The flow goes like this, Device -> MQTT -> Node-Red -> MQTT -> Device. For some devices, like a remote switch, I use tasmota rules. It flows like this. Device -> MQTT -> Device. HomeAssistant again can work as a monitoring device and node-red can still do automation on the sequence but can not interupt it.
Really informative and well presented!
Thank you!
I've been using Tasmota for a while (albeit only on one device in anger at present) and I'd heard of ESPHome recently, so I thought I'd check it out. Every other article I read was largely inconclusive, but made me think ESPHome might be a winner. However, watching your video has convinced me otherwise. I don't have anything fancy, just plugs and bulbs, so I don't need the configurability that ESPHome offers, plus the options for cocking up the config and bricking a device seems just a bit too high a risk. Since there's no real speed difference and I've been happy with Tasmota and MQTT till now, I think I'll be sticking with what I know. So thanks for helping me make up my mind and save me some time, much appreciated 👍
Things have definitely gotten easier even since this video especially with all the fixes on both the Tasmota and HA side for MQTT auto discovery. I'm still rolling the same here with Tasmota for my simple plugs, bulbs, switches and ESPHome for those oddball sensor devices. I do run a little different style of home automations where I use NodeRed a lot and interact with devices via MQTT and skip going through HA.
@@digiblurDIY I've got NodeRED installed, but I've not given it much thought as an automation tool as the automations engine in HA works for me - or at least it has done so far. Maybe in the near future I'll give it a try, and I'll either discover it's no better or I can't live without it.
I guess the take away is, if it works for you, then it's the right solution for you. Maybe I should stop over thinking the options!
MQTT is the center of my home automation stuff, HA is more of a states machine for me. NodeRed does the automations. I love it. I learned it first a few years ago. I feel it allows me focus more time on the business rules as I'm not googling commands and YAML syntax. Dragging lines and bubbles.
The fact that ESPHome doesn't require an MQTT broker is why, as a beginner in all things Home Assistant, I chose it over Tasmota.
I love that I could just Tuyaconvert it with my generic ESPHome firmware file, then modify it to what I want in the dashboard and then HA just automatically detects it and pops up a notification.
I haven't used Tasmota at all, haven't needed to, but now that I'm pretty well initiated into the whole home automation world, I could have a play.
I think, for beginners running just HA, ESPHome has the edge over Tasmota purely for ease of integration.
For the HASS users with Supervisor it's pretty simple to just hit install on MQTT which is about the the same as installing ESPHome addon.
@@digiblurDIY Installing Mosquitto is easy, it's the stuff that comes after that is less streamlined than ESPHome
Interesting video, I like Tasmota and like the web front end on it for configuration. One thing, could you explain how I can calibrate a SHT30 plugged into a D1 Mini flashed with Tasmota? (The humidity value is very skewed)
I've been using mostly Tasmota for flashing Sonoff and Shelly devices. Once I learned how to do the first one, the following devices were consistent and fairly easy to do (minus when needed to solder :-( ). Regarding MQTT, I think that has been pretty much transparent once I used the Mosquitto broker integration in HA. From there, it is very simple to configure Tasmota with the broker's details and that's it. For backup, I use Tasmo Backup. I found TasmoAdmin not usable at all, but your mileage might vary.
I also wanted to experiment with ESHome, so I've got a Wemo device connected to a water pressure sensor. There was a learning curve for that process, but once done, it is not too bad. HA also improved since this video was made with adding the flashing part built into the integration, which is very slick. That sensor has been rock solid and working like a swiss clock.
Thanks for the video!
It made it a little easier but only in some setups. It actually added a step in the case of doing OTA updates.
I agree on the Tasmoadmin as Tasmobackup is what I use.
I was literally typing which one should I choose into the discord, when the notification came up
Hopefully it gives a bit of extra information to help you choose the right one for the task.
nice !! another great vid mate
Glad you enjoyed
It's getting close to winter in Australia and I'd love to do a heat recovery system in my roof to blow the hot air from the roof back into the house. What is best for a project like this if I want to set up a rule that if the roof is hotter than the house it will turn on but work independently from home assistant if I need it to?
Thanks for this great video. The trick of SetOption13 does help a lot. There are couple of instances ESPHome is faster still. When I'm switching sonoff after some time of inactivity, like we do in most house lights, there is a delay, but if you keep flipping the switch then it is instant fast, not sure if related to device waking up, sleep mode or whatever, but ESPHome is def faster there. Second instance, when I integrate to Home Assistant service, ESPHome perform better than Tasmota + Node Red. Last, when I use for blinking light or beep a buzzer, Tasmota not consistent and have a noticeable delay vs ESPHome that works sharp.
That said, after changing all my devices to ESPHome I start having tons of quick 1-2 seconds disconnect in every device. Tried everything I could find online to fix, but nothing did. So, I started moving back to Tasmota which was always reliable. After switching half of devices, I noted the disconnects improved significantly. Not sure what the problem was, maybe HA handling that many devices on api. Now I'm back to Tasmota with only few ESPHome. If was not the disconnects I would def have stayed with ESPHome.
I had my test HA down and the plug I had connected kept rebooting. I later thought about it and it was due to HA being off. I'm glad I didn't have more attached to it and seeing things power cycle.
A magor difference with Tasmota over ESPhome is the Hue Bridge option, I find for my lights Home assistant Hue Bridge option for Alexa gets the colours mixed up where the native Tasmota doesn't.
One thing both can't seem to do in Home Assistant as good as the native firmware of WRGB bulbs is to combining the white colours so when you are on the white section of the colour wheel it produces RGB white and not true white, this is a different slider.
There is the White Blend Mode in Tasmota. Search for the RGBWWTable command.
@@Jax2342 Thats interesting I entered in RGBWWTable 255,255,255,255,0 which gave good results then also saw this page which removed the white slider community.home-assistant.io/t/rgbw-lights-with-tasmota-and-mqtt/54916/12 (without the RGBWWTable command google home didn't like any white)
I am choosing Esphome for simple reason: I had bad times for removing auto discovered mqtt devices from HA. 😩
YES!! Home Assistant needs this feature on many levels from ESPHome MQTT devices and Tasmota devices, those pesky auto discovery retained packets should be simple to remove with a simple delete of the device.
If you want to operate switches and relays, i.e. these plug-in sockets, then Tasmota is easy. Even if the sensor is supported.
But if you want to make complicated changes in the .bin then ESPhome is more suitable.
Yep. Totally my play with them. But I will say the Esphome esp8266 side has become unstable as of late.
Great vid. Lot of good beginner info...and as someone else from the south I could care less *how* you prononce tasmota!
Thank you! HA! I love it, it is a Tasmoto thing many won't understand.
First Tasmotoe!
Why "Tasmoto" instead of "Tasmota" though? Is this some inside joke I don't get?
All the same to me. It drives people nuts for some reason.
Great video!!
Thanks!
I'm surprised no one ever mentions ESPEasy. It still serves a good purpose.
I've used it a few times but it has been quite a while. Have they made the OTA process easier yet? I remember it being kind of confusing.
I have used ESPEasy and Tasmota. For general switches and basic sensors, I prefer Tasmota. I do prefer ESPEasy on devices with LED's and Displays though.
I believe Tasmota still integrates better with Discovery and is easier to setup for the SonOff devices it was designed for.
Please tell me more about the third party tasmota managing softwares that you mentioned. I didn't know such software exists. And they sound really useful. Do any of them let you send commands to the tasmota console without having to go to the individual device's page?
github.com/danmed/TasmoBackupV1
github.com/jziolkowski/tdm
Travis, I have discovery turned off because I hated having devices disappear when I had a power outage. Is there a way to keep devices adopted through MQTT discovery when they aren't available when the system doesn't see them? Thanks.
They should only go to unavailable due to LWT dropping. Are they disappearing completely?
@@digiblurDIY Yep, they were. Drove me nuts! I switched to yaml definitions and left it alone. I should also note that this behavior is several versions of HA old. I haven't used discovery for about 9 months.
you may need to change your device to static ip address.
That is the beauty of MQTT. No worry about the IP or the various methods it got there.
How you add your tasmota devices in HomeAssistant? Manul configuration or autodiscovery?
I use a combination of both but most of my stuff is manual as I started without manual.
Is it true that ESPhome will soon have a music sync option for RGB bulbs? If not, what's the best firmware for an E27 style RGB bulb? Tasmota or ESPHome and which one will work better with Hassio?
I haven't seen that feature yet. I still use Tasmota for my bulbs, switches, plugs, etc the simple devices.
@@digiblurDIY will I be able to use tuya-convert to go back and forth between Tasmota and ESPhome?
No, Tuya Convert is to exploit the Tuya software off. Once you have Tasmota on it, you'll need to flash your own ESPHome bin to it, then once you have ESPHome on it you'll have to flash Tasmota to it from ESPHome to go back and forth.
@@digiblurDIY Will that require opening the bulb and wiring it or can it be done via code?
All done right through the GUI of each. Be careful though as many devices you can't wire. Test it on a NodeMCU/Wemos D1 mini first.
This puts the speed business to rest.
Cheers man
I've been wanting to do the comparison in in/out speeds for quite some time as I've been curious since I've never had issues with speed on either project.
I can't believe anyone has noticed and bothered to complain about it when it happens that fast.
But nice to see that they are the same.
Thanks for the video, @digiblurDIY. Do you have a video about using different subnets for your iot devices?
No, I haven't done anything on Opnsense/pfSense yet.
Thanks Travis.
I'm new to HA so come from the perspective of what was easy for a newbie to get going. I was trying to configure a 5 led strip of individually addressable RGB leds (WS2812B). I was creating an indicator panel (for who is home and what's the weather etc each state would be represented by a different colour led). Tasmota was fine to control to control the colour of the whole strip but controlling each led didn't seem possible. ESPHome was relatively easy by comparison. So once I got the led strip going I converted my Sonoff TH16's to ESPHome as well. So I'm now an ESPHome fanboy.
You dont mention how hard it is to find the exact setoption-config of a unit on Tasmota where you have to go into console & check each option, like so with any other console-config command, Thats why i replaced Tasmota with ESPHome...Beside that when using autodiscovery the entities made are stuck in Home assistant/MQTT if either the unit breaks or you use it for another purpose & forget to Setoption19 0 before you flash the unit again....Also on ESPHome you just make a switch AND a light-output for the relay & then you can choose in HA which entity serves the purpose best...Tasmota..Setoption bla forgotten & so on :-)
If you have a really crazy setoption device then that's probably where I would switch it to ESPHome, never had to dig into them deeply and check each one myself.
And as mentioned before, yes HA needs an option to remove both auto discovered ESPHome MQTT and Tasmota devices.
@@digiblurDIY This little free program takes care of all the crap auto-discovery van make by allowing you to remove non-valid persistent stuff hanging around in MQTT & hence curing the "19 1"-issues :-)
mqtt-explorer.com/?fbclid=IwAR0HczPavWHfQeZPv6tOVcIkOk34a-LEU1dfZjAVj1HvvUd6GDBJchVns0s
How are you flashing the round plugs? I have been unsuccessful in getting tasmota on them. I'm ready to cut them open! :(
i did it with a raspberry pi www.digiblur.com/2019/11/tuya-convert-2-flash-tuya-smartlife.html follow this guide you will need a phone or tablet to connect to the wifi spot the pi will create also you will need to be connected thru ethernet to the pi, if it doesnt work the first time use ctrl + c or x dont really remember and try again thats how it worked for me i succesfully updated like 4 plugs
Use Tuya Convert ruclips.net/video/dt5-iZc4_qU/видео.html
@@digiblurDIY THANKS! I have tried that in the past, maybe before the new upgrades. I'll give it a shot again!
CRIKEY!!! I did this with my Pi 4, on virgin plugs, it never loads the firmware. I get vtrust-recovery, if I hold the button for 5 secs I get vtrust-flash, but can not load any firmware. :(
One advantage I see with MQTT versus API is that with the prior you don't need any single computer at home, and you can control and monitor the system without opening any port on your firewall. The ESPs are only clients on MQTT. Mosquitto may sit anywhere. I am not a friend of RP and even NUCs and the like. I rather rent a virtual server for 5 bucks a month and run mosquitto, nodered, possibly home assitant on there . A pity that Home Assistant does not support containers as well and pretends a separete machine with a separate operating system. I don't have to worry about electricity. For alarm systems I can use a charged through old phone as a hotspot gateway to my virtual server, and somebody cutting electricty before breaking in cannot compromise the alarm system. The phone will continue to maintain connectivity for a couple of hous. No need for a UPS on ethernet switches, the RP, a nuc or anything. A phone is its own UPS. No messing with SD cards. And backups can be totally automised and stepping back is trivial. In particular when you want to control and monitor several distant residences it is easy to integrate them into a single system. Reassuring to always know that you holiday hut is warm enough to not freeze the pipes and well above dewpoint without havining to give it a separate raspberry. In Europe internet also mobile is dirt cheap and coverage is very good. Many people have switched from Pies to NUC, because really noone anylonger use the GPIO pins on the server. I don't want to burn the 60 Dollar Pie short circuiting the wrong pins. An ESP is just a couple of dollars and can talk directly to the remote virtual server through the phone. Burning it hurts much less in terms of money and set-up effort. If you want to connect to weird but at times usefull radio standards, there are hubs for Bluetooth you cann connect to any USB connector without a computer but just power behind it e.g. for bluetooth. RPI to NUC was the first step, NUC to Virtual server in the cloud the next logical step. Your explanation are really enlightning. I like the unpretencious format and openness. For me personally HA is an overkill. I much prefer nodered. I have no need to monitor the powerlevel and location of my phone in my home control software. Flipping switches, getting alarm notification on IR and door sensors is good enough for me.
I run all my stuff on separate containers on my NAS I already have, so it doesn't have much of an in impact to begin with as the machine would already be running.
@@digiblurDIY im a much more casual user. It's at least a possibility to get started without spending. I was really impressed by your setuo
Hate yaml, but when i need to do something with servos or sensors I will go with ESPHome, Tasmota is too buggy and messy, only suitable for well known devices. But its always better to have an arduino project with wifi and json rest setup as a a template for any new IoT device, always works like a charm.
good informative video, thanks again. Recently notices under template for a power monitoring plug HLWBL CF1, HLWBL SEL assigned to GPIO pins . whats these? Did i miss something?
Those are the pins for the power monitoring chip assigned.
Awsome video! I got a lot of insight from it! Can I ask you a question as you seem very familiar with IoT and home automation. I am using Home Assistant at home as well and I have a couple of wireless switches running Tasmota. A couple of days ago there was a power outage in the building and after the power returned those switches lost their entire configurations and were in the default Access Point mode where I had to connect to their wireless network in order to connect them to my home network's router. Do you know any way to automatically handle this situation? Thanks and all the best to you!
Yep, covered that once or twice in a live stream. :) That's a feature for during setup in case you mess up something badly you can toggle the power 4-5 times in 10 seconds and it goes back to default configuration. Once I have them in production and how I want them I do a "setoption65 1" without the quotes on the console of each device to turn off that feature.
@@digiblurDIY Oh, wow! Thanks a lot!!! This is awsome!!! I guess I should checkout your other videos for more useful options that I could set! Thanks again and have a great one :))))
I worked for 2 days trying to configure a static IP using ESPHome on a Milfra MA05 because of 2 sensors and a button. I never got it working. ESPHome thinks setting a static IP is a bad "user experience". I had a real bad experience not being able to. They have documented a way to manually set an IP, but it breaks other things so it is useless.
I'm tired of Nabu Casa trying to make things super simple for newbs at the expense of taking things away from those that know how.
Want an idea for a video? There you go, set a static IP using ESPHome.
I want to say I have covered statics and I have it in many of my examples since I use it a lot with statics
@@digiblurDIY I'll search some more. I slowed this video down to see what you did and it's different now. I think maybe recent updates may have broken something. Time will tell. A few weeks ago I used static on a different device, easy peasy.
@@BowWowPewPewCQ Good alternative is instead setting a static DHCP lease on your router.
Wouldn't it be better to use the router to set a static IP?
Using MQTT you don't need to know the IP of the device most times. When you really do, send your present IP address to a known topic on Mosquitto as a retained message. Actually Tasmota does this by default. I have no experience with ESPHome, but MQTT has many advantages over API. not the least that you don't need static ip addresses.
Hi, I don't have a nas or hardware laying around to run HA or mqtt. Is tasmota enough for me? I just want to monitor my power usage using (PZEM 004T) and maybe control 2-4 bulb.
You would need to store this power monitoring data somewhere though? Or just look at it temporarily?
No I don't want to store any data, I just want to look/know how much energy I was using Monthly
Thank you very much for the amazing information you put out there. Your method of training is great and I've watch most of your videos. I've recently managed to finally integrate a Tasmota device into HA using the Mosquito broker, but not before a lot of struggle. I finally realized the device had to be on the same subnet for it to work. This is not the case for my ESPHome devices. I have a Vlan for my IoT stuff that only lets mDNS, Bonjour, Avahi, etc. through. Is it possible to let my Tasmota devices get discovered in my configuration or does it need a firewall rule letting all traffic between networks? Thanks for your help and keep up the amazing work!
How is the API connecting? It has to get across somehow. You only need to allow MQTT across but honestly home assistant should be blocked as well so stick it with those devices as there is far more risk out of an HA install than a little single core ESP chip.
@@digiblurDIY you are absolutely correct. I suspect it's because the api calls are found through mDNS or something like that. I have my HA setup on a Proxmox VM on my LAN, so now I have to figure out how to bridge that over to a Vlan... Thank you I will keep trying.
Looks like it is using TCP port 6053 so I would say you have a hole for that to work. esphome.io/components/api.html
@@digiblurDIY I will definitely try just punching a few holes to see if it works. Ultimately I will add a NIC to my Proxmox node and get that VM on my isolated network. Thanks for that. I have a PFSense firewall/router with multiple NICs to route out my networks so it should work quite easily. This is an awesome new world after years of home automation in the cloud with Smatthings. I look forward to your next videos.
@digiblurDIY It was easier than I thought. Enabled Proxmox bridge to be Vlans aware. Created a Vlans on the network that the Proxmox node is on. Assigned that Vlans directly to the VM running HA through the bridge. No extra NIC required. Fixed all my rules, NAT's, and DHCP settings in PFSense and bingo! Now HA sees all thing IoT on various IoT Vlans and they see it, but none of these can get on my LAN and WLAN.
Any one knows how to mount an external drive and use it as a NAS in home assistant? (running on Pi4). Since the computer is always on and mapping a drive don't require a lot of processing power I wonder how this add-on does not exist yet.
Thanks for the videos. I am trying to get into home automation with a purpose of toggling my ISP modem off and on when I loose connectivity to the Internet using a round plug like a Gosund. I believe this needs to be controlled by logic local to the switch since I may need to do the same with my access point. I have never programmed an Arduino or ESP but I do know how to program and figure there are examples out there to connect/disconnect WiFi and to ping a public IP. The question that I have is how do I go from code developed using something like a NodeMCU to flashing a sealed round plug. I am assuming I need a base framework like ESPHome or Tasmota to allow me to continue updating my custom firmware over the air. Any thoughts on what direction I should head? Thanks.
I know in Tasmota there is a ping command now that you could do a type of rule like this. I've seen a couple threads about it on their github.
@@digiblurDIY I have seen an esp8266-ping library on line. I am hoping to be able to use it to limit the number of hops since all I need to know is if I can get past my modem to my ISP so a response from any routable IP address would work..
github.com/arendst/Tasmota/pull/8119
@@digiblurDIY So do you suggest using Tasmota? How do I run custom code with Tasmota? Do I need to download the Tasmota source code and compile it with my code? Thanks for all the help.
Great video. Do you think it is safe to use ESPHome devices on main network? I like the simplicity of using device_name.local to add to HA. And seeing whether or not the device is online/offline in ESPHome dashboard which unfortunately I am unable to do if I separate them into Guest and main wifi.
They are open source for the most part so you'll probably be fine but I like to keep things separate myself.
Found this video after watching your other "extremely informative and easy to follow" video for Tuya Convert and converting my plugs which works great by the way, I was just wondering if it was possible to convert from Tasmota to EspHome?, and if it's even worth it.
Yes, you can use Esphome on devices if you want to go that route. I would highly recommend testing a conversion on a Wemos D1 mini or Nodemcu though in case something messes up. Create your bin with ESPHome, go to the Tasmota console and do a "setoption78 1" to disable the bin file checking. Then go to Firmware Upgrade and upload your bin file.
@@digiblurDIY grest, thanks
@@digiblurDIY How do you determine the board type to use in Esphome on sealed smart plugs like these smile.amazon.com/gp/product/B078SRSFD7/ref=ppx_yo_dt_b_search_asin_title?ie=UTF8&psc=1
Hi, great video!. Just a question, do you know any way to us an ESP8266 directly connected to a MQTT broker? I mean, do you have a script to do that? The idea is to use a ESP8266 with some additional sensors connected to a MQTT broker.
Do you have something like this? Any advice for that? Thanks!
On Tasmota it will be attached to the broker itself. On Esphome you can do the same if you enable MQTT.
20 seconds in and "*uck yeah bring on a proper Tasmota V ESPHome breakdown"
After seeing how easy it is to manage a Tasmota Device and the MQTT side of things I'm definitely giving it a go. After having 25+ ESPHome flashed devices and constantly struggling with API dropouts clogging up my logbooks for nearly a year I'm happy to try the 'dark side' :D Thanks for the well-informed tutorial! Keep up the good work with TasMOTO
Tasmoto for life YO! :) I don't think I mentioned it in the video, but I also use ESPHome with MQTT too. I do it more to remove the dependency of HA on things.
@@digiblurDIY good point, did you ever have hassles with API disconnects too? Thinking I'll try mqtt through esphome first
Yes. I had a few disconnects at times especially with an older custom component in one sensor. Mqtt worked fine though.
Interesting. For me, the ESPHome API has been rock solid, while MQTT has constantly caused issues.
Ouch. What is MQTT running on? That protocol is pretty solid as it has been tweaked and refined for the last day 20 years. It is the bread and butter center of my home automation. I would give up Homeassistant before I gave up MQTT.
Hey, I had 2 sonoff flashed with esphome, so I recently updated them, after the update, they stopped connecting to homeassistance. even though their led are flashing but no sign of them on my wifi {using Fing App}
Please help, I do not want to reinstall them because I have installed the sonoffs inside the cable extension plug and ceiling light.
Did you have the access point mode feature on them?
@@digiblurDIY no haven’t , after reading and searching the web, I guess I have to do it for next time :( ... thanks for responding
@@digiblurDIY no I haven’t , I guess I’ll have to do it the future
I watch every one of your videos but I still can't switch from Smartthings to HA. For the 4th time over 2 years I installed a HA update and I am unable to see my HA raspberry pi install. Very frustrating and unreliable, now I have to start over again
try hubitat instead
Next video, start calling it Tasmotie
Too close to a trademark, I don't need the YT bots to get me.
Thanks, Travis great comparison...I have currently 103 IoT flashed with Tasmota...I have now gone back and set option for auto-discover and speed... thank you...I have 25 K36 Kuled switches and I need to leave the "module type" at Sonoff Basic (1) for it to work properly..the KULED (0) messes up the switch at the wall...any ideas?
Module 0 is what is defined in the configure template screen. Sounds like a bad template in there.
@@digiblurDIY so why after you "setoption19 1" can you no longer connect switch thru google home... it does not work thru google commands...by the way, it is really easy to have the switch go in Lovelace...:)
Not to worry Travis...I figured out my problem...:)
Thanks nice one. Though if you put “vs.” in the header you should openly says which one :)
I said which is which?
digiblurDIY sorry not making myself clear. Awesome comparison is up here. I meant as not so experienced one I expected the final phrase “use this over the other” : )
Tasmotooooooo
Right on! You got it!
TasmotA not tasmotO
That's how I spelled it.
@@digiblurDIY But it's not how you constantly pronounce it. It's a small thing, but annoying....
All sounds the same to me with my accent.
this tasmota is so custom and loved that it grew hair and went to sex change. We are nobody to judge that, are we? :D
Gender is not binary.
I love your vids, but can you please stop saying TasmotO? 🤣
I think it's spelled Tasmota right? :)
@Jan Lenz got it. Tasmota
Thank you! It was bugging the hell out of me too! It's like telling everyone you just bought a new Toyoto.
So is PCBWay Chinese then if it is I for one will not be using it
Right on!
continue with tosmata
Or Tasmoto? Not sure which.
@@digiblurDIY hello Moto
Exactly where it is from.
TasmotOOOOOOO? Have a little respect for the project and call it by its actual name please.
I was saying Tasmota...didn't you hear it?
TL;DR: Tasmota (left) is noticeably slower than ESPHome (right). Both are fast enough anyway.
Lol. OK
No. With setoption13 1 they're the same speed.