Is your feature related to a problem?

Yes, the current implementation of websocket only allows to use the automatic path finding when 1 hop is specified, and there is a bug in path finding where not always a suitable path is found even when there is. As suggested by @NumberFour8 , the fix for the Path finding is not trivial and might take longer to fix it, so I propose to allow in the websocket connection to specify the path of the relayer and avoid using the path finding feature.

Describe the feature you'd like

Add a new queryParameter into the websocket connection endpoint /api/v3/session/websocket so it accepts the path to follow for using 1 hop.