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
Copy file name to clipboardExpand all lines: docs/ar-rSA/user/connections.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -29,9 +29,9 @@ Bluetooth Low Energy is the default and most common connection method on Android
29
29
30
30
31
31
32
-
You can filter devices by transport type using the filter chips at the top:
32
+
Use the transport selector — a segmented button row below the connection card — to switch between the Bluetooth, Network, and USB transports (one is active at a time):
> 💡 **Tip:** If your device doesn't appear, check that Bluetooth and Location permissions are granted, and that the radio is not already connected to another device.
37
37
@@ -77,7 +77,7 @@ Some Meshtastic radios support WiFi/Ethernet connectivity, allowing TCP-based co
77
77
### Connecting over the Network
78
78
79
79
1. Make sure the radio is on the same local network as your phone/desktop.
80
-
2. On the Connect screen, select the **Network** transport filter.
80
+
2. On the Connect screen, select **Network**in the transport selector.
81
81
3. Choose the radio one of two ways:
82
82
-**Scan for network devices** — toggle this on to auto-discover radios that advertise themselves on the local network (mDNS / `_meshtastic._tcp`). Discovered devices appear in the list; tap one to connect.
83
83
-**Add device manually…** — enter the radio's IP address (or hostname) and port (default: `4403`).
Copy file name to clipboardExpand all lines: docs/ar-rSA/user/discovery.md
+20-1Lines changed: 20 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -88,6 +88,25 @@ Additional features available from the results:
88
88
89
89
---
90
90
91
+
## Mesh Beacon
92
+
93
+
Mesh Beacon lets nodes invite others to join their mesh. A beaconing node periodically broadcasts an invitation — optionally advertising a channel, region, and modem preset — that nearby devices can hear even before they share a configuration.
94
+
95
+
Configure it under **Settings → Module Config → Mesh Beacon**:
96
+
97
+
-**Listen for beacons** — receive invitations broadcast by other nodes.
98
+
-**Broadcast beacon** — send your own invitation at a set interval, with an optional message and an offered channel.
99
+
100
+
Received invitations appear as **Mesh invitations** cards on the Discovery screen. Each card shows the sender's message plus the offered channel, region, preset, and signal quality, with these actions:
101
+
102
+
-**Join** — switch to the offered channel and preset (retunes the radio and reboots). When the offer matches your current frequency slot, an **Add channel** action adds it without a reboot.
103
+
-**Discover** — seed a Discovery scan with the offered preset so you can survey that mesh before joining (shown only when the beacon offers a preset).
104
+
-**Dismiss** — ignore the invitation.
105
+
106
+
Channels advertised by beacons also show up in the scan setup as **Beacon channels** — select one to include it as a scan target.
107
+
108
+
---
109
+
91
110
## Manual Exploration
92
111
93
112
The tools below are available at any time from the node list and node detail screens. Use them to investigate specific paths and build a topology picture, alongside or instead of a full scan.
@@ -169,7 +188,7 @@ The node list itself is a powerful discovery tool when you use its filtering and
169
188
170
189
### Infrastructure Audit
171
190
172
-
- Disable **Exclude infrastructure** to see Router, Repeater, Router Late, and Client Base nodes.
191
+
- Disable **Exclude infrastructure** to see Router, Router Late, and Client Base nodes.
173
192
- Check their signal quality and last-heard times to verify your infrastructure nodes are healthy.
174
193
175
194
See [Nodes](nodes) for full details on filtering and sorting options.
Copy file name to clipboardExpand all lines: docs/ar-rSA/user/map-and-waypoints.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,8 @@ Waypoints are shared geographic points of interest that all mesh members can see
53
53
3. Choose an icon/emoji for the waypoint.
54
54
4. Tap **Send** to share with the mesh.
55
55
56
+
Waypoints are addressed like messages: by default they broadcast on the primary channel, but a waypoint can also be sent on a specific channel or as a direct message to a single node.
57
+
56
58
### Waypoint Properties
57
59
58
60
| Property | الوصف |
@@ -116,9 +118,8 @@ Configure position behavior in **Settings → Position**.
116
118
117
119
## Map Sources
118
120
119
-
The app supports multiple maptile sources:
121
+
The base map depends on your app flavor: **Google Play** builds use Google Maps, while **F-Droid** and Desktop builds use OpenStreetMap. On top of the base map, additional tile sources are available as overlays or alternatives:
120
122
121
-
- OpenStreetMap (default)
122
123
- Satellite imagery (where available)
123
124
- Offline tiles (download map areas for offline use)
Copy file name to clipboardExpand all lines: docs/ar-rSA/user/messages-and-channels.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -179,6 +179,7 @@ Messages are queued and transmitted based on priority:
179
179
### Message Limits
180
180
181
181
-**Maximum length:** 200 bytes (approximately 200 characters for ASCII text)
182
+
- The 200-byte cap applies to the in-app composer — the mesh payload limit itself is ~233 bytes, so messages from other senders (e.g., App Functions or Android Auto) may arrive slightly longer
182
183
-**Rate limiting:** The mesh enforces airtime fairness; heavy message volume may be throttled
183
184
-**Delivery:** Messages are retried automatically if no acknowledgment is received
Copy file name to clipboardExpand all lines: docs/ar-rSA/user/mqtt.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -52,6 +52,12 @@ A gateway node with internet access (WiFi or Ethernet) publishes mesh messages t
52
52
| TLS | Secure connection to broker | Disabled |
53
53
| Map Reporting | Report position to public map | Disabled |
54
54
55
+
### MQTT Proxy on This Phone
56
+
57
+
If your node has no internet access of its own, it can use the connected phone as its MQTT gateway: enable **MQTT** and **Proxy to client enabled** in the module config, and the app relays MQTT traffic between the radio and the broker over your phone's internet connection.
58
+
59
+
The **MQTT proxy on this phone** toggle at the top of the MQTT settings screen shows whether this relay is currently running and lets you cut it off (or restart it) immediately — without editing and re-saving the device's MQTT configuration.
60
+
55
61
### Default Meshtastic Broker
56
62
57
63
The community maintains a public broker at `mqtt.meshtastic.org`. This is intended for general use and testing.
0 commit comments