Define the receiving path before changing the console
Receiving Bluetooth audio from a phone is different from playing Kodi audio through Bluetooth headphones. Draw the intended path: phone audio into LibreELEC, then onward to the actual speakers or receiver. Decide how that output should coexist with ordinary Kodi playback.
Use a phone and appliance you administer, with a short audio sample you control. Preserve the working configuration and keep a normal way to recover audio. A set of commands copied from another system can name devices that do not exist on yours, so the procedure must begin with inspection.
Use the documented advanced receiving approach
LibreELEC’s PulseAudio guide describes pairing the phone, stopping Kodi while configuring the audio device, and inspecting available sinks and sources with pactl. Source and sink names must come from the actual system. The output examples in that guide are examples, not universal identifiers.
Follow the current guide for the installed release and retain each relevant name privately. A Bluetooth device can be connected without being the intended input in the audio route. Keep that state separate from the selected speaker output. Do not enable unrelated network-audio modules while diagnosing a local Bluetooth input.
Configure only the identified input and output
Use the documented default-source and default-sink operations only after confirming their targets. Record the original choices so the change can be reversed. Keep the test narrow: one phone, one output and one known sample. A successful console command does not prove that audible data is flowing.
Restart Kodi as required by the documented sequence and inspect its output choice. Play the phone’s sample and confirm where sound emerges. Then check ordinary Kodi audio separately. These observations show whether the two intended tasks coexist; they do not establish a general multiroom-audio design.
Decide whether persistence is required
If this is a temporary diagnosis, restore the original route after collecting the result. If a persistent configuration is intended, use LibreELEC’s documented persistent configuration location and test a normal restart. Do not assume a live console change survives boot simply because it worked once.
Retain the actual input, output, release and observed result in private notes. The expected outcome is a deliberate receiving route on the owner’s appliance. It does not claim a tested universal Bluetooth bridge, bypass source-app restrictions or guarantee equal behavior across different audio hardware.
Questions answered
Why can I not paste another person’s PulseAudio device names?
Those names identify their actual inputs and outputs. Inspect your own system and use the intended real targets.
Does a working console change prove the setup will survive reboot?
No. Test persistence through the documented configuration route and an ordinary restart if that is required.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.