Missing requirement on 2026.2.1

[jonare77]

The problem

Getting this after 2026.2.1 upgrade.

Logger: homeassistant.setup
Kilde: setup.py:278
Første forekomst: 23:27:34 (1 occurrence)
Sist logget: 23:27:34

Setup failed for custom integration 'miele': Requirements for miele not found: ['flatdict==4.0.1'].

Version of miele integration having the issue?

2025.12.0b0

Version of Home Assistant Core having the issue?

2026.2.1

Anything in the logs that might be useful for us?

Tried last stable version and now latest beta of integration.

Additional information

No response

[astrandb]

The third party library is obviously not compatible with latest version of HA.

Note that this integration is deprecated and will not receive any updates by me (if someone makes a PR I may consider to merge it).

I strongly recommend that you switch to the official core integration. https://github.com/astrandb/miele?tab=readme-ov-file#important---moving-to-home-assistant-core

[jonare77]

Thanks for reply, havent been to active with HA lately and this has passed me bye. Will move to core intergration.

[brandmail]

The third party library is obviously not compatible with latest version of HA.

Note that this integration is deprecated and will not receive any updates by me (if someone makes a PR I may consider to merge it).

I strongly recommend that you switch to the official core integration. https://github.com/astrandb/miele?tab=readme-ov-file#important---moving-to-home-assistant-core

Hi @astrandb,

Thanks for your reply. But with both intergrations I get the errors:

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

2: Import from configuration.yaml not loaded

Installation method
Home Assistant OS
Core
2026.2.1
Supervisor
2026.02.1
Operating System
17.0
Frontend
20260128.6

Logs:

Logger: homeassistant.setup
Source: setup.py:425
First occurred: 07:58:29 (1 occurrence)
Last logged: 07:58:29

Error during setup of component miele: 'miele'
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/setup.py", line 425, in _async_setup_component
result = await task
^^^^^^^^^^
File "/config/custom_components/miele/init.py", line 401, in async_setup
cache = config[DOMAIN].get(

KeyError: 'miele'

Logger: homeassistant.config_entries
Source: config_entries.py:3969
First occurred: 07:59:47 (1 occurrence)
Last logged: 07:59:47

Error occurred loading flow for integration miele: Platform miele.config_flow not found

[astrandb]

Did you follow the above instructions in detail??

The log message indicates that you have not revoed the old integration properly:

File "/config/custom_components/miele/init.py", line 401, in async_setup
cache = config[DOMAIN].get(

That code line does not exist in neither this custom integration nor in the core version. You must have been using some other miele integration. I am sorry that I cannot help you with how to clear out any remnants of that integration.
But try this:

• You must remove the directory custom_components/miele and all files therein.
• You shold also look in your configuration.yaml and look for a [miele] section. Remove this section if present.
• Then restart HA before installing the core integration.

[brandmail]

Did you follow the above instructions in detail??

The log message indicates that you have not revoed the old integration properly:

File "/config/custom_components/miele/init.py", line 401, in async_setup
cache = config[DOMAIN].get(

That code line does not exist in neither this custom integration nor in the core version. You must have been using some other miele integration. I am sorry that I cannot help you with how to clear out any remnants of that integration. But try this:

• You must remove the directory custom_components/miele and all files therein.
• You shold also look in your configuration.yaml and look for a [miele] section. Remove this section if present.
• Then restart HA before installing the core integration.

@astrandb Thank you again for your answer, but I did everything what you mentioned. It's weird that it broke after the update :( .

The above error message is not anymore, but when I want to setup a new installation I get: Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

[trader-payne]

Can confirm too that the latest update borked it.

[brandmail]

@astrandb , I spoke to multiple people and they have exact the same problem as me. So it's now not only me. fyi

[astrandb]

@brandmail I don't doubt that there are more people with problems. The root cause is that this custom component relies on a thrird party library flatdict. For reasons that I don't know it does not load properly in recent versions of Home Assistant. Perhaps due to incompatibility with latest python release. I can't do anything about that until the library is updated by it's maintainer.

And finally, this custom_component is deprecated and has not got any material updates since the official core integration was released last spring. I am a volonteer in these projects and my capacity to give detailed, individual support to users is limited.

My firm recommendation is: Don't use this custom component anymore. Migrate to the core version. If you install it on a clean HA system it works for >10000 people. I just did that again and verified that it still works.

[brandmail]

@astrandb That means if you have the problem, you must reinstall Home Assistant, to provide a clean setup of Home Assistant?

And I already tried to install the core installation, delete every custom install and files that comes with that.

[trader-payne]

Update for my setup:

I ended up deleting the integration from HACS and cleaning up the config folder with the Miele leftovers, then installed the integration again via the HA store, and it works fine now

[astrandb]

@brandmail I think you have missed a step or done things in wrong order when you did the migration. The result is that files from previous integrations are left in the system and these remnants cause unpredictable behavior. I am sorry that I can’t help you as I don’t know what is left in your system.

[guschc]

I first experienced the same issue. Then simply followed the steps described somewhere here on how to move to the core version (more or less). It worked. It's a bit annoying that the entities changed names and on my dashboards I have a lot of "entity not found" entries now, but the error when starting the old Miele integration is gone.

[astrandb]

@guschc Good to hear that it works for you.
I fully understand the annoyance that entity have changed names. This is caused by a few internal changes that was necessary to comply with the requirements to get the integration accepted in core. However there is a migration function in the latest beta of the custom component that fixes 80-90% of these issues, but as the whole component cannot be loaded it doesn’t help much.

[brandmail]

It spontaneously worked for me, nothing I've changed... But for now working via the core one.