esphome-components

Custom ESPHome components, referenced from device configs via external_components (source: github://randybb/esphome-components) — no fork of ESPHome itself.

external_components:
  - source: github://randybb/esphome-components
    components: [audio_spectrum]

Components

Component	Description
ant_plus	ANT+ sensors (heart rate, power, speed, FE-C, temperature, batteries) on the chip’s own radio (nRF52840, zephyr fork, RadiANT)
aixun	Aixun devices on their UART or USB port (ESP32-S3 USB host): model and firmware version of any of them, P2408 power supply sensors, DC output and current limit
audio_spectrum	Pass-through speaker that computes a spectrum of the audio for a Winamp style analyzer display
creality_cfs	Creality CFS filament tags (MIFARE Classic) read by pn5180: decrypted record, sensors, writing tags
openprinttag	OpenPrintTag filament spool tags read by pn5180: sensors, raw record for the Home Assistant integration, writing the consumed weight
pn5180	PN5180 tag reader: ISO 15693 tags with their memory, UIDs of ISO 14443A tags (NTAG, MIFARE), a general tag reader for Home Assistant
stm32_bootloader	Flashes an STM32F1/F4 over HTTP through its ROM UART bootloader, BOOT0 and NRST driven by the ESP
swd	SWD probe on two GPIOs: SEGGER RTT of a Cortex-M target to the log, target reset, flashing STM32F1/F4 over HTTP

Tests

Compile tests in the layout of ESPHome’s CI (tests/components/<component>/common.yaml and test.<platform>.yaml on the shared bus packages of tests/test_build_components/), so a component’s tests move to an upstream PR as they are:

tests/run.sh                # all components
tests/run.sh pn5180         # one component
MODE=config tests/run.sh    # validate only

ant_plus has none, it builds only with the zephyr fork.