{"NAME":"XD800W","GPIO":[0,2272,0,2304,0,0,0,0,0,0,0,0,0,0],"FLAG":0,"BASE":54}

Models are marked as 802W to 808W there is just different top cover.

Please read TuyaMCU wiki entry to understand the terminology and configuration process.

Functions

• dpID 1 device mode: 0 = off / 1 = continuous Type1
• dpID 2 error notification ?: 0 = ok / 1 = error Type1
• dpID 3 set timer 0 = off / 1 = 1 hour / 2 = 3 hours / 3 = 6 hours not needed with Tasmota, there’s a Timer function Type4
• dpID 5 light switch: 0 = off / 1 = on Type1
• dpID 6 light mode: 0 = off / 1 = rgb cycle 3 = single color Type4
• dpID 8 led color: 14 char value in hex (can define only RGB and send HSV value as max: RRGGBBffff6464) Type4

I found the built in buzzer very loud so I dropped little hot glue to the center of it for quieter operation!

Configuration

Backlog TuyaMCU 11,1; TuyaMCU 12,5; TuyaMCU 21,7; TuyaMCU 24,8; TuyaMCU 61,4; 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 1 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

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#dptype1id2 do publish stat/%topic%/error %value% endon on tuyareceived#dptype4id4==1 do publish stat/%topic%/fanmode high endon on tuyareceived#dptype4id4==0 do publish stat/%topic%/fanmode low endon

NOTE: verify that dpId2 is used for error reporting and id4 for mist strenght. If not change to the right number

  GitHub Link

PCB