Heads up: The most recent firmware version (2.3.x) changed the MQTT root prefix. If you flashed the new version, you may see less people as they could still be using the older firmware.
Here is the relevant snipped from the release:
This release changes the MQTT root prefix to msh/2/e to bring it in line with the QR code version. So if you are connected to an MQTT broker, you will not be able to communicate with your peers that have not yet made the upgrade.
You can find some nodes around you at https://meshmap.net/, and if you click on the node you will see a section “On MQTT topic”. Those with the older firmware may appear under msh/2/c/LongFast, and those with the newer version under msh/2/e/LongFast. If you are in a different topic, you can’t see each other in the chat.
I’ve messed around with mqtt explorer to see all the different topics but haven’t left mqtt running for long on the node because I’m hoping to catch my first local. That and i need to find a smaller mqtt topic so it doesn’t bog everything down.
Nice! Welcome to the hobby _
Heads up: The most recent firmware version (2.3.x) changed the MQTT root prefix. If you flashed the new version, you may see less people as they could still be using the older firmware.
Here is the relevant snipped from the release:
You can find some nodes around you at https://meshmap.net/, and if you click on the node you will see a section “On MQTT topic”. Those with the older firmware may appear under msh/2/c/LongFast, and those with the newer version under msh/2/e/LongFast. If you are in a different topic, you can’t see each other in the chat.
I’ve messed around with mqtt explorer to see all the different topics but haven’t left mqtt running for long on the node because I’m hoping to catch my first local. That and i need to find a smaller mqtt topic so it doesn’t bog everything down.
Good luck! I still don’t have local contacts