Miele home assistant core integration

Novan007 · February 14, 2026, 6:18pm

Hello,

I’ve removed the Miele integration and HACs. I’ve restarted Home Assistant. The Miele was already installed through devices and services ( home assistant core), so I didn’t have to log in or enter a password. Is this normal?
Now I see that certain sensors are unknown (onbekend). Is this normal, or does the washing machine need to be tested first for these sensors?

tilz0R · February 14, 2026, 6:23pm

If the integration is built-in, then I recommend you go to the integration and delete your entries. If you used HACS integration, maybe the integration provided different sensors that the HA build-in one.

Home assistant will then (most likely, if auto detect is enabled) show you that new device is available and you can add it.

gingerpale · February 17, 2026, 2:59pm

Not sure this is the right place to put this, but since recent update I have a problem with the Miele Core integration running on Rpi4B. Before I used HACS Miele, but I removed it and installed core integration. This has worked and I still have the entities in my dashboard, but Miele integration is not loaded anymore. I get the following error:

Logger: homeassistant.util.package
Source: util/package.py:187
First occurred: 09:57:27 (3 occurrences)
Last logged: 09:57:33

Unable to install package flatdict==4.0.1: × Failed to build flatdict==4.0.1 ├─▶ The build backend returned an error ╰─▶ Call to setuptools.build_meta:__legacy__.build_wheel failed (exit status: 1) [stderr] Traceback (most recent call last): File “”, line 14, in requires = get_requires_for_build({}) File “/tmp/.tmpaqqWIb/builds-v0/.tmpaeUIBB/lib/python3.13/site-packages/setuptools/build_meta.py”, line 333, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=) ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “/tmp/.tmpaqqWIb/builds-v0/.tmpaeUIBB/lib/python3.13/site-packages/setuptools/build_meta.py”, line 301, in _get_build_requires self.run_setup() ~~~~~~~~~~~~~~^^ File “/tmp/.tmpaqqWIb/builds-v0/.tmpaeUIBB/lib/python3.13/site-packages/setuptools/build_meta.py”, line 520, in run_setup super().run_setup(setup_script=setup_script) ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “/tmp/.tmpaqqWIb/builds-v0/.tmpaeUIBB/lib/python3.13/site-packages/setuptools/build_meta.py”, line 317, in run_setup exec(code, locals()) ~~~~^^^^^^^^^^^^^^^^ File “”, line 1, in import sys ModuleNotFoundError: No module named ‘pkg_resources’ hint: This error likely indicates that [email protected] depends on pkg_resources, but doesn’t declare it as a build dependency. If flatdict is a first-party package, consider adding pkg_resources to its build-system.requires. Otherwise, either add it to your pyproject.toml under: [tool.uv.extra-build-dependencies] flatdict = [“pkg_resources”] or uv pip install pkg_resources into the environment and re-run with --no-build-isolation.
Unable to install package flatdict==4.0.1: × Failed to build flatdict==4.0.1 ├─▶ The build backend returned an error ╰─▶ Call to setuptools.build_meta:__legacy__.build_wheel failed (exit status: 1) [stderr] Traceback (most recent call last): File “”, line 14, in requires = get_requires_for_build({}) File “/tmp/.tmpv3qdzW/builds-v0/.tmpH3c0Dk/lib/python3.13/site-packages/setuptools/build_meta.py”, line 333, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=) ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “/tmp/.tmpv3qdzW/builds-v0/.tmpH3c0Dk/lib/python3.13/site-packages/setuptools/build_meta.py”, line 301, in _get_build_requires self.run_setup() ~~~~~~~~~~~~~~^^ File “/tmp/.tmpv3qdzW/builds-v0/.tmpH3c0Dk/lib/python3.13/site-packages/setuptools/build_meta.py”, line 520, in run_setup super().run_setup(setup_script=setup_script) ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “/tmp/.tmpv3qdzW/builds-v0/.tmpH3c0Dk/lib/python3.13/site-packages/setuptools/build_meta.py”, line 317, in run_setup exec(code, locals()) ~~~~^^^^^^^^^^^^^^^^ File “”, line 1, in import sys ModuleNotFoundError: No module named ‘pkg_resources’ hint: This error likely indicates that [email protected] depends on pkg_resources, but doesn’t declare it as a build dependency. If flatdict is a first-party package, consider adding pkg_resources to its build-system.requires. Otherwise, either add it to your pyproject.toml under: [tool.uv.extra-build-dependencies] flatdict = [“pkg_resources”] or uv pip install pkg_resources into the environment and re-run with --no-build-isolation.
Unable to install package flatdict==4.0.1: × Failed to build flatdict==4.0.1 ├─▶ The build backend returned an error ╰─▶ Call to setuptools.build_meta:__legacy__.build_wheel failed (exit status: 1) [stderr] Traceback (most recent call last): File “”, line 14, in requires = get_requires_for_build({}) File “/tmp/.tmpdI1ian/builds-v0/.tmptCOGhD/lib/python3.13/site-packages/setuptools/build_meta.py”, line 333, in get_requires_for_build_wheel return self._get_build_requires(config_settings, requirements=) ~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “/tmp/.tmpdI1ian/builds-v0/.tmptCOGhD/lib/python3.13/site-packages/setuptools/build_meta.py”, line 301, in _get_build_requires self.run_setup() ~~~~~~~~~~~~~~^^ File “/tmp/.tmpdI1ian/builds-v0/.tmptCOGhD/lib/python3.13/site-packages/setuptools/build_meta.py”, line 520, in run_setup super().run_setup(setup_script=setup_script) ~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^ File “/tmp/.tmpdI1ian/builds-v0/.tmptCOGhD/lib/python3.13/site-packages/setuptools/build_meta.py”, line 317, in run_setup exec(code, locals()) ~~~~^^^^^^^^^^^^^^^^ File “”, line 1, in import sys ModuleNotFoundError: No module named ‘pkg_resources’ hint: This error likely indicates that [email protected] depends on pkg_resources, but doesn’t declare it as a build dependency. If flatdict is a first-party package, consider adding pkg_resources to its build-system.requires. Otherwise, either add it to your pyproject.toml under: [tool.uv.extra-build-dependencies] flatdict = [“pkg_resources”] or uv pip install pkg_resources into the environment and re-run with --no-build-isolation.

I removed the core Miele integration and if I try to re-install it I get:

Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

What am I doing wrong?

gingerpale · February 19, 2026, 7:04pm

I found what was wrong!
For some reason, after deleting the “Miele HACS custom integration” and trying to install the “Miele Core integration” with “settings - devices & services - integrations - + add integration” and typing “Miele” I still got a the “Miele HACS integration” (which has the small orange box icon meaning “custom integration” in it). So after removing the complete /homeassistant/custom_components/Miele folder (with rm -rf /homeassistant/custom_components/Miele) and restarting HA, the correct “Miele Core Integration” showed up! Finally fixed it!