You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just setup Wyoming-satellite last weekend with Pi3 & Seed 2MIC HAT. All was going good until today when seemingly for no reason the system stopped functioning as it should, as it was. To begin with, in the logs I get this:
`Jan 3 12:19:29 SAT2W run[801]: INFO:root:Waiting for wake word
Jan 3 12:20:19 SAT2W run[801]: INFO:root:Disconnected from server
Jan 3 12:20:19 SAT2W run[801]: INFO:root:Connected to server
Jan 3 12:20:19 SAT2W run[801]: INFO:root:Waiting for wake word
Jan 3 12:21:00 SAT2W run[801]: INFO:root:Disconnected from server
Behavior: Wakeword needs repeating multiple times. Often I see yellow light come on (listening). At times it does take my question or command, there is an extended long period before I see yellow light go off. But this is what gets logged:
Jan 03 12:46:34 SAT2W run[1013]: Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono
Jan 03 12:46:50 SAT2W run[929]: INFO:root:Disconnected from server
Jan 03 12:46:50 SAT2W run[929]: ERROR:asyncio:Task exception was never retrieved
Jan 03 12:46:50 SAT2W run[929]: future: <Task finished name='wyoming event handler' coro=<AsyncEventHandler.run() done, defined at /home/sat1/wyoming-satellite/.venv/lib/python3.9/site-packages/wyoming/server.py:31> exception=ConnectionResetError(104, 'Connection reset by peer')>
Jan 03 12:46:50 SAT2W run[929]: Traceback (most recent call last):
Jan 03 12:46:50 SAT2W run[929]: File "/home/sat1/wyoming-satellite/.venv/lib/python3.9/site-packages/wyoming/server.py", line 37, in run
Jan 03 12:46:50 SAT2W run[929]: event = await async_read_event(self.reader)
Jan 03 12:46:50 SAT2W run[929]: File "/home/sat1/wyoming-satellite/.venv/lib/python3.9/site-packages/wyoming/event.py", line 79, in async_read_event
Jan 03 12:46:50 SAT2W run[929]: json_line = await reader.readline()
Jan 03 12:46:50 SAT2W run[929]: File "/usr/lib/python3.9/asyncio/streams.py", line 540, in readline
Jan 03 12:46:50 SAT2W run[929]: line = await self.readuntil(sep)
Jan 03 12:46:50 SAT2W run[929]: File "/usr/lib/python3.9/asyncio/streams.py", line 632, in readuntil
Jan 03 12:46:50 SAT2W run[929]: await self._wait_for_data('readuntil')
Jan 03 12:46:50 SAT2W run[929]: File "/usr/lib/python3.9/asyncio/streams.py", line 517, in _wait_for_data
Jan 03 12:46:50 SAT2W run[929]: await self._waiter
Jan 03 12:46:50 SAT2W run[929]: File "/usr/lib/python3.9/asyncio/selector_events.py", line 856, in _read_ready__data_received
Jan 03 12:46:50 SAT2W run[929]: data = self._sock.recv(self.max_size)
Jan 03 12:46:50 SAT2W run[929]: ConnectionResetError: [Errno 104] Connection reset by peer
Jan 03 12:46:50 SAT2W run[929]: INFO:root:Connected to server
Jan 03 12:46:50 SAT2W run[929]: INFO:root:Waiting for wake word
What troubles me most is that this did not start after a period of changing things, updating, etc.. This started at 9:16AM and the previous log entry is at 8:12 was normal:
Jan 3 08:12:44 SAT2W run[834]: INFO:root:Waiting for wake word
Jan 3 08:12:44 SAT2W run[1897]: Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono
Jan 3 08:12:47 SAT2W run[1901]: Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono
Jan 3 08:13:11 SAT2W run[1903]: Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono
Jan 3 08:13:16 SAT2W run[834]: INFO:root:Waiting for wake word
Jan 3 08:13:16 SAT2W run[1905]: Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 22050 Hz, Mono
Jan 3 08:13:17 SAT2W run[1908]: Playing raw data 'stdin' : Signed 16 bit Little Endian, Rate 22050 Hz, Mon
. Between that time I was busy at work in another room. Then the connect/discconnects began, and it was around 11:00AM that I sat down to look into this and began to see these errors. I did restart services, even rebooted the Pi. The behavior now is when I see "INFO:root:Waiting for wake word" I try the wake word, yellow light turns on...stays on long after short command was issued.. and then the asyncio error gets logged.
The text was updated successfully, but these errors were encountered:
I just setup Wyoming-satellite last weekend with Pi3 & Seed 2MIC HAT. All was going good until today when seemingly for no reason the system stopped functioning as it should, as it was. To begin with, in the logs I get this:
Behavior: Wakeword needs repeating multiple times. Often I see yellow light come on (listening). At times it does take my question or command, there is an extended long period before I see yellow light go off. But this is what gets logged:
What troubles me most is that this did not start after a period of changing things, updating, etc.. This started at 9:16AM and the previous log entry is at 8:12 was normal:
. Between that time I was busy at work in another room. Then the connect/discconnects began, and it was around 11:00AM that I sat down to look into this and began to see these errors. I did restart services, even rebooted the Pi. The behavior now is when I see "INFO:root:Waiting for wake word" I try the wake word, yellow light turns on...stays on long after short command was issued.. and then the asyncio error gets logged.
The text was updated successfully, but these errors were encountered: