Bluetooth audio

[Cctbrkr]

Hey guys!
Loving volumio and ironing out my soundsystem issues.

Final issues I’m finding is streaming Bluetooth connects fine and works a treat but after ~2mins drops out. The device still remains connected but the audio drops out and won’t return until you repair.

It seems others with raspberry experience this and I’m not afraid to install some scripts but thought I’d check here first.

Any tips or tricks?

[Cctbrkr]

Still experiencing this issue with new Version and with other bluetooth devices. Anyone had similar problems?

[wazzubrad]

I found your post via search because I am having the same issue. I have tested my tested my setup using multiple devices which can connect via Bluetooth (LG TV, iPhone, iPhone) and all three devices will stop playing the audio through the speakers after 1-3 minutes. You can see that each song I play continues to play although no sound is coming from the speakers. If I pause the track and the push play again, the sound will come back. Not sure how to access Bluetooth logs yet and also not sure if this is a Volumio or RPI issue yet.

[mcewan71]

I have the same issue. I am trying to use a Pi with Volumio installed to play sound from a Bluetooth enabled TV. I might get a few seconds on very low volume then it stops. This is a really dumb question - but do I need to attach a Linux compatible Bluetooth adapter to my Pi to get this working??

[mgafner]

Same issue here with Volumio 3.179

i enabled ssh and checked the log with this command:

sudo journalctl -f

the drop out always happens at this part of the log:

Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: Tunnel connection is inactive, restarting it
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: Starting Tunnel 1
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: Starting Tunnel Connection Checker
Jan 20 22:22:33 volumio-3.179 sudo[2200]: volumio : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/bin/systemctl restart sshtunnel.service
Jan 20 22:22:33 volumio-3.179 sudo[2200]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jan 20 22:22:33 volumio-3.179 autossh[2129]: received signal to exit (15)
Jan 20 22:22:33 volumio-3.179 systemd[1]: Stopping MyVolumio SSH Tunnel…
Jan 20 22:22:33 volumio-3.179 systemd[1]: sshtunnel.service: Main process exited, code=killed, status=15/TERM
Jan 20 22:22:33 volumio-3.179 systemd[1]: sshtunnel.service: Succeeded.
Jan 20 22:22:33 volumio-3.179 systemd[1]: Stopped MyVolumio SSH Tunnel.
Jan 20 22:22:33 volumio-3.179 volumio[1315]: ------------------------------------ BT MESSAGE: BT STATUS: running
Jan 20 22:22:33 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: Playing: false
Jan 20 22:22:33 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: VOLATILE: bluetooth
Jan 20 22:22:33 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: STATE:undefined
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreCommandRouter::servicePushState
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreStateMachine::pushState
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreCommandRouter::volumioPushState
Jan 20 22:22:33 volumio-3.179 volumio[1315]: verbose: UNSET VOLATILE
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: Bluetooth Detach Command
Jan 20 22:22:33 volumio-3.179 systemd[1]: Started MyVolumio SSH Tunnel.
Jan 20 22:22:33 volumio-3.179 sudo[2200]: pam_unix(sudo:session): session closed for user root
Jan 20 22:22:33 volumio-3.179 autossh[2203]: port set to 0, monitoring disabled
Jan 20 22:22:33 volumio-3.179 autossh[2203]: starting ssh (count 1)
Jan 20 22:22:33 volumio-3.179 autossh[2203]: ssh child pid is 2207
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreStateMachine::resetVolumioState
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreStateMachine::getcurrentVolume
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreCommandRouter::volumioRetrievevolume
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreCommandRouter::volumioStop
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreStateMachine::stop
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreStateMachine::setConsumeUpdateService undefined
Jan 20 22:22:33 volumio-3.179 volumio[1315]: verbose: UNSET VOLATILE
Jan 20 22:22:33 volumio-3.179 volumio[1315]: ------------------------------------ BT MESSAGE: BT STATUS: waiting
Jan 20 22:22:33 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: Playing: false
Jan 20 22:22:33 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: VOLATILE: undefined
Jan 20 22:22:33 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: STATE:undefined
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: MRS: Updating multiroomSync output
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: Remote SSH Started
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: Bluetooth Audio successfully Disabled
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: Bluetooth Successfully Detached
Jan 20 22:22:33 volumio-3.179 volumio[1315]: verbose: New Socket.io Connection to localhost:3000 from 127.0.0.1 UA: node-XMLHttpRequest Total Clients: 6
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: VolumeController:: Volume=69 Mute =false
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CoreStateMachine::pushState
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CorePlayQueue::getTrack 0
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CoreCommandRouter::executeOnPlugin: volumiodiscovery , saveDeviceInfo
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CoreCommandRouter::volumioPushState
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CoreStateMachine::updateTrackBlock
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CorePlayQueue::getTrackBlock
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CoreCommandRouter::volumioRetrievevolume
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CoreCommandRouter::volumioGetState
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CorePlayQueue::getTrack 0
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: MRS: Updating multiroomSync output
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: VolumeController:: Volume=69 Mute =false
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CoreStateMachine::pushState
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CorePlayQueue::getTrack 0
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: CoreCommandRouter::volumioPushState
Jan 20 22:22:34 volumio-3.179 volumio[1315]: info: MRS: Updating multiroomSync output
Jan 20 22:22:35 volumio-3.179 volumio[1315]: info: Executing endpoint metavolumio
Jan 20 22:22:35 volumio-3.179 volumio[1315]: info: CoreCommandRouter::executeOnPlugin: metavolumio , requestToMetaVolumio
Jan 20 22:22:37 volumio-3.179 volumio[1315]: ------------------------------------ BT MESSAGE: BT STATUS: paused
Jan 20 22:22:37 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: Playing: false
Jan 20 22:22:37 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: VOLATILE: undefined
Jan 20 22:22:37 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: STATE:undefined
Jan 20 22:22:40 volumio-3.179 volumio[1315]: ------------------------------------ BT MESSAGE: BT STATUS: idle
Jan 20 22:22:40 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: Playing: false
Jan 20 22:22:40 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: VOLATILE: undefined
Jan 20 22:22:40 volumio-3.179 volumio[1315]: BT PLUGIN MESSAGE: STATE:undefined

the dropping out can be reproduced with this command:

sudo /bin/systemctl restart sshtunnel.service

there must be something in the script of this sshtunnel.service that has an effect on bluetooth audio playing.

[mgafner]

no, it’s not the sshtunnel.service script, which is only a small script that starts an ssh tunnel to myvolumio.org.

This part of the log:

Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreStateMachine::resetVolumioState
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreStateMachine::getcurrentVolume
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreCommandRouter::volumioRetrievevolume
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreCommandRouter::volumioStop
Jan 20 22:22:33 volumio-3.179 volumio[1315]: info: CoreStateMachine::stop

why does Volumio “reset” and “stop” when the ssh tunnel is restarted?

[ashthespy]

@mgafner

why does Volumio “reset” and “stop” when the ssh tunnel is restarted?

Bluetooth stops playing after ~3 min

Thanks for your suggestion. We are aware of this issue and we are working on it. The SSH tunnel is not the cause, but rather a consequence of this issue. This seems to be due to a slight change in how the latest debian handles Bluetooth messages. It would be great if you could send a log just after bluetooth stops playing, so we verify also in your case. Thanks Follow this guide: Sending logs for troubleshooting - Volumio Documentation Paste the log link in this thread

Although going by the Community based change log for Volumio 3 there is an entry of " Fix for bluetooth interrupting playback"…

I hope you didn’t waste too much of your time debugging this – issue management for this project really needs some love…

[volumio]

@mgafner

sudo /bin/systemctl restart sshtunnel.service

Thanks for reporting, we were able to trace down the issue and fix it.

For those curious: for some reasons, the tunnel restart triggers a dbus message that Volumio interpretes as bluetooth being stopped (due to a recent bluez API change).

Now it’s fixed, the new release is due next week, and will include this.

Thanks a lot for your help and feedback