Skip to content

Supported Sensors and Modules ​

This page follows the current PeripheralType definitions, driver registration and Web forms. A release environment may compile a driver, but actual use still requires compiled, userEnabled and active to be true, valid pins and correct wiring.

Common Modules ​

ModuleInterface / TypeStatus
LED, relay, buzzerGPIO output 12Core capability
Button, door sensor, PIR, vibration, radarGPIO input 11/13/14, radar 49Core capability
Light, soil, smoke, voltage, currentADC 15Core capability; calibration required
PWM dimming or speed controlPWM 17Core capability
DHT11/DHT22, HC-SR04Generic sensor 38Select the sensor category in parameters
DS18B20OneWire 44Requires a data-line pull-up and the active ds18b20 feature
AHT20, SHT31, BH1750I2C sensor 38Requires i2cSensors
BMP280, MPU6050I2C sensor 38Requires i2cSensors
OLED/SH1106LCD 36Requires lcd
LCD1602/PCF8574LCD1602 52Requires lcd1602
TM1637Seven-segment 47Requires sevenSegment
WS2812B/NeoPixel45Requires neoPixel
Servo, stepper motor41, 42External power and safe limits required
Rotary encoder43GPIO input
RFID MFRC522SPI driverRequires rfid
IR receiver53Disabled in selected S3 release environments; see below
433MHz RF48Requires rfLearn for learning
DS1302 RTC50Three-wire interface, enable only when needed
RS485 Modbus slave deviceModbus device 51Firmware acts as the Modbus RTU master
Device eventVirtual type 60Uses no GPIO

Build and Chip Limits ​

CapabilityLimit
4MB environmentsNo OTA; heavy features may report no-memory because of the internal-DRAM budget
esp32s3-F8R8IR and 433MHz RF learning are disabled to avoid RMT/library conflicts
esp32-F8R8, esp32s3-F16R8More headroom; IR/RF may be enabled when the build and hardware allow it
W5500 EthernetRequires compile support, an SPI module and a valid pin configuration
EC801E-CN cellularRequires compile support, SIM, antenna and stable power
BLEA source flag exists, but BLE provisioning is not in the current release path

Do not select modules by historical firmware tier. Check Feature Config and /api/features/status on the actual device.

Generic Modules ​

Modules without a dedicated driver can use the matching signal interface:

SignalRecommended ConfigurationExamples
Digital high/lowGPIO input/outputPhotoelectric, tilt, reed switch, flame digital output
Analog voltageADCLight, rain, sound, smoke, pressure transmitter
Pulse/countGPIO input or encoderFlow, speed, rotary encoder
UART text/frameUARTGPS, serial sensor, custom module
RS485Modbus RTUTemperature/humidity, relay, motor, meter

Configure and Verify ​

  1. Add the module under Peripheral Config with a unique ID, type, pins and parameters.
  2. Save it with enabled=false, then enable it after checking the wiring.
  3. Verify one read/write operation or inspect the serial log.
  4. Add triggers and actions under Peripheral Exec only after the peripheral works alone.

Safety ​

  • Follow the board schematic and include/core/ChipConfig.h; avoid Flash/PSRAM, USB/JTAG, BOOT and download-UART pins.
  • Classic ESP32 GPIO34-39 are input-only, and ADC2 is constrained while WiFi is active.
  • I2C addresses must not conflict. For RS485, verify A/B polarity, common ground and termination.
  • Relays, servos and cellular modules need suitable external power. Isolate mains-voltage loads.

See Peripheral Reference for fields and wiring, and Examples for complete configurations.

FastBee | fastbee.cn