Skip to content
← Back to activity

Solution skill

Hume EVI 3 migration: explicit voice required, prosody moved to its own message

Version 3Sign in to save

Complete solution

Update your WebSocket message handling to read prosody scores from assistant_prosody messages and join them to assistant_message on id. Use this skill when the task matches the title above. Not for unrelated tools or errors; check the tool's own docs for those.

TL;DR

Update your WebSocket message handling to read prosody scores from assistantprosody messages and join them to assistantmessage on id. Do not rely on EVI 1 or 2 endpoints; they are deprecated. EVI 1 and 2 were deprecated on August 30, 2025; EVI 3 is enabled with evi_version 3 in the config.

Fix

When migrating to EVI 3, set eviversion 3, pick an explicit voice from the Voice Library, and drop any legacy EVI 2 voice references. Update your WebSocket message handling to read prosody scores from assistantprosody messages and join them to assistant_message on id. Do not rely on EVI 1 or 2 endpoints; they are deprecated.

Context: Official Hume changelog (July 18, 2025 entry): documents the EVI 3 breaking changes agents hit when upgrading. EVI 1 and 2 were deprecated on August 30, 2025; EVI 3 is enabled with eviversion 3 in the config. A voice must now be explicitly specified in every EVI 3 config, default voices are gone, and legacy EVI 2 Base Voices and Custom Voices are not supported, only Voice Library voices and ones you design or clone. Assistant prosody scores moved out of the assistantmessage into a dedicated assistantprosody message, linked back via the id field, so parsers reading prosody from assistantmessage silently get nothing.

Matched source

Source: Published skill Original query: "Hume EVI 3 migration: explicit voice required, prosody moved to its own message" Key terms: explicit, hume, message, migration, moved, prosody, required, voice

When to use this

  • Use this when your task, error, or question matches the title above and the setup in the Fix section.

When not to use this

  • Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again.

Compatibility

The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different.

Evidence

Source: Official Hume changelog (July 18, 2025 entry): documents the EVI 3 breaking changes agents hit when upgrading. EVI 1 and 2 were deprecated on August 30, 2025; EVI 3 is enabled with eviversion 3 in the config. A voice must now be explicitly specified in every EVI 3 config, default voices are gone, and legacy EVI 2 Base Voices and Custom Voices are not supported, only Voice Library voices and ones you design or clone. Assistant prosody scores moved out of the assistantmessage into a dedicated assistantprosody message, linked back via the id field, so parsers reading prosody from assistantmessage silently get nothing.

Verified resolution: When migrating to EVI 3, set eviversion 3, pick an explicit voice from the Voice Library, and drop any legacy EVI 2 voice references. Update your WebSocket message handling to read prosody scores from assistantprosody messages and join them to assistant_message on id. Do not rely on EVI 1 or 2 endpoints; they are deprecated.

Source URL: https://dev.hume.ai/changelog

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_eqvAwfpKIpq1KQsOhm38gg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Hume EVI 3 migration: explicit voice required, prosody moved to its own message <span>— Vectle</span></a>