new to Max2Play

Max2Play Home › Forums › Max2Play as Squeezebox (Player / Server) › new to Max2Play

Viewing 18 posts - 1 through 18 (of 18 total)
  • Back to forum
    Posted in: Max2Play as Squeezebox (Player / Server)
  • gls premium
    11. März 2018 at 18:42 #34320

    Hello All,

    I have setup a Raspi3 with 7″ display, in order to replace a dead Squeezebox Radio.
    In the end, this device should be on wifi, and streaming to a BT speaker.
    I burned the image, and purchased a license too.
    Now, I have a few questions.

    1. I have activated wifi beside LAN.
    If I check on my DHCP server I see THREE different IP named max2play.. What is the third?

    2. I see the following open ports:
    Starting Nmap 7.01 ( https://nmap.org ) at 2018-03-11 16:53 CET
    Nmap scan report for 192.168.xx.xx
    Host is up (0.023s latency).
    Not shown: 910 closed ports, 84 filtered ports
    PORT STATE SERVICE
    22/tcp open ssh
    80/tcp open http
    139/tcp open netbios-ssn
    445/tcp open microsoft-ds
    3389/tcp open ms-wbt-server
    5000/tcp open upnp
    MAC Address: B8:27:EB:96:74:BB (Raspberry Pi Foundation)
    I do not use any M$ device on my LAN: how can I remove Samba and all related stuff, so I can close ports 139,445,3389?
    Also, I do not plan to use Kodi on this machine, can I remove it? or should I leave it?

    3. Max2Play connected to the wrong local LMS, how can I switch to the correct one?
    Where are Squeezelite parameters saved?

    gls premium
    11. März 2018 at 22:12 #34324

    ok, #3 is fixed, I found Squeezelite advanced settings in the Player tab

    Heiner premium
    12. März 2018 at 18:04 #34349

    Hi gls,

    1. Please share your debug info log so we can see exactly what the third IP is assigned to.

    2. Manually closing ports or removing parts of Max2Play is not recommended or necessary. As you can see in the Health Checker under Settings/Reboot, the system already runs well. Kodi is just installed and never has to run if you do not need it.

    Another tip: The Pi3 shares an antenna for both WiFi and Bluetooth. So if you want to use both simultaneously, utilizing a WiFi dongle would be recommended.

    gls premium
    12. März 2018 at 19:25 #34356

    Heiner,

    thanks for your kind reply.

    I will share the debug info.
    At the moment, the host is unreachable.
    It looks very unstable, wifi side: first I thought it was too far (8m), then reduced to 4m, then 1m.
    Still, it dies and is lost from the network.
    I had read that simultaneous wifi & bt is not recommended, so I plugged in an USB BT dongle I had around.
    Should I have done it the other way round?

    Also, the Jivelite interface seems to have problems visualizing the menus (wrong resolution?), and does not show the clock when idle.
    I am concerned that the display might degrade, with the same information on all day long.

    -GianLuca

    gls premium
    12. März 2018 at 22:46 #34360

    here is the network information:

    eth0 Link encap:Ethernet HWaddr b8:27:eb:96:74:bb
    inet6 addr: fe80::c73a:d9be:ec41:b71a/64 Scope:Link
    UP BROADCAST MULTICAST MTU:1500 Metric:1
    RX packets:0 errors:0 dropped:0 overruns:0 frame:0
    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)

    lo Link encap:Local Loopback
    inet addr:127.0.0.1 Mask:255.0.0.0
    inet6 addr: ::1/128 Scope:Host
    UP LOOPBACK RUNNING MTU:65536 Metric:1
    RX packets:40 errors:0 dropped:0 overruns:0 frame:0
    TX packets:40 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1
    RX bytes:3348 (3.2 KiB) TX bytes:3348 (3.2 KiB)

    wlan0 Link encap:Ethernet HWaddr b8:27:eb:c3:21:ee
    inet addr:192.168.xxx.83 Bcast:192.168.xxx.255 Mask:255.255.255.0
    inet6 addr: fe80::ba27:ebff:fec3:21ee/64 Scope:Link
    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
    RX packets:7042 errors:0 dropped:0 overruns:0 frame:0
    TX packets:1988 errors:0 dropped:0 overruns:0 carrier:0
    collisions:0 txqueuelen:1000
    RX bytes:574718 (561.2 KiB) TX bytes:1047388 (1022.8 KiB)

    ### WLAN ###
    wlan0 IEEE 802.11 ESSID:“xxxxxx“
    Mode:Managed Frequency:2.437 GHz Access Point: BC:F6:85:66:F4:1C
    Bit Rate=54 Mb/s Tx-Power=31 dBm
    Retry short limit:7 RTS thr:off Fragment thr:off
    Power Management:off
    Link Quality=58/70 Signal level=-52 dBm
    Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
    Tx excessive retries:179 Invalid misc:0 Missed beacon:0

    Jivelite and Display Debug Info are empty.

    This is Raspberry Debug Info:

    #### BOOT CONFIG TXT ####
    # For more options and information see
    # http://rpf.io/configtxtreadme
    # Some settings may impact device functionality. See link above for details

    # uncomment if you get no picture on HDMI for a default „safe“ mode
    #hdmi_safe=1

    # uncomment this if your display has a black border of unused pixels visible
    # and your display can output without overscan
    #disable_overscan=1

    # uncomment the following to adjust overscan. Use positive numbers if console
    # goes off screen, and negative if there is too much border
    #overscan_left=16
    #overscan_right=16
    #overscan_top=16
    #overscan_bottom=16

    # uncomment to force a console size. By default it will be display’s size minus
    # overscan.
    #framebuffer_width=1280
    #framebuffer_height=720

    # uncomment if hdmi display is not detected and composite is being output
    #hdmi_force_hotplug=1

    # uncomment to force a specific HDMI mode (this will force VGA)
    #hdmi_group=1
    #hdmi_mode=1

    # uncomment to force a HDMI mode rather than DVI. This can make audio work in
    # DMT (computer monitor) modes
    #hdmi_drive=2

    # uncomment to increase signal to HDMI, if you have interference, blanking, or
    # no display
    #config_hdmi_boost=4

    # uncomment for composite PAL
    #sdtv_mode=2

    #uncomment to overclock the arm. 700 MHz is the default.
    #arm_freq=800

    # Uncomment some or all of these to enable the optional hardware interfaces
    #dtparam=i2c_arm=on
    #dtparam=i2s=on
    #dtparam=spi=on

    # Uncomment this to enable the lirc-rpi module
    #dtoverlay=lirc-rpi

    # Additional overlays and parameters are documented /boot/overlays/README

    # Enable audio (loads snd_bcm2835)
    dtparam=audio=on
    gpu_mem=128
    dtoverlay=iqaudio-dacplus
    lcd_rotate=2

    # Disable internal BT
    dtoverlay=pi3-disable-bt

    And this is BT Debug Info:

    #### Bluetooth Installation ####

    #### Bluetooth Dongle ####
    hci0: Type: BR/EDR Bus: USB
    BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
    UP RUNNING
    RX bytes:2164060 acl:45 sco:0 events:308897 errors:0
    TX bytes:133095890 acl:463247 sco:0 commands:58 errors:0

    #### DEVICE JBL Spark ####
    [00:1D:DF:D1:88:46]
    Name: JBL Spark
    Alias: JBL Spark [rw]
    Address: 00:1D:DF:D1:88:46
    Icon: audio-card
    Class: 0x240400
    Paired: 1
    Trusted: 1 [rw]
    Blocked: 0 [rw]
    Connected: 1
    UUIDs: [AudioSink, AVRemoteControlTarget, AdvancedAudioDistribution, AVRemoteControl]

    #### PACMD LIST | grep active ####
    active port: <analog-output>
    active port: <unknown-output>
    active profile: <output:analog-stereo>
    active profile: <a2dp>

    #### PACMD LIST | grep sink ####
    Default sink name: bluez_sink.00_1D_DF_D1_88_46
    module.description = „When a bluetooth sink or source is added, load module-loopback“
    module.description = „Automatically restore the default sink and source“
    module.description = „When a sink/source is removed, try to move its streams to the default sink/source“
    name: <module-always-sink>
    module.description = „Mantiene sempre almeno un sink caricato anche se è nullo“
    module.description = „When a sink/source is idle for too long, suspend it“
    module.description = „Load filter sinks automatically when needed“
    module.description = „BlueZ 5 Bluetooth audio sink and source“
    2 sink(s) available.
    name: <bluez_sink.00_1D_DF_D1_88_46>
    bluetooth.protocol = „a2dp_sink“
    name: <bluez_sink.00_1D_DF_D1_88_46.monitor>
    sinks:
    sinks:
    bluez_sink.00_1D_DF_D1_88_46/#1: JBL Spark
    bluez_sink.00_1D_DF_D1_88_46.monitor/#1: Monitor of JBL Spark
    1 sink input(s) available.
    sink: 1 <bluez_sink.00_1D_DF_D1_88_46>
    module-stream-restore.id = „sink-input-by-application-name:ALSA plug-in [squeezelite]“

    #### X-SERVER RUNNING ####
    1

    #### PULSEAUDIO RUNNING ####
    1 S 1000 1000 1 3 80 0 – 42465 – ? 00:01:55 pulseaudio

    #### PACMD LIST-CARDS | DEBUG COMPLETE ####
    2 card(s) available.
    index: 0
    name: <alsa_card.platform-soc_audio>
    driver: <module-alsa-card.c>
    owner module: 6
    properties:
    alsa.card = „0“
    alsa.card_name = „bcm2835 ALSA“
    alsa.long_card_name = „bcm2835 ALSA“
    alsa.driver_name = „snd_bcm2835“
    device.bus_path = „platform-soc:audio“
    sysfs.path = „/devices/platform/soc/soc:audio/sound/card0“
    device.string = „0“
    device.description = „bcm2835 ALSA“
    module-udev-detect.discovered = „1“
    device.icon_name = „audio-card“
    profiles:
    output:analog-mono: Mono analogico Output (priority 100, available: unknown)
    output:analog-stereo: Stereo analogico Output (priority 6000, available: unknown)
    off: Spento (priority 0, available: unknown)
    active profile: <output:analog-stereo>
    sinks:
    alsa_output.platform-soc_audio.analog-stereo/#0: bcm2835 ALSA Stereo analogico
    sources:
    alsa_output.platform-soc_audio.analog-stereo.monitor/#0: Monitor of bcm2835 ALSA Stereo analogico
    ports:
    analog-output: Uscita analogica (priority 9900, latency offset 0 usec, available: unknown)
    properties:

    index: 1
    name: <bluez_card.00_1D_DF_D1_88_46>
    driver: <module-bluez5-device.c>
    owner module: 26
    properties:
    device.description = „JBL Spark“
    device.string = „00:1D:DF:D1:88:46“
    device.api = „bluez“
    device.class = „sound“
    device.bus = „bluetooth“
    bluez.path = „/org/bluez/hci0/dev_00_1D_DF_D1_88_46“
    bluez.class = „0x240400“
    bluez.alias = „JBL Spark“
    device.icon_name = „audio-card-bluetooth“
    profiles:
    a2dp: High Fidelity Playback (A2DP Sink) (priority 10, available: unknown)
    off: Spento (priority 0, available: yes)
    active profile: <a2dp>
    sinks:
    bluez_sink.00_1D_DF_D1_88_46/#1: JBL Spark
    sources:
    bluez_sink.00_1D_DF_D1_88_46.monitor/#1: Monitor of JBL Spark
    ports:
    unknown-output: Bluetooth Output (priority 0, latency offset 0 usec, available: unknown)
    properties:

    unknown-input: Bluetooth Input (priority 0, latency offset 0 usec, available: no)
    properties:

    • This reply was modified 6 years, 8 months ago by gls.
    Heiner premium
    13. März 2018 at 13:51 #34391

    Hi gls,

    – Using either dongle should improve the quality of connection
    – Only the IP address of wlan0 should be visible, are you still having three IP’s?
    – You need to use or install the Joggler Skin in Jivelite, its custom for 7″ RPi Touchscreen
    – You can set up a screensaver in Jivelite’s Settings, there you can also see how it until it should show up

    gls premium
    13. März 2018 at 17:51 #34402

    thanks, Heiner.

    I see only two IPs now on my DHCP list.

    However, it’s not connected to LAN, so I do not understand why it should obtain two addresses from my DHCP.

    Beside that, it’s very unstable.
    After a fresh reboot, I cat /var/log/syslog and crashed the system, ssh port stopped responding and I get „no route to host“.

    Heiner premium
    14. März 2018 at 15:29 #34422

    Hi gls,

    What does the debug info say? Is the second IP listed under any entry?

    Did you look at the Health Checker during the crash? Depending on your setup, if you have too many peripherals connected, the Pi might reach its limit in terms of power management. To rule this out as a source of error, please try recreating the issue without any periphery connected.

    gls premium
    14. März 2018 at 16:44 #34423

    Hello Heiner,

    it’s tricky because if I cat /var/log/syslog it will crash the network and have to pull the plug.

    However, in part of the log I saw many messages like:
    brcmfmac: _brcmf_set_multicast_list: setting mcast_list failed
    which Google relates to a Raspi loosing the network.

    The pages I found are somewhat old, should I do an rpi-update?
    Since the problem is acknowledged, there might be a patch.

    Anyway, at the moment it is connected only to LAN, and I see only one IP address listed, so I suppose the problem it’s in the wlan0 setup.

    I have no peripherals connected, excepting the BT dongle.

    Heiner premium
    15. März 2018 at 12:34 #34445

    Hi gls,

    Thanks for sharing.

    For what purpose are you using SSH? Max2Play is intended to run headless over web interface, so any SSH commands or edits make it difficult for me to recreate your issue and find a universal fix if there could indeed be a general problem.

    You can do a package upgrade in our Raspberry Settings at any time.

    If it’s not a hassle for you, you can try running a fresh image and try to recreate the issue when setting up WiFi via our WiFi/LAN web interface.

    You can check the Debug Info window below to see which adapters are connected and get IP addresses.

    gls premium
    15. März 2018 at 13:38 #34447

    Hi Heiner,

    I agree to re-start from scratch, because now the situation is very compromised: wifi doesn’t work anymore, and the Jivelite display has a wrong resolution, preventing the correct navigation. Too many hard reboots, I guess…

    I use ssh just because I am used to, and have only Linux hosts on my network.

    I will let you know later..

    thanks for your assistance,

    -GianLuca

    gls premium
    16. März 2018 at 22:27 #34488

    Hello Heiner,

    so I did restart from scratch, avoiding any manual intervention via ssh.

    1. burn image, expand image
    2. launch Raspi, eth0 connection
    3. setup wifi (no connection), Squeezelite, update Max2Play (Settings/Reboot)
    4. power off, moved Raspi in wifi range, reboot
    5. wifi so slow it’s no use, power off and reconnect via eth0
    6. from Raspberry/Settings, update&&upgrade, power off
    7. moved to wifi, now speed is ok
    8. install BT plugin, connect speaker, testing ok
    9. later Raspberry became unreachable (wifi crashed?), so I had to connect a keyboard, log in and shutdown -r, avoiding pulling the plug.

    To sum up, still very unstable, still double IP shown in wifi page:
    „Status: WiFi USB adapter status is active. WiFi connection status is active (IP: 192.168.xxx.yy 192.168.xxx.zz)
    (Only WPA/WPA2-Encryption possible)“

    Also, no easy way to reboot from Jivelite: when network crashes, you have to connect a keyboard.

    Last, even after update&&upgrade was executed, I saw a message like „14 packages have been kept back“.
    Is there a way to do a dist-upgrade from the web interface?

    thanks,
    best regards,
    -Gian

    Heiner premium
    19. März 2018 at 13:49 #34531

    Hi Gian,

    No dist-upgrade, we have Stretch Beta that will come out officially soon.

    What router are you using M2P with?

    gls premium
    19. März 2018 at 14:28 #34537

    Hello Heiner,

    my firewall is Ipfire.

    Now, it’s been up for the whole weekend without problems on WIFI or BT, and I was very happy… but.

    I thought it was a good idea to freeze the sd card with the plugin, but when it rebooted, no Jivelite, no webpage..

    I only have port 22 and 3389 open..

    How do I revert to previous state?

    -Gian

    gls premium
    20. März 2018 at 13:02 #34553

    Hi Heiner,

    I’m stuck with the player not working, but have ssh access.

    Have you got a script to revert the sd card to writable?

    It would be nice if the plugins had a compatibility warning.

    Maybe I should have known, but I think it should be clearly stated in the plugin page that the SD cannot be made read only if max2play runs on wifi.

    -G

    Heiner premium
    22. März 2018 at 10:56 #34637

    Hi Gian,

    Did you use the write-only plugin? It should work with WiFi. It does not work with plugins that continously access and write on the SD card like the Squeezebox Server.
    Please try out our new Stretch-based image.

    gls premium
    22. März 2018 at 20:22 #34667

    yes, I did use the write-only plugin.

    I resorted to do the install process all over one more time.. now it’s back in business, but..

    After I put the player to sleep from the LMS web interface with:

    http://myLMS:9000/status.html?p0=sleep&p1=2400

    when I woke up in the morning, Jivelite did not show the hour anymore, just a black screen.. and is still black.

    gls premium
    23. März 2018 at 16:51 #34706

    now it’s back showing the hour… it’s a bit temperamental!

Viewing 18 posts - 1 through 18 (of 18 total)

You must be logged in to reply to this topic.

Register here