Closed alexgtn closed 6 years ago
If you check the topic under which that is happening, you will see that's an internal topic used by Mosca.
I would recommend to use Aedes which has a instance.subscribe
https://github.com/mcollina/aedes#subscribe feature that enables you to listen to specific patterns (similar to a MQTT client) but from within a broker instance.
@mcollina interesting! I'll check that out. Thanks for the reply.
The server receives the clientID as a
packet.payload
on "published" and on "client disconnect".Example sequence of messages the broker is receiving on "published":
Is that normal behaviour? Should I manually filter out the clientId in case I don't want it?
Thank you!