AwesomeTTS AssertionError with ElevenLabs: "bad elevenlabs key similarity_boost" on macOS (Anki 25.09.2)

Hi, I’m getting an assertion error when trying to use ElevenLabs in AwesomeTTS. Could you give me a solution?

Environment:

  • Anki: 25.09.2 (3890e12c) (ao)
  • Add-on: AwesomeTTS - Add speech to your flashcards (ID: 1436550454)
  • Python: 3.13.5
  • Qt/PyQt: Qt 6.9.1 / PyQt 6.9.1
  • Platform: macOS-26.1-arm64-arm-64bit-Mach-O

What happens

  • When I open AwesomeTTS and select the ElevenLabs service (or try to load its options), it throws an AssertionError.

Error message

Traceback (most recent call last):
File "/Users/aa/Library/Application Support/Anki2/addons21/1436550454/awesometts/gui/base.py", line 628, in _on_service_activated
options = self._addon.router.get_options(svc_id, force_options_reload=force_options_reload)
File "/Users/aa/Library/Application Support/Anki2/addons21/1436550454/awesometts/router.py", line 218, in get_options
svc_id, service = self._fetch_options_and_extras(svc_id, force_options_reload=force_options_reload)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/Users/aa/Library/Application Support/Anki2/addons21/1436550454/awesometts/router.py", line 739, in _fetch_options_and_extras
assert self._services.normalize(option['key']) == 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
option['key'], "bad %s key %s" % (svc_id, option['key'])
^^^^^^^^^^^^^
AssertionError: bad elevenlabs key similarity_boost
===Add-ons (active)===
(add-on provided name [Add-on folder, installed at, version, is config changed])
AwesomeTTS - Add speech to your flashcards ['1436550454', 2025-08-16T10:02, 'None', mod]
===IDs of active AnkiWeb add-ons===
1436550454
===Add-ons (inactive)===
(add-on provided name [Add-on folder, installed at, version, is config changed])

What I tried:

  • Removed the add-on once and reinstalled it.
  • Restarted Anki.
  • Restarted the MacBook itself.
  • Uninstalled Anki installed via Homebrew and reinstalled it again with Homebrew.

You should contact the developer by clicking "Contact Author’ on the add-on page – or whatever other method they request.

1 Like

Thank you for your reply.
I clicked “Contact Author” on the add-on page and found a solution in the following issue.
It solved the problem.

1 Like