When you continue a session, with hermes protocol, you can add a string value in msg.payload.customData. This custom value is sent after with the intent message and with ended session too.
With intentFilter parameter, you can use intent yesno and in customdata, the origin intent or anything you want.
I think that customData is not sent with 2nd intent as snips does.
i m also interrested in continuing a session could you give me a hint on how to implement that ? didn t see anything in the docs about the implementation itself ( i may be blind )
Additional information that can be provided by the handler. Each message related to the new session - sent by the Dialogue Manager - will contain this data
The customData field is forwarded for message sent by the Dialogue Manager, in this case only SessionStarted, SessionQueued, SessionEnded. In that case customData is filled in (at least judging from the source code). But customData has to be filled in the StartSession message, which is sent by the wake word component IIRC. What you can do however, is update customData when you send the continueSession message. That will be stored and forwarded by Rhasspy later.
What I mean is Rhasspy just reacts to dialogue manager messages and acts accordingly. But I’m just a contributor, Rhasspy core developers could help in better figuring this out.
I see now. Ok Rhasspy doesn’t do that currently. I believe it was implemented following the Hermes protocol as documented by Snips. I can’t find any reference for customData in NLU intent messages. customData is a feature exclusive to dialogue manager messages.
However… you say Snips does do that. So does it mean it’s undocumented maybe? Who knows…
Anyway, maybe you could open an issue on GitHub for this.