You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, i use your node for streaming webcams and it works great. Thank you for that!
I only had one issue. The original msg ID (_msgid) is not passed through. So i cant merge this node output with other splitted messages . When a node dont passes al previous info and dont pass the original ID it is hard to keep parts of flows together and keep flow information complete
See: https://nodered.org/docs/creating-nodes/
Nodes should document what properties they ADD to messages, and they should be consistent and predictable in their behaviour.
The text was updated successfully, but these errors were encountered:
But just FYI with 3.x of that node, released this week, the functionality has completely changed, and there is no expectation of msg continuity on the output anymore. It is a purely asynchronous flow now, so you probably need to rethink how you are using it. Feel free to open a ticket there for more help when you upgrade.
Hi, i use your node for streaming webcams and it works great. Thank you for that!
I only had one issue. The original msg ID (_msgid) is not passed through. So i cant merge this node output with other splitted messages . When a node dont passes al previous info and dont pass the original ID it is hard to keep parts of flows together and keep flow information complete
See: https://nodered.org/docs/creating-nodes/
Nodes should document what properties they ADD to messages, and they should be consistent and predictable in their behaviour.
The text was updated successfully, but these errors were encountered: