BETA — Open to testers. Tell us what to fix on @vomehome or via a tester code.

Our Home Assistant 2026.11 cycle, in numbers

Four integrations in the new Home Assistant Marketplace, remote access you can watch from Home Assistant, a steadier CHAP standby and six releases of our MCP server. The four weeks between Home Assistant 2026.10 and 2026.11, counted the way Home Assistant counts its own.

Posted 5 November 2026 releaseshome-assistantmarketplacemcp

Home Assistant 2026.11 came out on 4 November. The developers posted its numbers the same evening: 5,827 pull requests from 557 people in one month. We liked the idea, so here are ours for the same four weeks, from the 2026.10 release on 7 October to 2026.11 on 4 November.

The numbers

  • 4 weeks, the same window as Home Assistant 2026.11
  • 383 commits across 23 public repositories, 177 of them in Vome itself (the app and integration, this site, the sync server and the MCP server)
  • 181,769 lines added, 58,537 removed
  • 40 versions of the Vome app, integration and CHAP app, 15 of the MCP server, and 77 tagged releases in all
  • 7 new public repositories
  • 36% of the new lines in Vome itself are tests
  • 1 person, writing with Claude Code: every commit in Vome itself says so

Those counts leave out generated files and the copy of the integration that ships inside the app, and count a change once even when it landed on two branches. Our 383 is a rounding error next to Home Assistant's 5,827, and nothing here exists without theirs.

Four integrations in the Marketplace

Home Assistant 2026.11 builds HACS into Home Assistant itself, as the Marketplace under Settings. What is in its catalogue installs from a release with no GitHub account and no restart. Anything else needs a GitHub connection before it can be added, and gets no update checks without one. So being in the catalogue matters more than it did, and four of ours got in this cycle:

  • Vome: the integration behind everything on this site. Search for Vome in the Marketplace.
  • Mosaic: a live-tile Start screen for Home Assistant, after Windows Phone. Tiles turn over to their controls, and the house tab draws your floors lit where the lights are on. Try it on our demo home, no account needed.
  • APC PDU Manager: switch and watch the outlets of APC switched power strips over SNMP.
  • InfoMentor: your children's school and preschool schedules, news and timeline from the InfoMentor school platform, with a phone notification for new notices. Our fork of lnd3's integration.

A fifth, Energy Sensor Generator, which adds the kWh sensors the Energy dashboard wants to devices that only report watts, is still in review. The idea was good enough that Home Assistant now does part of it itself: its Energy dashboard reads watts directly for the live view. The kWh totals behind the graphs still need an energy sensor, which is what this makes, for every device at once.

More of what we make for Home Assistant is on GitHub, not in the catalogue yet, among it house.wad, which turns your floor plan into a Doom level you can walk around.

Remote access you can watch

Your Vome link now shows up in Home Assistant itself (app 0.3.69 to 0.3.72):

  • a Remote access sensor that says whether the tunnel is up;
  • a Repairs issue when it has been down for ten minutes, and another that says why a link was refused;
  • a warning before a trial key or a health-check link runs out;
  • Download diagnostics on the integration, with every secret blanked.

We also renamed HomeLink, our tunnel into the devices on your home network, to Home Tunnel.

Safer by default

Ahead of the integration's review for the catalogue (app 0.3.67 to 0.3.74):

  • every Vome action is for administrators only;
  • the integration no longer writes your YAML. The Vome app does, and each change it makes is in your logbook;
  • no key can mint a Home Assistant token through Vome. Our 20 October security sweep found that one, and the full list is on our security page.

A steadier CHAP standby

CHAP keeps a second Home Assistant ready to take over if yours stops. It is still early, and this cycle it got a lot of attention (CHAP app 0.2.4 to 0.2.12):

  • the standby now keeps up with the main: Home Assistant, the Supervisor, the operating system and the apps it runs;
  • the main tells you when it cannot send, rather than letting the standby fall quietly behind;
  • you choose the folders to leave out of syncing, and a nearly full disk warns you by page and email;
  • you decide when the home moves back, and can call a move off.

For your coding agent

Our MCP server lets Claude Code, Claude Desktop, Cursor and others work on your Home Assistant through Vome. It went from 0.11 to 0.17.3. New this cycle:

  • setting up the Energy dashboard, and smoothing meter glitches out of its statistics;
  • people and the trackers that follow them;
  • uploading files to your configuration;
  • watching states even on a home without the Vome integration;
  • telling you Home Assistant is restarting instead of passing on a raw error;
  • the store tools working with the new Marketplace.

Coming next

On test homes now, not yet released: Vome listed on Home Assistant's own Model Context Protocol page beside ESPHome, backups to Vome that fill Home Assistant's progress bar while they upload, and AI that looks at your camera pictures and hears your voice commands. We will write them up when they reach you.

Rather not do this alone?
The Vome assistant will walk you through this guide a step at a time, and can do some of it for you.
Sign in for AI help

Something wrong or missing here? Tell us — these pages are written from real work, so corrections are welcome.