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
I cannot unsubscribe from a topic.
msg = { topic: "myTopic", payload: "_unsubscribe:nodeName" }
After sending the unsubscribe, I can still get mqtt subscriptions from "myTopic." Then when I subscribe to "myTopic" again, I receive redundant messages.
I see from the comments that this is a known issue:
"One node can be subscribed to the same topic more than once, so if you send two msgs with msg.topic set to i.e. "testTopic", then node will receive two msgs for one msg published to the topic. It's not battle tested yet, so I will be happy for any feedback."
I "battle tested" this and it becomes a problem over time. I have written code (using the RBE node) to filter out redundant messages. So far, the only way I can truly "unsubscribe" is to re-deploy the flow.
The text was updated successfully, but these errors were encountered:
I cannot unsubscribe from a topic.
msg = { topic: "myTopic", payload: "_unsubscribe:nodeName" }
After sending the unsubscribe, I can still get mqtt subscriptions from "myTopic." Then when I subscribe to "myTopic" again, I receive redundant messages.
I see from the comments that this is a known issue:
"One node can be subscribed to the same topic more than once, so if you send two msgs with msg.topic set to i.e. "testTopic", then node will receive two msgs for one msg published to the topic. It's not battle tested yet, so I will be happy for any feedback."
I "battle tested" this and it becomes a problem over time. I have written code (using the RBE node) to filter out redundant messages. So far, the only way I can truly "unsubscribe" is to re-deploy the flow.
The text was updated successfully, but these errors were encountered: