Forum Replies Created
-
-
17. Oktober 2017 at 12:37 #31936
Hi guys,
@Aufschlagzuender: Spotty’s Spotify Connect beta feature had been added since version 1.9, so you should definitely have it.@wmrch: Which output device do you use and which version of librespot is active in your plugin? Please also try deactivating WPS, as Foz mentioned.
17. Oktober 2017 at 12:31 #31935Hi foz,
The automatic switch between these players is still being worked on and will probably be available in the next update. Until then, the direct change of output can always cause issues.
17. Oktober 2017 at 11:52 #31932Hallo Reinhard,
Wir konnten nun das Problem der ungewollten Verbindungstrennung rekreieren. Dies geschah nach ca. 30 Minuten. Wir werden versuchen, eine Lösung für diese Problematik zu finden, aber es scheint sich um ein Verbindungs/Stromproblem des Raspberry Pi Bluetooth-Empfängers zu handeln.
Wir werden nun einen weiteren Test vornehmen mit stärkerer Stromversorgung und ohne jegliche Peripherie, um Stromprobleme als Fehlerquelle ausschließen zu können.
17. Oktober 2017 at 11:19 #31929Hallo Daniel,
Höchstwahrscheinlich liegt das Problem an der HDD, wenn diese keine eigene Stromversorgung hat. In diesem Fall empfehlen wir, entweder einen powered USB HUB zu nutzen, oder die HDD an einem anderen Gerät zu betreiben und zu im Netzwerk zu mounten.
17. Oktober 2017 at 11:16 #31928Hi Muchacho,
Bitte deaktiviere noch den gmedia renderer und shaiport, um diese als Fehlerquelle auszuschließen (autostart entfernen, reboot).
17. Oktober 2017 at 11:14 #31926Hi wartel,
Unfortunately, there is currently not any option to do this.
17. Oktober 2017 at 11:12 #31923Hi patrick,
Thanks for the quick follow-up and the detailed problem and fix, much appreciated 🙂
17. Oktober 2017 at 11:09 #31922Hi fa,
What happens when you start Kodi without reinitialize active and after rebooting?
17. Oktober 2017 at 11:04 #31921Hi Alexander,
The WiFi should be the only possible connectivity and you should not be able to access Max2Play otherwise, if you disconnected the ethernet cable right after reboot.
Are you accessing it via HDMI, or did you revert back to ethernet?
Also, if you router is WPS compatible, please try using the WPS push button method with Max2Play: https://www.max2play.com/en/how-tos/how-to-wifi-configuration-with-wps-and-max2play/
17. Oktober 2017 at 10:27 #31920Hi frenchclem,
You can run the LMS on any compatible device. It will recognize the Max2Play players if they are in the same network.
You will find various versions of LMS for Linux. Here, you can find the new version’s current releases: http://downloads.slimdevices.com/nightly/?ver=7.9
16. Oktober 2017 at 17:20 #31906Hi theonlyfoz,
Thanks for the feedback.
Please do try to „reinstall“ with the button on Spotify Connect to get the latest version of librespot in order make sure the issue is not connected to this version.
13. Oktober 2017 at 14:44 #31891Hi Fred,
As mentioned, the name „max2play“ should in fact work as well (as long there is only one „max2play“ in your network).
However, if you are using an ethernet connection, you can also set a fixed IP in our WiFi/LAN menu’s dropdown options.
13. Oktober 2017 at 12:29 #31888Hi Fred,
IP is always your best bet as it cannot be confused.
The slash at the end is only for accessing the web interface via browser as it hinders them from automatically redirecting to the Google search. So when using the Playername, only use the exact wording as in your Playername field.
Naming the port is also not necessary.
Issues with resolving the playername might be connected to your home network’s parsing of your player name or other devices in your environment.
You can try renaming your device to see whether this solves the issue.
However, having the IP entered should not be a problem and would definitely work, which is why we added it as an automatic example next to the field. Why do you want to avoid using the IP?
13. Oktober 2017 at 10:30 #31885Hi bollinim,
Thanks for the follow-up. As stated, we will try to amend this issue in our future release to allow all squeezebox features to work seamlessly with MultiSqueeze, as well. 🙂
13. Oktober 2017 at 10:08 #31884Hi Alexander,
Could you try establishing the WiFi again, rebooting and removing the LAN cable immediately after clicking reboot in the web interface to make sure the Pi does not prioritize the ethernet connection while starting.
12. Oktober 2017 at 16:04 #31877Hi Jochen,
Die Rechte bezogen sich auf die Ordner selbst. Diese sollten alle keinen speziellen Schreibschutz oder Sonderrechte besitzen was lesen und schreiben angeht.
Ansonsten kannst du noch versuchen, einen anderen Benutzer anzulegen, um dies als Fehlerquelle auszuschließen.
12. Oktober 2017 at 15:17 #31876Hi Alexander,
Please check your WiFi/LAN menu’s Access Point Autostart Mode and deactivate it if it’s active (remove the tick and click „save“).
Afterwards, you can check the Debug Info, whether your WiFi connection is properly established. If you still cannot access the internet (you can check by trying to update the system), please share the contents of the Debug Info here.
12. Oktober 2017 at 12:11 #31873Hi bollinim,
We checked out our systems handling of the MAC addresses in detail.
While it does set the same ones for MultiSqueeze per default, these are not identical. So there should not be an issue in your local network.
If you need them to be registered in mysqueezebox.com, you have to manually change the address in the command line options with the parameter
-m YOURMACADDRESS.11. Oktober 2017 at 16:19 #31866Hi nbmorgan,
Thanks for sharing, which issue exactly are you referring to and can you elaborate a little?
11. Oktober 2017 at 15:44 #31864Hi tom,
The fixed IP should definitely work. You do get two IP addresses but this should not be an issue for your services. Please detail which services stop working and we should be able to find the root cause for them.
However, we are working on a more sophisticated solution for this issue in our upcoming new version based on Raspbian Stretch.
11. Oktober 2017 at 13:38 #31862Hi schmefan,
Unfortunately, we have not had the chance to test specific display with our image yet.
But Max2Play is based on Raspbian Jessie, so if you find a guide or driver for this OS, it should work with Max2Play as well.
11. Oktober 2017 at 11:34 #31860Hi mcp,
Your GPIO pins probably overlap with the ones the Pi-DAC uses. Here is an overview of which ones you can use: https://pinout.xyz/pinout/pi_dac
You can change this selection in our Raspberry Settings.
10. Oktober 2017 at 15:46 #31854Hi Mike,
Bitte versuche einmal, die Wiedergabe über Squeezebox Server und Squeezelite zu testen.
10. Oktober 2017 at 12:31 #31846Hallo Reinhard,
Danke für das Angebot. Wir werden das Thema Bluetooth morgen nochmal gründlich besprechen und melden uns dann umgehend hier.
10. Oktober 2017 at 12:29 #31845Hi Muchacho,
Danke für den Log.
Hattest du den zuvor genannten Parameter erfolgreich einfügen können?
10. Oktober 2017 at 12:26 #31844Hi Daniel,
Falls du es noch nicht versucht hast, hier sind noch ein paar hilfreiche Beiträge zum Thema FLIRC: https://www.max2play.com/en/forums/topic/infrared-remote-for-max2play-rpi-squeezebox/
10. Oktober 2017 at 12:18 #31843Hi MrMoeK,
What happens if you click connect again, especially on your end device? The pairing process has to be accepted by the speakers. If you click connect on a red device from the list, the Pi will try to pair this device. If the device is in pairing mode, the listed red device should turn green after pairing.
10. Oktober 2017 at 9:26 #31839Hallo Gebhard,
Erstmal danke für die netten Worte!
Leider können wir keine direkte Aussage treffen bezüglich der Höchstgrenze für den Server-Pi, da diese von vielen verschiedenen Faktoren abhängt in deinem System, auch abseits von Bibliothek und parallelen Streams. Der Konsens ist jedoch, dass der Raspberry Pi 3 die meisten Aufgaben des LMS sehr gut meistert. Dabei kommt dir das MP3-Format auch zu Gute. Ich würde dir empfehlen, einfach mal einen LMS auf dem Pi laufen zu lassen, um zu sehen wie gut es mit deiner Konfiguration klar kommt. 😉
10. Oktober 2017 at 9:20 #31838Hallo Poseidon,
Hast du die Version 7.9 installiert? Bitte gehe außerdem sicher, dass dein BT-Gerät im Web Interface grün erscheint und auf deinem Gerät als gepairt.
Bitte führe außerdem deine bisherigen Schritte aus, damit wir nachvollziehen können, was vielleicht schief gelaufen sein könnte.
-
