core: AVM FRITZ!Box Tools core integration is not working anymore
The problem
After updating to 2021.7.0 The AVM FRITZ!Box Tools core integration is not working anymore. Here the relevant parts of the log:
2021-07-07 16:42:39 ERROR (MainThread) [homeassistant.setup] Setup failed for fritz: Unable to import component: cannot import name 'get_all_profiles' from 'fritzprofiles' (/usr/local/lib/python3.9/site-packages/fritzprofiles/__init__
.py)
and several times
2021-07-07 16:42:49 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration fritz: cannot import name 'get_all_profiles' from 'fritzprofiles' (/usr/local/lib/python3.9/site-packages/fritzprofiles/__init__.py)
2021-07-07 16:42:49 ERROR (MainThread) [homeassistant] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 696, in async_create_flow
integration.get_platform("config_flow")
File "/usr/src/homeassistant/homeassistant/loader.py", line 498, in get_platform
cache[full_name] = self._import_platform(platform_name)
File "/usr/src/homeassistant/homeassistant/loader.py", line 503, in _import_platform
return importlib.import_module(f"{self.pkg_path}.{platform_name}")
File "/usr/local/lib/python3.9/importlib/__init__.py", line 127, in import_module
return _bootstrap._gcd_import(name[level:], package, level)
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 972, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
File "<frozen importlib._bootstrap>", line 1030, in _gcd_import
File "<frozen importlib._bootstrap>", line 1007, in _find_and_load
File "<frozen importlib._bootstrap>", line 986, in _find_and_load_unlocked
File "<frozen importlib._bootstrap>", line 680, in _load_unlocked
File "<frozen importlib._bootstrap_external>", line 855, in exec_module
File "<frozen importlib._bootstrap>", line 228, in _call_with_frames_removed
File "/usr/src/homeassistant/homeassistant/components/fritz/__init__.py", line 17, in <module>
from .common import FritzBoxTools, FritzData
File "/usr/src/homeassistant/homeassistant/components/fritz/common.py", line 18, in <module>
from fritzprofiles import FritzProfileSwitch, get_all_profiles
ImportError: cannot import name 'get_all_profiles' from 'fritzprofiles' (/usr/local/lib/python3.9/site-packages/fritzprofiles/__init__.py)
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 153, in async_init
flow, result = await task
File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 171, in _async_init
flow = await self.async_create_flow(handler, context=context, data=data)
File "/usr/src/homeassistant/homeassistant/config_entries.py", line 703, in async_create_flow
raise data_entry_flow.UnknownHandler
homeassistant.data_entry_flow.UnknownHandler
What is version of Home Assistant Core has the issue?
core-2021.7.0
What was the last working version of Home Assistant Core?
core-2021.6.6
What type of installation are you running?
Home Assistant Container
Integration causing the issue
AVM FRITZ!Box Tools
Link to integration documentation on our website
https://www.home-assistant.io/integrations/fritz/
Example YAML snippet
No response
Anything in the logs that might be useful for us?
see above.
Additional information
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 40 (21 by maintainers)
I have got it working.
Now I have to figure out if the custom HACS Fritzbox Tools integration tool still has any value.
I do not agree. It is good practice to just open an issue so that others see that this issue exists and can help or learn from it. It saved me a lot of time that I first checked if it was a known issue and it also gave me some hints to solve.
Thanks a lot @groenmarsmannetje, your method worked for me as well! It seems there is some incompatibility between the updated core integration and the custom component.
We require that. We don’t support custom components and it pollutes our working field with unrelated things. Making maintainers chasing ghosts and thus wasting time.
You don’t have to agree.
As the above concludes and shows, the custom component installs incompatible dependencies. This is not in our control or anything we can help/improve.
Closing this issue on our end.