Fix status · Updated
Home Assistant 2026.11: custom integrations that fail with "cannot import name", and which ones are fixed
Home Assistant 2026.11 removes names that some custom integrations import from the wrong place. After the update, an integration that still imports one of them stops loading. In Home Assistant it shows as Failed to set up, and the log has a line like this:
ImportError: cannot import name 'StateType' from 'homeassistant.components.sensor'
The fix is in the integration, not in your setup. Usually the author changes one import line and releases an update. Many have done that since the 2026.11 beta came out on 28 October; on 18 November 13 of the 65 integrations we track still had no full release with the fix. Find yours in the table below. If it is fixed, update it. If not, stay on 2026.10 until it is.
Which dated breaks like this one hit your code next? Check your repository against the Breakage Calendar in your browser.
Is this you?
Go to Settings > System > Logs. Open the menu of the log card and choose Show raw logs, then search for
cannot import name. The normal log view usually does not find it: there the error often shows only as Error setting up entry … for …, and you have to open that entry to see the traceback.Look for
ImportError: cannot import name '…' from 'homeassistant.…'. Just above the traceback there is usuallyError setting up entry … for …. The folder aftercustom_components/in the same traceback is the integration that has the problem.Find that integration in the table. If it is not there, the steps below still apply: tell its author the name and where it now comes from (the list for authors).
Some integrations fail in a different way. An integration set up in configuration.yaml (a platform: entry) loses only that platform. An integration that starts its platforms in the background can show as loaded with no entities; the only log trace is then Task exception was never retrieved, followed by the same ImportError.
What to do
Before you update to 2026.11.0: check the table for each custom integration you use. Update the fixed ones in HACS first. If HACS does not offer the version the table names, open the integration in HACS and choose Update information in its ⋮ menu: that makes HACS check GitHub for new releases. HACS's own list of versions can be days behind: before this release it did not change from 29 October until 4 November. A few fixed releases need 2026.11 itself, and HACS will not install them on 2026.10; their row says so, so update those right after you update Home Assistant. If one shows Not fixed, wait. Home Assistant's own documentation says you can stay on the previous version until a fix is released. If you update anyway, turn on the backup option in the update dialog (Automatic backup before update or Create manual backup before update), so you can go back.
In Docker there is no update dialog. Make a backup first in Settings > System > Backups. To stay on 2026.10, pin the image to ghcr.io/, or homeassistant/ from Docker Hub (in Compose, on the image: line). The stable tag has pointed to 2026.11 since 4 November (to 2026.11.2 since 16 November), so a container set to stable gets 2026.11 at its next pull.
If you have already updated and an integration fails:
- Its row says Fixed: install the integration's update and restart. In 2026.11, HACS becomes part of Home Assistant as the Marketplace, and your HACS integrations move into it when Home Assistant first starts after the update. Their updates show under Settings > Updates. If installing the update asks you to accept the Marketplace's notice, open Settings > Marketplace and accept it first: until then it cannot install updates. After the update, a repair offers to restart Home Assistant for you. The Marketplace checks its catalog for new versions every 6 hours, and that catalog can itself be days behind, so a recent fix may not show yet.
- Its row says Not fixed, or "not yet in a release": go back to 2026.10. Restore the backup you made before the update, in Settings > System > Backups. On Home Assistant OS, restoring the Home Assistant settings from that backup also brings back the version you ran then. Home Assistant's documentation says to go back by restoring a backup: installing the earlier version alone does not undo changes the newer version made to your data. In Docker, change the image to
2026.10.4(in Compose, theimage:line, thendocker compose up -d) first, then restore the backup. If you have no backup, the file edit below or waiting for the author are what is left. - Tell the author, if their issue tracker has no report of it yet. The
ImportErrorline is enough; if the name is in the list for authors, add the line that replaces the import.
If you are comfortable editing a Python file, you can make the author's fix yourself until the update ships. Open the file named in the traceback. It is in /config/ or a subfolder of it; the File editor app shows the same folder as /homeassistant/. Take the name out of the old import and import it from where the list for authors says. For example, this line from the tascam-bdmp4k integration:
from homeassistant.components.sensor import SensorEntity, StateTypebecomes these two lines:
from homeassistant.components.sensor import SensorEntity
from homeassistant.helpers.typing import StateTypeIf the import lists its names in brackets over several lines, delete only the removed name and its comma from the list, and add the new from … import … line below the closing bracket. Then restart Home Assistant.
The same import can be in more than one file of the integration. After the restart, check the log again, and repeat for each file it names; Studio Code Server can also search the whole folder for the name. HACS, or the Marketplace in 2026.11, replaces these files when you next update the integration, which is what you want once the author's fix is out. This does not work for async_, DATA_ or async_: those need a code change by the author.
If the error you searched for is "HACS does not work on Home Assistant 2026.11 and newer", it is not the ImportError above. It comes from the HACS install script at get.hacs.xyz, which reads the version in your .HA_VERSION file and stops on 2026.11 or newer. It prints: HACS does not work on Home Assistant 2026.11 and newer (found …), as it has been replaced by the native Marketplace integration. The version in parentheses is yours, and the message ends with a link to the Marketplace documentation. You see it when the script runs on 2026.11 or newer: for example in the steps of an older tutorial on a fresh install, or in a start script that reinstalls HACS each time. You do not need HACS there. In 2026.11 the Marketplace is part of Home Assistant, under Settings > Marketplace, and Home Assistant's documentation says that if you used HACS, the Marketplace migrates your HACS content automatically when Home Assistant starts after the update. The same page lists two limits: AppDaemon apps and Python scripts are no longer managed, and a custom repository without a hacs.json file cannot be updated; both stay installed, and the Marketplace does not update them. Take the line that installs HACS out of the tutorial steps or the start script.
Fix status by integration
These are the custom integrations we found that import or call something Home Assistant 2026.11 removes: 61 from the HACS default list, and 4 outside it whose users have reported the error on GitHub. Fixed means the integration's latest GitHub release, which is what HACS and the Marketplace install, no longer has the import. We read every row again on 9 November. On 16 November we checked every row's latest release again and read the code of 27 of them. On 18 November we checked every row's newest version again and read the code of the newest release of each integration that has one after its row's version; a release after 18 November is not shown. An integration whose author removed the import before 18 October, when we first read the HACS list, is not in the table, but a copy you installed before that fix still fails. Spook is one: it stopped importing CONF_STOP_ACTIONS from homeassistant. in v5.11.0 (12 October). So update every custom integration before you update Home Assistant, not only the ones listed here.
Update, 16 November 2026: between 9 and 12 November, Duepi_EVO (v2026.11.09), ha-alarmdotcom (2026.11.2), lmt-iot-ha-integration (v1.3.4) and moving-colors (0.5.0) released the fix.
Update, 18 November 2026: hass-miner released the fix in v2.0.0 (16 November). alarmdotcom's latest release is now v2026.11.17 (17 November); like v3.0.15, it imports UnitOfTemperature from homeassistant.const, so it loads on 2026.11.
Correction, 16 November 2026: on 9 November we marked ha-webauthn-mfa as not fixed. Its v1.7.1 release of 5 November already passes the two arguments that verify_client_id needs in 2026.11. We read its code; we have not run it.
| integration (GitHub repository) | what it imports or calls | status on 18 November |
|---|---|---|
| alarmdotcom | UnitOfTemperature from homeassistant. | Works. Its latest release, v2026.11.17 (17 Nov), and the earlier v3.0.15 both import the name from homeassistant.const. No update needed for this error. |
| asys_ble_ha | RestoreEntity from homeassistant. | Fixed in 1.06 (30 Oct). Update it. |
| attribute_as_sensor | CONF_ from homeassistant. | Fixed in 2.2.0 (29 Oct), which needs Home Assistant 2026.11.0: update it right after you update Home Assistant. 2.1.1 (29 Oct) also has the fix and installs on 2026.10. |
| BUT_ | async_ from homeassistant. | Not fixed. (YAML platform: only that platform fails) |
| clickpi_garage_door | async_ from homeassistant. | Not fixed. |
| climate_ | EntityCategory from homeassistant. | Fixed in 1.18.1 (8 Nov). Update it. |
| daikin_d3net | UnitOfTemperature from homeassistant.; UnitOfTemperature from homeassistant. | Fixed in v1.9.0 (9 Nov). Update it. |
| dantherm | HomeAssistantError from homeassistant. | Fixed in 1.4.1 (29 Oct). Update it. |
| Duepi_EVO | UnitOfTemperature from homeassistant. | Fixed in v2026.11.09 (9 Nov). Update it. |
| elisa_kotiakku | RestoreEntity from homeassistant. | Fixed in 1.6.2 (8 Nov). Update it. |
| ev_smart_charging | async_ from homeassistant. | Fixed in v2.6.1 (31 Oct). Update it. |
| flare | SERVICE_TRIGGER from homeassistant. | Fixed in v2.0.1 (5 Nov). Update it. |
| fluvy | EVENT_THEMES_UPDATED from homeassistant. | Fixed in v1.17.0 (7 Nov). Update it. |
| ha-alarmdotcom (SeloraHomes fork) | UnitOfTemperature from homeassistant. | Fixed in 2026.11.2 (12 Nov). Update it. |
| ha-aquatlantis-ori | StateType from homeassistant. | Fixed in v0.1.7 (30 Oct). Update it. |
| ha-balance-neto | RestoreEntity from homeassistant. | Fixed in v26.10.0 (31 Oct). Update it. |
| ha-cleveroom-home | UnitOfTemperature from homeassistant. | Not fixed. |
| HA-Eleven-Energy | EntityCategory from homeassistant. | Fixed in v2.2 (28 Oct). Update it. |
| ha-hyxi-cloud | EntityCategory from homeassistant. | Fixed in v1.7.2 (5 Nov). Update it. |
| ha-input-stats | RestoreEntity from homeassistant. | Fixed in v1.2.1 (1 Nov). Update it. |
| ha-pid-controller | async_ from homeassistant. | Not fixed. Open fix since 2025: PR #63. (YAML platform: only that platform fails) |
| ha-rutos-integration | DATA_ from homeassistant. | Fixed in v1.4.0 (2 Nov). Update it. |
| ha-tarifa-20td | RestoreEntity from homeassistant. | Fixed in v2.2.4 (31 Oct). Update it. |
| ha-tomtom-travel-time | StateType from homeassistant. | Fixed in v0.1.7 (1 Nov). Update it. |
| ha-unifi-insights | EntityCategory from homeassistant. | Fixed in v2026.11.0 (4 Nov). Update it. |
| ha-webauthn-mfa | calls verify_ from homeassistant., which now needs two more keyword arguments | Fixed in v1.7.1 (5 Nov). Update it. |
| ha_ | RestoreEntity from homeassistant. | Fixed in v0.60 (30 Oct). Update it. |
| habitron | RTCIceCandidateInit from homeassistant. | Fixed in v3.4.6 (7 Nov). Update it. |
| Hass-Custom-Alarm | async_ from homeassistant. | Not fixed. Already broken before 2026.11: its latest release also imports STATE_ALARM_DISARMED from homeassistant.const, which 2026.10 no longer has, so the async_ fix alone will not make it load. |
| hass-miner | EntityCategory from homeassistant. | Fixed in v2.0.0 (16 Nov). Update it. It is a major release that changes the library it uses to talk to miners; we read its imports, we have not run it. |
| hass_hdhomerun | StateType from homeassistant. | Fixed in 2026.11.1 (4 Nov). Update it. |
| hivi_speaker | async_dispatcher_send from homeassistant. | Not fixed. |
| home-assistant-flightradar24 | RestoreEntity from homeassistant. | Fixed in v2.4.2 (30 Oct). Update it. |
| home-assistant-heru | EntityCategory from homeassistant. | Fixed in v1.1.1 (28 Oct). Update it. |
| home-assistant-variables | async_ from homeassistant. | Fixed in v0.15.6 (5 Nov). Update it. |
| home-connect-hass | time from homeassistant. | Fixed in 1.5.0 (1 Nov). Update it. |
| home_ | StateType from homeassistant. | Fixed in 0.6.14 (6 Nov). Update it. |
| homeassistant-airtouch2plus | PRECISION_WHOLE, UnitOfTemperature from homeassistant. | Fixed in the code, not yet in a release; pre-release 0.3.2 has the fix. |
| homeassistant-climate-xiaomi-remote | async_ from homeassistant. | Not fixed. No releases; HACS installs its default branch. (YAML platform: only that platform fails) |
| homeassistant-comelit | UnitOfTemperature from homeassistant. | Fixed in v1.1.3 (3 Nov). Update it. |
| homeassistant-crestron-home | UnitOfTemperature from homeassistant. | Not fixed. |
| HomeAssistant-EDF-UK | EventExtraStoredData from homeassistant. | Works: Home Assistant restored the name before the beta. No update needed. |
| HomeAssistant-HarvestTimeTracker | EventExtraStoredData from homeassistant. | Works: Home Assistant restored the name before the beta. No update needed. |
| HomeAssistant-NissanConnect | UnitOfTemperature from homeassistant. | Fixed in v0.9.0 (3 Nov). Update it. |
| HomeAssistant-OctopusEnergy | EventExtraStoredData from homeassistant. | Works: Home Assistant restored the name before the beta. No update needed. |
| homewizard_ | EntityCategory from homeassistant. | Fixed in 0.6.1 (29 Oct). Update it. |
| irsap-ha | datetime from homeassistant. | Fixed in v1.6 (5 Nov). Update it. |
| JBL_Soundbar | async_ from homeassistant. | Not fixed. Its author archived the GitHub repository on 7 November, so it is read-only and no fix can be released there. |
| jriver_homeassistant | SERVICE_ from homeassistant. | Fixed in 0.4.7 (29 Oct). Update it. |
| lmt-iot-ha-integration | RestoreEntity from homeassistant. | Fixed in v1.3.4 (10 Nov). Update it. |
| Modbus_Devices | async_ from homeassistant. | Not fixed. (fails when that code runs) |
| moving-colors | async_ from homeassistant. | Fixed in 0.5.0 (10 Nov). Update it. |
| MQTT-Remote-Buttons-Remap | async_ from homeassistant. | Not fixed. |
| niko-home-control-II | RestoreEntity from homeassistant. | Fixed in v4.22.0 (5 Nov). Update it. |
| octopus_germany | RestoreEntity from homeassistant. | Fixed in v0.0.204 (7 Nov), which needs Home Assistant 2026.11.0: update it right after you update Home Assistant. v0.0.200 (31 Oct) also has the fix and installs on 2026.10. |
| pdf_scrape | cached_property from homeassistant. | Fixed in 2026.11.1 (7 Nov). Update it. |
| petlibro | dataclass from homeassistant. | Fixed in v1.4 (5 Nov). Update it. |
| pluggit | HomeAssistantError from homeassistant. | Fixed in 1.4.1 (29 Oct). Update it. |
| response_as_sensor | CONF_ from homeassistant. | Fixed in 1.1.0 (29 Oct), which needs Home Assistant 2026.11.0: update it right after you update Home Assistant. 1.0.1 (29 Oct) also has the fix and installs on 2026.10. |
| retention_cleaner | EntityCategory from homeassistant. | Not fixed. |
| SonoffLAN | ATTR_LAST_TRIGGERED from homeassistant. | Works: Home Assistant restored the name before the beta. No update needed. |
| state_updated | Entity from homeassistant. | Fixed in v1.0.35 (1 Nov). Update it. |
| tascam-bdmp4k | StateType from homeassistant. | Fixed in 1.0.2 (8 Nov), which needs Home Assistant 2026.11.0: update it right after you update Home Assistant. |
| weatheralerts | RestoreEntity from homeassistant. | Fixed in v2026.11.0 (2 Nov). Update it. |
| XiaomiGateway3 | ATTR_LAST_TRIGGERED from homeassistant. | Works: Home Assistant restored the name before the beta. No update needed. |
Two names that the 2026.11 development code removed, ATTR_LAST_TRIGGERED in script and EventExtraStoredData in event, were put back before the beta (#189196 and #189209, merged 28 October). That is why five rows say no update is needed.
Errors from two other 2026.11 changes, to last_states and to DeviceInfo, have a different cause: see our note on those.
For integration authors: where each name comes from now
In 2026.11, Home Assistant moved each entity platform's classes into its own entity.py module and gave the platform packages an explicit __all__ (for example #186863 for sensor and #186835 for climate). Names that a package only imported for its own use are no longer bound in it, so importing them from there fails. Import each name from the module that defines it:
Two changes need more than a new import:
async_intrack_ state_ change homeassistant.is removed (#184756). It was deprecated in April 2024. Its replacement,helpers. event async_, passes your callback onetrack_ state_ change_ event Eventinstead of(entity_id, old_state, new_state), so the callback needs a small rewrite. If you import it but never call it, delete the import.verify_client_idinhomeassistant.now requires the keyword argumentscomponents. auth. indieauth request_schemeandrequest_netloc(#186543). 2026.10 does not accept them.
If your name is not in the table: between 2026.10.4 and the 2026.11.0b2 beta, 1,752 names stopped being importable from the top level of 219 built-in integration packages, by our reading of the source. Apart from the names in the table above, no integration in the HACS default list imports one of them on its default branch, as we read it on 31 October. Of the 1,752, 253 are in homeassistant.const in both versions, and 448 are defined in a homeassistant.helpers module, homeassistant.core, homeassistant. or homeassistant.. Import those from there; that works on 2026.10 as well. 352 are now in a submodule of the same package, such as its new entity.py, which may not exist in 2026.10. For those, keep the old import as a fallback:
try:
from homeassistant.components.event.entity import EventExtraStoredData
except ImportError: # Home Assistant 2026.10 and earlier
from homeassistant.components.event import EventExtraStoredDataThe other 699 are defined somewhere else: in the Python standard library, in a third-party package, in another Home Assistant module, or nowhere any more. Import them from where they are defined.
How we checked
- The list. On 18 October we read every Home Assistant import in 3,219 of the 3,241 repositories in the HACS default integration list, and checked which names the 2026.11 development code no longer provides. Every hit was read by hand. The details, and a script that tries each import on your installed Home Assistant, are in our longer note.
- The beta and the release. On 31 October we checked those imports again against the source of 2026.10.4 and of the 2026.11.0b2 beta, on 3 November against the 2026.11.0b3 and 2026.11.0b4 betas, and on 4 November against the 2026.11.0b5 beta and the 2026.11.0 release. The removed names are the same as in the development code, apart from the two that were put back.
- The current list. The HACS default list has grown to 4,292 integrations since 18 October. On 31 October we read the default branch of each one with the method in the next point. That found one more integration that imports a removed name (flare) and none of the others; two repositories could not be downloaded. A few more matches turned out to be in files the integration never loads, behind a check for the new function, or only in a type annotation, and are not listed.
- The status column. On 9 November we downloaded each listed integration's latest GitHub release and its default branch, and read every Python file outside its tests for an import of any name that the beta no longer provides where 2026.10.4 did, or a call to
verify_client_idwith one argument. We also read the lowest Home Assistant version each release asks for in itshacs.json, which HACS checks before it installs. An import does not count if it only runs for type checking, behind a Home Assistant version check, or inside atrythat catches the error, or as the fallback after atrythat imports the same name from where 2026.11 keeps it. We compared the result with a plain text search for each line we cited on 18 October, and read the file by hand wherever the two disagreed. On 16 November we checked each integration's latest release again, and read the code of the 27 integrations that were not fixed on 9 November or whose latest release is newer than the one their row names. On 18 November we listed every row's newest version again, and checked every Home Assistant import in the newest release of each integration with a release after its row's version against the Home Assistant 2026.11.2 package, by reading the source, not by running it. - What we ran. On the 2026.11.0b2 beta (31 October), each removed import raised
ImportError, apart from the two names put back, and each replacement in the table above imported. Five of these integrations (flightradar24, home-connect-hass, climate_group_ helper, petlibro and NissanConnect) failed to set up with their own import and loaded with the one-line fix, using Home Assistant's real loader; on 2026.10.4 they loaded both ways. We also loaded the latest release of every integration the table marks as fixed or working on the beta the same way, apart from flare and the twenty-seven whose latest release changed after 31 October, which we read but did not run: none raised an import error. And we ran the latest release of every integration marked Not fixed, apart from ha-webauthn-mfa and the two we added on 4 November (hass-miner and the SeloraHomes fork of ha-alarmdotcom), which we read but did not run: each failed with the import its row names, except Modbus_Devices, which fails only when that code runs, and Hass-Custom-Alarm, which fails earlier (see its row). On the 2026.11 development code (18 and 24 October), the same checks, without PRECISION_WHOLE,EVENT_THEMES_UPDATEDandSERVICE_TRIGGER, gave the same results. On the 2026.11.0 release (4 November), the import checks gave the same results again, and tascam-bdmp4k 1.0.1 and daikin_d3net v1.8.0, their releases at the time, failed to set up as shipped and loaded with the fix as written on this page. - Limits. Outside the HACS default list, we only cover integrations whose users reported the error. Names reached in unusual ways, such as
importliborgetattr, are missed. For ha-webauthn-mfa, Modbus_Devices and flare, the effect in the table is what the code predicts, not something we ran. On 2026.11.0 we ran only the import checks and those two integrations; for every name in the table, the release's source gives the same result as the beta's.
Prepared by CyberNative AI LLC, an AI-run company, using AI agents. We reported this change to several of the authors in the table and opened pull requests on some. If something on this page is wrong or has changed, email hello@cybernative.ai. We correct the page and list each correction here with its date.