Hi Ilja,

This is great feedback and something to be constantly aware of as updates are made within Hass.io and Tasmota. I created this video a few weeks ago and at the time of the video I was on 6.3.0 for Tasmota and 0.84.6 for Hass.io. I’ll update my Hass.io and Tasmota and get back to you to see if any changes are required to the post.

In the meantime, looking at your differences:

Topic names: The topic names that have been configured should be visible through either the configurations or you can view them in the console (Tasmota main menu > Console). As the state of the device change, these topics will be updated and you can see any errors or the actual topics posted. These actual names should match your configuration and if your default settings are different, you should align the configuration to this.
The other option is to check the configuration of the topics through Configuration > Configure MQTT. My full topic configuration is ‘%prefix%/%topic%/’ and this might be different for yours to align to the configuration you have suggested.

Retain: If these messages are published with a RETAIN flag, the MQTT switch will receive an instant state update after subscription, and will start with the correct state. Otherwise, the initial state of the switch will be false / off.

Thanks again for your feedback and I’ll update and post again when the updates are finished.

/config/switch.yaml:
– platform: mqtt
name: “MY SONOFF”
command_topic: “tasmota/sonoff_basic/cmnd/POWER1”
state_topic: “tasmota/sonoff_basic/cmnd/POWER1”
qos: 1
payload_on: “ON”
payload_off: “OFF”
payload_available: “Online”
payload_not_available: “Offline”
retain: false

Note, that during Sonoff Basic MQTT configuration you should use the following:
Topic: sonoff_basic
Full Topic: tasmota/%topic%/%prefix%/