Discussions

Ask a Question
Back to all

Knowledge Base Greeting Not Playing with Streaming Avatar SDK v2.0.13

The greeting/intro message configured in a Knowledge Base is not being triggered when using the Streaming Avatar SDK, despite working correctly in the
HeyGen embed.

Environment

  • SDK Version: @heygen/streaming-avatar v2.0.13
  • Framework: Next.js 14.2.16
  • Language: Spanish (es)
  • Knowledge Base ID: [configured with intro message]

Current Implementation

// Avatar configuration
const config = {
  quality: AvatarQuality.Low,
  avatarName: "Alessandra_CasualLook_public",
  knowledgeId: "588f6e52f25e4f228666c0c3d799860f", // KB with greeting configured
  voice: {
    voiceId: "1e080de3d73e4225a7454797a848bffe",
    rate: 1,
    emotion: VoiceEmotion.SERIOUS,
  },
  language: "es",
  voiceChatTransport: VoiceChatTransport.WEBSOCKET,
  sttSettings: {
    provider: STTProvider.DEEPGRAM,
    confidence: 0.55,
  },
};

// Session initialization
const newToken = await fetchAccessToken();
initAvatar(newToken);
await startAvatar(config);
await startVoiceChat({ isInputAudioMuted: true }); // Tried both true/false

Expected Behavior

- Avatar connects
- Greeting message from Knowledge Base plays automatically
- User can then speak after greeting completes

Actual Behavior

- Avatar connects successfully
- Video stream works
- Voice chat activates
- ❌ No greeting message plays
- Avatar waits in listening state

What I've Tried

1. ✅ Starting voice chat with isInputAudioMuted: true (muted initially)
2. ✅ Starting voice chat with isInputAudioMuted: false (unmuted)
3. ✅ Using useSilencePrompt: true parameter
4. ✅ Manual trigger with speak({ text: "", taskType: "talk" })
5. ✅ Verified Knowledge Base has intro message configured in labs.heygen.com
6. ✅ Verified same KB works perfectly in HeyGen embed

Additional Context

- The HeyGen embed with the same Knowledge Base ID plays the greeting perfectly
- The official HeyGen Interactive Avatar Next.js Demo (which was working days ago) also now fails to play greetings
- This suggests a potential regression or change in SDK v2.0.13 behavior