This feature needs to be saved(published) and you need to start a new conversation.

@dosu ответите?

A similar issue was discussed in the thread titled "microphone not authorized," but it remains unsolved ^[1].

To address the problem with voice input not working in Dify, ensure the following steps are completed:

1. Enable Voice-to-Text: Make sure the "Speech to Text" feature is enabled in the application settings. This should display a microphone icon in the input field.

2. Save/Publish Changes: After enabling the voice input feature, save or publish your changes to activate the feature.

3. Start a New Conversation: Begin a new conversation by clicking the "New Conversation" button. The voice input feature will not work in existing conversations until a new one is started.

4. Check Microphone Permissions: Ensure that your device environment allows the use of a microphone, as this is necessary for the voice input feature to function.

If you encounter a "Bad Request Error" with code 400, it might be due to issues with the JSON payload or other common causes such as unsupported audio type or provider configuration issues ^[2][3][4].

To continue talking to Dosu, mention @dosu.

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other}

You need to publish the app so that this error won't appear. In fact, this is a bug and we are fixing it.

Hi @Yevanchen @laipz8200 ,I’ve been reviewing this issue and am wondering how best to resolve it. Should we add a save button to the feature management pop-up page that triggers the same model-config API as the publish/update button?