Another good video Travis. I like the fact now that you can set a lot of this up inside home assistant. For those of us that aren't intelligent enough to know all of the set options and rules and all that that tasmoda can do it seems like it's so much easier now. Great video.
Thank you for the video. I was stuck at some point with one device running tasmota, and your tip to check console helped. I totally ignored console in this case :/
OMG I didn't know this detach from relay option.. it's a game changer! I can use a long press on the garage light button to open\close the garage door, or open\close shaders in a room using the existing light switch without additional buttons! You rock mate :) Thank you so much
@@digiblurDIY I just tried with no results. I'm using a sonoff mini with an external momentary pushbutton connected to s1 and s2 inputs. Maybe it's because this is known by tasmota as a "switch" instead of a "button"? I think Button1 is the small onboard button. I found that SetOption114 is used to detach switches from relays instead of buttons as with setoption73. Do you think I can simply replace button with switch in rule?
@@digiblurDIY Tried with so114 but detaching switches exposes only a few action to HA (no multiple presses or long press) so I changed the definition of Switch1 to Button2 in tasmota model configuration. This way it exposes to HA both button1 and button2 with multiple actions. Of course I'm using a momentary switch as external switch to the Mini. However it works!!
Travis you Rock great job. I use rules for 20 multiple button switches and this would it much better to see what we have going on with our remote actions.
Thank you for your always precious videos. 80% of my Domotic is based on your tutorials. Coooollll!!! If I have understood correctly, Tasmota integration is kind of a broker for devices with modified Tasmota firmware, but to see these devices/entities in HA you have to put SetOption19 to 0 in Consolle. So, if you only use modified devices, you might no longer use an MQTT broker, right?
No, it still relies on MQTT, I mean after all that is part of the acronym of Tasmota. MQTT is the way and I'd get rid of my home automation software before I get rid of MQTT. The integration is just an automatic way to configure them in HA.
Nice! Thanks again Travis. I'm slowly bringing things online in my spare time, which unfortunately, DRASTICALLY affects WAF points. Things like this will definitely help. I picked up several of the Gosund switches that you demonstrated the multi press actions on a long time ago. What's a good way to store presets (ie, 1 press lamp 1 on 65% brightness, 2 press lamp 2 on 65% brightness, 3 press ceiling fan lights all on 65% brightness, 4 press all lights on 100%)?
Either make an automation like I did to set those devices, or you could have them trigger a scene/script. Or if you are a NodeRed person like I am you could also trigger a NodeRed flow.
Travis, thank you very much for this helpful and explainable video! Perhaps the time has finally come for me to switch all my Tasmota devices (especially Sonoff Basic) to the new integration. However, I am still concerned about what will happen if I set "SetOption19 0" on all my existing Tasmota devices and use the new integration? Won't that mess up all the existing entities? So what would be the correct procedure to migrate from the old method "SetOption19 1" to the new integration? Are there already good instructions? Thanks again!
One of those things I would probably do a test device to see how things react as I know HA likes to make new entities of things and put the 2 after it but you should be able to change the entity name in HA. Transition from Auto Discovery If you have been using SetOption19 for device discovery, setting it to SetOption19 0 will remove your Tasmota device from the MQTT device list and add it to the Tasmota integrations in HA. They will be treated as new entities in Home Assistant but if you previously used default values they will use the same entity_id as the MQTT discovery devices.
@@digiblurDIY Oh, that sounds pretty hassle-free! Then I'll do that sometime soon. And, thanks to your detailed instructions, I'll also try my hand at "rules". I will definitely do that soon. Thanks for your help and your inspiring videos! Have a good time and stay healthy!
Wow-what a bonus. Got my Sonoff basic making magic happen in D house. Just got get MQtt to discover. But this child is cutting up. I will say the button count does not leave much of a fudge factor.
Reviewing this video I was able to discover my MQTT option 19 1. Bingo it showed up in MQTT broker. I recall your help on earlier discord . Thanks a bunch. Just trying to rule1 on button1T#state=10 do power1 toggle endon. shows hold in console on press. Still trying to get the sand out my eyes.
SO19 1 is the old method and shouldn't be used. The HA Tasmota integration is the way going forward. If you want multipress, decouple it with SO73 1 and do make sure to reboot the device and you'll the actions pop up in HA.
Hi digiblurDIY, I have a MJ-SD01 Dimmer (72) running on Tasmota 8.2.0.1 can I upgrade to the newer version on Tasmota and have the same function as the 8.2.0.1? i.e. red light when off blue light when on etc... P.S. Great Videos, I always learn something new. :)
Yes. You can upgrade to the latest fork I have for that dimmer on my github page or you can try the built in module for that device. Look in the configure module screen for PWM Dimmer. Thanks! Always cool to connect with everyone out there.
I've just enabled this in my HA. Works well and discovers new devices well. Is there any reason to try to re-associate my SO 19 devices with the integration? I have 37 Tasmota entities that were added by the old method that do not register with the "new" method. Also, I'm wondering if the integration ones will show up in TasmoAdmin plugin? Thanks for the great vids.
I don't use Tasmoadmin myself due to the issues it caused for me. Tasmobackup is what I use now. If your other devices are working fine there's nothing wrong with leaving them but if you get bored. Switch a few a week.
Not sure if you found a solution, but all you need to do is to issue an SO19 0 then restart the device. If that fails, do an SO19 1 then SO19 0. Also, you need to be on Tasmota 19.2 or later firmware. Don't know either about TasmoAdmin. I use Tasmobackup on my devices and it can see them still.
Nice video ! I need to clarify a question that I ask myself: does Homeassistant automatically detect a new device from any service as soon as it is configured for example in mqtt? I remain convinced that it does but not at home and I think there is a parameter that I miss. Thanks in advance for your help!
Yep! You can check out my MQTT Retains video if you want to learn more when you have time. But for real quick, download MQTT Explorer (google it), connect it to your same MQTT Broker. Now look for a branch named "tasmota", then "discovery" you should see a bunch of MAC IDs for your devices. Shut down MQTT Explorer, restart your MQTT broker, open MQTT Explorer. Do you see those discovery messages still there? If so then your persistence is working.
I do actually have a question based on this video. Now surely the rule within Tasmota is the best way to have the button toggle the switch. But let's say I prefer automation (and this is just for purio knowledge and curiosity), the trigger would be that light.bedroom entity (or device), but how would you trigger the relay within Tasmota from HA, I didn't see an additional entity being created in order to be the able to trigger the realy. In my opinion, when decoupled, 2 entities should become part of the device, the button (switch domain or sensor with the value of "clicks") and the relay (light domain). Thanks :)
When you decouple the buttons from relays it does not make additional entities. It makes additional triggers to kick off automations from. You'd simply make the same automation as I did except make it off single press and toggle its own relay.
Right, the light/switch entity still controls the relay. You are simply decoupling the button on the device and turning them into automation triggers to do your evil bidding.
Nice video, but personally I would prefer epshome, it's way easier laying out the logic in a yaml than remember what setoption xyz do. The end of video -> LOLed.
Thanks for this video, what you say about dns name how to do it? can you do it so that if you want to write a name instead of ip on local net ? i will love learn how,
i've integrated all my tasmota devices into mqtt far from now, and my automations via node red. Is there any advantage of using this new integration besides that wifi data (signal, ssid...) thx!!!! (your family is beautiful!!)
If you already have it working then definitely don't fix it. It's more of one of those things you don't have to do it the old way anymore. And thank you!
Thank you for this great video. Recently i started using the Tasmota integration and did setoption 19 to 0 on all devices, but with some recent HA updates, not all, after the restart of HA most Tasmota devices where offline. Because the Tasmota integration seems to conflict with the MQTT integration and I need that for other devices, I removed the Tasmota integration and setoption 19 back to 1. So I am wondering if anyone else experiences the same issue.
Curious how this would work if your device was set to activate by remote switch. Like my ceiling fan, uses a sonoff mini, but using my normal light switch to activate it, I can’t really do a long press since it’s normal to flip the switch and let it stay there, and turning it back off stops that fan. Or would you now momentarily flip it then back to turn the fan on? Guess I should just try it..
@@digiblurDIY I like using the regular switches, the aftermarket smart switches just don’t look right, they are a little bit thicker and the wall plates are thicker too. But I can make them act like momentary with a quick on and off right?
hey Travis, long time no speak. I'm back again as I'mve decided to jump ship from hubitat to HA. I'm just trying to set a tuya converted smart plug that was configured and working perfectly on hubitat on HA. I can see on the device console that MQT is connected, but Tasmota within HA is not detecting it. Scratching my head here...Do I have to change / upgrade the firmware or something before this can work properly with HA? it's a U3S smart plug model. your input is already much appreciated. Cheers.
Ah, it's coming back to me. ...okay, so I've flash it with minimal bin v11, then when I tried flashing with the tasmota.bin, it says that it doesn't have enough space. I've now managed to install 9.2. Will that suffice or do you recommend me trying to install as latest version possible?
I would love to see a video on how to use the Espcams with esphome and with home assistant and motioneye, as of now if you do you run into the issue with the token for the cam expiring after a few minutes, the solution is to use a long lived token but how the heck do you do that with HA and a esphome device?
@@digiblurDIY I can't post a link in comments but if you search Amazon for espcam you will see them, they are very simple cams powered by the esp32 and cheap. When used with motioneye the automation possibilities are awesome but they have a very short duration without the long lived token
Oh those. I was never impressed with the quality/cost ratio on them so you won't see me recommending them or touching that subject. $40 POE cams with crazy quality and ONVIF/RTSP are hard to beat.
I don’t know if it’s my impatience or imagination, but I’ve had experience in the integration not working if HA discovery is enabled. I’ve found that by making sure discovery is off (SO19 0), tasmotized devices that didn’t previously show up in the integration suddenly do show up.
I followed along and moved my Tasmota switches from Auto-discovered MQTT to native. The multi-press is awesome, but I can't get the Tasmota-controlled single-press toggle to work at all
@@digiblurDIY Yes console seems happy, too. My multi-press automations in HA work fine, so does single toggle. When I defined rule1 like you prescribe in this video, I get a 16:00:34.968 CMD: rule1 on button#state=10 do power1 toogle endon 16:00:34.974 RUL: Stored uncompressed, would compress from 41 to 29 (-29%) 16:00:34.979 MQT: stat/FoyerLight/RESULT = {"Rule1":"ON","Once":"OFF","StopOnError":"OFF","Length":41,"Free":470,"Rules":"on button#state=10 do power1 toogle endon"} 16:01:22.814 MQT: stat/FoyerLight/RESULT = {"Button1":{"Action":"SINGLE"}}
It would be a good idea to have the option in the tasmota integration to be able to choose the type of entity you want to have. Putting this in the device firmware would make it to big perhaps. Thanks for your answers!
Definitely liked the end of the video!
The outros are always fun to make and share!
Another good video Travis. I like the fact now that you can set a lot of this up inside home assistant. For those of us that aren't intelligent enough to know all of the set options and rules and all that that tasmoda can do it seems like it's so much easier now. Great video.
Very true! Breaking down the barriers making it super easy to throw into Home Assistant.
Man that makes doing multiple actions so much easier! I was just trying to figure this out the other day
Glad I could help!
Thank you for the video. I was stuck at some point with one device running tasmota, and your tip to check console helped. I totally ignored console in this case :/
Glad I could help!
Lovely Jubbly, mate! Great content, as always. Loved the outtro...such a beautiful family 😘- God bless you all!
I found that little jewel of a stare with the quick back pedal and knew what had to be done.
OMG I didn't know this detach from relay option.. it's a game changer! I can use a long press on the garage light button to open\close the garage door, or open\close shaders in a room using the existing light switch without additional buttons! You rock mate :) Thank you so much
The detach thing is definitely gold. I use it all over the house with various automations and such. I love the long press and multipress stuff.
@@digiblurDIY I just tried with no results. I'm using a sonoff mini with an external momentary pushbutton connected to s1 and s2 inputs. Maybe it's because this is known by tasmota as a "switch" instead of a "button"? I think Button1 is the small onboard button. I found that SetOption114 is used to detach switches from relays instead of buttons as with setoption73. Do you think I can simply replace button with switch in rule?
Yes. Switches are so114
@@digiblurDIY Tried with so114 but detaching switches exposes only a few action to HA (no multiple presses or long press) so I changed the definition of Switch1 to Button2 in tasmota model configuration. This way it exposes to HA both button1 and button2 with multiple actions. Of course I'm using a momentary switch as external switch to the Mini. However it works!!
8 hours of trail an error, thanks to this video i got it 😂
Travis you Rock great job.
I use rules for 20 multiple button switches and this would it much better to see what we have going on with our remote actions.
Thanks! All down to where you want the automations to live, so many ways to skin a cat here.
So glad you're saying TasmotA properly now! 😛
I have always said it properly 😎
This video is gold!
Many thanks!
Thank you for all your awesome videos btw
Glad you like them!
Great content as always! thanks Travis...
My pleasure!
Great info Travis, thank you.
Thank you for your always precious videos. 80% of my Domotic is based on your tutorials. Coooollll!!! If I have understood correctly, Tasmota integration is kind of a broker for devices with modified Tasmota firmware, but to see these devices/entities in HA you have to put SetOption19 to 0 in Consolle. So, if you only use modified devices, you might no longer use an MQTT broker, right?
No, it still relies on MQTT, I mean after all that is part of the acronym of Tasmota. MQTT is the way and I'd get rid of my home automation software before I get rid of MQTT.
The integration is just an automatic way to configure them in HA.
Informative as always Travis thanks. Question. What is the advantage to changing your switch entity to a light?
Grabs the right icon and ties into the voice assistants correctly. There might be others as well.
Very good job. Thank You.
Nice! Thanks again Travis. I'm slowly bringing things online in my spare time, which unfortunately, DRASTICALLY affects WAF points. Things like this will definitely help. I picked up several of the Gosund switches that you demonstrated the multi press actions on a long time ago. What's a good way to store presets (ie, 1 press lamp 1 on 65% brightness, 2 press lamp 2 on 65% brightness, 3 press ceiling fan lights all on 65% brightness, 4 press all lights on 100%)?
Either make an automation like I did to set those devices, or you could have them trigger a scene/script. Or if you are a NodeRed person like I am you could also trigger a NodeRed flow.
Travis, thank you very much for this helpful and explainable video! Perhaps the time has finally come for me to switch all my Tasmota devices (especially Sonoff Basic) to the new integration. However, I am still concerned about what will happen if I set "SetOption19 0" on all my existing Tasmota devices and use the new integration? Won't that mess up all the existing entities? So what would be the correct procedure to migrate from the old method "SetOption19 1" to the new integration? Are there already good instructions? Thanks again!
One of those things I would probably do a test device to see how things react as I know HA likes to make new entities of things and put the 2 after it but you should be able to change the entity name in HA.
Transition from Auto Discovery
If you have been using SetOption19 for device discovery, setting it to SetOption19 0 will remove your Tasmota device from the MQTT device list and add it to the Tasmota integrations in HA. They will be treated as new entities in Home Assistant but if you previously used default values they will use the same entity_id as the MQTT discovery devices.
@@digiblurDIY Oh, that sounds pretty hassle-free! Then I'll do that sometime soon. And, thanks to your detailed instructions, I'll also try my hand at "rules". I will definitely do that soon. Thanks for your help and your inspiring videos! Have a good time and stay healthy!
Wow-what a bonus. Got my Sonoff basic making magic happen in D house. Just got get MQtt to discover. But this child is cutting up. I will say the button count does not leave much of a fudge factor.
Not sure what that means? Multipress?
@@digiblurDIY Yes, I did not multi-press existed.
Reviewing this video I was able to discover my MQTT option 19 1. Bingo it showed up in MQTT broker. I recall your help on earlier discord . Thanks a bunch.
Just trying to rule1 on button1T#state=10 do power1 toggle endon. shows hold in console on press. Still trying to get the sand out my eyes.
SO19 1 is the old method and shouldn't be used. The HA Tasmota integration is the way going forward. If you want multipress, decouple it with SO73 1 and do make sure to reboot the device and you'll the actions pop up in HA.
very good 100%
Thanks for nice content and quick question what switch are you used in here
Stitch?
Fixed it switch
This one. www.digiblur.com/p/treatlife-smart-switch-ss01s-single-pole.html?m=1
@@digiblurDIY thanks
Hi digiblurDIY, I have a MJ-SD01 Dimmer (72) running on Tasmota 8.2.0.1 can I upgrade to the newer version on Tasmota and have the same function as the 8.2.0.1? i.e. red light when off blue light when on etc... P.S. Great Videos, I always learn something new. :)
Yes. You can upgrade to the latest fork I have for that dimmer on my github page or you can try the built in module for that device. Look in the configure module screen for PWM Dimmer.
Thanks! Always cool to connect with everyone out there.
Thanks!
Welcome!
I've just enabled this in my HA. Works well and discovers new devices well. Is there any reason to try to re-associate my SO 19 devices with the integration? I have 37 Tasmota entities that were added by the old method that do not register with the "new" method. Also, I'm wondering if the integration ones will show up in TasmoAdmin plugin? Thanks for the great vids.
I don't use Tasmoadmin myself due to the issues it caused for me. Tasmobackup is what I use now. If your other devices are working fine there's nothing wrong with leaving them but if you get bored. Switch a few a week.
Not sure if you found a solution, but all you need to do is to issue an SO19 0 then restart the device. If that fails, do an SO19 1 then SO19 0. Also, you need to be on Tasmota 19.2 or later firmware. Don't know either about TasmoAdmin. I use Tasmobackup on my devices and it can see them still.
Nice video ! I need to clarify a question that I ask myself: does Homeassistant automatically detect a new device from any service as soon as it is configured for example in mqtt? I remain convinced that it does but not at home and I think there is a parameter that I miss. Thanks in advance for your help!
The HA Tasmota integration will automatically detect new devices once you add the MQTT settings in Tasmota.
Love you vids ,,, quick question how can you tell if my mosquito.conf is correct? is their a way to test if persistence is working like it should?
Yep! You can check out my MQTT Retains video if you want to learn more when you have time. But for real quick, download MQTT Explorer (google it), connect it to your same MQTT Broker. Now look for a branch named "tasmota", then "discovery" you should see a bunch of MAC IDs for your devices. Shut down MQTT Explorer, restart your MQTT broker, open MQTT Explorer. Do you see those discovery messages still there? If so then your persistence is working.
@@digiblurDIY tyvm brother 👍
so 30 changes it to a light?! I'm always learning new stuff from your videos
Yup! Much easier than creating a template in HA off the switch.
I do actually have a question based on this video. Now surely the rule within Tasmota is the best way to have the button toggle the switch.
But let's say I prefer automation (and this is just for purio knowledge and curiosity), the trigger would be that light.bedroom entity (or device), but how would you trigger the relay within Tasmota from HA, I didn't see an additional entity being created in order to be the able to trigger the realy.
In my opinion, when decoupled, 2 entities should become part of the device, the button (switch domain or sensor with the value of "clicks") and the relay (light domain).
Thanks :)
When you decouple the buttons from relays it does not make additional entities. It makes additional triggers to kick off automations from. You'd simply make the same automation as I did except make it off single press and toggle its own relay.
@@digiblurDIY I see, so that light entity is still directly "attached" to the relay, correct?
Right, the light/switch entity still controls the relay. You are simply decoupling the button on the device and turning them into automation triggers to do your evil bidding.
@@digiblurDIY I see, thanks for clarifying :)
Nice video, but personally I would prefer epshome, it's way easier laying out the logic in a yaml than remember what setoption xyz do. The end of video -> LOLed.
That's the beauty of this. No code and no setoption. And best of all no dependency on HA. I do use Esphome as well though for those oddball sensors.
Thanks for this video, what you say about dns name how to do it? can you do it so that if you want to write a name instead of ip on local net ? i will love learn how,
Yes. You can create a dns record on your local DNS to point to your broker. Easy to do with PiHole.
i've integrated all my tasmota devices into mqtt far from now, and my automations via node red. Is there any advantage of using this new integration besides that wifi data (signal, ssid...)
thx!!!! (your family is beautiful!!)
If you already have it working then definitely don't fix it. It's more of one of those things you don't have to do it the old way anymore. And thank you!
@@digiblurDIY if it aint broken... ;D thanks!!!
Thank you for this great video. Recently i started using the Tasmota integration and did setoption 19 to 0 on all devices, but with some recent HA updates, not all, after the restart of HA most Tasmota devices where offline. Because the Tasmota integration seems to conflict with the MQTT integration and I need that for other devices, I removed the Tasmota integration and setoption 19 back to 1. So I am wondering if anyone else experiences the same issue.
Sounds like some persistence issues with mqtt. What broker are you using?
@@digiblurDIY I am using the MQTT Mosquitto broker on my Synology NAS.
Definitely could be a persistence issue you should definitely test that. I explained how in another comment on this video somewhere
do all the devices need to be on 9.2 or later as stated? I have many sonoffs controlling simple lights that leaving well enough has been my thought
If you want to use the integration, yes.
Curious how this would work if your device was set to activate by remote switch. Like my ceiling fan, uses a sonoff mini, but using my normal light switch to activate it, I can’t really do a long press since it’s normal to flip the switch and let it stay there, and turning it back off stops that fan. Or would you now momentarily flip it then back to turn the fan on? Guess I should just try it..
You can get a momentary switch if you want to do multipress.
@@digiblurDIY I like using the regular switches, the aftermarket smart switches just don’t look right, they are a little bit thicker and the wall plates are thicker too. But I can make them act like momentary with a quick on and off right?
hey Travis, long time no speak. I'm back again as I'mve decided to jump ship from hubitat to HA. I'm just trying to set a tuya converted smart plug that was configured and working perfectly on hubitat on HA. I can see on the device console that MQT is connected, but Tasmota within HA is not detecting it. Scratching my head here...Do I have to change / upgrade the firmware or something before this can work properly with HA? it's a U3S smart plug model. your input is already much appreciated. Cheers.
Add you using Tasmota 9.2 or better with full Tasmota version?
Ah, it's coming back to me. ...okay, so I've flash it with minimal bin v11, then when I tried flashing with the tasmota.bin, it says that it doesn't have enough space. I've now managed to install 9.2. Will that suffice or do you recommend me trying to install as latest version possible?
something is not right now with the plug with ver 9.2. the webui is running ever so slowly. ...too slow for my liking...
Blocked network services such as no ntp will do that or something polling it all the time via http like Tasmoadmin.
I also recommend upgrading to 11.0
I would love to see a video on how to use the Espcams with esphome and with home assistant and motioneye, as of now if you do you run into the issue with the token for the cam expiring after a few minutes, the solution is to use a long lived token but how the heck do you do that with HA and a esphome device?
Espcams? I haven't heard of that brand before.
@@digiblurDIY I can't post a link in comments but if you search Amazon for espcam you will see them, they are very simple cams powered by the esp32 and cheap. When used with motioneye the automation possibilities are awesome but they have a very short duration without the long lived token
Oh those. I was never impressed with the quality/cost ratio on them so you won't see me recommending them or touching that subject. $40 POE cams with crazy quality and ONVIF/RTSP are hard to beat.
I don’t know if it’s my impatience or imagination, but I’ve had experience in the integration not working if HA discovery is enabled. I’ve found that by making sure discovery is off (SO19 0), tasmotized devices that didn’t previously show up in the integration suddenly do show up.
That is correct, if you enable so19 that turns off the integration piece.
I followed along and moved my Tasmota switches from Auto-discovered MQTT to native. The multi-press is awesome, but I can't get the Tasmota-controlled single-press toggle to work at all
Did you enable the rule?
@@digiblurDIY Yes console seems happy, too. My multi-press automations in HA work fine, so does single toggle. When I defined rule1 like you prescribe in this video, I get a
16:00:34.968 CMD: rule1 on button#state=10 do power1 toogle endon
16:00:34.974 RUL: Stored uncompressed, would compress from 41 to 29 (-29%)
16:00:34.979 MQT: stat/FoyerLight/RESULT = {"Rule1":"ON","Once":"OFF","StopOnError":"OFF","Length":41,"Free":470,"Rules":"on button#state=10 do power1 toogle endon"}
16:01:22.814 MQT: stat/FoyerLight/RESULT = {"Button1":{"Action":"SINGLE"}}
16:50:34.394 CMD: rule1 0
16:50:34.403 MQT: stat/FoyerLight/RESULT = {"Rule1":"OFF","Once":"OFF","StopOnError":"OFF","Length":41,"Free":470,"Rules":"on button#state=10 do power1 toogle endon"}
16:50:42.763 CMD: rule1 1
16:50:42.771 MQT: stat/FoyerLight/RESULT = {"Rule1":"ON","Once":"OFF","StopOnError":"OFF","Length":41,"Free":470,"Rules":"on button#state=10 do power1 toogle endon"}
@@digiblurDIY It works now that I substituted a 2 where you have toggle ¯\_(ツ)_/¯
Weird. Never used 2 there myself but it is the same. If it works it works. Don't fix it.
Where did you get the Tasmota shirt 😂
Wife made it for me a while back.
I have a shelly 2.5, 1 output is light and 1 is a fan. How to integrate this?
Unfortunately so30 sets both as light or relay. Sounds like a feature request time.
You could do a template in HA on one.
I made it in yaml for now, until a future adaptation
It would be a good idea to have the option in the tasmota integration to be able to choose the type of entity you want to have. Putting this in the device firmware would make it to big perhaps. Thanks for your answers!
if i turn on the light in home assistant it goes to off within a few seconds, but the actual light stays on
Try to enable So59 to report state changes on any change.
6:41
20:50:28 CMD: so30 1
20:50:28 MQT: stat/diylight/RESULT = {"Command":"Unknown"}
Whats going on ?
Older version of Tasmota maybe?
mom LASER EYES.
I told her I wanted to do like some slo'mo' laser beam animations. Of course I got the same look and thought differently.
@@digiblurDIY lolololol
Im Dutch and i don't even know how to pronounce it, i can say the developers name without any problems tho