Help controlling RGBW bulbs flashed with Tasmota firmware?

[ee21]

I'm looking to embark on a project where I will be flashing some Tuya-flavored RGBW bulbs, using Tasmota firmware, so that they can be locally controlled.

I've done some research and it sounds like MQTT is the method of controlling them following the flash, but am a little green when it comes to MQTT, and have never used the "homeassistant" auto discover feature baked into the mctMQTT HS4 plugin.

This is the guide I will be following for the most part, which talks about a "template" for use and some specific MQTT configurations, but unfortunately which seems to maybe be specific to the actual Home Assistant platform. I did some additional research and found older mcsMQTT thread postings that seem to indicate this plugin will work very much the same way on HS4, but am a little lost as far as how exactly to integrate the new bulb with mcsMQTT on HS4.

Do I start by using something like MQTT Explorer to discover the available topics, and then try and set this up from scratch, or is there a way to get the plugin to try and do this automatically somehow?

I don't actually have a flashed bulb in my hands yet to play with, which is part of my problem. I would like to be somewhat confident it might actually work before I do, so was hoping someone could nudge me in the right direction, where I might go after I do actually have a flashed bulb, that would be much appreciated.

https://danielbkr.net/flashing-bulbs-ota/

[Michael McSharry]

The first thing to be aware is that TuyaConvert is a security exploit of the Tuya firmware. Latest version of Tuya devices often have newer firmware for which this exploit will not work. There is no way to know until you try it.

When you do have Tasmota installed to replace Tuya the first step is to get Tasmota onto your WiFi network. Tasmota will setup a WiFi AP with SSID that has some variant of Tasmota or Sonoff as part of its SSID. Conntect to this SSID and use browser to go to 192.168.4.1. A Tasmota page will appear and you will then go to the Configuration button, WiFi button and enter the SSID and password of your normal WiFi network. Reboot Tasmota. It will now be connected to your WiFi network and will have assigned an IP address. Use your router or other tool to get the IP and then use it in a browser just like you did 192.168.4.1 before.

I believe a fresh install of Tasmota will think it is a Sonoff Basic single channel relay with button. You will want to change this to be whatever device you actually have. This is done form the Configuration Button / Configure Module button or will be done by using a template if your device is not a standard Tasmota-recognzied device. Since you are just starting out I suggest skipping this step until after you have done the absolute minimum to get the device into Homeseer.

Next is to setup your MQTT. This is Configuration Button / Configure MQTT. For Host enter the IP of your Homeseer computer. Again there are other settings that you will want to change later, but now only doing the minimum to get into HS.

Assume you have installed mcsMQTT plugin in HS and it has been enabled via HS Plugins. Cycle power on the Tasmota device. It will send startup information via MQTT and mcsMQTT will be listening. Go to the mcsMQTT MQTT page, Association tab. You will see a table with the info sent by Tasmota. Any of these pieces of information can be reflected in a HS device by clicking on the "A" column checkbox.

Once you have gotten to this point you have completed you proof of concept to know you can integrate Tasmota with HS via MQTT. You will now go back an configure you Tasmota device to what is really is vs. Sonoff Basic and setup other things in the Tasmota configuration. I can explain further, but this should give you what you need to gain confidence that you will be able to do what you want.

[ee21]

Wow thank you, very detailed response. My main concern was how to get the bulb and mcsMQTT talking, which I didn't realize the bulb had it's own configuration page accessible via IP address.

In the past I have integrated other MQTT brokers, which you have to sort of set the plugin to go out and ask those other brokers for information. I've never experienced setting up a device that would reach out itself to "inform" the broker so to speak.

Thank you.