14:53:06+00:00 warn [voice-call] Streaming enabled but realtime transcription provider "openai" is not registered 14:53:06+00:00 warn [voice-call] Streaming enabled but realtime transcription provider "openai" is not registered 15:48:51+00:00 warn [voice-call] Streaming enabled but realtime transcription provider "openai" is not registered

TL;DR

• The voice-call plugin can be fixed by ensuring the STT provider is registered before loading the plugin, likely by reordering initialization steps or introducing a delay.

Guidance

• Review the changes introduced in commit a23ab9b906dc6a4f6b24bb3f681f395eb792dbcd to understand how the initialization order or timing might have been altered.
• Verify the registration status of the "openai" STT provider before attempting to use the voice-call plugin.
• Consider adding a check or a synchronization mechanism to ensure the STT provider is fully registered and ready before enabling the voice-call plugin.
• Test the voice-call functionality with different provider configurations to isolate if the issue is specific to "openai" or a more general problem.

Example

No specific code example can be provided without more context on the initialization and registration processes of the STT providers and the voice-call plugin.

Notes

The exact fix depends on the internal workings of the OpenClaw system, particularly how plugins and providers are initialized and registered. The logs suggest a race condition, but the solution might involve code changes, configuration adjustments, or both.

Recommendation

• Apply a workaround by adjusting the initialization order or introducing a delay to ensure the STT provider is registered before the voice-call plugin is loaded, as this directly addresses the identified race condition.