BlitzWolf 400ml Aroma Diffuser (BW-FUN3)
BlitzWolf 400ml

Available from:

Install method:

GPIO #Component
GPIO00 None
GPIO01 Tuya Tx
GPIO02 None
GPIO03 Tuya Rx
GPIO04 None
GPIO05 None
GPIO09 None
GPIO10 None
GPIO12 None
GPIO13 None
GPIO14 None
GPIO15 None
GPIO16 None
GPIO17 None
WARNING: New Tuya devices have replaced their Wi-Fi module with one incompatible with Tasmota!!!
Tuya-Convert might not be possible for this device since the template was added (2021-04-25).


  • dpId 1 Diffuser on/off
  • dpId 2 Strength min/max
  • dpId 3 Count hours (0 = continuous 1 = 1 hour 2 = two hours 3 = three hours)
  • dpId 5 LED on/off
  • dpId 6 LED mode (rgb_cycle/color)
  • dpId 8 For color LED, require 14 char value in hex


After applying the template and configuring Wi-Fi and MQTT issue

Backlog TuyaMCU 11,1; TuyaMCU 12,5; TuyaMCU 21,7; TuyaMCU 24,8; TuyaMCU 61,2; TuyaMCU 62,6

After a restart issue the rest of configurations:

Backlog TuyaRGB 3; DimmerRange 1,255; TuyaEnumList 1,1; TuyaEnumList 2,1; Rule0 1

Label webUI buttons and set friendly names for power outputs:

Backlog WebButton1 Diffuser; WebButton2 Light; FriendlyName1 Diffuser Fan; FriendlyName2 Diffuser Light 

Rules used to prevent the device going into countdown mode (f.e. using on device controls) and complete MCU status update on restart. Second rule turns on RGB cycle mode instead of using Tasmota light schemes which don’t work with this device.

Rule1 on tuyareceived#dptype4id3!=0 do tuyasend4 3,0 endon on scheme#data!=0 do backlog0 scheme 0; tuyaenum2 0 endon

What you get

  • Power1 turns the diffuser on or off in stored mist strength mode as device power status
  • Power2 controls the light as an RGB Light.
  • TuyaEnum1 is for mist strength status and control: 0 for low / 1 for high
  • TuyaEnum2 is for light mode status and control: 0 for RGB cycle / 1 for solid color

Home Assistant configuration

Use blueprint import button then create an automation from the blueprint which will send MQTT discovery payloads to Home Assistant. New entities should appear under the same Device Card in Tasmota integration.

First we need to create a ruleset to send data to specific topics used in HA configurations:

Rule2 on tuyareceived#dptype5id11 do publish stat/%topic%/error %value% endon on tuyareceived#dptype4id2==1 do publish stat/%topic%/fanmode high endon on tuyareceived#dptype4id2==0 do publish stat/%topic%/fanmode low endon

NOTE: verify that dpId11 is used for error reporting. If not change to the right number

GitHub Link