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
MQTT nodes continously show 'disconnected' if the topic for Messages sent on connection (birth message) or Message sent on an unexpected disconnection (will message) contains a # (pound sign)
Expected Behavior
The node should be connecting so a '#' in the (birth message) or (will message) should not be allowed.
Steps To Reproduce
edit an MQTT node (in or out)
edit Server
select Messages tab
in Messages sent on connection (birth message) or Message sent on an unexpected disconnection (will message) put a # (pound sign) in the topic
Hi Paul, quick update to let you know I have resolved your issue (by preventing bad publish topics being sent) but have been working on a deeper underlying issue regarding MQTT client connections hanging around in memory and firing events - this was discovered during my testing & was indirectly due to the publishing of a bad birth topic.
A fix will be incoming before too long (just tiding it up, removing the reams and reams of debug messages etc).
Current Behavior
MQTT nodes continously show 'disconnected' if the topic for
Messages sent on connection (birth message)
orMessage sent on an unexpected disconnection (will message)
contains a#
(pound sign)Expected Behavior
The node should be connecting so a '#' in the (birth message) or (will message) should not be allowed.
Steps To Reproduce
Server
Messages
tabMessages sent on connection (birth message)
orMessage sent on an unexpected disconnection (will message)
put a#
(pound sign) in the topicExample flow
The text was updated successfully, but these errors were encountered: