Squeezelite plugin xml template

[J V]

Hello,

I'm at the moment unable to run a Loxberry, but would like to work on integrating e.g. the Squeezelite plugin. On the wiki it says

http://www.loxwiki.eu/display/LOXBERRY/Squeezelite+Player

-
Für die erforderlichen UDP Eingänge stellt das Squeezelite Player Plugin direkt das Template für die Zonen deiner Logitech Media Server Installation bereit (achte darauf, dass beim Aufruf alle Player verbunden sind).

Lade mit dem Link unten dieses Template herunter und speichere es in den Ordner C:\ProgramData\Loxone\Loxone Config <version>\Templates\VirtualIn\VIU_LMSGateway.xml
-
and
-
Mit Klick auf den Pfeil nach rechts (bei jeder Zone) wird eine Vorlage für virtuelle Ausgänge für diese Zone heruntergeladen. Speichere diese Vorlagen im Ordner C:\ProgramData\Loxone\Loxone Config <version>\Templates\VirtualOut\VO_LMS_<Zonenname>.xml
-
My German is limited, but I understand that it means that you can generate an xml template for a given zone, one for virtual inputs and one for virtual outputs. Is it possible to post such these xml templates? I know I will have to modify it manually (mac address, zone name, ...), but at least I would have the correct virtual outputs and can continue integrating them.

Thanks!


Jörg

[Christian Fenzl]

Hi Jörg,
the templates are generated with the known players of your LMS installation.

This is the template for the VO template generator. You have to replace the variables.

https://github.com/christianTF/LoxBerry-Plugin-squeezelite/blob/dev/templates/multi/virtualout.xml

[J V]

Thanks, exactly what I need! (I intend to replace my current implementation that uses EventGhost as an LMS gateway with Loxberry, but I can start with using the same commands)
I did not know it was online already...

Is there also one for the virtual inputs?


Jörg

[Christian Fenzl]

VI's are not a template like VO's - they are directly generated in the code (https://github.com/christianTF/LoxBe...atebuilder.cgi Line 150).
But they are specific to what my plugin sends.

[J V]

Yes, I phrased it wrong... I also have this huge list of virtual inputs now and it is a shame that they are appearing in more or less the order they were created (no way of reordering or grouping them - it would be so nice to just have folders there). They are mainly for having buttons in Loxone that can be tied to a command or non-squeezebox devices though.

The code you linked shows me how you name the inputs you have, but I get most of that data directly from the xap plugin on LMS and parsed directly in Loxone. The main thing would the information on the currently playing song, for which I use I was using virtual http text inputs that are set using EventGhost (it parses the data from the xap packet and sets the string using the http input). I suspect you do something similar in your plugin (I found "usehttpfortext"), is that the case? And if so, how did you name the virtual text inputs?

Thanks!

[Christian Fenzl]

Yes, texts are sent via http.
Here is a screenshot how my plugin expects the virtual text inputs: http://www.loxwiki.eu/display/LOXBER...teing%C3%A4nge

[J V]

Thanks! So they are called LMS <mac> name, and same for title and mode.
This really helps me. It is a bit difficult to develop a new config from a distance (and without access), but knowing the correct names should already help me a lot. I will match the names of the inputs I have where possible, that should make the change to Loxberry easier later on. For sure there will be a big testing phase once I try the finished config, but as these are things I have played with (and got working), I should not have many issues.

Thanks again!