head to head · open source
integration vs local_roborock_server
integration has 7,886 GitHub stars, 1,612 forks, 164 open issues and last shipped yesterday. local_roborock_server has 1,300 stars, 79 forks, 25 open issues and last shipped 13 days ago. integration leads on adoption by 507% (7,886 vs 1,300 stars). integration is written in Python under MIT; local_roborock_server is written in Python under MIT. integration has attracted 20% as many forks as stars, local_roborock_server 6%. integration was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (home-assistant), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| integration | local_roborock_server | |
|---|---|---|
| GitHub stars | ★ 7.9K | ★ 1.3K |
| License | MIT | MIT |
| Written in | Python | Python |
| Last push | 2026-11-13 | 2026-11-01 |
| Forks | ⑂ 1.6K | ⑂ 79 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick integration if
- You weight community size — 7.9K stars and counting
- You want the MIT license terms
- Your stack matches Python
- You value the larger contributor base for long-term maintenance
pick local_roborock_server if
- You want the local_roborock_server feature set and don't need the biggest community
- You prefer the MIT license terms
- Your stack matches Python
- You evaluated both and local_roborock_server fits your workflow better
About integration
HACS (Home Assistant Community Store) Manage (Install, track, upgrade) and discover custom elements for Home Assistant directly from the UI. What? HACS is an integration that gives the user a powerful UI to handle downloads of custom needs. Highlights of what HACS can do: Help you discover new custom elements. Help you download new custom elements. Help you keep track of your custom elements. Manage(download/update/remove) Shortcuts to repositories/issue tracker Useful links General documentation Configuration FAQ GitHub Discord Become a GitHub sponsor? ❤️ BuyMe Coffee Beer? 🍺🙈 Issues If When you experience…
read the full integration overview →
About local_roborock_server
Roborock Local Server [![GHCR][badge ghcr]][link ghcr] Run Roborock's cloud backend on your own local network. Your vacuum keeps live maps and local controls on an isolated LAN without internet access, requiring no hardware modifications or firmware rooting. Why this exists While Home Assistant communicates with Roborock vacuums over a local protocol, two constraints previously prevented running them completely offline: 1. Cloud locked maps: Roborock routes all map data strictly through their cloud servers (despite the vacuum storing the map locally). 2. Cloud health checks: If a vacuum cannot reach Roborock's…
read the full local_roborock_server overview →
More in Miscellaneous
Related comparisons
More Internet of Things (IoT) projects
Compare either of these against the rest of the Internet of Things (IoT) field.
Frequently asked questions
Is integration or local_roborock_server more popular?
integration has 7,886 GitHub stars and local_roborock_server has 1,300. integration has the larger community by that measure.
Are integration and local_roborock_server free?
Both are open source. integration is licensed under MIT and local_roborock_server under MIT. Neither carries a licence fee.
What is the difference between integration and local_roborock_server?
integration is written in Python and local_roborock_server in Python. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, integration or local_roborock_server?
Choose integration if you want the larger community (7,886 stars) or its MIT licence terms. Choose local_roborock_server if its feature set, stack or MIT licence fits better. Both are self-hostable.