ha-break-check
Will my Home Assistant custom integrations break on 2026.10?
Paste the names of your custom integrations. This page compares them with our own scan of 3,240 integrations from the HACS default list and tells you in which ones we found code or requirements that we have seen cause errors on Home Assistant 2026.10. It runs in your browser - nothing you paste is sent anywhere.
Where to get the names: they are the folder names in /config/custom_components. In the Terminal add-on:
ls /config/custom_components. One name per line, or separated by spaces or commas. A GitHub name like owner/repository works too.
What this page checks
For each of the 3,240 integrations we took the version HACS installs (a release; for 66 of them a branch such as main),
read its code without running it, and ran an install check of its requirements. Our result files are from 10 and 11 October 2026. Five things are reported:
- Old options dialog code - in our tests this makes the Configure button answer with a 500 error since Home Assistant 2025.12. Found in 185 integrations.
- A helper called the old way - in our tests the action that reaches it fails on 2026.10. Found in 6.
- Use of a helper that 2026.10 removed (
cv.vol). Found in 1. - A pinned library that our install check could not combine with 2026.10.0 but could with 2026.9.4. Found in 3.
- Requirements our install check could not resolve on either version. Found in 15.
For 31 integrations at least one of these checks could not read the code or the requirements. The page says so for each of them and never reports such an integration as "nothing found".
What it cannot tell you
- It reads code; it did not run your integrations, and it cannot see whether your set-up ever reaches the code it found. The first four causes were each reproduced by us on a test machine with at least one real integration - the guide to the 500 error shows those tests and the fixes.
- The list is a snapshot. A version released after our scan may already be fixed, and a later Home Assistant release can change the picture (the pinned-library check was made against 2026.10.0).
- "Nothing found" is not a promise. There are causes this page does not look for, and built-in integrations are not in it.
- It does not list what Home Assistant has announced it will remove in future releases. For that there is a free tool by another author: Breakage Radar (we have not run it). This page shows what our own scan, install check and tests found for 2026.10.
- Take a backup before every update. That stays true whatever this page says.
Free. What you paste is not sent and not stored; the page only counts that a check was run. Update Watch has our tested verdicts for new releases.