MS4H - Support

[Dütt]

Du verwendest Bookworm das wir aktuell nicht supportet nur in der Beta und ist aber nicht voll getestet. Du brauchst Bullseye steht aber auch so alles im Handbuch.

Gruß Marco

[tollertenya]

Du verwendest Bookworm das wir aktuell nicht supportet nur in der Beta und ist aber nicht voll getestet. Du brauchst Bullseye steht aber auch so alles im Handbuch.

Gruß Marco

Danke hatte wohl das falsche DietPi Image erwischt. Habe jetzt plain Debian 11 installiert und den MS4H umgezogen.

[c4yc0]

hismastersvoice are you willing to accept code contributions?

[hismastersvoice]

4 sure... Depending if the changes don't interrupt other functions

[c4yc0]

OK, so just to make sure - there is no repository I can use? Just files in https://music-server.net/download/install.zip?

[hismastersvoice]

Send me a zip only with the changed files.
I'll check and integrate it.

[c4yc0]

Do you also don't have Spotify albums and bands images in Loxone UI? The reason seems to be that when I access my loxone server locally over IP it immediately switches to their dyns dns (links as https://10-0-2-81.(...).dyndns.loxonecloud.com/#/(...)) which is over https but all Spotify images that music4home are served via http (i.e. http://10.0.2.55:7092/http://10.0.2.....jpg/image.jpg). Having http stuff in a https makes browsers to reject to load it. Having an exception doesn't help. The same problem is in the native app. It seems that music4home sets up this proxy server on 7092 which is over http and this doesn't work well with Loxone. Is it only my setup or a bug?

[Labmaster]

I am not fully into this, but i think that this has nothing to do with the MS4H itself because the Image and Image Proxy handling is done by the LMS itself and not by a component of the MS4H, or am i wrong ???

BTW:
With the LMS Plugin Image Proxy you can modify and add own ImageProxy Server locations to the LMS

[c4yc0]

You are partly right - LMS is managing these images but there is another proxy server at 7092 that sends request to it. These are on musc4home and they forward requests to the one on the LMS.

You can see that also in the link I provided, that you can see in Loxone's html page:

http://10.0.2.55:7092/http://10.0.2.55:9000/imageproxy/https://t.scdn.co/media/derived/rock_9ce79e0a4ef901bbd10494f5b855d3cc_0_0_274_274.jpg/image.jpg

. The first part of the list is http proxy at 7092 - set up by music4home by cors_proxy.createServer().listen(config.cors_port) in opt/music_server/msg/service/music-server/index.js. That's why I suspect it might be problem that other experience when accessing through loxone dyn dns.

[Labmaster]

Sorry, it seems this is related to the MusikServerGateway (MSG) only.
I don't use MSG for good reason, you never know how long this feature will last before loxone will do anything against it.

I only use the LMS Web interface additionally with control from Loxone MS over UDP / VI...

[c4yc0]

Yes, I assumed this topic is MSG support only. I'm curious if other see that problem as well?

[Tombek]

Ich habe ein Raspberry Pi 4 mit DietPi. Darauf habe ich den LyrionMusicServer v9.0.2 sowie die neueste Version von MS4H installiert.
Nach der Installation hatte ich zunächst Probleme mit Apache, da die Webseite nach der MS4H-Installation im Browser nicht richtig angezeigt wurde – dieses Problem habe ich mittlerweile gelöst.

Leider funktioniert die MS4H-Webseite immer noch nicht richtig, da nur das obere Menü angezeigt wird und dieses nicht reagiert.
Dies ist meine erste Installation und ich habe bisher noch keine Soundkarten angeschlossen.

[hismastersvoice]

Du hast vermutlich Bookworm anstatt Bullseye installiert.

[Tombek]

Danke, du hattest recht – jetzt funktioniert es gut.