#Node Red Assist Pipeline Issue

1 messages · Page 1 of 1 (latest)

ruby elm
#

Node Red logs

Nov 20:22:22 - [red) Uncaught Exception:
28 Nov 20:22:22 - [error] UnhandledPromiseRejection: This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected
with the reason "#<0bject>".
[20:22:22] INFO: Service Node-RED exited with code I (by signal 0)

#

In the node Red flow I'm using a Home Assistant API node that uses the Home Assistant addon config and this is the following payload being sent,

{
type: "assist pipeline/run",
start_stage": "tts",
end_stage": "tts",
input: {
"text": "Are you sure you want to print " & msg.payload & "?"
},
pipeline: msg.pipeline_id
}

#

And the supervisor throws the following errors,

23-11-28 23-11-28 20:22:22 20:22:22 INFO (MainThread) [supervisor.api.proxy] Home Assistant Websocket API error: Cannot proxy websocket message of unsupported type: 257
(MainThread) [supervisor.api.proxy] Home Assistant Websocket API connection is closed

short compass
#

i don't think this has to do with the voice functionality, but rather it's a question for #add-ons-archived maybe

still... have you tried the same request with another client other than NodeRed to access the core via Websockets?