Forum Replies Created
22. November 2016 at 16:51 #24093
Here’s the last lines of the BT log:
Name: HUAWEI Y3000100
Alias: HUAWEI Y3000100 rw
Trusted: 1 rw
Blocked: 0 rw
UUIDs: 0000180000001000800000805f9b34fb 0000180100001000800000805f9b34fb AudioSource AVRemoteControlTarget HeadsetAudioGateway OBEXObjectPush HandsfreeAudioGateway PhoneBookAccess
No pairing and no connection22. 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 ….
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
21. November 2016 at 16:47 #24058
- This reply was modified 4 years, 1 month ago by castalla.
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.
Grrrrrrrrrrrrrrrrrrrrr21. 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.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:
add the line
name_servers=n.n.n.n (the actual dns nameserver address)
It should be a lot easier than this!19. März 2016 at 23:01 #19376
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:
Had a look at the file and it doesn’t contain any PermitRootLogin line ???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.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 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.