Error adding integration {"message":"Invalid handler specified"}

[jasjeetsuri]

Describe the bug
Trying to add the integration via devices menu in HA, and get the error:
Config flow could not be loaded: {"message":"Invalid handler specified"}

To Reproduce
Steps to reproduce the behavior:

1. Install latest addon via HACS
2. Add the integration via devices menu
3. Popup returns the error: Config flow could not be loaded: {"message":"Invalid handler specified"}

Expected behavior
Install and ask for the IP of the AVR.

Logging
2024-12-12 18:32:12.095 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading flow for integration yamaha_ynca: No module named 'ynca'

Logger: homeassistant.config_entries Source: config_entries.py:3314 First occurred: 6:56:10 PM (3 occurrences) Last logged: 6:59:45 PM

Error occurred loading flow for integration yamaha_ynca: No module named 'ynca'

In browser console:
HTTP 404 POST http://192.168.1.173:8123/api/config/config_entries/flow

Environment

• Home Assistant operating environment (OS/Container/Supervised/Core): 2024.12.1
• Integration version: v7.13.0
• Last working version (if known): Was working with v7.11.0 and 2024.12.1 release of HA

Additional context
Addon just stopped working today, no changes to my system.

[jasjeetsuri]

I managed to fix it by:

1. Enter HA (k3s) container (k exec -it -n home-assistant home-assistant-d85b95897-zcwz4 -- sh)
2. Run python -m pip install ynca
3. Restart HA
4. Add the Yamaha YNCA integration and follow the wizard

[mvdwetering]

Strange, I got a similar report on another integration of mine where it could not download/install the Python package. No rootcause or solution there found yet.

I wonder what is causing it. Both integrations combined there are well over 1700 installs according to Home Assistant analytics website, so it seems a rare occurrence. Unfortunately I am not having these issues and it is kind of impossible to debug these things from a distance since this is something Home Assistant should take care of.

Only common thing right now between the reports seems to be you both use container install on k3s.