Forum Replies Created

Viewing 30 posts - 181 through 210 (of 266 total)
  • 16. März 2016 at 12:06 #19307

    @q20: never had such an error. Installation and Startup on every testsetup went OK so far. Did you change something else on your SD-Card-image? The error is indicating missing user rights to start the squeezebox server – maybe your installation is broken (SD-card error). In this case you should start with a fresh SD-Card-Image.

    Make sure to install Squeezebox Server Nightly 7.9 (otherwise it won’t start because of missing libraries).

    15. März 2016 at 15:02 #19277

    Hi castalla,

    the addon is just made for one BT-device to be connected at a time. It is not meant to run different squeezelite instances for different BT-devices. Although it is possible to easiliy switch the output to another BT-speaker by:
    – „disconnect“ from currently connected BT-Speakers
    – „reconnect“ the speakers you want to use

    On the Jessie-based Image, once BT-speakers are connected pulseaudio (soundserver) will change to play on the BT-speakers. If no BT-speakers are connected squeezelite will default play on the main soundcard. By this you don’t have to change anything in your settings -> just power on BT-Speakers and they will start to play!

    The Beta should work for you – maybe you changed some settings while playing with different BT-devices? There is a cronjob in the background running every minute, that detects if BT-speakers are connected.
    I just had the problem, that after reconnecting I had to stop and start squeezelite manually, although the output device was correctly set and the squeezelite was running (sounds quite similar to your problem)… maybe I need to add a restart to squeezelite after a successful connection. I think this was mainly because squeezelite was still playing (didn’t pause the stream).

    If you power off your BT-speakers and power on later again (what you do in normal usage), they should be connected automatically and the stream for squeezelite should be pointed to the BT-speakers (after maximium 1 minute).

    14. März 2016 at 12:58 #19252


    At first: Thanks a lot for testing and your impressions!

    Important note for BETA versions:
    There is the SD-Card-Image Beta (Jessie Image) AND the Max2Play Update Beta (> 2.28 for testing). The Max2Play Beta Update can only be run with a activated licence and can be found on the settings page in the web interface. For the Bluetooth Addon there are some changes in the main Max2Play version that are not coming with installation of the bluetooth addon.

    2 different versions of the Bluetooth Addon:
    The Jessie Image and the Old Wheezy based Image of Max2Play do have a complete different Bluetooth Support. Using the latest Max2Play Update both should automatically connect once the BT-device that is choosen on the Bluetooth addon page is powered on. Only the last choosen BT-device will be automatically connected. Right now it is not possible to connect to more than one BT-device at a time. When you want to switch to an other BT-speaker you have to choose it in the BT-Addon (click reconnect).

    You need the Beta-Updates of Max2Play to get the autoconnect functionality for squeezelite without the need of restarting

    I never tested with the RPi V1 but it should work. Your Squeezelite player seems to have trouble to connect to the Alsa bluetooth-device. Your settings are fine and the BT-device is connected (very good). Maybe some other audio player is blocking the audio-device. Try to stop Shairport and Kodi (if running) and restart Squeezelite. If this doesn’t help, you may give the Jessie Image (Beta) from our Download-page a try as this uses another way to play the audio.


    14. März 2016 at 11:14 #19249


    I am sorry, but the licence verification was not available on the weekend due to some changes in our server architecture (bringing SSL encryption). It is now working again. If your licence is not marked as active please remove your email / licence code, click save and enter it again to make sure it is updated and saved.

    : I had to remove your post about how to bypass validation.

    11. März 2016 at 14:58 #19202


    das Raspberry Pi-Image wird leider nicht funktionieren auf dem Pogoplug. Da müsste basierend auf einem Pogoplug Image das Webinterface und die Player installiert werden, was unter umständen allerdings sehr aufwändig ist (bis alles funktioniert). Aktuell gibt es da leider keine Lösung.

    10. März 2016 at 11:42 #19185

    Hi Mike,

    currently only external devices can be used as target.

    Just an idea: You may use a second SD-Card with Max2Play and the Imageburner addon to create and store the image from the „Main“ SD-card.

    10. März 2016 at 11:36 #19184


    the main problem is, that:

    „I still get no video output even for sandard Max2play interface – screen is just blank
    I get a similar error message when trying to start Kodi (as shown below)“

    this is why Kodi is not able to show anything on the screen (as stated in the error message on start up).

    How to fix: Make sure to connect the HDMI-Cable on startup of the XU4 and turn on TV/monitor. Make sure to use a quality HDMI-cable. Some thin cables may not work…

    Hope this helps!

    7. März 2016 at 16:51 #19151


    • most apps are working with the RPi 3 and the current Beta (make sure to update to latest Max2Play-beta)
    • WPS is currently not working with Raspberry Pi 3 integrated WiFi (thanks Bort for investigating) – I think there are some driver issues that need to be solved. External USB-Wi-Fi sticks are working with WPS.
    • I built a bluetooth addon that wants to be tested – if you like you can get it from – this will let you connect to bluetooth speakers and let kodi / squeezelite and other players use it as audio output

    If you want to upgrade to the latest packages, you should call „apt-get update && apt-get upgrade“. This can also be done at the bottom of the web interface on the Raspberry PI Settings Addon.

    I am still testing and preparing to build the final version of Max2Play 2.28. If you experience any problems in the Beta with Kodi 15.2 or other Addons, this is the place to post them 🙂

    All the best

    7. März 2016 at 16:37 #19150


    did you use the Beta-Download of the newest Max2Play for Raspberry Pi 3 (based on Debian Jessie) from the Download Page? This should work out of the Box and Jivelite is already installed.

    1. März 2016 at 17:57 #18950

    Hi Teetertank,

    I did a lot of testing to reproduce your setup, but did not find anything going wrong. The mountpoints where loaded correctly. I added a „unmount“ option to the latest Max2Play-Beta (available from 2.28 in regular Max2Play) that lets you unmount the USB-storage before unplugging it.

    One important note: I always use a powered USB-Hub when connecting hard-drives via USB as the power-supply of the Odroid XU4 might not be strong enough to handle the external hard drive. If you directly connect your hard drives this might be the problem.

    26. Februar 2016 at 16:11 #18781

    Hi Elembee,

    it seems like the squeezebox server is not starting at all. Can you post the Debug Log from the Squeezebox Server page – this should have some details. You may also try to install Squeezebox Server 7.9 nightly.

    Common problem is a full SD-card (no space left, not expanded). If this happens you should start from scratch. You may see if you have space left on the bottom of the settings page (Debug Info) in the web interface.


    19. Februar 2016 at 15:05 #18595

    Hi Malina,

    there should not be any delay or bad quality in airplay with shairport – even on the older Rapsberry Pi B.

    First thing: what version of Max2Play do you use? Did you try it with the latest Max2Play 2.27 from the download page?

    A few ideas:
    – remove squeezelite from autostart and stop it
    – remove kodi from autostart and stop it if it is running
    – check the load of your pi in the Debug output on the settings page of the webinterface (at the bottom)
    – do you have WiFi or LAN connection?
    – do you output audio with HDMI or with a separate DAC or soundcard (if so, try an other sound output)

    19. Februar 2016 at 12:20 #18593

    Noch ein kleiner Nachtrag zum Thema:

    Aktuell ist es mit Max2Play nur möglich Squeezelite und Kodi gleichzeitig laufen zu lassen. Dafür muss in den erweiterten Einstellungen von Squeezelite die Option „nutze USB-Soundkarte“ aktiviert werden. Wichtig dabei ist, dass Kodi eine andere Soundkarte als Squeezelite nutzt. Z.B. USB-DAC/HifiBerry DAC oder AMP für Squeezelite und HDMI für Kodi.

    Zum Aktivieren von Airplay über Squeezelite bietet sich das Addon Shairtunes an, welches auf der Squeezebox Server Seite im Webinterface einfach installiert werden kann. Danach wird Shairport nicht mehr benötigt und Airplay über Squeezelite und Kodi sind gleichzeitig möglich.

    16. Februar 2016 at 17:23 #18525

    Hi azr,

    manually running in a browser works, but a call by a machine (Squeezebox Server) might be interrupted by Googles abuse system as stated here:

    What you can do as a workaround:
    – install your own Text-to-speech software on the raspberry (e.g. espeak) with
    apt-get update && apt-get install espeak

    – generate WAV-Files by calling the text-to-speech-engine the following way and save to your media-path

    /usr/bin/espeak "zefix+noch+eins" -w /media/yourtext.wav
    # get more infos with: espeak --help
    # set language, voice, speed and more...

    – make sure the Squeezebox Server is not trying to convert the files: deactivate flac and mp3 in Squeezebox-Server Settings -> Advanced -> File types -> WAV (I had to do this, otherwise it did not play sound)

    – test and play the generated file

    You may also create your own HTTP-service that acts the same way like the Google TTS Engine and creates the WAV-file. You could do this by creating a Max2Play-Addon that takes the words as HTTP-GET Parameter, runs espeak and generates the WAV-File in the background and sends it as result of the HTTP-Call (if the file already exists it would just send it). The Addon should also have a installer for espeak and a basic set up (default language, voice, reading speed).

    Maybe anyone likes to implement this feature? I could help you with special questions. There might be others waiting for this one 🙂


    12. Februar 2016 at 11:14 #18468

    Hi noop and asplundj,

    thanks for sharing your scripts!

    If you like to add this feature to Max2Play you could contribute to the Github project of Max2Play.

    There is one thing, that could be improved to use the capabilities of the Max2Play-Framework: Max2Play automatically runs the script „/opt/max2play/“ as cronjob every minute. This script looks for autostart parameters and can be used to run your script too (instead of doing the loop every 10 sec and permanently running the script).

    In your scenario it would be easy to add a checkbox on the Kodi page of the max2play web interface that sets a parameter (e.g. AUTOSTART_STOP_KODI_BY_HDMI_STATUS) in /opt/max2play/autostart.conf to make the script run optional and to activate / deactivate it with the web interface.

    To add a checkbox to the kodi page you should have a look at this 2 pages:

    view file to add checkbox in HTML:

    Autostart/Stop Kodi by HDMI Status: <input type="checkbox" <?php if($sp->view->AUTOSTART_STOP_KODI_BY_HDMI_STATUS) echo "checked"; ?> value="1" name="AUTOSTART_STOP_KODI_BY_HDMI_STATUS" />

    controller file to set parameter AUTOSTART_STOP_KODI_BY_HDMI_STATUS in /opt/max2play/autostart.conf

    there is an easy function for setting a Parameter in a file (add this to the existing „save“ action in Xbmc.php):

    if($_GET['action'] == 'save'){							
        $this->selectAutostart(isset($_GET['autostart']) ? 1 : 0);
        // Set selected Status
        $this->saveConfigFileParameter('/opt/max2play/autostart.conf', 'AUTOSTART_STOP_KODI_BY_HDMI_STATUS', isset($_REQUEST['AUTOSTART_STOP_KODI_BY_HDMI_STATUS']);
    // Get Status for Checkbox in view file (add this at the End of the function __construct)
    $this->view->AUTOSTART_STOP_KODI_BY_HDMI_STATUS = $this->getConfigFileParameter('/opt/max2play/autostart.conf', 'AUTOSTART_STOP_KODI_BY_HDMI_STATUS');

    The parameter for the autostart can be checked in the script „/opt/max2play/“ and run your script if set to 1.

    # Add this to /opt/max2play/ 
    AUTOSTART_STOP_KODI_BY_HDMI_STATUS=$(cat /opt/max2play/autostart.conf | grep AUTOSTART_STOP_KODI_BY_HDMI_STATUS=1 | wc -l)
         /opt/max2play/ &
    14. Dezember 2015 at 16:13 #17325

    Super – freut mich! Vielen Dank für die Anleitung zu der Konfiguration von Alsa mit den Bindings.

    14. Dezember 2015 at 14:30 #17322

    Hallo Tim,

    aktuell gibt es im Webinterface keinen Parameter den du dafür direkt nutzen kannst. Allerdings gibt es die Funktion, die den Squeezelite Player deaktiviert, sobald über Shairport ein Stream abgespielt wird. Diese Funktion kannst du „umbasteln“ damit es die GPIO Pins anspricht.

    Der Punkt, an dem du ansetzen kannst, ist in dem Max2Play Startscript von Shairport /etc/init.d/shairport in der Zeile 20, die die „on-start“ und „on-stop“ Parameter beinhaltet. Darin kannst du deine eigenen Scripte mit Parametern hinterlegen.

    if [ ! "$LMSIP" = "" ]; then
        SHAIRPORT_OPTIONS="--on-start '/opt/max2play/ shutup' --on-stop '/opt/max2play/ resume'"

    Dann schaut das z.B. so aus (die if-Anweisung rausnehmen)

    SHAIRPORT_OPTIONS="--on-start '/opt/ activate' --on-stop '/opt/ deactivate'"

    Viele Grüße

    11. Dezember 2015 at 15:52 #17289

    Hallo kippi,

    mit dem Multisqueeze Addon bist du daran gebunden, welche Ausgabemöglichkeiten der Squeezelite Player sieht. Auf der Audioplayer Seite hast du ganz unten eine „Debug“ Ausgabe, die alle Soundausgabemöglichkeiten zeigt. Auf der Konsole siehst du es z.B. mit /opt/squeezelite/squeezelite -l

    Wenn die Soundkarte es unterstützt einzelne Kanäle (z.B. Front Links) mit separaten Inhalten zu bespielen, könntest du eine Alsa-Konfiguration dafür erstellen bzw. die existierende ändern. Diese sollte dann auch Squeezelite erkennen. Wie genau das geht, kann ich leider nicht sagen, allerdings könntest du diese Frage z.B. im Squeezebox Forum stellen. Hier findet sich bestimmt jemand der dabei helfen kann.

    11. Dezember 2015 at 15:44 #17288

    Hallo Tim,

    die Schwierigkeit liegt an der Erkennung, ob Musik abgespielt wird.

    Das ist mit Shairport (Airplay) relativ einfach, da man hier Start- und Stopparameter übergeben kann, die jeweils Scripte ausführen wenn ein Stream startet oder stopt. Wenn es dir also nur um Shairport geht, dann ist es kein Problem damit die GPIO Pins zu schalten. Dazu bearbeitest du z.B. das Startscript unter /etc/init.d/shairport (allerdings kannst du dann keine Max2Play-Updates mehr durchführen)

    Mit Squeezelite und anderen Audioplayern kenne ich leider keine verlässliche Möglichkeit, den Zustand (spielt ab / pause) zu erkennen.

    11. Dezember 2015 at 15:38 #17287

    Hi elemay,

    it is not that difficult (little programmer skills required) to create some buttons or a new menu in Jivelite. You may have a look at the „Kodi Control“ Addon that I created to start / stop Kodi on the device. You should have a look at the files in the Jivelite applets folder:


    To create a new menu for your FHEM control, you should start with copying an existing applet, rename it and start playing… There is some documentation on LUA development on other websites.

    One thing you might also be interested in is coming within next weeks: voice control via Siri or Google Now. With a Z-Wave-Server running on Max2Play you can also control FHEM via HTTP-Calls with Apples Siri.

    10. Dezember 2015 at 12:46 #17228

    Hi Olly,

    I never really used the type NFS to mount any folders on a media device at home. Instead I always use SMB/CIFS as this is really easy. The help instructions are really misleading on this (just changed this for the current BETA and the next release), thanks for pointing this out!

    You might try setting up a simple SMB-Share on your Diskstation (with a user login) and connect to this (probably fastest solution).

    If you want to stick to the NFS Type and the mounting on Max2Play says everything worked fine, you may check if the Setup of your NFS-Share on the Diskstation is complete (try accessing the NFS share from another computer in your network).

    @Claudio: Thanks for your input! I added the „*“ option to the help instructions.

    9. Dezember 2015 at 18:58 #17215

    Hi giacva,

    Please update to the latetest Max2Play Beta (on settings page) and Update Kodi again („Start installation“ on Kodi-Tab of web interface). Afterwards the PVR-Plugins from Max2Play Repository should work.

    Background: There was a recent update by the developers of kodi-platform (changed the name of a library) that is needed to run the PVR-Addons. Otherwise it will bring that DLL-Error (missing library


    9. Dezember 2015 at 18:52 #17213

    Hi Olly,

    usually it’s easier to use the cifs mount option instead of nfs. The shared folders in your diskstation should be set up very easy with cifs.

    If you want to stay with nfs try following:
    – set the Path to „“ (remove „//“ in front)
    – remove all options (user and password are not set with nfs and will result in an error)
    – set the mountpoint to „/mnt/mountdir“. I just changed this in the Max2Play-Beta, that it automatically creates subfolders and its parentdirectories if these are not existing.


    9. Dezember 2015 at 16:08 #17201

    Hallo fblu,

    wenn bei dir trotz des Kernelupdates und der Installation der aktuellsten Jivelite-Version die Backgroundbeleuchtung mit dem BlankScreenSaver von Jivelite anbleibt, dann kannst du mal versuchen auf der Konsole (über SSH einloggen) den Befehl „per Hand“ zu testen:
    – Wichtig ist, dass die Datei „/sys/class/backlight/rpi_backlight/bl_power“ existiert
    – Mit dem Befehl „echo 1 > /sys/class/backlight/rpi_backlight/bl_power“ (in die Datei wird der Wert 1 eingetragen) sollte die Beleuchtung ausgeschalten werden

    Falls die Datei vorhanden ist, aber das Abschalten nicht funktioniert liegt es ggf. am Netzteil oder Kabel. Siehe auch der Post von malf_21.

    26. November 2015 at 18:59 #17042

    Hallo malf_21,

    das scheint ein Problem mit der Stromversorgung zu sein. Für das Display solltest du ein 2A Netzteil verwenden und bei zusätzlichen anderen Verbrauchern ggf. ein zusätzlichen USB-Hub mit separater Stromversorgung verwenden.

    Viele Grüße

    26. November 2015 at 13:14 #17039

    Please Update Max2Play to the latest version (2.25) and the plugins should update too.

    26. November 2015 at 12:25 #17037

    Hi RichG,

    the option is in the „RPI Display“ Addon. You have to uncheck „LCD as Default Display“ and then it will output to HDMI.

    20. November 2015 at 13:59 #16976

    CEC für Jivelite zu aktivieren ist sicher möglich. Allerdings geht das nicht mit dem 7″ Display sondern nur über HDMI an einem angeschlossenen TV. Ich werde das mal testen und ggf. in Jivelite als Option hinzufügen.

    20. November 2015 at 12:47 #16971

    Hallo zusammen,

    danke für die Infos in diesem Thread. Da die aktuelle Max2Play-Kernelversion wie von Manfred geschrieben diese Funktion noch nicht unterstützt, bin ich gerade dabei einen neuen Kernel mit der Backlight-Unterstützung zu erstellen. Diesen werde ich dann noch testen und als Update im RPI-Display-Plugin Mitte nächster Woche zusammen mit einem Max2Play Update zur Verfügung stellen.
    Dabei wird es auch ein Update für Jivelite geben, damit hier automatisch die Hintergrundbeleuchtung deaktiviert wird, sobald der schwarze Bildschirmschoner (BlankScreensaver) aktiv ist.

    Viele Grüße

    • This reply was modified 8 years, 7 months ago by flysurfer.
    19. November 2015 at 12:15 #16962

    Hi Olaf,

    the hardware choice depends on what you need / want. Basically I would recommend a Raspberry Pi for player purpose as it offers more options for soundcards (DACs and AMPs) and community support is better. Also the system itself is more „stable“. The Odroid C1+ supports just the HifiShield (DAC) from hardkernel (quality is similar to the HifiBerry DAC+).
    Max2Play only supports the 3.2 inch Touchscreen Display Shield for the C1+. Software like Jivelite need some settings to display properly on small displays – this is why this thread mentions a skin for a 2.8″ display, that is needed to show Jivelite correct on the 3.2″ display.

    You may have a look at our shop as we offer different bundles that work very well together with Max2Play.

Viewing 30 posts - 181 through 210 (of 266 total)