I have the same problem, but I always assumed it was Apple's fault. I don't know why the HAs/Airpods have the final say.

I don't think there's a way around it on the iphone, but I was able to cobble a fix for my macbook at least. It uses Shortery to run a Shortcut whenever my HA connects. The Shortcut runs a shell script that uses https://github.com/deweller/switchaudio-osx/ to determine the built-in mic and switch back to it immediately:

BUILTIN_MIC_ID=$(switch-audio --list-input | jq 'map(select(.name == "MacBook Pro Microphone")) | .[0].id') switch-audio --set-input="$BUILTIN_MIC_ID"

▲

Barbing 8 hours ago | parent | next [-]

Nice.

And AirPodsSanity (& SoundAnchor) offer polished options here. Maybe using that same script underneath!

▲

fouc 11 hours ago | parent | prev [-]

Interesting, wouldn't the MBP microphone be even further away than the HA's microphone?

▲

Doohickey-d 11 hours ago | parent [-]

It's also my experience that people who use the Airpods audio in meetings = poor sound, whereas when they switch to the Macbook, it's much better.

I think the Macbook does some more advanced beamforming stuff to filter out sound coming from other directions.

	▲	mschuster91 5 hours ago \| parent [-]
		> I think the Macbook does some more advanced beamforming stuff to filter out sound coming from other directions. It does, and that also gave the Asahi Linux team some serious headache when trying to get the microphones working on the ARM MacBooks - the team involved in that had to delve deep into DSP black magic to get usable sound working out of the three microphones [1]. [1] https://news.ycombinator.com/item?id=43461701