Forum Replies Created

Viewing 30 posts - 1 through 30 (of 34 total)
  • 22. November 2016 at 22:31 #24113


    Changed the BT dongle in the Pi ….

    My Pi B seems to struggle and becomes sluggish

    At least it works as a proof of concept

    I assume this would also work with other BT devices (eg. Fire TV)?

    22. November 2016 at 20:06 #24108

    Just tested phone with a BT speaker – phone discovers speaker immediately

    22. November 2016 at 19:30 #24107

    Tried many times! All I get it is the yellow log – nothing on the phone.

    I’ve connected the phone to other bluetooth devices without problems

    I don’t have another phone to try.

    22. November 2016 at 17:51 #24101

    Max2Play is NOT listed

    22. November 2016 at 17:36 #24097

    No message appears on phone.

    22. November 2016 at 16:51 #24093

    Here’s the last lines of the BT log:

    Name: HUAWEI Y3000100
    Alias: HUAWEI Y3000100 rw
    Address: 3C:DF:BD:12:C4:XX
    Icon: phone
    Class: 0x58020c
    Paired: 0
    Trusted: 1 rw
    Blocked: 0 rw
    Connected: 0
    UUIDs: 0000180000001000800000805f9b34fb 0000180100001000800000805f9b34fb AudioSource AVRemoteControlTarget HeadsetAudioGateway OBEXObjectPush HandsfreeAudioGateway PhoneBookAccess

    No pairing and no connection

    22. November 2016 at 16:37 #24092

    I set up speakers earlier this year – worked okay.

    I’ve been down the command-line BT route before – if it works, fine. When it doesn’t, then it’s easy to reduce everything to a complete mess!

    Max2play claim this is simple – not my experience! The onpage instructions are confusing as there is no clear distinction between what’s necessary for speakers versus the stream methods.

    The two routes should be clearly set apart.

    22. November 2016 at 16:09 #24088

    Another fail ….

    Reconnect gives:

    Using BluetoothCTL Manager
    Make sure to set the soundcard of your audioplayers to PULSE (advanced settings Squeezelite) to get them to work with Bluetooth!
    Controller 00:1B:10:00:05:94 max2play default

    Device 3C:DF:BD:12:C4:xx HUAWEI Y3000100
    scan on
    …….. etc

    • This reply was modified 7 years, 3 months ago by castalla.
    22. November 2016 at 15:35 #24084

    Well – day 2 of frustration and head-scratching ….

    Turn BT on smartphone – enters discovery mode – scan from max2play. Phone appears in list in RED

    So what now? Any attempt to connect fails.


    21. November 2016 at 19:15 #24076

    Partial success!

    I now have bluetooth installed!

    Before the stream step – do I simply switch BT on the phone, then scan from max2play for the phone? Is that what you mean by connect the phone and max2play?

    21. November 2016 at 18:19 #24070


    I’ll continue tomoorow. Thanks.

    21. November 2016 at 17:30 #24068

    Nope! I always expand the FS on install.

    I’m now reinstalling LMS, then I’ll install BT again.

    To be clear – for the stream route, I don’t need to mess with any audioplayer setting?

    21. November 2016 at 17:17 #24066

    Thanks – but no help really. This last attempt just refused to install BT = claiming it was ‚finished‘ but no screen indication that it was installed.

    Does this require the beta img or is 2.38 enough?

    21. November 2016 at 16:47 #24058

    I finally realised from all the disparate bits of information that I need the Jessie img.

    However, after installing, updating to the beta, adding the BT module and installing LMS, I am no further forward. The BT install appears to be successful (apart from some blurb about jivelite and pulseaudio ???). However the BT page never shows BT as installed – just repeatedly offers to install BT.

    I am now doing reinstall number 8 of the whole system.

    I only want the server stream feature – no speakers or direct audio.


    21. November 2016 at 14:23 #24048

    I have spent hours attempting to get the new server stream working … the latest failure is:

    Wheezy Image is not supported!

    Update Configfile – existing Entry changed
    bluetooth successfully removed from autostart
    Update Configfile – existing Entry changed
    bluetooth successfully added to autostart

    The install instructions are NOT clear enough.

    I installed bluetooth – then paired my smartphone – then attempted to create the stream

    Nothing – other than the above error message.

    31. März 2016 at 11:22 #19543

    Thanks for the feedback!

    25. März 2016 at 2:40 #19457

    One excellent feature of the max2play setup is that the equalizer works with BT speakers.

    I’ve often found that some BT speakers have poor tone aspects.

    A big plus for max2play!

    24. März 2016 at 21:53 #19455

    I had hoped that the latest ‚Switch audio output on disconnect‘ feature might have improved the BT service for more than 1 speaker. Sadly, no.

    There are still severe problems switching between speakers. Even when it works – which seems almost hit’n’miss – it is far from user-friendly or intuitive. At one point in testing, it was impossible to switch off the speaker until I stopped max2play itself.

    Wouldn’t it be possible to auto-stop squeezelite when a speaker is disconnected, in the same way it could autostart when connected?

    20. März 2016 at 3:01 #19379

    Apart from the above task …. changing the dns in Jessie requires the following:

    Using DNS Servers in Debian/Jessie


    add the line

    name_servers=n.n.n.n (the actual dns nameserver address)

    to /etc/resolvconf.conf

    It should be a lot easier than this!

    • This reply was modified 7 years, 11 months ago by castalla.
    • This reply was modified 7 years, 11 months ago by castalla.
    19. März 2016 at 23:17 #19377

    Adding the line works.

    What a performance!

    19. März 2016 at 23:01 #19376

    Hmmm ….

    To enable SSH login for a root user on Debian Linux system you need to first configure SSH server. Open /etc/ssh/sshd_config and change the following line:
    PermitRootLogin without-password
    PermitRootLogin yes

    Had a look at the file and it doesn’t contain any PermitRootLogin line ???

    19. März 2016 at 22:46 #19375

    No changes. Login as pi, sudo passwd root … changed successfully. Login as root … access denied

    Tried su with root password – changed password again – successful change. Login as root … access denied

    Must need a root login routine enabled.

    19. März 2016 at 22:06 #19373


    Doesn’t work.

    sudo passwd root allows successful change


    access is denied on login


    19. März 2016 at 22:00 #19372


    18. März 2016 at 15:28 #19359

    I still cannot get BT speakers to auto switch.

    I think this is a big minus for the BT function even if it can be done via the max2play gui. Essentially this means in order to switch speakers the user has to have access to the gui – this is clumsy as the normal access to a sb player is via a controller NOT another interface. Once max2play is running it should be left in the background and only accessed for maintainance issues.

    I still think a model based on a unique squeezelite instance associated with a specific speaker would be a more user-friendly solution.

    15. März 2016 at 15:28 #19279

    Thanks – will continue testing!

    14. März 2016 at 19:27 #19266

    Sorry – the latest BETA doesn’t work for me. The speaker shows as connected. But there’s no sound and the stream cannot be paused/stopped. If I reboot, then the stream is still connected (?) and plays from last point but again without sound. All very confusing!

    I sill think the BT implementation needs a rethink – each speaker should start a squeezelite instance when it is connected AND close the instance when it disconnects.

    The normal procedure for sb players is that they appear in the gui listing when they are ON and they disappear when they are OFF.

    At the moment ‚max2play‘ appears permanently in the listing – sort of ‚virtually on‘

    12. März 2016 at 12:49 #19225

    I’m using the Jessie beta 2.28

    12. März 2016 at 2:20 #19222

    I’ve finally got 3 different BT speakers connected and working (I suspect some of my set-up issues mat be due to the usb dongle I’m using).

    After a few hours of testing – which have gone well – I feel there is a fundamental design flaw in the max2play model.

    In essence, using BT speakers turns the speaker into a virtual player. As it stands, max2play appears as one player which is not aware of which speaker is actually switched on. As I experience it, it’s not possible to switch between speakers without rebooting max2play.

    A better model would be to start/stop squeezelite when a BT speaker is actually switched on/off. At the moment max2play appears as a player even if no speaker is actually switched on.

    For static systems this is not an issue – but as most BT speakers are battery powered and are not ‚always on‘ then it becomes an issue.

    11. März 2016 at 20:51 #19219

    I think this needs input from Stephan ! Sorry.

Viewing 30 posts - 1 through 30 (of 34 total)