homecore.io

What It Is

homeCore is a local-first smart home automation platform written in Rust, positioned around “one binary, no cloud dependencies.” It runs on the user’s own hardware, and its core automation logic can execute offline without a cloud account, internet connection, or subscription fee. The documentation also makes clear that the project is still a work in progress; the author says, “Runs my house. Not yet packaged for yours.” In other words, it is more of a system for developers and early adopters than a mature consumer-ready product.

Core Capabilities

Its architecture uses MQTT as the unified device communication layer: plugins publish device state, while HomeCore publishes commands. A basic installation includes the rumqttd Broker, so no separate MQTT service is required. Core modules include state bridging, a rule engine, scheduler, mode management, timers and switch virtual devices, plus REST + WebSocket APIs. Automation rules are stored as RON files, support hot reloading at runtime, and can also be created, edited, and deleted through the API. Rules include triggers, conditions, actions, execution history, and dry-run testing.

Language, Plugins, and Ecosystem

HomeCore’s core is built on Rust and Tokio, with an emphasis on concurrent I/O. Plugins run as separate processes and can be written using the Rust, Python, Node.js, or .NET SDKs. Officially listed plugins cover Lutron RadioRA2/Caseta, Philips Hue, Z-Wave JS, YoLink, Sonos, WLED, ISY/IoX, and more. Plugin isolation is mainly handled at the MQTT layer; for true per-topic access control, the documentation recommends using an external Mosquitto Broker.

Pricing and Open Source

The documentation explicitly states that there are no subscription fees, and that all HomeCore repositories are dual-licensed under MIT and Apache-2.0. There is no information about a commercial edition, hosted version, enterprise support, or paid plans, so it can be considered a free, open-source, self-hosted project.

Pros, Cons, and Who It’s For

Its strengths are thorough local-first design, API-first architecture, clear structure, hot-reloadable rules, and friendly multi-language plugin extensibility. Its downsides are that the installation process is still developer-oriented and requires tools such as cargo, curl, jq, and websocat; it is also not yet packaged for regular users, so maturity and ease of use are limited. It is best suited to users comfortable with the command line, Rust/MQTT, and smart home ecosystems, as well as those looking to replace cloud-based automation or build custom plugins.

Access from China

The documentation does not provide information about China network access, mirrors, payments, or localization, so this is unknown. Since the project depends on GitHub, the Rust toolchain, and potentially its plugin ecosystem, users in China may need to consider network stability. Alternatives include Home Assistant, openHAB, Node-RED, and similar platforms.