Apple Homepod Mini being accessed from new Fedora KDE install on older PC

Wanted to know if anyone ever heard of this happening before. Repurposed older (4thGeni5) Dell with clean install of Fedora KDE 43. Testing playback of Youtube , sound goes to apple speaker. System shows no Bluetooth connections. Never attempted to pair any devices. PC is on 2.4 band of home wifi. Apple support didn’t think it was a big deal.

Streaming to HomePods happens over WiFi, not Bluetooth.

I’m not all that familiar with KDE, is there a sound output switcher? Does the HomePod show up there and can you change the output?

Can you run the following commands in the terminal and provide the output?

pactl list modules short

pactl list sinks short

This is to check see if the pipewire/pulseaudio raop-discover module is loaded, which enables discovering and playing audio through airplay speakers, and if the HomePod is showing up in the list of sinks that pipewire is detecting.

If that module is enabled it would explain why the speaker can be streamed to. Fedora comes with everything needed to auto discover and enable streaming to Airplay enabled speakers that are on the same network, no pairing needed. That feature is normally disabled by default though, but you can enable it temporarily with the pactl application in the terminal, or permanently via config files.

Sorry new to all this. the second command you show gave e this output:

71 raop_sink.Bedroom-macaddress.local.192....*.7000 Pipewire s161e 2ch 44100hz

of course i left out actual address and number. Thanks for the info however. I learned something today.

It looks like it was a private IP so probably not a big deal, but good to be cautious.

It does also look like pipewire is detecting the AirPlay speaker via the module I described.

If the speaker remains available after a reboot then pipewire has likely been configured to enable it by default. Curious if it was that way following a fresh install, but easy enough to disable. Can’t remember the location of the config file off the top of my head but it should just involve commenting out or removing one line in the config file

Thanks for the quick reply. Im gonna look it up and try to disable it.