Homebridge is a lightweight Node.js server that bridges non-HomeKit and non-Matter smart home devices into Apple HomeKit and the Matter ecosystem. It operates as a long-running daemon with a plugin architecture: community plugins (npm packages with keyword `homebridge-plugin`) register accessories and platforms via a well-defined API. The server manages plugin lifecycles, accessory caching, child bridge processes for isolation, and supports both HAP (HomeKit Accessory Protocol) and Matter (via `@matter/main`) protocols. Matter support is opt-in and lazy-loaded to avoid startup overhead. The codebase is written in TypeScript with ESM, uses vitest for testing, and includes extensive CI/CD pipelines. It demonstrates strong engineering practices: clean abstractions for plugin registration, IPC between parent and child processes, port allocation, state management, and error handling. However, the Matter integration is deeply coupled to the evolving matter.js library, and some workarounds for controller-specific behavior (e.g., Apple Home) introduce fragility. Overall, it is a well-crafted, production-quality bridge server with reusable patterns for logging, storage, and cluster command mapping.
This repository is a Homebridge plugin for Xiaomi Miot devices, allowing control of various smart home devices through Homekit. It supports a wide range of device types, including fans, heaters, humidifiers, air purifiers, and more. The plugin integrates Miot devices into Homekit, enabling control from the native Homekit iOS app and Siri.
This is a Homebridge plugin (`@switchbot/homebridge-switchbot`) that bridges SwitchBot IoT devices (lights, curtains, locks, sensors, vacuums, etc.) into Apple HomeKit using both HAP and Matter protocols. It communicates via Bluetooth Low Energy (BLE) and the SwitchBot OpenAPI cloud API, with configurable fallback and rate-limiting. The plugin provides a rich configuration UI served through Homebridge Config UI X, including device discovery, credential management, and advanced polling settings. The architecture follows a platform plugin pattern with two platform classes (HAP and Matter), a resilient client layer (debounce, circuit breaker, daily budget tracking), a device factory and abstract base class for device-specific implementations, and extensive Matter cluster mappings. While the codebase is well-structured and actively maintained, it suffers from a large monolithic platform file (~2800 lines), low test coverage (~1.36%), and a dependency conflict requiring `--legacy-peer-deps` during installation. ESLint configuration also fails in CI. Nonetheless, the plugin is feature-rich, handles edge cases like BLE encryption and OpenAPI rate limits, and includes a polished custom UI.