Home Assistant's map broke overnight, and it's a good reminder about free services
Here's a thing that happened to a lot of Home Assistant setups last month: every map broke at once. Nothing on anyone's server changed. The free service drawing the map tiles started stamping "API key required" across its images, and that was that. Home Assistant 2026.10 fixes it properly, and I think the way it was fixed is the interesting bit, because it's a pattern worth copying across your whole homelab.
The short version: your self-hosted, local-first setup almost certainly leans on a handful of free services run by someone else. That's fine. Just know which ones they are.
What actually happened
The project's own 2026.10 release notes are refreshingly plain about it. In the 2026.9 cycle, "the map provider we relied on started stamping an 'API key required' message across its map images, breaking every map in Home Assistant at once." The notes don't name the provider, and I'm not going to either, because it doesn't matter. Serving map tiles at scale costs real money, and asking for a key on a free service is a completely reasonable thing for a provider to do. It just happens to be the kind of change you find out about when the wall tablet in the hallway goes blank.
The fix in 2026.10 wasn't "find another free tile provider". Instead, Home Assistant moved from pre-rendered map images to vector tiles served by the OpenStreetMap Foundation, and your device now draws the map itself. The Map tiles integration docs say it "proxies those requests and caches recently used tiles in memory to improve performance and help keep the map usable during brief upstream or internet outages." The release notes add that this means your browser doesn't contact external tile servers directly.
So three things got better at once: the map is sharper (vectors scale, pictures don't), it rides out a short internet hiccup, and your phone isn't hitting a third-party server every time you open the Map dashboard. Older devices that can't render vector maps fall back to a simpler map from the same servers. It's automatic and needs no configuration, so if you've updated, you're done.
The new dependency is still a dependency
This is the bit I'd want a mate to understand before they relax completely. Moving to the OpenStreetMap Foundation is a better-aligned choice, not a dependency-free one, and the Foundation is admirably upfront about that.
Its Vector Tile Usage Policy puts it in one line: "OpenStreetMap data is free for everyone to use. Our tile servers are not." The servers run on donated resources with limited capacity, availability is "on a best effort basis" with no SLA, and access can be blocked without notice if a pattern of use causes problems. The policy also recommends not hardcoding the tile URL, so a project can switch without a software update if the service is disrupted.
None of that is a criticism. It's exactly the kind of honesty you want from a free service, and the vector tiles themselves were a long project: the Foundation announced the deployment in July 2025 after months of testing. A donation-funded foundation with a published usage policy is a sturdier thing to lean on than an arrangement nobody wrote down. But the map in your Home Assistant still depends on somebody else's servers being up and willing.
If the map is important to you, the policy page has a quiet tip for anyone who can't meet its requirements: OpenStreetMap data is free, so plenty of other providers serve tiles made from it, and you can run your own. That's a real option for the keen, though honestly, for a map you glance at to see if someone's left work yet, it's not worth the faff.
The free things your homelab quietly leans on
Now the opinion. The map story isn't really about maps. It's a nudge to do a short, boring audit of the free services your "local" setup depends on, before one of them changes its terms on a random Tuesday.
Home Assistant makes a start on this easy. Every integration's documentation page states its IoT class, from a classification the project introduced back in 2016: Local Push, Local Polling, Cloud Push, Cloud Polling, or Assumed State. The cloud ones are the ones that need "an active internet connection", and that 2016 post lists the downside bluntly: it doesn't work "if the internet is down or the company stops support".
A good example of how easy these are to forget: the weather integration in most installs, Met.no, is Cloud Polling. The docs describe it as a free service with no API key, run by the Norwegian Meteorological Institute and NRK, and say usage is subject to Met.no's terms of service, including fair-use policies. At the time of writing, its docs page says it's used by 83.5% of active installations. It's a lovely service. It's also, by definition, somebody else's server.
My list of things worth writing down, for Home Assistant and beyond:
- Anything that draws a map or looks up an address. You've just seen why.
- Weather and other data feeds. Usually free, usually polled, usually fine until they aren't.
- Cloud Polling and Cloud Push integrations. The docs page tells you which ones they are.
- Where your containers come from. If an image registry changes its free limits or a project moves its images, your next update is where you find out.
- Push notifications to your phone. Worth checking how they actually reach you and what sits in between.
For each one, I'd ask two questions. What breaks if this needs a key tomorrow? And would I notice before the family does? You don't need an answer for everything. "The weather card would be empty for a day while I sorted it" is a perfectly acceptable answer. The point is to know which outages are an annoyance and which ones take out an automation you actually rely on, like the heating or the bins reminder.
The pattern worth stealing
What I like about Home Assistant's fix is the shape of it, more than the map itself. Route the external request through something you run, cache what you can so a short outage doesn't show, and pick a provider whose terms are written down and whose incentives line up with yours. That's a pattern you can apply to plenty of your own setup, and it's the boring option that keeps working.
Free services aren't the enemy here. Most of the homelab world runs on them, and the people running them are usually doing it out of generosity or as a loss leader. The only real mistake is not knowing you're depending on one until the morning it changes.