Is there a plan to merge the Fan component to the main branch? This need to be done to bring it into Homebridge Esphome Ts

So I've been sifting through the code and it seems like there is no output for color-mode being sent to esphome from homebridge. I use HomeKit and it requires a color mode to be sent for it to be able to switch to white from rgb colors. Instead it sends "white" in rgb values.

this is a log from the esphome device:
[16:25:45][VV][api.service:617]: on_light_command_request: LightCommandRequest {
key: 2880471878
has_state: YES
state: YES
has_brightness: YES
brightness: 0.78
has_color_mode: NO
color_mode: COLOR_MODE_UNKNOWN
has_color_brightness: NO
color_brightness: 0
has_rgb: YES
red: 1
green: 0.239216
blue: 0.976471
has_white: NO
white: 0
has_color_temperature: NO
color_temperature: 0
has_cold_white: NO
cold_white: 0
has_warm_white: NO
warm_white: 0

and this is what it responds with after:
[16:25:45][I][light:392]: 'studio-posters' - Keeping current color mode RGB for call without color mode.
[16:25:45][D][light:036]: 'studio-posters' Setting:
[16:25:45][D][light:051]: Brightness: 78%
[16:25:45][D][light:058]: Red: 100%, Green: 24%, Blue: 98%
[16:25:45][D][light:085]: Transition length: 1.0s
[16:25:45][VV][api.service:122]: send_light_state_response: LightStateResponse {
key: 2880471878
state: YES
brightness: 0.78
color_mode: COLOR_MODE_RGB
color_brightness: 1
red: 1
green: 0.239216
blue: 0.976471
white: 1
color_temperature: 0
cold_white: 1
warm_white: 1
effect: ''
}

My yaml file is this: (This could not be fully correct because I was messing with it after I had already uploaded to my light)
substitutions:
devicename: studio-posters
device_name: Studio Posters

esphome:
name: $devicename

esp8266:
board: esp01_1m

Enable logging

logger:
level: VERY_VERBOSE

Enable Home Assistant API

api:
password: ""

ota:
password: ""

wifi:
ssid: !secret wifi_ssid
password: !secret wifi_password
power_save_mode: light

Enable fallback hotspot (captive portal) in case wifi connection fails

ap:
ssid: "$devicename Fallback Hotspot"
password: "iH0ebRQ9vEyv"

captive_portal:

Define a light entity

light:

• platform: rgbww
  name: $devicename
  red: output_red
  green: output_green
  blue: output_blue
  cold_white: output_cold_white
  warm_white: output_warm_white
  color_interlock: true
  constant_brightness: true
  restore_mode: RESTORE_AND_ON

Example configuration entry

switch:

• platform: restart
  name: "$device_name Restart"

sensor:

• platform: wifi_signal
  name: "WiFi Signal Sensor"
  update_interval: 60s

#script:

- on_light_command_request

Define output pins

output:

• platform: esp8266_pwm
  id: output_red
  pin: GPIO4
  max_power: .8
• platform: esp8266_pwm
  id: output_green
  pin: GPIO12
  max_power: 0.70
• platform: esp8266_pwm
  id: output_blue
  pin: GPIO14
  max_power: 0.75
• platform: esp8266_pwm
  id: output_warm_white
  pin: GPIO13
• platform: esp8266_pwm
  id: output_cold_white
  pin: GPIO5

I programed a device with two switches: one is a typical GPIO switch, the other is a virtual (platform) switch. esphome log shows the following:
[19:52:55][C][gpio.output:010]: GPIO Binary Output:
[19:52:55][C][gpio.output:011]: Pin: GPIO5 (Mode: OUTPUT, INVERTED)
[19:52:55][C][switch.gpio:048]: GPIO Switch 'gpio switch'
[19:52:55][C][switch.gpio:049]: Pin: GPIO12 (Mode: OUTPUT)
[19:52:55][C][switch.gpio:071]: Restore Mode: Restore (Defaults to OFF)
[19:52:55][C][template.switch:058]: Template Switch 'virtual switch'
[19:52:55][C][template.switch:059]: Restore State: NO
[19:52:55][C][template.switch:060]: Optimistic: NO

esphome-ts found the GPIO switch and is able to control it as expected. However, esphome-ts didn't "see" the virtual switch. Is this normal?