That clarified a general picture, thank you.
I assume you are exclusively referring to Anki typing cards? The add-on is probably searching for the standard Anki typing field on the back of a card, as I don’t see any other way it could assess the correctness of an answer, and playing the sound based on that.
Because the standard input is very limited in its functionality (it does not work on AnkiWeb, does not allow making multiple-choice cards, does not cooperate with the card’s on-screen keyboard on iphones, etc.), the template uses its own system, which a general-use add-on unlikely to be taking into account.
There are a few things you can try.
If you are fine with losing some of the functionality mentioned above, you can revert to the stock Anki typing by replacing the following line found on the front of the card:
<input id="typeans" type="text" inputmode="text" autocorrect="off" autocomplete="off" autocapitalize="off" spellcheck="false">
with the Anki’s default field replacement:
{{type:Learnable}}
The template is written in a way to have this as a possible fallback, although it wasn’t tested extensively.
If this modification causes any bugs, you can also try one of the older versions (if I remember correctly, v3.32 was the last one built on the stock Anki input). Naturally, this will come at a cost of all the functionality introduced in the later updates.
Alternatively, as I mentioned before, a bit of JS can be added to the “user posterior scripts” section to trigger a sound independently of any add-ons, based on the template card state.