debug the output from the cast node full msg
never mind
the cast node is outputing msg.payload you can change that to any thing you wish by using function or template.
In node-red I had loads of different HTTP IN nodes with different URLs and then loads of different cast nodes and I was specifying the different TTS message text under each cast node etc.
I was then sending the different URLs from different scenes in Vera etc.
This is much better now with a dynamic setup. Means I have a lot less stuff in node-red and also I now can specify the TTS message text in the Vera scenes.
Well pleased thanks for your help !
This is was what I was doing previously before the dynamic:
The path can be fully specified, such as /user , or include named parameters that accept any value, such as /user/:name . When named parameters are used, their actual value in a request can be accessed under msg.req.params .
You could then use a switch node to direct to different flows using msg.req.params
You would probably find it easier to set up Reactor notify http activitiy, to send http request when switches are turned on or off, using the scene flow we just got working.