Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Assistant not ready to talk #7

Open
palas94 opened this issue Apr 13, 2020 · 4 comments
Open

Assistant not ready to talk #7

palas94 opened this issue Apr 13, 2020 · 4 comments

Comments

@palas94
Copy link

palas94 commented Apr 13, 2020

In the tutorial https://blog.rasa.com/how-to-build-a-voice-assistant-with-open-source-rasa-and-mozilla-tools/ , I have excecuted all the steps exactly till the end. Nothing shows any errors.

The tutorial says : If you refresh the Rasa voice interface in your browser, you should see that an assistant is ready to talk.

However when I refresh my browser, the bouncing ball keeps on bouncing. No interface appears with the start button.

I'd like to know what part of the code responds to the request from the rasa server, and stops the bouncing ball screen and serves a new screen.

Thank you.

@sara-tagger
Copy link

Thanks for raising this issue, @dakshvar22 will get back to you about it soon✨

Please also check out the docs and the forum in case your issue was raised there too 🤗

@AmoteChen
Copy link

same question...
The page of voice-interface did changed, and I can use the microphone. However, after I speaking some words, these is no text input...
Could you please help me to solve to problem?

@AmoteChen
Copy link

In the tutorial https://blog.rasa.com/how-to-build-a-voice-assistant-with-open-source-rasa-and-mozilla-tools/ , I have excecuted all the steps exactly till the end. Nothing shows any errors.

The tutorial says : If you refresh the Rasa voice interface in your browser, you should see that an assistant is ready to talk.

However when I refresh my browser, the bouncing ball keeps on bouncing. No interface appears with the start button.

I'd like to know what part of the code responds to the request from the rasa server, and stops the bouncing ball screen and serves a new screen.

Thank you.

you can change some codes in socketio_connector.py, then you may see the page u want, but still may face the same problem as mine that the microphone input cannot transfer into text.

Here is the change:

in function blueprint()
about line 184

change the code into:
sio = AsyncServer(async_mode="sanic", cors_allowed_origins='*')

@straeter
Copy link

straeter commented Mar 5, 2021

Faced the same issue when using Mozilla Firefox. However, in Chrome it worked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants