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 am using uMQTTBroker.h very successfully to create my networks, but have some issues to understand.
Can you point me to how to identify:
Number of CURRENTLY connected clients
Text of TOPICs connected
I do get this information once from the functions “onConnect” and “onData” but would benefit from the ability to print to the serial port in the LOOP, debug information as CLIENTS connect and disconnect .
Issue:
Two CLIENTS are connected. Power OFF #1; BROKER properly identifies the unit as “offline”.
However, the BROKER also gets a message that CLIENT #2 goes “offline” then quickly back “online”.
Is this “normal” MQTT functionality????
Thanks for any thought you can provide.
The text was updated successfully, but these errors were encountered:
I am using uMQTTBroker.h very successfully to create my networks, but have some issues to understand.
Can you point me to how to identify:
Number of CURRENTLY connected clients
Text of TOPICs connected
I do get this information once from the functions “onConnect” and “onData” but would benefit from the ability to print to the serial port in the LOOP, debug information as CLIENTS connect and disconnect .
Issue:
Two CLIENTS are connected. Power OFF #1; BROKER properly identifies the unit as “offline”.
However, the BROKER also gets a message that CLIENT #2 goes “offline” then quickly back “online”.
Is this “normal” MQTT functionality????
Thanks for any thought you can provide.
The text was updated successfully, but these errors were encountered: