Ross ROSS = Recommend OSS · open-source software intelligence for agents

OMOTE-Community/OMOTE-Firmware

Open Source Remote - Firmware observed · 2026-08-28

github.com/OMOTE-Community/OMOTE-Firmware · homepage · C++ · GPL-3.0 (copyleft) observed · 2026-08-28

Health v2 · maintenance only

59/100

  • Activity 66
  • Release rhythm 35
  • Longevity 83

Flags: no_releases

How is this computed?

round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-02. Adoption (stars, forks) is never an input.

  • gap_med: n/a
  • age_days: 1172
  • days_rel: n/a
  • days_push: 208
  • n_releases_24m: 0

Full methodology

Adoption not part of the score

1775 stars · 179 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded

OMOTE-Firmware is the ESP32 Arduino firmware for the OMOTE open-source universal remote, providing an LVGL touchscreen UI that controls TVs and amplifiers via infrared, media players via Bluetooth, and smart home devices via MQTT. It also includes an LVGL GUI simulator that runs on Windows, Linux, and macOS for developing and testing the interface without hardware.

Use cases

  • build a DIY universal remote for TV and amplifier with infrared
  • control Fire TV or other media players over Bluetooth from a handheld remote
  • control smart home devices via MQTT from a physical remote
  • decode IR codes from existing remotes
  • develop and test an LVGL touchscreen UI on desktop before flashing hardware
  • customize remote buttons and device layouts for my own devices

When to choose

  • you own or plan to build OMOTE ESP32 hardware and want an open, customizable universal remote
  • you want to prototype an LVGL embedded UI in a desktop simulator
  • you need IR, BLE, and MQTT control combined in one handheld device
  • you are comfortable compiling and flashing firmware with PlatformIO

When to avoid

  • you want a prebuilt, consumer-ready remote with a web configuration interface (not yet available)
  • you need to control devices via Wi-Fi protocols other than MQTT (e.g., proprietary APIs)
  • you are not comfortable building firmware yourself, since no prebuilt binaries are published
  • you need a remote for devices that use RF (e.g., 433 MHz) rather than IR, BLE, or MQTT

Facets

application · maturity active

embedded gui workflow-automation websocket iot embedded-systems hardware cross-platform iot embedded windows cpp universal-remote esp32-firmware lvgl infrared mqtt bluetooth platformio smart-home touchscreen simulator automation linux macos

2 sources

Member repositories

RepositoryRoleHealth v2
OMOTE-Community/OMOTE-Firmwaremain59

For agents

markdown · JSON · MCP: product_card(name="OMOTE-Community/OMOTE-Firmware")

Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem