Hello , need to update documentation to ASSISTANT V2 node (ok_watson from starter-kits)

[PhilippeComte]

Hello , The sample flow node uses an assistant node . Newly created services are based on the latest ASSISTANT V2 and that works with ASSISTANT V2 nodes . Note : you must deploy you Skill to an assistant and copy the assistant id in the parameters of the assistant V2 node There is an issue to get the answer pronounced by the TTS service : I keep having a "No response" from the machine voice even though the debug trace seems to imply that the answer has been provided by the Assistant service... The cause is a change in the format of the json format of the Assistant answer (see below)

[chughts]

If you are using Assistant V2, then the structure of the output from the node will be different. You will need to modify how the response is unmarshaled. I don't think there is a sample flow yet, so you have the opportunity to be the first to create one.

[PhilippeComte]

Great tip ! Not sure I can choose an old version of the Assistant service.
I created the Assistant service today and only the use of the new assistant V2 Noe Red node allowed the OK Watson flow to start working (but without understanding the output message) That explains while I receve the message.payload always contains "no response" after the set payload and tweet function . To make it simple (without the tweet function) , is the answer from Assistant in a different object than msg.payload.output.text ? Is it msg.payload.output.response_type.text ? Hope I'll manage to get it working sooner or later !

[PhilippeComte]

Hello Soheel, the very minimum to get the text to speech to work (no tweet ) is :

msg.payload = msg.payload.output.generic[0].text; return msg;

It works for a simple flow but has limitations (see below)

[chughts]

Re Assistant V1 - You can use the Assistant Workspace Management Node to list all your workspaces and workspace IDs, which should be all you need to use the Assistant V1 node.

[PhilippeComte]

thank you @chughts