Please try activating the automatic access point mode in our WiFi/LAN menu, click reboot and remove the ethernet cable from your device. Afterwards (ca. 40 seconds later) a new WiFi network by the name of max2play should appear. Please follow these steps to connect to your wifi network.
To be sure, your phone tablet were also not able to pair with the speakers or not able to pair with Max2Play? The latter would be logical as we have not included pairing input devices via BT in our newest Stretch image.
Ich habe eben mit einem Stretch Image keine Probleme gehabt bei 7.9 nightly. Ich werde versuchen noch einen Tester mit unserem Jessie Image erneut zu testen.
As previously discussed, I will check your key right away here to make sure this is not an error on our part and then give you further instructions via mail. Thank you
Könntest du den Stick nochmal mit einem frischen Stretch Image versuchen zu laden? Die meisten Sticks sollten automatisch erkannt werden, sobald sie eingesteckt wurden. Du kannst dies prüfen im Debug Info Fenster. Dort sollten sowohl wlan0 als auch wlan1 auftauchen. Bitte deaktiviere auch wlan0 in den Raspberry Settings.
Yes, you can use MultiSqueeze to designate different names from the M2P device. Just make sure that the other instance of Squeezelite deactivated from autostart to avoid confusion 😉
Try removing periphery if connected from the Pi and make sure you have a power supply of at least 2.5A connected to rule out insufficient power management.
@Mr: Natürlich, bitte per Mail für weitere Details 😉
@anesthesia: You are running your LMS on the Pi Zero? Could you tell me why you would not prefer your new 3B+? Anyway, please check your router’s web interface, it should have your device and LMS listed in some way. If not, please check the debug info log of the Squeezebox Server menu and paste it here.
@Jens: There does still seem to be a little issue with a WiFi+7″ Touchscreen setup. After the screen is set up with Jivelite in fullscreen and can even access all other players, the web interface is no longer accessible. After a hard reboot, it is accessible again. But we will further investigate.
@Ric: Kannst du springt zum nächsten Player weiter erläutern? Das Problem an sich kann mit der gleichzeitigen Nutzung von WiFi und Bluetooth zusammenhängen. Grundsätzlich ist das Repairing aber eh für den Speaker gedacht und nicht für den Pi. Dieser sollte ja eigentlich durchgehend laufen.
@anesthesia: Could you try setting up a fresh image with our Automatic Access Point Mode? We did not encounter this issue during testing and want to make sure it is not occurring with the auto AP as well in your system.
Worauf beziehst du dich? Im neuen Stretch Image funktionieren sowohl WPS, Automatic Accesspoint Mode sowie die normale Einrichtung des WLAN’s tadellos in unseren Tests.
Viewing 30 posts - 1,831 through 1,860 (of 4,111 total)
English
German
