search

E3V3A / TESTT

TEST -- This is only a test repo - nothing here
0 stars 0 forks source link

Exceeded maximum allowed stream duration #39

Open E3V3A opened 6 years ago

E3V3A commented 6 years ago

After the "command" hot word, if nothing else is spoken a time out is triggered. 

Error: 11 OUT_OF_RANGE: Exceeded maximum allowed stream duration of 65 seconds.

I would expect MMM-Assistant to return to a listening state, waiting for a new hot word to be spoken. Unfortunately after this error MMM-Assistant becomes unresponsive and does not react to hot words.

E3V3A commented 6 years ago

@drftg Yeah, I got the same error just the other day. Need to look into this. and also we should check if we can use a different way to store the temp file. BTW. That error you got, where did you see that?

Mine was:

[ASSTNT] Conversation Error: { Error: Invalid 'audio_in': audio frame length is too long.
    at ClientDuplexStream._emitStatusIfDone (/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/node_modules/grpc/src/client.js:255:19)
    at ClientDuplexStream._receiveStatus (/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/node_modules/grpc/src/client.js:233:8)
    at /home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/node_modules/grpc/src/client.js:757:12 code: 3, metadata: Metadata { _internal_repr: {} } }
[ASSTNT] Conversation Error: Error: write after end
    at writeAfterEnd (_stream_writable.js:166:12)
    at ClientDuplexStream.Writable.write (_stream_writable.js:217:5)
    at Conversation.write (/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/google-assistant/components/conversation.js:163:18)
    at Socket.mic.on.data (/home/pi/MagicMirror/modules/MMM-Assistant/node_helper.js:312:43)
    at emitOne (events.js:96:13)
    at Socket.emit (events.js:188:7)
    at readableAddChunk (_stream_readable.js:176:18)
    at Socket.Readable.push (_stream_readable.js:134:10)
    at Pipe.onread (net.js:543:20)

It could also be gPRC problem...

Unfortunately after this error MMM-Assistant becomes unresponsive and does not react to hot words.

Yep, but if you load the MM from another device, I guess it would reset?

E3V3A commented 6 years ago

This is the log

[ASSTNT] RecognizeStream Error:  { Error: 11 OUT_OF_RANGE: Exceeded maximum allowed stream duration of 65 seconds.
    at createStatusError (/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/grpc/src/client.js:64:15)
    at ClientDuplexStream._emitStatusIfDone (/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/grpc/src/client.js:270:19)
    at ClientDuplexStream._receiveStatus (/home/pi/MagicMirror/modules/MMM-Assistant/node_modules/grpc/src/client.js:248:8)
    at /home/pi/MagicMirror/modules/MMM-Assistant/node_modules/grpc/src/client.js:804:12
  code: 11,
  metadata: Metadata { _internal_repr: { 'content-disposition': [Object] } },
  details: 'Exceeded maximum allowed stream duration of 65 seconds.' }

So storage space does not seem to be a problem for me

Yep, but if you load the MM from another device, I guess it would reset?

I always start via ssh using npm start so no auto restarting