search

esphome / issues

Issue Tracker for ESPHome
https://esphome.io/
291 stars 36 forks source link

Should we support Lolin32 Lite? #1933

Closed sergeolkhovik closed 3 years ago

sergeolkhovik commented 3 years ago

ESPHome supports lolin32, lolin_d32, lolin_d32_pro boards, but not lolin32_lite (https://docs.platformio.org/en/latest/boards/espressif32/lolin32_lite.html#board-espressif32-lolin32-lite).

Operating environment/Installation (Hass.io/Docker/pip/etc.): Docker, latest version.

ESP (ESP32/ESP8266, Board/Sonoff):

Chineese version ESP32 Lolin32 Lite (https://www.aliexpress.com/item/33009178296.html)

ESPHome version (latest production, beta, dev branch)

Latest version (1.16.2 I think)

Description of problem:

I'm not sure if there's any significant difference (https://docs.platformio.org/en/latest/platforms/espressif32.html#wemos) that's why I'm asking should we add support for Lolin32 Lite or simple lolin32 as board should be enough? I'm asking this because I'm having very strange behaviour on this board + si7021/am2320 (while all is fine on wemos d1 mini esp8266).

Problem-relevant YAML-configuration entries:

esphome:
  name: ap3
  platform: ESP32
  board: lolin32_lite

Logs (if applicable):

% esphome-docker ap3.yaml compile
INFO Reading configuration ap3.yaml...
Failed config

esphome: [source ap3.yaml:2]
  name: ap3
  platform: ESP32

  Could not find board 'lolin32_lite'. Valid boards are alksesp32, bpi-bit, d-duino-32, esp-wrover-kit, esp32-devkitlipo, esp32-evb, esp32-gateway, esp32-poe, esp32-poe-iso, esp32-pro, esp320, esp32cam, esp32dev, esp32doit-devkit-v1, esp32thing, esp32vn-iot-uno, espea32, espectro32, espino32, featheresp32, firebeetle32, fm-devkit, frogboard, heltec_wifi_kit_32, heltec_wifi_lora_32, heltec_wifi_lora_32_V2, heltec_wireless_stick, hornbill32dev, hornbill32minima, intorobot, iotaap_magnolia, iotbusio, iotbusproteus, lolin32, lolin_d32, lolin_d32_pro, lopy, lopy4, m5stack-core-esp32, m5stack-fire, m5stack-grey, m5stick-c, magicbit, mhetesp32devkit, mhetesp32minikit, microduino-core-esp32, nano32, nina_w10, node32s, nodemcu-32s, odroid_esp32, onehorse32dev, oroca_edubot, pico32, pocket_32, pycom_gpy, quantum, sparkfun_lora_gateway_1-channel, tinypico, ttgo-lora32-v1, ttgo-t-beam, ttgo-t-watch, ttgo-t1, turta_iot_node, vintlabs-devkit-v1, wemos_d1_mini32, wemosbat, wesp32, widora-air, xinabox_cw02.
  board: lolin32_lite [source ap3.yaml:4]
close-issue-app[bot] commented 3 years ago

This issue was auto-closed because the issue template was not filled out. The ESPHome developers invest lots of time to maintain this project, so please at least fill out the issue template so that a bunch of standard questions don't need to be asked again each time. Thank you for taking the time to report a bug, hopefully it can be resolved soon.