Thanks for sharing the response. This makes a lot of sense from a technical perspective.
From a usability perspective though, I don't know that I agree that this is the correct thing to do.
This obviously caught out a lot of people. People that aren't going to think this is good behavior no matter what. I recall someone pleading "Microsoft - please, please, please don't change the WebApp to mute the audio sources properly!!!!" =)
I realize that this change wasn't your decision, so I'm not trying to lambast you here. I'm just stating why the change still doesn't make sense to me despite the technical reasoning in the hopes someone admits this wasn't the win they thought it was and maybe undoes it? Yeah, I know. One can hope though.
When I change most application settings, I don't expect the setting to take effect for all other applications. I don't need or necessarily want the mic muted across the board. I have a perfectly good reminder that Teams is muted up there on the display. Having Teams control features on hardware based on a shared name is a decision that didn't seem to take a lot of other context into consideration. And if it was such a compelling reason, why doesn't Teams also control my USB mic? They could have made that change too. I really hope it's not on the way. =)
Sure, Shokz could address the issue by toning down the "you're muted dummy" sound. Though, this assumes that muting the whole mic is Teams' responsibility, which again I'd argue it isn't. I like that my mic gives me a notification when the whole mic is muted. It lets me know I took action at the hardware when nothing on the UI might otherwise indicate that. And I've got buttons on the mic to control that.
At the very least, a setting to control this behavior would be a win. Whether that's in Teams or Shokz firmware. The former would probably be easier though.