rtlamr2mqtt is a Home Assistant add-on and standalone Docker container that reads utility meters (electric, gas, water) using an RTL-SDR USB receiver and publishes readings to MQTT. The application runs rtl_tcp to interface with the SDR hardware and rtlamr to decode meter transmissions, parsing the JSON output and publishing formatted readings, HA auto-discovery payloads, and status to an MQTT broker. It supports sleep/wake cycles to conserve resources on Raspberry Pi, automatic process restart with backoff, USB device reset on timeout, and listen mode for discovering unknown meter IDs. The architecture is fully async (asyncio TaskGroup) with three independent tasks: MeterReader (rtlamr output parsing), MQTTPublisher (aiomqtt-based MQTT communication), and ManagedProcess (generic async subprocess lifecycle manager). It can run as a Home Assistant add-on (auto-discovers MQTT via Supervisor API) or standalone with a YAML config file.
This repository provides the Home Assistant add-on packaging for Zigbee2MQTT, a Zigbee to MQTT bridge. It contains Docker build configurations, entrypoint scripts, and add-on metadata to run Zigbee2MQTT as a managed add-on within Home Assistant OS or Supervised installations. The actual Zigbee2MQTT application is fetched from its upstream repository during Docker build (either a stable release or the dev branch for the edge variant). The add-on supports serial device passthrough, socat for remote serial forwarding, MQTT auto-discovery via Home Assistant services, and an ingress-enabled web frontend. The codebase is primarily configuration and build orchestration; there is no application logic beyond the entrypoint script that translates add-on configuration into environment variables for Zigbee2MQTT. It is a well-structured, actively maintained add-on following Home Assistant best practices, but offers no reusable software components outside the Home Assistant ecosystem.
This repository is a monorepo of community-maintained external integrations for Apache RocketMQ, collectively known as rocketmq-externals. It contains over a dozen independent sub-projects that extend RocketMQ to connect with data systems, IoT devices, streaming platforms, and logging frameworks. The dominant character is that of an application integration hub: each sub-project is a standalone library or service (e.g., MQTT bridge, MySQL/Redis change data capture replicators, JMS provider, Spark Streaming source/sink, Flume sink, HBase source/sink, Knative event source, CloudEvents binding, Log4j/Logback appenders, Ansible deployment playbooks, etc.). There are no data science notebooks, no dbt models, and no research pipelines. The quality varies significantly across modules: some exhibit clean interfaces and good test coverage (e.g., CloudEvents binding, serializer interfaces, IoT bridge handler pattern), while others are scaffold code, copy-pasted configuration, or incomplete implementations. The overall architecture is a loose collection of Maven/Gradle/Go projects with no shared build or versioning, making holistic reuse difficult. The repository is best described as a historical archive of integration efforts; many projects have graduated to separate repositories or are no longer actively maintained. Technical debt is high due to outdated dependencies (e.g., old RocketMQ versions, Spark 2.3, Netty 4.1.26, Log4j 1.2) and inconsistent coding practices. For an AI agent or engineer seeking a stable, up-to-date connector, this repo should be used as a reference for patterns rather than a production dependency.