-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HomeAssistant: Stream domain is failing to initialize at start #5849
Comments
This is a known issue for the 32-bit ARM archs,. I have added a warning in the wiki page that This is due to the voice assistance introduced in 2023. @jcastang what do you think? |
@th0ma7 is there any chance to build the |
@hgy59 as mentioned on discord, I'll be AFK for two weeks. |
It's an extreme solution and my point was not to remove package :D Stream is loaded as a domain included in manifest for "default_config:" |
@hgy59 re-reading your post, yes that is feasible assuming both ffmpeg and py311 are already built, and using spksrc.python.mk ... You would then need to check if ffmpeg lib really is available then += the associated rpath like what's being done in chromaprint, tvh or comskip to the additional-ldflags... And also symlink a few things i to lib/pkgconfig In effect, re-using what's done in tvh would probably work. Then of course add ffmpeg as spk depend. |
This is an issue for 32 Raspberry Pi too and has some discussions in HA community: |
I'm having the same issue. |
Is this a new Bug?
Package Name
home assistant
Package Version
2023.7.3
Device Model
DJ213J
Device Architecture
ARMv7
Firmware Version
7.1
What happened?
At start HA tries to setup Stream domain wich relies on PyAV.
PyAV fails to build at HA start with this message:
It make HA extremely slow to start as it will try to setup PyAV multiple times.
Reproduction steps
error
...
Install Log
Service Log
No response
Other Logs
No response
The text was updated successfully, but these errors were encountered: