Remote HTTP Timeout

I’m running Rhasspy on a Raspberry Pi using Docker. I’m attempting to configure Remote HTTP for Intent Recognition, TTS, and STT using the instructions in the Rhasspy documentation. I’m pointing it to another server with Rhasspy also deployed via Docker. When I point my Raspberry Pi to the server I get the following error during Intent Recognition.

When I have the Pi configured to run these processes locally I have no issues. I can also manually call the server API from the command line on my Pi and get a response so the issue doesn’t seem to be the API on the server or communication between the two.

Any help here would be greatly appreciated.

[WARNING:2021-08-04 13:54:30,301] rhasspyserver_hermes: Message queue missing (topic=hermes/error/nlu, id=d4d57094-9666-47fd-a21d-2c53a9ee9c80)
[DEBUG:2021-08-04 13:54:30,300] rhasspyserver_hermes: Handling NluError (topic=hermes/error/nlu, id=d4d57094-9666-47fd-a21d-2c53a9ee9c80)
[ERROR:2021-08-04 13:54:29,953] rhasspyserver_hermes:
Traceback (most recent call last):
File “/usr/lib/rhasspy/.venv/lib/python3.7/site-packages/quart/”, line 1821, in full_dispatch_request
result = await self.dispatch_request(request_context)
File “/usr/lib/rhasspy/.venv/lib/python3.7/site-packages/quart/”, line 1869, in dispatch_request
return await handler(**request_.view_args)
File “/usr/lib/rhasspy/rhasspy-server-hermes/rhasspyserver_hermes/”, line 1452, in api_text_to_intent
File “/usr/lib/rhasspy/rhasspy-server-hermes/rhasspyserver_hermes/”, line 2706, in text_to_intent_dict
text, intent_filter=intent_filter, site_id=site_id
File “/usr/lib/rhasspy/rhasspy-server-hermes/rhasspyserver_hermes/”, line 524, in recognize_intent
handle_intent(), messages, message_types
File “/usr/lib/rhasspy/rhasspy-server-hermes/rhasspyserver_hermes/”, line 995, in publish_wait
result_awaitable, timeout=timeout_seconds
File “/usr/lib/python3.7/asyncio/”, line 423, in wait_for
raise futures.TimeoutError()
[DEBUG:2021-08-04 13:54:29,952] rhasspyserver_hermes: Publishing 22 bytes(s) to rhasspy/handle/toggleOn
[DEBUG:2021-08-04 13:54:29,951] rhasspyserver_hermes: → HandleToggleOn(site_id=‘officePi’)
[DEBUG:2021-08-04 13:53:59,924] rhasspyserver_hermes: Publishing 272 bytes(s) to hermes/nlu/query
[DEBUG:2021-08-04 13:53:59,924] rhasspyserver_hermes: → NluQuery(input=‘what time is it’, site_id=‘officePi’, id=‘884374ac-cc88-440a-b281-99d062ace9fa’, intent_filter=None, session_id=‘884374ac-cc88-440a-b281-99d062ace9fa’, wakeword_id=None, lang=None, custom_data=None, asr_confidence=None, custom_entities=None)
[DEBUG:2021-08-04 13:53:59,919] rhasspyserver_hermes: Subscribed to hermes/error/nlu
[DEBUG:2021-08-04 13:53:59,917] rhasspyserver_hermes: Publishing 22 bytes(s) to rhasspy/handle/toggleOff
[DEBUG:2021-08-04 13:53:59,916] rhasspyserver_hermes: → HandleToggleOff(site_id=‘officePi’)

Did you ever figure this out? I have the same problem attempting to do the same thing


I added the satellite id’s in those 3 remotehttp fields on the BASE station and it seems to work