If you run Home Assistant, you've already solved the hardest problem in the smart home: talking to three thousand kinds of device. Lights, locks, sensors, vacuums, obscure Zigbee gadgets from a brand that no longer exists — HA speaks to all of them. And since 2025 it ships an MCP server, so an AI assistant can already reach in and control them.
So when a project like DoSync shows up describing itself as a protocol between AI and physical devices, the fair question from anyone in the HA community is: why would I need that? I already have HA, and now AI can talk to HA directly.
That's the right question, and I want to answer it honestly — including the part where the answer is "you probably don't."
What Home Assistant is, precisely
HA does three jobs: it integrates with devices, it runs automations, and it gives you a UI. The first job is the one that matters here, and it's genuinely excellent. HA is the richest device-integration layer that exists. Nothing should try to replace that, and DoSync doesn't — it reads devices from HA through a bridge that's already in the repo.
But notice what HA's model is, underneath: it's still commands. "Turn on light.living_room." "Set climate.bedroom to 21." The HA MCP server exposes those same commands to an AI. The intelligence about what to do — what should happen when there's an emergency, when nobody's home, when a sensor reads something strange — lives either in an automation you wrote in advance, or in the AI sending the commands. HA executes; it doesn't decide.
That's not a criticism. It's just the layer HA operates at: it aggregates devices and gives you a uniform way to command them.
Where a different layer might sit
DoSync operates one layer up, and only does one thing: it turns a semantic intent into a coordinated, auditable set of actions.
You don't tell it "turn on these ten lights, unlock that door, send this SMS." You express a goal — ensure_safety, away_mode — and a resolver decides which devices are relevant based on what they've declared they can do, executes the actions, and writes every one of them to a tamper-evident SHA-256 audit log. The devices can come from HA, or from a direct adapter (WiZ over UDP, GPIO on a Pi, BLE, MQTT). HA is one source of "bodies," not the center.
Three things distinguish that from sending commands through the HA MCP:
Intents, not commands. The AI says what it wants to achieve; the resolver works out the rest from declared device capabilities. Add a device and it participates automatically — no automation to rewrite.
An audit log built for accountability. Every action and the reason it fired, in a SHA-256 hash chain: each entry includes the hash of the previous one, so editing or deleting a past entry breaks the chain and is detectable on verification. To be precise about what that buys you — it protects against undetected after-the-fact modification of the history, not against an attacker with root on the hub (who could rewrite the whole chain). HA's recorder and logbook give you a searchable history, which is great for "what happened"; the hash chain adds "and you can show it wasn't altered" — which matters when an auditor, an insurer, or an incident review needs a record they can trust, and matters not at all for everyday automation.
Multiple sources under one contract. DoSync coordinates devices from HA and from other adapters under a single semantic model with policies and certification. HA is one especially rich source among several.
And here's the part most projects won't say
For the vast majority of what people use Home Assistant for — "turn on the porch light when I get home," "set the thermostat back at night" — you do not need DoSync. HA's own automations and its MCP server cover that completely. Adding a coordination layer would be extra infrastructure earning you nothing.
DoSync earns its place only when two things are true at once: coordination matters (one goal has to fan out across many devices, reliably, possibly in an emergency) and traceability matters (you need an auditable record of what acted and why).
A concrete home example: an elderly parent lives alone, and you've built a fall-response setup — a sensor trips and the home should unlock the door for paramedics, turn every light to full, and message the family, all at once, and you need to be able to say afterward exactly what fired and when. That's coordination plus traceability in a house, not a factory. Outside cases like that — most of what HA does day to day — the extra layer earns you nothing.
If that's not your situation, stay with HA and enjoy it. That's not me being modest; it's me not wanting to sell you a layer you won't use.
How they actually fit together
The honest picture isn't DoSync versus Home Assistant. It's DoSync using Home Assistant — treating HA as one of the best places to source devices, and adding a semantic, auditable coordination layer above it for the narrow set of cases that need one. HA keeps owning its integrations. The connecting AI stays where the intelligence belongs — outside, expressing intent. DoSync is just the nervous system in between.
If you're in that narrow set of cases, it's worth a look. If you're not, you already have what you need — and if you're genuinely not sure which side of the line you're on, open an issue describing your setup and I'll tell you straight whether it's worth the trouble.
GitHub: https://github.com/giulianireg-spec/dosync-protocol
Web: https://dosync.dev/
License: Apache 2.0
