TJH

Forum Replies Created

Viewing 29 posts - 1 through 29 (of 29 total)
  • Posted in:
  • 22. Januar 2021 at 22:05 #50634

    Hi. Did you ever get this working? Unifi and Max2Play would suit me too.

    15. Mai 2019 at 22:22 #45410

    Any news on this?
    I do run 2 Pi, one for pihole and one for Max2Play.
    I’m tempted to try to get them both on one, but I know I’ll spend hours on it and it won’t work because I’ve done something stupid!
    A plugin would be fantastic.

    8. Dezember 2018 at 15:44 #42614

    Dear Heiner
    Does Maz2play have any plans to support the pHat Beat?
    It looks ideal for a small (lowfi) SBox player – switches and all, like the old SB Radio I have that isn’t goint to live for ever……
    Tim H

    10. April 2018 at 22:47 #35113

    I have downloaded and reinstalled the Jessie image (and updated as suggested on first boot) and the filesystem mount works, LMS works and the printserver works. Yay!

    I’ll keep it as it is for a while without updating anything.

    Thanks for your help and keep up the good work.

    Tim

    4. April 2018 at 0:41 #34955

    Thanks. Please let me know as I need to print!
    I’ll have to go back to a dedicated print server box till it’s fixed 😢

    1. April 2018 at 19:16 #34928

    CUPS printserver is still no good.
    When I use pi/Max2Play I still see:

    Add Printer
    Add Printer Error
    Unable to add printer:
    Forbidden

    ????

    25. März 2018 at 12:03 #34721

    Danke.
    The stretch image works!
    Share mounted OK (only seems to like lower case share name?)
    LMS 7.9 nightly installed ok
    Music and spotify ok

    BUT
    CUPS Printserver not accepting user = root, password = max2play –
    I put it in over and over again without being able to get in to set up printserver –
    eventually it gives up and just tells me that I am forbidden and can’t do anything.
    I’ve also tried User = pi, password = raspberry and a few others.
    I’m using Chrome and have also tried Edge.
    (Could it be something to do with the certificate not being recognised so https isn’t available)

    Any help appreciated.

    • This reply was modified 3 years, 8 months ago by  TJH.
    22. März 2018 at 14:55 #34657

    I did update Max2Play to beta and reinstall the latest nightly 7.9 on 19 March but LMS wouldn’t start as per my last post.

    Is the latest nightly 7.9 LMS not as up to date as the version in Max2Play beta?

    I’ll try redoing the beta Max2Play update without any LMS update and see if the LMS sent with the beta will start.

    In future I’ll just not bother with updates!

    19. März 2018 at 22:49 #34542

    …so after a weekend away, I’ve had another attempt.
    New image burned to new SD card.
    Updated to beta.
    Share name changed.
    Share now mounts OK.

    Latest LMS 7.9 nightly installed.

    LMS won’t start (same error message. apt-get -f -s install doesn’t help).

    Was ist los??

    12. März 2018 at 19:06 #34354

    via Max2Play Run Command

    apt-get -f -s install

    got SBServer to start

    12. März 2018 at 18:31 #34352

    ….also I noticed during the package update

    You might want to run ‚apt-get -f install‘ to correct these.
    The following packages have unmet dependencies:
    logitechmediaserver : Depends: libio-socket-ssl-perl but it is not installed
    E: Unmet dependencies. Try using -f.

    12. März 2018 at 18:28 #34351

    Dear Heiner
    I hope you had a good holiday (and aren’t sitting with two snowboarding broken wrists like me).
    Worse and worse I’m afraid.
    I am trying to start again from scratch.
    1) Latest Max2Play image downloaded and burned onto formatted SC card, Max2Play updated
    2) Pi kernel and packages updated via Max2Play
    3) Max2Play gives error when trying to fix IP address:

    Debug: Saving WPA-Supplicant (Successfully initialized wpa_supplicant Could not read interface wlan0 flags: No such device WEXT: Could not set interface ‚wlan0‘ UP wlan0: Failed to initialize driver interface )
    IP-Address set to 192.168.0.21
    Restarting Interface (especially WLAN0) might take some time (up to 1 minute)!
    Data saved

    4) Share moved and renamed on Seagate NAS (public share called SMusic, running services SMB, NFS and FTP).
    5) New user max2play added to server users, password max2play.

    6) Share won’t mount using cifs

    mount error(22): Invalid argument Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)
    Mountpoint NOT added! Please refer to the description below!
    Path //192.168.0.6/SMusic
    Mountpoint /mnt/smusic
    Type cifs
    Options user=max2play,password=max2play,sec=ntlm,iocharset=utf8

    7) Share will mount using nfs

    Mountpoint successfully added
    Path //192.168.0.6/shares/SMusic
    Mountpoint /mnt/smusic
    Type nfs
    Options (left blank)

    8) Latest Squeezeserver 7.9 nightly installed
    9) Max2Play wont’t start Squeezeserver

    Trying to launch … NOT successful Click here to show detailed information

    We trust you have received the usual lecture from the local System
    Administrator. It usually boils down to these three things:

    #1) Respect the privacy of others.
    #2) Think before you type.
    #3) With great power comes great responsibility.

    sudo: no tty present and no askpass program specified

    10) Haven’t tried getting the printserver working yet

    Any ideas?

    9. März 2018 at 15:14 #34297

    ….and now I can’t even mount //192.168.0.6/media (/mnt/media cifs user=Max2Play,password=Max2Play,sec=ntlm, iocharset=utf8)

    9. März 2018 at 13:41 #34296

    Heiner – it’s all gone again!

    Yesterday I updated everything on the Pi, remounted the NAS share, rebooted (as per lat post) and all my music became visible, got indexed and was available to play. This morning it’s all gone again.

    The music is on a Seagate NAS at //192.168.0.6/Media/Music/Final and then into folders /Artist_Name

    //192.168.0.6/Media is mounted OK in Max2Play as /mnt/media

    Squeezebox server sees /mnt/media/Music/Final but does not see any /Artist_Name folders and does not see or index any music files

    Spotify and podcasts keep on working, it’s just my local network music library that gets lost.

    Any ideas?

    8. März 2018 at 20:40 #34287

    All seems ok now.
    I removed the filesystem mount add in, rebooted the pi, put the filesystem mount back, updated Squeezebox Server to the latest nightly, deleted and readded the NAS share with the same name and credentials.
    Squeezebox Server now sees the files and folders and is busy reindexing 9269 files.
    Who knows what it was, but it’s sorted. Maybe a glitch in the old SBox Server version?

    7. März 2018 at 15:46 #34263

    The share is open to all on my home network and did not need a login.
    It worked with:

    user=,password=,sec=ntlm,iocharset=utf8
    or
    user=name,password=pass,sec=ntlm,iocharset=utf8

    in the filesystem mount box.
    Now either shows as mounted ok in the filesystem mount but the files and folders aren’t visible in Squeezebox.

    I’ll try your suggestions tonight.

    28. November 2017 at 14:38 #32674

    Thanks. I have done the beta update and the kernel has updated ok.

    Are kernel updates essential?

    25. November 2017 at 22:02 #32636

    Danged if I can get the ImageBurner plugin to work as m.max2play suggests:

    utilise my NAS as backup target for all my Max2Play devices.

    I have mounted the NAS backup destination directory apparently successfully (same way I mounted the NAS music directory which Squeezeserver sees OK).
    I have put the mountpoint and a filename into the box at the bottom of the imageburner page (/mnt/Max2Play/Pi.img)
    I get this:

    Installation started – This Messages refreshes every 3 seconds to show current installation status. When finished this message disappears.
    START creating Image to /home/pi/PiServer25-11-17.img
    No valid Device choosen – must be sda or sdb
    FINISHED

    The destination in the message (/home/pi/PiServer25-11-17.img) is not what I put in the box (/mnt/Max2Play/PiServer25-11-17.img)

    The flashing message keeps going and going till I refresh the webpage, when it is replaced by the message that the burn failed and the progressfile is being deleted.

    The debug file contains

    #### FILESYSTEMS SD-CARD ####
    fdisk: cannot open /dev/: Is a directory

    I am obviously missing something important. Any advice?

    23. November 2017 at 20:25 #32607

    there is an option to deactivate the plugins

    I can’t see it. I can only see reset Max2Play to factory configuration.

    23. November 2017 at 19:38 #32605

    Is this fixed yet in the current image download (rather than the beta)?

    20. November 2017 at 16:51 #32551

    Did a clean install of the latest Max2Play image and all now updates OK.

    3 RPis, 3 installs = a whole day reconfiguring (Server Pi2 with HiFiberry Dac+ phone, Zero player with HiFiberry Digi, Pi3 with screen as controller, plus Squezebox and SB Radio). A way of preserving and passing on things like player/server name, fixed IP address, WIFi login, Squeezebox login and plugins details, Spotify login etc etc would save a lot of time. Is there any way Max2Play could ask about these during installation and load them up? (As if you haven’t enough to do already!)

    Thanks for a great system keeping home streaming alive and affordable (ie for those of us not in the Sonos league).

    14. November 2017 at 20:23 #32489

    Lots of configs of course! Squeezebox, Spotify, NAS, etc etc.

    Can I back up all the settings at once then restore them after a clean reinstall?

    14. November 2017 at 14:45 #32481

    I did update Max2Play first and also the non-kernel update but the kernel update still fails with the invalid hash message and the kernel stays at 4.4.20 😞

    13. November 2017 at 10:40 #32442

    At present my active speakers take a digital input (AVI ADM 9.1RS, DAC in speakers, sub out from speakers). The question is whether the Allo Piano would sound better or not.

    First world problem!

    12. November 2017 at 16:30 #32431

    It seems as if Allo 2.1 / Max2Play is still being developed.
    I got excited when I first saw there was a DAC with sub out, but it looks as though it would be wise to wait until it works out of the box and is fully supported.
    Any idea when this might be?

    9. Februar 2017 at 12:15 #26767

    Thank you. Method 1 worked perfectly for the windows 10 pc.

    I still can’t print from my android phone. I’ve started a separate topic to ask which Android print app others find works best.

    Tim

    21. Januar 2017 at 20:31 #26179

    Doh!!!!

    Fixed easily.
    1) Clear browser cookies
    2) Refresh the admin page (//192.168.0.21:631/admin/ for me)
    3) Reenter the correct admin username and password („root“, „max2play“)
    4) Search for printers
    5) Problem solved!

    I hope this helps someone else.

    Tim H

    28. September 2016 at 2:58 #23233

    I’ve just set „Soundcard = sysdefault-snd_hifiberry_dacplus…“ in Squeezelight advanced settings (it was equal-equal)
    SUCCESS
    Not only does Squeezelight start, but there is great sound coming from the HifiBerry digi+

    I have no idea why or how or what it all means.

    Justink – Why not try this too and see if it works for you? Good luck.

    (I can go to sleep late but happy)

    28. September 2016 at 2:34 #23229

    I have a similar problem with a digi+ headphone socket output.
    New Pi3 + HifiBerry Digi+ (jack socket version)
    Clean install of latest Max2Play
    No sound at all from Digi+ output – only from Pi’s own headphone socket.

    I’ve tried all the suggestions – disabled the Pi’s own output, disabled bluetooth, activated the USB soundcard in audioplayer advanced settings, rebooted several times – nothing.

    And now even worse Squeezelight won’t start – error message:
    „Trying to launch … NOT successful Click here to show detailed information
    squeezelite: pcm_params.c:170: snd1_pcm_hw_param_get_min: Assertion `!snd_interval_empty(i)‘ failed.“

    Any help out there please would be appreciated.

    Thanks

    PS
    I’ve mounted the HifiBerry using nylon spacers rather than metal ones. I hope all the conncections between Pi and HifiBerry are via the header pins and metal spacers are not required for a ground connection!
    Also the HifiBerry worked OK when it was in a Pi2, just not in my shiny new Pi3 🙁

    • This reply was modified 5 years, 2 months ago by  TJH.
    • This reply was modified 5 years, 2 months ago by  TJH.
    • This reply was modified 5 years, 2 months ago by  TJH.
Viewing 29 posts - 1 through 29 (of 29 total)