Mopidy freezed after choose TTS or Radio in Home Assistant


i would like to ask you.
I have Odroid device with Home Assistant (newest version) and connected speaker over 3,5mm jack.
I’ve installed Mopidy and it’s working fine, but…

  • it’s not possible to udpate it (it’s not main problem)
  • If i choose TTS or Radio from Media, Mopidy freezed…
    I’ve created short video to describe my probelm :slight_smile:

Can you help me please?
And i would like to install spotify extension but i dont know how i can do it :frowning: in Home Assistant

Thank you so much

I can’t tell from a video (log files are better) but it looks like the installation is partly broken but I’ve no idea about how Mopidy works with Home Assistant, I think this is a question for whoever created that integration.

Hi, thank you. I’ve tried reinstall mopidy but still not work.
Here is log files -

s6-rc: info: service mopidy: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service mopidy successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
[20:08:22] INFO: e[32mCreate media folder if not existinge[0m
[20:08:23] INFO: e[32mApply addon settingse[0m
[20:08:23] INFO: e[32mStart Mopidy…e[0m
INFO 2023-04-12 20:08:48,262 [102:MainThread] mopidy.main
Starting Mopidy 3.3.0
INFO 2023-04-12 20:08:48,400 [102:MainThread] mopidy.config
Loading config from builtin defaults
INFO 2023-04-12 20:08:48,404 [102:MainThread] mopidy.config
Loading config from file:///etc/mopidy.conf
INFO 2023-04-12 20:08:48,405 [102:MainThread] mopidy.config
Loading config from command line options
INFO 2023-04-12 20:08:48,453 [102:MainThread] mopidy.internal.path
Creating dir file:///root/.config/mopidy
INFO 2023-04-12 20:08:52,266 [102:MainThread] mopidy.main
Enabled extensions: stream, mpd, m3u, http, iris, radionet, softwaremixer, file
INFO 2023-04-12 20:08:52,266 [102:MainThread] mopidy.main
Disabled extensions: none
INFO 2023-04-12 20:08:53,408 [102:MainThread] mopidy.commands
Starting Mopidy mixer: SoftwareMixer
INFO 2023-04-12 20:08:53,412 [102:MainThread] mopidy.commands
Starting Mopidy audio
INFO 2023-04-12 20:08:53,416 [102:MainThread] mopidy.commands
Starting Mopidy backends: FileBackend, M3UBackend, StreamBackend, RadioNetBackend
INFO 2023-04-12 20:08:53,450 [102:Audio-2 (_actor_loop)]
Audio output set to “autoaudiosink”
INFO 2023-04-12 20:08:53,450 [102:MainThread] mopidy.commands
Starting Mopidy core
INFO 2023-04-12 20:08:53,476 [102:MainThread] mopidy.commands
Starting Mopidy frontends: IrisFrontend, HttpFrontend, MpdFrontend
INFO 2023-04-12 20:08:53,478 [102:IrisFrontend-8 (_actor_loop)] mopidy_iris.core
Starting Iris 3.64.1
INFO 2023-04-12 20:08:53,481 [102:HttpFrontend-10 (_actor_loop)]
HTTP server running at [::ffff:]:6680
INFO 2023-04-12 20:08:53,485 [102:MainThread]
MPD server running at [::ffff:]:6600
INFO 2023-04-12 20:08:53,488 [102:MainThread] mopidy.commands
Starting GLib mainloop

Well, it looks like Mopidy has started up correctly. What messages appear in the logs when the actual error occurs?