Data from 2 xenons to one argon

With Mesh.subscribe() you subscribe to a prefix so any event that starts with that prefix will be investigated by the subscriber but the event publisher can attach its own ID to that event name and hence tell the subscriber where the event originated

But sorry that I can't refrain from stressing the point: That could be found in the docs
https://docs.particle.io/reference/device-os/firmware/xenon/#subscribe-

Another source to investigate is this very forum
e.g.