- Welcome to Eastmesh.
Recent posts
#1
General Discussion / Re: First timer questions - ch...
Last post by Nastic - Apr 11, 2026, 10:26 AMHi and welcome aboard sorry for the slow response. The companion is your chat nodes they come in USB Bluetooth or wifi.
Devices will send out an advert packet and should appear in your contacts if your device heeard them. you can also scan device QR codes in the meshcore app to add them. Map.eastmesh.au now supports generating them.
If you didn't see repeats it's a good chance your msg hasn't gone out trying again a couple of time won't hurt
If you send the message multiple times it will show up as multiple messages for anyone rxing but the mesh is pretty chill so double posts shouldn't upset anyone but if you have seen repeats it's unlikely a second message will go any further
The path your message takes is stored in packet and can be shown if you toggle the option in the app. Jeeves and meshbot are both automated
Join the meshcore Australia discord it's actually active and everyone is happy to help out a new user https://discord.gg/RjSvF2FbQ
Devices will send out an advert packet and should appear in your contacts if your device heeard them. you can also scan device QR codes in the meshcore app to add them. Map.eastmesh.au now supports generating them.
If you didn't see repeats it's a good chance your msg hasn't gone out trying again a couple of time won't hurt
If you send the message multiple times it will show up as multiple messages for anyone rxing but the mesh is pretty chill so double posts shouldn't upset anyone but if you have seen repeats it's unlikely a second message will go any further
The path your message takes is stored in packet and can be shown if you toggle the option in the app. Jeeves and meshbot are both automated
Join the meshcore Australia discord it's actually active and everyone is happy to help out a new user https://discord.gg/RjSvF2FbQ
#2
General Discussion / First timer questions - channe...
Last post by skeptopotamus - Apr 10, 2026, 10:49 AMHello,
First time using Meshcore and mesh networks in general. I couldn't find answers to these questions in the Eastmesh FAQ or the MeshCore FAQ. Some of these might be etiquette.
What type of node is a "chat client"? As opposed to a companion, room server or repeater.
How do I discover rooms that are available to join?
If I send a message and there are no repeats, does that mean I should send it again?
If I resend a message multiple times, will it spam people who see the repeats or will it just ensure more coverage?
How do people reply with those concise traceroutes in the #ping channel?
Please be gentle. I'm new!
First time using Meshcore and mesh networks in general. I couldn't find answers to these questions in the Eastmesh FAQ or the MeshCore FAQ. Some of these might be etiquette.
What type of node is a "chat client"? As opposed to a companion, room server or repeater.
How do I discover rooms that are available to join?
If I send a message and there are no repeats, does that mean I should send it again?
If I resend a message multiple times, will it spam people who see the repeats or will it just ensure more coverage?
How do people reply with those concise traceroutes in the #ping channel?
Please be gentle. I'm new!
#3
General Discussion / Re: East coast map
Last post by Nastic - Mar 16, 2026, 10:29 PMIt won't show up on the map until an adverts been heard from it once a observer sees one it should pop up
#4
General Discussion / Re: East coast map
Last post by VK7III - Mar 16, 2026, 07:26 PMI had some issues getting my V3 linking with eastmesh but it's working now and my repeater "VK7Iii Hadspen" chats happily with obs.eastmesh.au and is visible there BUT I cannot find out why it isn't showing on the map!
#5
Meshcore / Re: Firmware using MQTT withou...
Last post by Nastic - Mar 14, 2026, 07:14 AMHey mate I believe it's a problem with the https that I'm using I haven't had a chance to work out exactly why it doesn't work but a community member patched the firmware to work for us
https://github.com/xJARiD/MeshCore
But I'm not sure if it's been updated to 1.14
Edit: I had a look at the default implementation it looks like it doesn't support https for extra servers only http I'll have to open up an extra port to support it
Try using port 9883
https://github.com/xJARiD/MeshCore
But I'm not sure if it's been updated to 1.14
Edit: I had a look at the default implementation it looks like it doesn't support https for extra servers only http I'll have to open up an extra port to support it
Try using port 9883
#6
Meshcore / Firmware using MQTT without a ...
Last post by VK7III - Mar 13, 2026, 04:01 PMHas anyone had success with the firmware, https://github.com/agessaman/MeshCore/tree/mqtt-bridge-implementation which enables wifi and sends mqtt packets without another computer, connecting to Eastmesh?
I have installed the firmware on a Heltec V3 and it works well with US and EU servers but will not play nicely with Eastmesh.
I get the following error:
DEBUG: RadioLibWrapper: noise_floor = -101
E (411528) MQTT_CLIENT: mqtt_message_receive: received a message with an invalid header=0x48
E (411529) MQTT_CLIENT: esp_mqtt_connect: mqtt_message_receive() returned -1
E (411532) MQTT_CLIENT: MQTT connect failed
MQTT: MQTT broker disconnected
DEBUG: RadioLibWrapper: noise_floor = -102
It also doesn't like timezone "Australia/Hobart" but works with "Australia/Sydney"
0x48 being an "H" is Eastmesh returning HTTP?
I'm not wise in these matters ...
Rowan
I have installed the firmware on a Heltec V3 and it works well with US and EU servers but will not play nicely with Eastmesh.
I get the following error:
DEBUG: RadioLibWrapper: noise_floor = -101
E (411528) MQTT_CLIENT: mqtt_message_receive: received a message with an invalid header=0x48
E (411529) MQTT_CLIENT: esp_mqtt_connect: mqtt_message_receive() returned -1
E (411532) MQTT_CLIENT: MQTT connect failed
MQTT: MQTT broker disconnected
DEBUG: RadioLibWrapper: noise_floor = -102
It also doesn't like timezone "Australia/Hobart" but works with "Australia/Sydney"
0x48 being an "H" is Eastmesh returning HTTP?
I'm not wise in these matters ...
Rowan
#7
General Discussion / Re: History tool
Last post by Smithy - Mar 13, 2026, 09:01 AMThanks mate, I'll take another look at the peers tool.
#8
General Discussion / Re: History tool
Last post by Nastic - Mar 13, 2026, 01:38 AMThe history lines are hops in the path I'll be honest I'm not sure what the different colours mean I should really ask the Dev. The peers tool will show you neighbours for a selected node
#9
General Discussion / History tool
Last post by Smithy - Mar 09, 2026, 07:56 PMHey Nastic,
Could you explain the "History tool" and what the data shows on the map? Are the lines direct connections or routing end points etc.
Thanks!
Could you explain the "History tool" and what the data shows on the map? Are the lines direct connections or routing end points etc.
Thanks!
#10
General Discussion / Re: East coast map
Last post by Nastic - Feb 26, 2026, 09:01 PMSorry for the slow reply as you probably noticed this place is a ghost town. Most traffic does come from companion nodes but most people don't share a location. The map uses the path that's stored in the packet to show the line on the map.