ESPHome and Anavi Miracle Controller Setup

I am trying to setup a Anavi Miracle controller with the ESPHome add on. I have the starter kit with two LED strips and did purchase two additional sensors, a MPU-6050 (accel/gyro) and a SHT40 (temp/hum).

I believe that I can use ESPHome to fully setup the controller and sensors but may be wrong. I was able to successfully flash the .yaml I built below. Through ESPHome I am seeing the device come online so I think it is working to a point, but the controller is only flashing a red light and don’t know what the issue could be. I only had enough cables to connect one sensor at the moment so during the boot process I only had the MPU-6050 connected with I2C. I found an example .yaml file that I used as a template but due to FastLED not working by default I cant even test the example one I found.

Has anyone used the Anavi controller before and is ESPHome the simplest solution? What about adding additional sensors? I saw in the documentation that you need the Arduino IDE to flash and edit the firware to accept different types of sensors. It would still work the the same as flashing it with ESPHome correct?

#wifi is setup correctly using my login
wifi:
  ssid: "SET-YOUR-WIFI" #edited out
  password: "SET-YOUR-WIFI-PASSWORD" #edited out

  # Enable fallback hotspot (captive portal) in case wifi connection fails
  ap:
    ssid: "Anavi Miracle Controller"
    password: "yhr8PZ0rwFUC"

captive_portal:

# Enable logging
logger:

# When no client connects to the native API within 5 minutes a
# watchdog kicks in and reboots the device. Therefore by default
# the Home Assistant API is disabled. Enabled it only if you will
# use it.

api:
  password: "opensource"

ota:
  password: "opensource"

# Please note that if an I2C sensor module is not attached ESPHome
# will report an error and the status LED will be blinking rapidly.
# To avoid this case either disable the status LED or any I2C
# sensor module that you don't plan to attach.
status_led:
  pin: GPIO16

light:
#first three lines commented out and changed to neopixelbus
#  - platform: fastled_clockless
#    chipset: WS2812B
#    rgb_order: GRB
  - platform: neopixelbus
    variant: WS2812
    type: GRB
    pin: GPIO12
    num_leds: 10
    name: "LED1"
    effects:
      - addressable_rainbow:
      - addressable_rainbow:
          name: Rainbow Effect With Custom Values
          speed: 10
          width: 50
      - addressable_color_wipe:
      - addressable_color_wipe:
          name: Color Wipe Effect With Custom Values
          colors:
            - red: 100%
              green: 100%
              blue: 100%
              num_leds: 1
            - red: 0%
              green: 0%
              blue: 0%
              num_leds: 1
          add_led_interval: 100ms
          reverse: False

#  - platform: fastled_clockless
#    chipset: WS2812B
#    rgb_order: GRB
  - platform: neopixelbus
    variant: WS2812
    type: GRB
    pin: GPIO14
    num_leds: 10
    name: "LED2"
    effects:
      - addressable_rainbow:
      - addressable_rainbow:
          name: Rainbow Effect With Custom Values
          speed: 10
          width: 50
      - addressable_color_wipe:
      - addressable_color_wipe:
          name: Color Wipe Effect With Custom Values
          colors:
            - red: 100%
              green: 100%
              blue: 100%
              num_leds: 1
            - red: 0%
              green: 0%
              blue: 0%
              num_leds: 1
          add_led_interval: 100ms
          reverse: False

i2c:
  sda: GPIO4
  scl: GPIO5
  scan: False

#font:
#  - file: 'arial.ttf'
#    id: font1
#    size: 12

#display:
#  - platform: ssd1306_i2c
#    model: "SSD1306 128x64"
#    address: 0x3C
#    lambda: |-
#      it.print(0, 0, id(font1), "ANAVI");
#      it.print(0, 15, id(font1), "Miracle");
#      it.print(0, 27, id(font1), "Controller");
#apds9960:
#  address: 0x39
#  update_interval: 60s

# There are some known ESPHome issue with DHT22 therefore the
# model has been explicitly configured. For more details have a
# look at the notes in the documentation and the reported issues:
# https://github.com/esphome/issues/issues/792
# https://esphome.io/components/sensor/dht.html

sensor:
  #- platform: bh1750
  #  name: "BH1750 Illuminance"
  #  address: 0x23
  #  measurement_time: 69
  #  update_interval: 5s

  - platform: bmp085
    temperature:
      name: "BMP180 Temperature"
    pressure:
      name: "BMP180 Pressure"
    update_interval: 10s

# By default HTU21D I2C sensor module is disabled because it is
# not included in any of the kits of ANAVI Miracle Controller.

#  - platform: htu21d
#    temperature:
#      name: "HTU21D Temperature"
#    humidity:
#      name: "HTU21D Humidity"
#    update_interval: 10s
    
#  - platform: sht4x
#    temperature:
#      name: "SHT4x Temperature"
#    humidity:
#      name: "SHT4x Humidity"
#    update_interval: 10s
  
  - platform: mpu6050
    address: 0x68
    #accel_x:
    #  name: "MPU6050 Accel X"
    #accel_y:
    #  name: "MPU6050 Accel Y"
    #accel_z:
    #  name: "MPU6050 Accel z"
    gyro_x:
      name: "MPU6050 Gyro X"
    gyro_y:
      name: "MPU6050 Gyro Y"
    gyro_z:
      name: "MPU6050 Gyro z"
    #temperature:
    #  name: "MPU6050 Temperature"
    update_interval: 1s

# There are known "ESP8266 Various Connection Issues" when
# the binary sensor is enabled. It affects ANAVI Miracle Controller
# therefore by default apds9960 is disabled:
# https://github.com/esphome/issues/issues/455
# However, below is an example how to enabled it if needed:

#  - platform: apds9960
#    type: CLEAR
#    name: "APDS9960 Clear Channel"

#binary_sensor:
#  - platform: apds9960
#    direction: UP
#    name: "APDS960 Up Movement"

Update:

This is working. Just took awhile for my device to come up as discovered in HA. Set it up from there and worked perfectly.