mirror of
https://github.com/meshtastic/Meshtastic-Android.git
synced 2026-10-02 08:34:34 -04:00
docs: publish channels: main api
This commit is contained in:
github-actions[bot] committed
1 parent
c5d17d4d84
commit
404983bc5b
326 files changed
+2630
-2630
No files matched your search
@@ -95,7 +95,7 @@
|
||||
<h1 class="cover"><span>Robolectric</span><wbr><span>Ble</span><wbr><span><span>Bonding</span></span></h1>
|
||||
<div class="platform-hinted with-platform-tabs" data-platform-hinted="data-platform-hinted">
|
||||
<div class="platform-bookmarks-row" data-toggle-list="data-toggle-list"><button class="platform-bookmark" data-filterable-current=":core:testing/androidMain" data-filterable-set=":core:testing/androidMain" data-active="" data-toggle=":core:testing/androidMain">android</button></div>
|
||||
<div class="content sourceset-dependent-content" data-active="" data-togglable=":core:testing/androidMain"><div class="symbol monospace"><span class="token keyword">object </span><a href="index.html">RobolectricBleBonding</a><span class="source-link-wrapper"><span class="source-link" data-element-type="source-link">(<a href="https://github.com/meshtastic/Meshtastic-Android/blob/main/core/testing/src/androidMain/kotlin/org/meshtastic/core/testing/RobolectricBleBonding.kt#L44">source</a>)</span></span></div><p class="paragraph">Reusable Robolectric helpers for driving Android Bluetooth bonding logic in <code class="lang-kotlin">androidHostTest</code> source sets.</p><p class="paragraph">These let a unit test exercise the real <code class="lang-kotlin">AndroidBluetoothRepository.bond()</code> (and any future BLE bonding code) without an emulator and without a production seam. They rely on two Robolectric behaviors (verified against Robolectric 4.16.x):</p><ul><li><p class="paragraph"><a href="https://developer.android.com/reference/kotlin/android/bluetooth/BluetoothAdapter.html#getremotedevice">android.bluetooth.BluetoothAdapter.getRemoteDevice</a> caches the returned <a href="https://developer.android.com/reference/kotlin/android/bluetooth/BluetoothDevice.html">BluetoothDevice</a> by address in a static map, so the shadow configured here is the <i>same</i> instance production code reads when it calls <code class="lang-kotlin">getRemoteDevice(mac)</code> internally.</p></li><li><p class="paragraph"><span data-unresolved-link="org.robolectric.shadows/ShadowBluetoothDevice/createBond/#/PointingToDeclaration/">ShadowBluetoothDevice.createBond</span> calls <code class="lang-kotlin">checkForBluetoothConnectPermission()</code> first, so tests must call <a href="grant-bluetooth-connect-permission.html">grantBluetoothConnectPermission</a> or <code class="lang-kotlin">createBond()</code> throws <a href="https://developer.android.com/reference/kotlin/java/lang/SecurityException.html">SecurityException</a> instead of returning a value.</p></li></ul><p class="paragraph">Isolation note: because the device cache is static and survives across tests in the same JVM, give each test a distinct MAC so bond-state cannot bleed between tests.</p></div> </div>
|
||||
<div class="content sourceset-dependent-content" data-active="" data-togglable=":core:testing/androidMain"><div class="symbol monospace"><span class="token keyword">object </span><a href="index.html">RobolectricBleBonding</a><span class="source-link-wrapper"><span class="source-link" data-element-type="source-link">(<a href="https://github.com/meshtastic/Meshtastic-Android/blob/main/core/testing/src/androidMain/kotlin/org/meshtastic/core/testing/RobolectricBleBonding.kt#L44">source</a>)</span></span></div><p class="paragraph">Reusable Robolectric helpers for driving Android Bluetooth bonding logic in <code class="lang-kotlin">androidHostTest</code> source sets.</p><p class="paragraph">These let a unit test exercise the real <code class="lang-kotlin">AndroidBluetoothRepository.bond()</code> (and any future BLE bonding code) without an emulator and without a production seam. They rely on two Robolectric behaviors (verified against Robolectric 4.16.x):</p><ul><li><p class="paragraph"><a href="https://developer.android.com/reference/kotlin/android/bluetooth/BluetoothAdapter.html#getRemoteDevice(kotlin.ByteArray)">android.bluetooth.BluetoothAdapter.getRemoteDevice</a> caches the returned <a href="https://developer.android.com/reference/kotlin/android/bluetooth/BluetoothDevice.html">BluetoothDevice</a> by address in a static map, so the shadow configured here is the <i>same</i> instance production code reads when it calls <code class="lang-kotlin">getRemoteDevice(mac)</code> internally.</p></li><li><p class="paragraph"><span data-unresolved-link="org.robolectric.shadows/ShadowBluetoothDevice/createBond/#/PointingToDeclaration/">ShadowBluetoothDevice.createBond</span> calls <code class="lang-kotlin">checkForBluetoothConnectPermission()</code> first, so tests must call <a href="grant-bluetooth-connect-permission.html">grantBluetoothConnectPermission</a> or <code class="lang-kotlin">createBond()</code> throws <a href="https://developer.android.com/reference/kotlin/java/lang/SecurityException.html">SecurityException</a> instead of returning a value.</p></li></ul><p class="paragraph">Isolation note: because the device cache is static and survives across tests in the same JVM, give each test a distinct MAC so bond-state cannot bleed between tests.</p></div> </div>
|
||||
</div>
|
||||
<div class="tabbedcontent">
|
||||
<div class="tabs-section" tabs-section="tabs-section"><button class="section-tab" data-active="" data-togglable="CONSTRUCTOR,TYPE,PROPERTY,FUNCTION">Members</button></div>
|
||||
|
||||
+1
-1
@@ -94,7 +94,7 @@
|
||||
<div class="cover ">
|
||||
<h1 class="cover"><span>Connection</span><wbr><span>Action</span><wbr><span><span>Button</span></span></h1>
|
||||
</div>
|
||||
<div class="platform-hinted " data-platform-hinted="data-platform-hinted"><div class="content sourceset-dependent-content" data-active="" data-togglable=":feature:connections/commonMain"><div class="symbol monospace"><div class="block"><div class="block"><span class="token annotation builtin">@</span><a href="https://developer.android.com/reference/kotlin/androidx/compose/runtime/Composable.html"><span class="token annotation builtin">Composable</span></a></div></div><span class="token keyword">fun </span><a href="-connection-action-button.html"><span class="token function">ConnectionActionButton</span></a><span class="token punctuation">(</span><span class="parameters "><span class="parameter ">onClick<span class="token operator">: </span><span class="token punctuation">(</span><span class="token punctuation">)</span><span class="token operator"> -> </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-unit/index.html">Unit</a><span class="token punctuation">, </span></span><span class="parameter ">icon<span class="token operator">: </span><a href="https://developer.android.com/reference/kotlin/androidx/compose/ui/graphics/vector/ImageVector.html">ImageVector</a><span class="token punctuation">, </span></span><span class="parameter ">text<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-string/index.html">String</a><span class="token punctuation">, </span></span><span class="parameter ">modifier<span class="token operator">: </span><a href="https://developer.android.com/reference/kotlin/androidx/compose/ui/Modifier.html">Modifier</a><span class="token operator"> = </span>Modifier<span class="token punctuation">, </span></span><span class="parameter ">style<span class="token operator">: </span><a href="-connection-action-button-style/index.html">ConnectionActionButtonStyle</a><span class="token operator"> = </span>ConnectionActionButtonStyle.Filled<span class="token punctuation">, </span></span><span class="parameter ">enabled<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-boolean/index.html">Boolean</a><span class="token operator"> = </span><span class="token boolean">true</span><span class="token punctuation">, </span></span><span class="parameter ">iconContentDescription<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-string/index.html">String</a><span class="token operator">?</span><span class="token operator"> = </span>null</span></span><span class="token punctuation">)</span><span class="source-link-wrapper"><span class="source-link" data-element-type="source-link">(<a href="https://github.com/meshtastic/Meshtastic-Android/blob/main/feature/connections/src/commonMain/kotlin/org/meshtastic/feature/connections/ui/components/ConnectionActionButton.kt#L41">source</a>)</span></span></div><p class="paragraph">Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (<a href="https://developer.android.com/reference/kotlin/androidx/compose/material3/ButtonDefaults.html#iconsize">ButtonDefaults.IconSize</a>, <a href="https://developer.android.com/reference/kotlin/androidx/compose/material3/ButtonDefaults.html#iconspacing">ButtonDefaults.IconSpacing</a>, and the variant-appropriate <code class="lang-kotlin">*WithIconContentPadding</code>) so every scan / add / empty-state affordance renders identically.</p><h4 class="tableheader">Parameters</h4><div class="table"><div class="table-row table-row_content" data-filterable-current=":feature:connections/commonMain" data-filterable-set=":feature:connections/commonMain"><div class="main-subrow keyValue "><div class=""><span class="inline-flex"><div><u><span>icon</span><wbr><span>Content</span><wbr><span><span>Description</span></span></u></div></span></div><div><div class="title"><p class="paragraph">accessibility label for the leading icon. Defaults to <code class="lang-kotlin">null</code> because the visible <a href="-connection-action-button.html">text</a> usually describes the action; override when the icon carries information the text does not.</p></div></div></div></div></div></div></div>
|
||||
<div class="platform-hinted " data-platform-hinted="data-platform-hinted"><div class="content sourceset-dependent-content" data-active="" data-togglable=":feature:connections/commonMain"><div class="symbol monospace"><div class="block"><div class="block"><span class="token annotation builtin">@</span><a href="https://developer.android.com/reference/kotlin/androidx/compose/runtime/Composable.html"><span class="token annotation builtin">Composable</span></a></div></div><span class="token keyword">fun </span><a href="-connection-action-button.html"><span class="token function">ConnectionActionButton</span></a><span class="token punctuation">(</span><span class="parameters "><span class="parameter ">onClick<span class="token operator">: </span><span class="token punctuation">(</span><span class="token punctuation">)</span><span class="token operator"> -> </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-unit/index.html">Unit</a><span class="token punctuation">, </span></span><span class="parameter ">icon<span class="token operator">: </span><a href="https://developer.android.com/reference/kotlin/androidx/compose/ui/graphics/vector/ImageVector.html">ImageVector</a><span class="token punctuation">, </span></span><span class="parameter ">text<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-string/index.html">String</a><span class="token punctuation">, </span></span><span class="parameter ">modifier<span class="token operator">: </span><a href="https://developer.android.com/reference/kotlin/androidx/compose/ui/Modifier.html">Modifier</a><span class="token operator"> = </span>Modifier<span class="token punctuation">, </span></span><span class="parameter ">style<span class="token operator">: </span><a href="-connection-action-button-style/index.html">ConnectionActionButtonStyle</a><span class="token operator"> = </span>ConnectionActionButtonStyle.Filled<span class="token punctuation">, </span></span><span class="parameter ">enabled<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-boolean/index.html">Boolean</a><span class="token operator"> = </span><span class="token boolean">true</span><span class="token punctuation">, </span></span><span class="parameter ">iconContentDescription<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-string/index.html">String</a><span class="token operator">?</span><span class="token operator"> = </span>null</span></span><span class="token punctuation">)</span><span class="source-link-wrapper"><span class="source-link" data-element-type="source-link">(<a href="https://github.com/meshtastic/Meshtastic-Android/blob/main/feature/connections/src/commonMain/kotlin/org/meshtastic/feature/connections/ui/components/ConnectionActionButton.kt#L41">source</a>)</span></span></div><p class="paragraph">Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (<a href="https://developer.android.com/reference/kotlin/androidx/compose/material3/ButtonDefaults.html#IconSize">ButtonDefaults.IconSize</a>, <a href="https://developer.android.com/reference/kotlin/androidx/compose/material3/ButtonDefaults.html#IconSpacing">ButtonDefaults.IconSpacing</a>, and the variant-appropriate <code class="lang-kotlin">*WithIconContentPadding</code>) so every scan / add / empty-state affordance renders identically.</p><h4 class="tableheader">Parameters</h4><div class="table"><div class="table-row table-row_content" data-filterable-current=":feature:connections/commonMain" data-filterable-set=":feature:connections/commonMain"><div class="main-subrow keyValue "><div class=""><span class="inline-flex"><div><u><span>icon</span><wbr><span>Content</span><wbr><span><span>Description</span></span></u></div></span></div><div><div class="title"><p class="paragraph">accessibility label for the leading icon. Defaults to <code class="lang-kotlin">null</code> because the visible <a href="-connection-action-button.html">text</a> usually describes the action; override when the icon carries information the text does not.</p></div></div></div></div></div></div></div>
|
||||
</div>
|
||||
<div class="footer">
|
||||
<div class="footer--container">
|
||||
|
||||
@@ -158,7 +158,7 @@
|
||||
</span></span></div>
|
||||
<div>
|
||||
<div class="title">
|
||||
<div class="platform-hinted " data-platform-hinted="data-platform-hinted"><div class="content sourceset-dependent-content" data-active="" data-togglable=":feature:connections/commonMain"><div class="symbol monospace"><div class="block"><div class="block"><span class="token annotation builtin">@</span><a href="https://developer.android.com/reference/kotlin/androidx/compose/runtime/Composable.html"><span class="token annotation builtin">Composable</span></a></div></div><span class="token keyword">fun </span><a href="-connection-action-button.html"><span class="token function">ConnectionActionButton</span></a><span class="token punctuation">(</span><span class="parameters "><span class="parameter ">onClick<span class="token operator">: </span><span class="token punctuation">(</span><span class="token punctuation">)</span><span class="token operator"> -> </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-unit/index.html">Unit</a><span class="token punctuation">, </span></span><span class="parameter ">icon<span class="token operator">: </span><a href="https://developer.android.com/reference/kotlin/androidx/compose/ui/graphics/vector/ImageVector.html">ImageVector</a><span class="token punctuation">, </span></span><span class="parameter ">text<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-string/index.html">String</a><span class="token punctuation">, </span></span><span class="parameter ">modifier<span class="token operator">: </span><a href="https://developer.android.com/reference/kotlin/androidx/compose/ui/Modifier.html">Modifier</a><span class="token operator"> = </span>Modifier<span class="token punctuation">, </span></span><span class="parameter ">style<span class="token operator">: </span><a href="-connection-action-button-style/index.html">ConnectionActionButtonStyle</a><span class="token operator"> = </span>ConnectionActionButtonStyle.Filled<span class="token punctuation">, </span></span><span class="parameter ">enabled<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-boolean/index.html">Boolean</a><span class="token operator"> = </span><span class="token boolean">true</span><span class="token punctuation">, </span></span><span class="parameter ">iconContentDescription<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-string/index.html">String</a><span class="token operator">?</span><span class="token operator"> = </span>null</span></span><span class="token punctuation">)</span></div><div class="brief "><p class="paragraph">Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (<a href="https://developer.android.com/reference/kotlin/androidx/compose/material3/ButtonDefaults.html#iconsize">ButtonDefaults.IconSize</a>, <a href="https://developer.android.com/reference/kotlin/androidx/compose/material3/ButtonDefaults.html#iconspacing">ButtonDefaults.IconSpacing</a>, and the variant-appropriate <code class="lang-kotlin">*WithIconContentPadding</code>) so every scan / add / empty-state affordance renders identically.</p></div></div></div>
|
||||
<div class="platform-hinted " data-platform-hinted="data-platform-hinted"><div class="content sourceset-dependent-content" data-active="" data-togglable=":feature:connections/commonMain"><div class="symbol monospace"><div class="block"><div class="block"><span class="token annotation builtin">@</span><a href="https://developer.android.com/reference/kotlin/androidx/compose/runtime/Composable.html"><span class="token annotation builtin">Composable</span></a></div></div><span class="token keyword">fun </span><a href="-connection-action-button.html"><span class="token function">ConnectionActionButton</span></a><span class="token punctuation">(</span><span class="parameters "><span class="parameter ">onClick<span class="token operator">: </span><span class="token punctuation">(</span><span class="token punctuation">)</span><span class="token operator"> -> </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-unit/index.html">Unit</a><span class="token punctuation">, </span></span><span class="parameter ">icon<span class="token operator">: </span><a href="https://developer.android.com/reference/kotlin/androidx/compose/ui/graphics/vector/ImageVector.html">ImageVector</a><span class="token punctuation">, </span></span><span class="parameter ">text<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-string/index.html">String</a><span class="token punctuation">, </span></span><span class="parameter ">modifier<span class="token operator">: </span><a href="https://developer.android.com/reference/kotlin/androidx/compose/ui/Modifier.html">Modifier</a><span class="token operator"> = </span>Modifier<span class="token punctuation">, </span></span><span class="parameter ">style<span class="token operator">: </span><a href="-connection-action-button-style/index.html">ConnectionActionButtonStyle</a><span class="token operator"> = </span>ConnectionActionButtonStyle.Filled<span class="token punctuation">, </span></span><span class="parameter ">enabled<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-boolean/index.html">Boolean</a><span class="token operator"> = </span><span class="token boolean">true</span><span class="token punctuation">, </span></span><span class="parameter ">iconContentDescription<span class="token operator">: </span><a href="https://kotlinlang.org/api/core/kotlin-stdlib/kotlin/-string/index.html">String</a><span class="token operator">?</span><span class="token operator"> = </span>null</span></span><span class="token punctuation">)</span></div><div class="brief "><p class="paragraph">Shared "icon + label" button used throughout the Connections screen. Centralises M3 sizing conventions (<a href="https://developer.android.com/reference/kotlin/androidx/compose/material3/ButtonDefaults.html#IconSize">ButtonDefaults.IconSize</a>, <a href="https://developer.android.com/reference/kotlin/androidx/compose/material3/ButtonDefaults.html#IconSpacing">ButtonDefaults.IconSpacing</a>, and the variant-appropriate <code class="lang-kotlin">*WithIconContentPadding</code>) so every scan / add / empty-state affordance renders identically.</p></div></div></div>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
|
||||
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
+160
-160
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
File diff suppressed because one or more lines are too long.
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | الوصف |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | الوصف |
|
||||
------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | الوصف |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
Output duration (milliseconds) | How long a single alert lasts |
|
||||
Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | الوصف |
|
||||
--------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | الوصف |
|
||||
-------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Range test enabled | Activate range testing |
|
||||
Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | الوصف |
|
||||
-------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update interval (seconds) | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | الوصف |
|
||||
--------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update Interval | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | الوصف |
|
||||
---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum broadcast (seconds) | Minimum time between alert broadcasts |
|
||||
State broadcast (seconds) | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
Setting | الوصف |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | الوصف |
|
||||
-------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update interval (seconds) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | الوصف |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update Interval | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Setting | الوصف | Default |
|
||||
------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
الجهة | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
Setting | الوصف | Default |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
الجهة | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Апісанне |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Апісанне |
|
||||
------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Апісанне |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
Output duration (milliseconds) | How long a single alert lasts |
|
||||
Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Апісанне |
|
||||
--------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Апісанне |
|
||||
-------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Range test enabled | Activate range testing |
|
||||
Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Апісанне |
|
||||
-------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update interval (seconds) | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Апісанне |
|
||||
--------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update Interval | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | Апісанне |
|
||||
---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum broadcast (seconds) | Minimum time between alert broadcasts |
|
||||
State broadcast (seconds) | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
Setting | Апісанне |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | Апісанне |
|
||||
-------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update interval (seconds) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | Апісанне |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update Interval | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Setting | Апісанне | Default |
|
||||
------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Рэгіён | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
Setting | Апісанне | Default |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Рэгіён | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Настройка | Описание |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Съгласен съм. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Настройка | Описание |
|
||||
----------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Съгласен съм. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Настройка | Описание |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Външните известия са активирани | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Използване на PWM зумер | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
Output duration (milliseconds) | How long a single alert lasts |
|
||||
Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Тон на звънене | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Настройка | Описание |
|
||||
--------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Външните известия са активирани | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Използване на PWM зумер | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Тон на звънене | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Настройка | Описание |
|
||||
-------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Тест на обхвата е активиран | Activate range testing |
|
||||
Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Запазване на .CSV в хранилище (само за ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Настройка | Описание |
|
||||
------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Интервал на актуализиране (секунди) | How often to broadcast neighbor list |
|
||||
Предаване през LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Настройка | Описание |
|
||||
------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Интервал на актуализиране | How often to broadcast neighbor list |
|
||||
Предаване през LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -223,8 +223,8 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Използване на режим INPUT_PULLUP | Enable the pin's internal pull-up resistor |
|
||||
Minimum broadcast (seconds) | Minimum time between alert broadcasts |
|
||||
State broadcast (seconds) | Periodic state broadcast interval |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Приятелско име | Custom name for this sensor |
|
||||
|
||||
@@ -232,12 +232,12 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Настройка | Описание |
|
||||
------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter е активиран | Activate people counting |
|
||||
Интервал на актуализиране (секунди) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Настройка | Описание |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter е активиран | Activate people counting |
|
||||
Интервал на актуализиране | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -76,7 +76,7 @@ On **Settings → LoRa**.
|
||||
Регион | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Предварително зададени | Speed/range tradeoff | LongFast |
|
||||
Брой отскоци | Maximum retransmit hops | 3 |
|
||||
Мощност на предаване | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Използване на предварително зададени настройки | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Descripció |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Descripció |
|
||||
------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Descripció |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
Output duration (milliseconds) | How long a single alert lasts |
|
||||
Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Descripció |
|
||||
--------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Descripció |
|
||||
-------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Range test enabled | Activate range testing |
|
||||
Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Descripció |
|
||||
-------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update interval (seconds) | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Descripció |
|
||||
--------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update Interval | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | Descripció |
|
||||
---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum broadcast (seconds) | Minimum time between alert broadcasts |
|
||||
State broadcast (seconds) | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
Setting | Descripció |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | Descripció |
|
||||
-------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update interval (seconds) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | Descripció |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update Interval | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Setting | Descripció | Default |
|
||||
------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Regió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
Setting | Descripció | Default |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Regió | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -55,7 +55,7 @@ until you agree:
|
||||
-------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Souhlasím. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Interval hlášení mapy | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -91,8 +91,8 @@ and each can drive the LED, the buzzer and the vibration motor separately, givin
|
||||
Výstupní pin vybračního motorku (GPIO) | Pin the vibration motor is wired to |
|
||||
Použít PWM bzučák | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Použít I2S jako bzučák | Send the alert through an I2S audio output instead |
|
||||
Doba trvání výstupu (v milisekundách) | How long a single alert lasts |
|
||||
Interval opakovaného zvonění | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Vyzváněcí tón | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Nastavení | Popis |
|
||||
------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- |
|
||||
Test pokrytí povolen | Activate range testing |
|
||||
Interval odesílání zpráv | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Uložit .CSV do úložiště (pouze ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Nastavení | Popis |
|
||||
----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Informace o sousedech povoleny | Activate neighbor broadcasting |
|
||||
Interval aktualizace (v sekundách) | How often to broadcast neighbor list |
|
||||
Přenos přes LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Nastavení | Popis |
|
||||
------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Informace o sousedech povoleny | Activate neighbor broadcasting |
|
||||
Interval aktualizace GPS | How often to broadcast neighbor list |
|
||||
Přenos přes LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Nastavení | Popis |
|
||||
----------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detekční senzor povolen | Activate detection sensor |
|
||||
GPIO pin ke sledování | GPIO pin connected to sensor |
|
||||
Typ spouštění detekce | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Použít INPUT_PULLUP režim | Enable the pin's internal pull-up resistor |
|
||||
Minimální vysílání (sekundy) | Minimum time between alert broadcasts |
|
||||
Vysílání stavu (v sekundách) | Periodic state broadcast interval |
|
||||
Poslat zvonek s výstražnou zprávou | Include bell character in alerts |
|
||||
Přezdívka | Custom name for this sensor |
|
||||
Nastavení | Popis |
|
||||
---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detekční senzor povolen | Activate detection sensor |
|
||||
GPIO pin ke sledování | GPIO pin connected to sensor |
|
||||
Typ spouštění detekce | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Použít INPUT_PULLUP režim | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Poslat zvonek s výstražnou zprávou | Include bell character in alerts |
|
||||
Přezdívka | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Nastavení | Popis |
|
||||
----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter povolen | Activate people counting |
|
||||
Interval aktualizace (v sekundách) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Nastavení | Popis |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter povolen | Activate people counting |
|
||||
Interval aktualizace GPS | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -76,7 +76,7 @@ On **Settings → LoRa**.
|
||||
Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Předvolby | Speed/range tradeoff | LongFast |
|
||||
Počet skoků | Maximum retransmit hops | 3 |
|
||||
Vysílací výkon | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Ruční nastavení frekvence | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Použít předvolbu | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Einstellung | Beschreibung |
|
||||
----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Ich stimme zu. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Kartenberichtsintervall (Sekunden) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Einstellung | Beschreibung |
|
||||
------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Ich stimme zu. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Einstellung | Beschreibung |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Externe Benachrichtigungen aktiviert | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Ausgabe LED (GPIO) | Pin the LED is wired to |
|
||||
Ausgabe LED aktiv hoch | Whether the LED pin is active high or low |
|
||||
Ausgabe Summer (GPIO) | Pin the buzzer is wired to |
|
||||
Ausgabe Vibration (GPIO) | Pin the vibration motor is wired to |
|
||||
Benutze PWM Summer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
I2S als Buzzer verwenden | Send the alert through an I2S audio output instead |
|
||||
Ausgabedauer (GPIO) | How long a single alert lasts |
|
||||
Nervige Verzögerung (Sekunden) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Klingelton | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Einstellung | Beschreibung |
|
||||
------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Externe Benachrichtigungen aktiviert | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Ausgabe LED (GPIO) | Pin the LED is wired to |
|
||||
Ausgabe LED aktiv hoch | Whether the LED pin is active high or low |
|
||||
Ausgabe Summer (GPIO) | Pin the buzzer is wired to |
|
||||
Ausgabe Vibration (GPIO) | Pin the vibration motor is wired to |
|
||||
Benutze PWM Summer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
I2S als Buzzer verwenden | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nervige Verzögerung | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Klingelton | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Einstellung | Beschreibung |
|
||||
------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Reichweitentest aktiviert | Activate range testing |
|
||||
Sendernachrichtenintervall (Sekunden) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sendeintervall | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Speichere .CSV im Speicher (nur ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Einstellung | Beschreibung |
|
||||
------------------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Nachbarinformationen aktiviert | Activate neighbor broadcasting |
|
||||
Aktualisierungsintervall (Sekunden) | How often to broadcast neighbor list |
|
||||
Übertragen über LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Einstellung | Beschreibung |
|
||||
------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Nachbarinformationen aktiviert | Activate neighbor broadcasting |
|
||||
GPS Abfrageintervall | How often to broadcast neighbor list |
|
||||
Übertragen über LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Einstellung | Beschreibung |
|
||||
------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Erkennungssensor aktiviert | Activate detection sensor |
|
||||
Zu überwachender GPIO-Pin | GPIO pin connected to sensor |
|
||||
Typ der Erkennungsauslösung | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Eingang PULLUP Einstellung | Enable the pin's internal pull-up resistor |
|
||||
Minimale Übertragungszeit (Sekunden) | Minimum time between alert broadcasts |
|
||||
Statusübertragung (Sekunden) | Periodic state broadcast interval |
|
||||
Glocke mit Warnmeldung senden | Include bell character in alerts |
|
||||
Anzeigename | Custom name for this sensor |
|
||||
Einstellung | Beschreibung |
|
||||
----------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Erkennungssensor aktiviert | Activate detection sensor |
|
||||
Zu überwachender GPIO-Pin | GPIO pin connected to sensor |
|
||||
Typ der Erkennungsauslösung | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Eingang PULLUP Einstellung | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
Übertragungsintervall | Periodic state broadcast interval |
|
||||
Glocke mit Warnmeldung senden | Include bell character in alerts |
|
||||
Anzeigename | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Einstellung | Beschreibung |
|
||||
------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Besucherzähler aktiviert | Activate people counting |
|
||||
Aktualisierungsintervall (Sekunden) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Einstellung | Beschreibung |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Besucherzähler aktiviert | Activate people counting |
|
||||
GPS Abfrageintervall | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Einstellung | Beschreibung | Standardwert |
|
||||
-------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Voreinstellungen | Speed/range tradeoff | LongFast |
|
||||
Anzahl der Weiterleitungen | Maximum retransmit hops | 3 |
|
||||
Sendeleistung | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Frequenz überschreiben | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Voreinstellung verwenden | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spreizfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Fehlerkorrektur | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandbreite | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequenzschlitz | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Senden aktiviert | Turning this off makes the node receive-only | On |
|
||||
Duty-Cycle überschreiben | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Aus |
|
||||
MQTT ignorieren | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
OK für MQTT | Allow your packets to be forwarded to MQTT by gateways | Aus |
|
||||
Empfangsverstärkung | Extra receive gain on SX126x radios; costs a little current | Aus |
|
||||
PA Fan deaktiviert | Turn off the power-amplifier fan on hardware that has one | Aus |
|
||||
Einstellung | Beschreibung | Standardwert |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Region | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Voreinstellungen | Speed/range tradeoff | LongFast |
|
||||
Anzahl der Weiterleitungen | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequenz überschreiben | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Voreinstellung verwenden | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spreizfaktor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Fehlerkorrektur | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandbreite | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequenzschlitz | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Senden aktiviert | Turning this off makes the node receive-only | On |
|
||||
Duty-Cycle überschreiben | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Aus |
|
||||
MQTT ignorieren | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
OK für MQTT | Allow your packets to be forwarded to MQTT by gateways | Aus |
|
||||
Empfangsverstärkung | Extra receive gain on SX126x radios; costs a little current | Aus |
|
||||
PA Fan deaktiviert | Turn off the power-amplifier fan on hardware that has one | Aus |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Περιγραφή |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Περιγραφή |
|
||||
------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Περιγραφή |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
Output duration (milliseconds) | How long a single alert lasts |
|
||||
Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Περιγραφή |
|
||||
--------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Περιγραφή |
|
||||
-------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Range test enabled | Activate range testing |
|
||||
Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Περιγραφή |
|
||||
-------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update interval (seconds) | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Περιγραφή |
|
||||
--------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update Interval | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | Περιγραφή |
|
||||
---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum broadcast (seconds) | Minimum time between alert broadcasts |
|
||||
State broadcast (seconds) | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
Setting | Περιγραφή |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | Περιγραφή |
|
||||
-------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update interval (seconds) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | Περιγραφή |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update Interval | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Setting | Περιγραφή | Default |
|
||||
------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Περιφέρεια | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
Setting | Περιγραφή | Default |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Περιφέρεια | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Descripción |
|
||||
------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Estoy de acuerdo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Tiempo entre Reportes de Posición (en Segundos) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Descripción |
|
||||
--------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Estoy de acuerdo. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Descripción |
|
||||
--------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Notificaciones externas activadas | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Salida LED (pin GPIO) | Pin the LED is wired to |
|
||||
LED de salida activo en alto | Whether the LED pin is active high or low |
|
||||
Salida buzzer (pin GPIO) | Pin the buzzer is wired to |
|
||||
Salida vibratoria (pin GPIO) | Pin the vibration motor is wired to |
|
||||
Utilizar buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Utilizar el Buzzer como uno I2S | Send the alert through an I2S audio output instead |
|
||||
Duración en las salidas (milisegundos) | How long a single alert lasts |
|
||||
| Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Tono de notificación | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Descripción |
|
||||
----------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Notificaciones externas activadas | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Salida LED (pin GPIO) | Pin the LED is wired to |
|
||||
LED de salida activo en alto | Whether the LED pin is active high or low |
|
||||
Salida buzzer (pin GPIO) | Pin the buzzer is wired to |
|
||||
Salida vibratoria (pin GPIO) | Pin the vibration motor is wired to |
|
||||
Utilizar buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Utilizar el Buzzer como uno I2S | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Tono de notificación | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Descripción |
|
||||
------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Test de alcance activado | Activate range testing |
|
||||
Periodo entre los mensajes del transmisor (segundos) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Guardar el .CSV en el almacenamiento (Esp32) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Descripción |
|
||||
--------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Información de Vecinos | Activate neighbor broadcasting |
|
||||
Intervalo de refresco (segundos) | How often to broadcast neighbor list |
|
||||
Transmitir en LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Descripción |
|
||||
-------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Información de Vecinos | Activate neighbor broadcasting |
|
||||
Intervalo de actualización | How often to broadcast neighbor list |
|
||||
Transmitir en LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | Descripción |
|
||||
----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Sensor detector activado | Activate detection sensor |
|
||||
Pin GPIO para monitorizar | GPIO pin connected to sensor |
|
||||
Tipo de detección para activar | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Utilizar el modo de entrada PULL_UP | Enable the pin's internal pull-up resistor |
|
||||
Tiempo mínimo de transmisión (segundos) | Minimum time between alert broadcasts |
|
||||
Periodo entre transmisión de estado (segundos) | Periodic state broadcast interval |
|
||||
Mandar la campana con el mensaje de alerta | Include bell character in alerts |
|
||||
Mote | Custom name for this sensor |
|
||||
Setting | Descripción |
|
||||
-------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Sensor detector activado | Activate detection sensor |
|
||||
Pin GPIO para monitorizar | GPIO pin connected to sensor |
|
||||
Tipo de detección para activar | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Utilizar el modo de entrada PULL_UP | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Mandar la campana con el mensaje de alerta | Include bell character in alerts |
|
||||
Mote | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | Descripción |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Activar el Contador de Paquetes | Activate people counting |
|
||||
Intervalo de refresco (segundos) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | Descripción |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Activar el Contador de Paquetes | Activate people counting |
|
||||
Intervalo de actualización | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Setting | Descripción | Por defecto |
|
||||
----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Predefinidos | Speed/range tradeoff | LongFast |
|
||||
Número de saltos | Maximum retransmit hops | 3 |
|
||||
Potencia de transmisión | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Sobreescribir frecuencia | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Usar predefinido | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Factor de dispersión | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Ratio de Codificación | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Ancho de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Banda de Frecuencia | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmisión habilitada | Turning this off makes the node receive-only | On |
|
||||
Sobreescribir el Tiempo de Trabajo | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignorar Paquetes MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Permitir MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
Aumentar ganancia de RX | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
Ventilador del Amplificador apagado | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
Setting | Descripción | Por defecto |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Región | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Predefinidos | Speed/range tradeoff | LongFast |
|
||||
Número de saltos | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Sobreescribir frecuencia | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Usar predefinido | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Factor de dispersión | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Ratio de Codificación | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Ancho de banda | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Banda de Frecuencia | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmisión habilitada | Turning this off makes the node receive-only | On |
|
||||
Sobreescribir el Tiempo de Trabajo | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignorar Paquetes MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Permitir MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
Aumentar ganancia de RX | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
Ventilador del Amplificador apagado | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ Naabriinfo moodul võimaldab igal sõlmel levitada nimekirja sõlmedest, mida se
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Luba moodul.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Teised sõlmed, millel on naabriinfo lubatud, teevad sama.
|
||||
|
||||
@@ -90,7 +90,7 @@ Konfigureeri oma sõlm nii, et see osutaks sinu privaatsele maaklerile sobivate
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Sätted | Kirjeldus |
|
||||
-------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Nõustun. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Kaardi raporti sagedus (sekund) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Sätted | Kirjeldus |
|
||||
------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Nõustun. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
Vaata [MQTT](mqtt) üksikasjalikumat kasutusjuhendit, mis sisaldab teavet krüpteerimise, privaatsuse ja vahendaja seadistamise kohta,.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Kasulik seadmet
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Sätted | Kirjeldus |
|
||||
--------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Luba Välised teated | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Väljund LED (GPIO) | Pin the LED is wired to |
|
||||
Väljund LED aktiivne | Whether the LED pin is active high or low |
|
||||
Väljund summer (GPIO) | Pin the buzzer is wired to |
|
||||
Väljund värin (GPIO) | Pin the vibration motor is wired to |
|
||||
Kasuta PWM summerit | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Kasuta I2S summerina | Send the alert through an I2S audio output instead |
|
||||
Väljundi kestvus (millisekundit) | How long a single alert lasts |
|
||||
Häire ajalõpp (sekundit) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Helin | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Sätted | Kirjeldus |
|
||||
---------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Luba Välised teated | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Väljund LED (GPIO) | Pin the LED is wired to |
|
||||
Väljund LED aktiivne | Whether the LED pin is active high or low |
|
||||
Väljund summer (GPIO) | Pin the buzzer is wired to |
|
||||
Väljund värin (GPIO) | Pin the vibration motor is wired to |
|
||||
Kasuta PWM summerit | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Kasuta I2S summerina | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Helin | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automatiseeritud vahemiku testimise tööriist sõlmede vahelise ühenduse kvali
|
||||
Sätted | Kirjeldus |
|
||||
--------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Ulatustest lubatud | Aktiveeri levi test |
|
||||
Saatja sõnumi sagedus (sekundit) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Salvesta .CSV faili (ainult ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO juhtimine kärgvõrgu kaudu. Võimaldab kaugsõlmel lugeda või kirjutada G
|
||||
|
||||
Levitab teavet otse kuuldud naabrite kohta, võimaldades kärgvõrgu topoloogia kaardistamist. Iga lubatud sõlm jagab perioodiliselt nimekirja teistest sõlmedest, mida ta kuuleb ja nende signaali kvaliteedist.
|
||||
|
||||
Sätted | Kirjeldus |
|
||||
----------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Naabruskonna teave lubatud | Aktiveeri naabrite leviring |
|
||||
Uuenduste sagedus (sekundit) | Kui tihti naabrite nimekirja levitada |
|
||||
Saada LoRa kaudu | Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval |
|
||||
Sätted | Kirjeldus |
|
||||
-------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Naabruskonna teave lubatud | Aktiveeri naabrite leviring |
|
||||
GPS-i küsimise intervall | Kui tihti naabrite nimekirja levitada |
|
||||
Saada LoRa kaudu | Edasta naabriinfot ka LoRa kaudu, mitte ainult MQTT/telefoni kaudu. Vaikimisi võtit ja nime kasutavat kanalit pole saadaval |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Juhib toetatud riistvaral NeoPixeli või muid adresseeritavaid RGB LEDe. Saab ka
|
||||
|
||||
Muudab sõlme liikumis- või ukseanduri hoiatussüsteemiks. Kui GPIO sisend tuvastab oleku muutuse (liikumine tuvastatud, uks avatud), levitab sõlm kärgvõrgu kaudu hoiatusteate.
|
||||
|
||||
Sätted | Kirjeldus |
|
||||
------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
|
||||
Tuvastusandur lubatud | Aktiveeri tuvastusandur |
|
||||
GPIO klemmi jälgimine | GPIO sisend on anduriga ühendatud |
|
||||
Identifitseerimistüüp | Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav) |
|
||||
Kasuta INPUT_PULLUP režiimi | Enable the pin's internal pull-up resistor |
|
||||
Minimaalne edastusaeg (sekund) | Minimaalne aeg hoiatusteadete levitamisel |
|
||||
Oleku edastus (sekund) | Perioodilise oleku levitamise intervall |
|
||||
Saada kõll koos hoiatussõnumiga | Lisa märguannetesse hoiatuskella sümbol |
|
||||
Kasutajasõbralik nimi | Selle anduri kohandatud nimi |
|
||||
Sätted | Kirjeldus |
|
||||
------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
|
||||
Tuvastusandur lubatud | Aktiveeri tuvastusandur |
|
||||
GPIO klemmi jälgimine | GPIO sisend on anduriga ühendatud |
|
||||
Identifitseerimistüüp | Kuidas klemmi olek vastab tuvastussündmusele (nt aktiivne kõrge/madal, serva poolt käivitatav) |
|
||||
Kasuta INPUT_PULLUP režiimi | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimaalne aeg hoiatusteadete levitamisel |
|
||||
State Broadcast Interval | Perioodilise oleku levitamise intervall |
|
||||
Saada kõll koos hoiatussõnumiga | Lisa märguannetesse hoiatuskella sümbol |
|
||||
Kasutajasõbralik nimi | Selle anduri kohandatud nimi |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Loendab lähedalasuvaid seadmeid, kuulates passiivselt sondimistaotlusi, mida telefonid ja sülearvutid võrkude skannimisel edastavad. Available only on ESP32 devices.
|
||||
|
||||
Sätted | Kirjeldus |
|
||||
----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter lubatud | Aktiveeri inimeste loendamine |
|
||||
Uuenduste sagedus (sekundit) | Kui tihti loendeid esitada |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Sätted | Kirjeldus |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter lubatud | Aktiveeri inimeste loendamine |
|
||||
GPS-i küsimise intervall | Kui tihti loendeid esitada |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Vihje:** Paxloendur on kasulik jalakäijate liikluse hindamiseks matkaradade alguses, ürituste toimumiskohtades või muudes kohtades. Arvud on ligikaudsed – üks inimene võib kaasas kanda mitut seadet.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Sätted | Kirjeldus | Vaikimisi |
|
||||
------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
|
||||
Regioon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Määramata (tuleb seadistada) |
|
||||
Eelseadistused | Speed/range tradeoff | LongFast |
|
||||
Hüpete arv | Maks uuesti saadetud hüpet | 3 |
|
||||
Saatevõimsus | Transmission power (dBm); 0 = max allowed for region | 0 (regiooni maks) |
|
||||
Tühista sagedus | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Kasuta eelseadistust | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Levitustegur | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Kodeerimiskiirus | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Ribalaius | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Sageduspesa | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Edastus lubatud | Turning this off makes the node receive-only | On |
|
||||
Töötsükli tühistamine | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Väljas |
|
||||
Keela MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok MQTTi | Allow your packets to be forwarded to MQTT by gateways | Väljas |
|
||||
RX võimendatud võimendus | Extra receive gain on SX126x radios; costs a little current | Väljas |
|
||||
PA ventilaator keelatud | Turn off the power-amplifier fan on hardware that has one | Väljas |
|
||||
Sätted | Kirjeldus | Vaikimisi |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------- |
|
||||
Regioon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Määramata (tuleb seadistada) |
|
||||
Eelseadistused | Speed/range tradeoff | LongFast |
|
||||
Hüpete arv | Maks uuesti saadetud hüpet | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (regiooni maks) |
|
||||
Tühista sagedus | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Kasuta eelseadistust | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Levitustegur | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Kodeerimiskiirus | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Ribalaius | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Sageduspesa | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Edastus lubatud | Turning this off makes the node receive-only | On |
|
||||
Töötsükli tühistamine | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Väljas |
|
||||
Keela MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok MQTTi | Allow your packets to be forwarded to MQTT by gateways | Väljas |
|
||||
RX võimendatud võimendus | Extra receive gain on SX126x radios; costs a little current | Väljas |
|
||||
PA ventilaator keelatud | Turn off the power-amplifier fan on hardware that has one | Väljas |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ Naapuritieto-moduuli antaa jokaisen radion lähettää listan radioista, jotka s
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Ota moduuli käyttöön.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Myös muut radiot, joissa naapuritieto on käytössä, toimivat samalla tavalla.
|
||||
|
||||
@@ -88,7 +88,7 @@ Määritä radiosi osoittamaan omaan välityspalvelimeesi oikeilla tunnistetiedo
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Asetus | Kuvaus |
|
||||
--------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Hyväksyn. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Karttaraportoinnin aikaväli (sekuntia) | Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Asetus | Kuvaus |
|
||||
------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Hyväksyn. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | Kuinka usein sijainti julkaistaan. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
Katso [MQTT](mqtt) saadaksesi yksityiskohtaisen käyttöoppaan, joka sisältää salauksen, tietosuojan ja välityspalvelimen määrityksen.
|
||||
|
||||
@@ -90,8 +90,8 @@ Käynnistimiä on kaksi – saapuva **viesti** ja vastaanotettu **BEL**-ohjausme
|
||||
Ulostulon värinä (GPIO) | Värinämoottori on kytketty nastaan |
|
||||
Käytä PWM-äänimerkkiä | Ohjaa summeria PWM:llä, jolloin voidaan toistaa ääniä yhden kiinteän taajuuden sijaan |
|
||||
Käytä I2S protokollaa äänimerkille | Lähetä hälytys sen sijaan I2S-äänilähdön kautta |
|
||||
Ulostulon kesto (millisekuntia) | Kuinka kauan yksittäinen hälytys kestää |
|
||||
Hälytysaikakatkaisu (sekuntia) | Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä |
|
||||
GPIO Output Duration | Kuinka kauan yksittäinen hälytys kestää |
|
||||
Toistokehotuksen aikakatkaisu | Toista hälytystä tämän ajan, kunnes se kuitataan. 0 poistaa toistuvan muistutuksen käytöstä |
|
||||
Soittoääni | PWM-summerilla toistettava RTTTL-soittoääni. Voidaan tuoda tiedostosta |
|
||||
|
||||
### Store & Forward module
|
||||
@@ -121,7 +121,7 @@ Automaattinen kuuluvuustestityökalu radioiden välisen yhteyden laadun arvioint
|
||||
Asetus | Kuvaus |
|
||||
------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Kuuluvuustesti käytössä | Ota kuuluvuustesti käyttöön |
|
||||
Viestien lähetyksen aikaväli (sekuntia) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Tallenna .CSV (ESP32 ainoastaan) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -193,11 +193,11 @@ GPIO-ohjaus mesh-verkon kautta. Mahdollistaa etäradion lukea tai kirjoittaa GPI
|
||||
|
||||
Lähettää tietoa suoraan kuulluista naapureista mahdollistaen verkon topologian kartoituksen. Jokainen käyttöön otettu radio jakaa säännöllisesti luettelon muista radioista, jotka se kuulee, sekä niiden signaalin laadun.
|
||||
|
||||
Asetus | Kuvaus |
|
||||
-------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Naapuritiedot käytössä | Ota naapuritiedon lähetys käyttöön |
|
||||
Päivityksen aikaväli (sekuntia) | Kuinka usein naapuriluettelo lähetetään |
|
||||
Lähetä LoRa:n kautta | Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä |
|
||||
Asetus | Kuvaus |
|
||||
------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Naapuritiedot käytössä | Ota naapuritiedon lähetys käyttöön |
|
||||
GPS-kyselyn aikaväli | Kuinka usein naapuriluettelo lähetetään |
|
||||
Lähetä LoRa:n kautta | Lähetä myös naapuritiedot LoRa:n kautta, ei pelkästään MQTT:n tai puhelimen kautta. Ei käytettävissä kanavalla, joka käyttää oletusavainta ja nimeä |
|
||||
|
||||
Katso [Paikallinen mesh-haku](discovery), miten naapuritietoja käytetään mesh-verkon rakenteen tutkimiseen.
|
||||
|
||||
@@ -215,27 +215,27 @@ Ohjaa tuetuissa laitteissa olevaa NeoPixeliä tai muita osoitteellisia RGB-LEDej
|
||||
|
||||
Muuttaa radiosi liike- tai ovitunnistimeen perustuvaksi hälytysjärjestelmäksi. Kun GPIO-pinni havaitsee tilamuutoksen (liike havaittu, ovi avattu), radio lähettää hälytysviestin verkkoon.
|
||||
|
||||
Asetus | Kuvaus |
|
||||
------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Tunnistinsensori käytössä | Ota tunnistusanturi käyttöön |
|
||||
GPIO-pinni valvontaa varten | Anturiin kytketty GPIO-pinni |
|
||||
Tunnistuksen tyyppi | Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu) |
|
||||
Käytä INPUT_PULLUP tilaa | Ota pinnin sisäinen ylösvetovastus käyttöön |
|
||||
Minimilähetys (sekuntia) | Hälytyslähetysten vähimmäisaika |
|
||||
Tilatiedon lähetys (sekuntia) | Tilatiedon lähetysväli |
|
||||
Lähetä äänimerkki hälytyssanoman kanssa | Sisällytä soittomerkkimerkki hälytyksiin |
|
||||
Käyttäjäystävällinen nimi | Tälle anturille määritetty nimi |
|
||||
Asetus | Kuvaus |
|
||||
--------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Tunnistinsensori käytössä | Ota tunnistusanturi käyttöön |
|
||||
GPIO-pinni valvontaa varten | Anturiin kytketty GPIO-pinni |
|
||||
Tunnistuksen tyyppi | Miten pinnin tila vastaa havaitsemistapahtumaa (esim. aktiivinen korkea/matala taso tai reunalaukaisu) |
|
||||
Käytä INPUT_PULLUP tilaa | Ota pinnin sisäinen ylösvetovastus käyttöön |
|
||||
Minimum time between detection broadcasts | Hälytyslähetysten vähimmäisaika |
|
||||
State Broadcast Interval | Tilatiedon lähetysväli |
|
||||
Lähetä äänimerkki hälytyssanoman kanssa | Sisällytä soittomerkkimerkki hälytyksiin |
|
||||
Käyttäjäystävällinen nimi | Tälle anturille määritetty nimi |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
Henkilöt, jotka lasketaan WiFi- ja BLE-hakukyselyiden perusteella. Laskee lähellä olevia laitteita kuuntelemalla passiivisesti koepyyntöjä, joita puhelimet ja kannettavat tietokoneet lähettävät etsiessään verkkoja. Saatavilla vain ESP32-laitteissa.
|
||||
|
||||
Asetus | Kuvaus |
|
||||
-------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
PAX-laskuri käytössä | Ota henkilölaskenta käyttöön |
|
||||
Päivityksen aikaväli (sekuntia) | Kuinka usein laskentatiedot raportoidaan |
|
||||
WiFi-signaalin RSSI-kynnys | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE-signaalin RSSI-kynnys | Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm) |
|
||||
Asetus | Kuvaus |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
PAX-laskuri käytössä | Ota henkilölaskenta käyttöön |
|
||||
GPS-kyselyn aikaväli | Kuinka usein laskentatiedot raportoidaan |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | Sama raja-arvo BLE-mainospaketeille (oletus: -80 dBm) |
|
||||
|
||||
> 💡 **Vinkki:** PAX-laskuri on hyödyllinen jalankulkijamäärien arviointiin retkeilyreittien lähtöpisteissä, tapahtumapaikoilla tai muissa kohteissa. Laskentatulokset ovat arvioita — yhdellä henkilöllä voi olla useita laitteita mukana.
|
||||
|
||||
|
||||
@@ -75,7 +75,7 @@ On **Settings → LoRa**.
|
||||
Alue | Taajuusalueen sääntelyalue. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Ei asetettu (on määritettävä) |
|
||||
Esiasetukset | Nopeuden ja kantaman välinen kompromissi | LongFast |
|
||||
Hyppyjen määrä | Suurin hyppyjen määrä | 3 |
|
||||
Lähetysteho | Lähetysteho (dBm): 0 = alueen sallima enimmäisteho | 0 (alueen enimmäisteho) |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (alueen enimmäisteho) |
|
||||
Taajuuden ohitus | Ohittaa lasketun käyttötaajuuden (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (käytä laskettua arvoa) |
|
||||
Käytä esiasetusta | Oletusarvoisesti käytössä. Poista tämä käytöstä, jos haluat määrittää hajotuskerroin-, koodausnopeus- ja kaistanleveysasetukset käsin modeemiesiasetuksen sijaan | Käytössä |
|
||||
Levennyskerroin (Spread Factor) | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | Esiasetuksesta |
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Description |
|
||||
------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
J'accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Intervalle de rapport cartographique (secondes) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Description |
|
||||
-------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
J'accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Description |
|
||||
-------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Notifications externes activées | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
LED extérieure (GPIO) | Pin the LED is wired to |
|
||||
Sortie LED active à l’état haut | Whether the LED pin is active high or low |
|
||||
Buzzer extérieur (GPIO) | Pin the buzzer is wired to |
|
||||
Sortie vibreur (GPIO) | Pin the vibration motor is wired to |
|
||||
Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Utiliser l'I2S comme buzzer | Send the alert through an I2S audio output instead |
|
||||
Durée de sortie (en millisecondes) | How long a single alert lasts |
|
||||
Durée de répétition de la sortie (secondes) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Description |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------- |
|
||||
Notifications externes activées | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
LED extérieure (GPIO) | Pin the LED is wired to |
|
||||
Sortie LED active à l’état haut | Whether the LED pin is active high or low |
|
||||
Buzzer extérieur (GPIO) | Pin the buzzer is wired to |
|
||||
Sortie vibreur (GPIO) | Pin the vibration motor is wired to |
|
||||
Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Utiliser l'I2S comme buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Délai d'expiration du message | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Description |
|
||||
-------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Test de portée activé | Activate range testing |
|
||||
Intervalle de message de l'expéditeur (secondes) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Description |
|
||||
------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Infos de voisinage activées | Activate neighbor broadcasting |
|
||||
Intervalle de mise à jour (secondes) | How often to broadcast neighbor list |
|
||||
Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Description |
|
||||
----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Infos de voisinage activées | Activate neighbor broadcasting |
|
||||
Fréquence de récupération GPS | How often to broadcast neighbor list |
|
||||
Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -223,8 +223,8 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec
|
||||
Broche GPIO à surveiller | GPIO pin connected to sensor |
|
||||
Type du déclencheur de détection | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Utiliser le mode INPUT_PULLUP | Enable the pin's internal pull-up resistor |
|
||||
Diffusion minimale (secondes) | Minimum time between alert broadcasts |
|
||||
Diffusion de l'État (secondes) | Periodic state broadcast interval |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Envoyer une sonnerie avec un message d'alerte | Include bell character in alerts |
|
||||
Nom convivial | Custom name for this sensor |
|
||||
|
||||
@@ -232,12 +232,12 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Paramètre | Description |
|
||||
------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter activé | Activate people counting |
|
||||
Intervalle de mise à jour (secondes) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Paramètre | Description |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter activé | Activate people counting |
|
||||
Fréquence de récupération GPS | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -76,7 +76,7 @@ On **Settings → LoRa**.
|
||||
Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Préréglages | Speed/range tradeoff | LongFast |
|
||||
Nombre de sauts | Maximum retransmit hops | 3 |
|
||||
Puissance d'émission | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Description |
|
||||
------------------------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
J'accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Intervalle de rapport cartographique (secondes) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Description |
|
||||
-------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
J'accepte. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Description |
|
||||
-------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Notifications externes activées | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
LED extérieure (GPIO) | Pin the LED is wired to |
|
||||
Sortie LED active à l’état haut | Whether the LED pin is active high or low |
|
||||
Buzzer extérieur (GPIO) | Pin the buzzer is wired to |
|
||||
Sortie vibreur (GPIO) | Pin the vibration motor is wired to |
|
||||
Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Utiliser l'I2S comme buzzer | Send the alert through an I2S audio output instead |
|
||||
Durée de sortie (en millisecondes) | How long a single alert lasts |
|
||||
Durée de répétition de la sortie (secondes) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Description |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------- |
|
||||
Notifications externes activées | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
LED extérieure (GPIO) | Pin the LED is wired to |
|
||||
Sortie LED active à l’état haut | Whether the LED pin is active high or low |
|
||||
Buzzer extérieur (GPIO) | Pin the buzzer is wired to |
|
||||
Sortie vibreur (GPIO) | Pin the vibration motor is wired to |
|
||||
Utiliser le buzzer PWM | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Utiliser l'I2S comme buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Délai d'expiration du message | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Sonnerie | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Description |
|
||||
-------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Test de portée activé | Activate range testing |
|
||||
Intervalle de message de l'expéditeur (secondes) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Enregistrer .CSV dans le stockage (ESP32 seulement) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Description |
|
||||
------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Infos de voisinage activées | Activate neighbor broadcasting |
|
||||
Intervalle de mise à jour (secondes) | How often to broadcast neighbor list |
|
||||
Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Description |
|
||||
----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Infos de voisinage activées | Activate neighbor broadcasting |
|
||||
Fréquence de récupération GPS | How often to broadcast neighbor list |
|
||||
Transmettre par LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -223,8 +223,8 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec
|
||||
Broche GPIO à surveiller | GPIO pin connected to sensor |
|
||||
Type du déclencheur de détection | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Utiliser le mode INPUT_PULLUP | Enable the pin's internal pull-up resistor |
|
||||
Diffusion minimale (secondes) | Minimum time between alert broadcasts |
|
||||
Diffusion de l'État (secondes) | Periodic state broadcast interval |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Envoyer une sonnerie avec un message d'alerte | Include bell character in alerts |
|
||||
Nom convivial | Custom name for this sensor |
|
||||
|
||||
@@ -232,12 +232,12 @@ Turns your node into a motion or door sensor alert system. When a GPIO pin detec
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Paramètre | Description |
|
||||
------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter activé | Activate people counting |
|
||||
Intervalle de mise à jour (secondes) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Paramètre | Description |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter activé | Activate people counting |
|
||||
Fréquence de récupération GPS | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -76,7 +76,7 @@ On **Settings → LoRa**.
|
||||
Région | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Préréglages | Speed/range tradeoff | LongFast |
|
||||
Nombre de sauts | Maximum retransmit hops | 3 |
|
||||
Puissance d'émission | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Remplacer la fréquence | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Utiliser un préréglage | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Facteur de propagation | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Cur síos |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Cur síos |
|
||||
------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Cur síos |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
Output duration (milliseconds) | How long a single alert lasts |
|
||||
Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Cur síos |
|
||||
--------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Cur síos |
|
||||
-------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Range test enabled | Activate range testing |
|
||||
Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Cur síos |
|
||||
-------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update interval (seconds) | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Cur síos |
|
||||
--------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update Interval | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | Cur síos |
|
||||
---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum broadcast (seconds) | Minimum time between alert broadcasts |
|
||||
State broadcast (seconds) | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
Setting | Cur síos |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | Cur síos |
|
||||
-------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update interval (seconds) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | Cur síos |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update Interval | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Setting | Cur síos | Default |
|
||||
------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Réigiún | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
Setting | Cur síos | Default |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Réigiún | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Descrición |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Descrición |
|
||||
------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Descrición |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
Output duration (milliseconds) | How long a single alert lasts |
|
||||
Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Descrición |
|
||||
--------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Descrición |
|
||||
-------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Range test enabled | Activate range testing |
|
||||
Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Descrición |
|
||||
-------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update interval (seconds) | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Descrición |
|
||||
--------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update Interval | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | Descrición |
|
||||
---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum broadcast (seconds) | Minimum time between alert broadcasts |
|
||||
State broadcast (seconds) | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
Setting | Descrición |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | Descrición |
|
||||
-------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update interval (seconds) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | Descrición |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update Interval | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Setting | Descrición | Default |
|
||||
------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Rexión | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
Setting | Descrición | Default |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Rexión | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Opis |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Opis |
|
||||
------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Opis |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
Output duration (milliseconds) | How long a single alert lasts |
|
||||
Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Opis |
|
||||
--------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Opis |
|
||||
-------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Range test enabled | Activate range testing |
|
||||
Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Opis |
|
||||
-------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update interval (seconds) | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Opis |
|
||||
--------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update Interval | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | Opis |
|
||||
---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum broadcast (seconds) | Minimum time between alert broadcasts |
|
||||
State broadcast (seconds) | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
Setting | Opis |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | Opis |
|
||||
-------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update interval (seconds) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | Opis |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update Interval | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Setting | Opis | Zadano |
|
||||
------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
Setting | Opis | Zadano |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Regija | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Deskripsyon |
|
||||
--------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map reporting interval (seconds) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Deskripsyon |
|
||||
------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
I agree. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Deskripsyon |
|
||||
------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
Output duration (milliseconds) | How long a single alert lasts |
|
||||
Nag timeout (seconds) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Deskripsyon |
|
||||
--------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
External notification enabled | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Output LED (GPIO) | Pin the LED is wired to |
|
||||
Output LED active high | Whether the LED pin is active high or low |
|
||||
Output buzzer (GPIO) | Pin the buzzer is wired to |
|
||||
Output vibra (GPIO) | Pin the vibration motor is wired to |
|
||||
Use PWM buzzer | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
Use I2S as buzzer | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Ringtone | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Deskripsyon |
|
||||
-------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |
|
||||
Range test enabled | Activate range testing |
|
||||
Sender message interval (seconds) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Save .CSV in storage (ESP32 only) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Deskripsyon |
|
||||
-------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update interval (seconds) | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Deskripsyon |
|
||||
--------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Neighbor Info enabled | Activate neighbor broadcasting |
|
||||
Update Interval | How often to broadcast neighbor list |
|
||||
Transmit over LoRa | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | Deskripsyon |
|
||||
---------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum broadcast (seconds) | Minimum time between alert broadcasts |
|
||||
State broadcast (seconds) | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
Setting | Deskripsyon |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Detection Sensor enabled | Activate detection sensor |
|
||||
GPIO pin to monitor | GPIO pin connected to sensor |
|
||||
Detection trigger type | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
Use INPUT_PULLUP mode | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Send bell with alert message | Include bell character in alerts |
|
||||
Friendly name | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | Deskripsyon |
|
||||
-------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update interval (seconds) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | Deskripsyon |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter enabled | Activate people counting |
|
||||
Update Interval | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
@@ -71,24 +71,24 @@ On **Settings → Device configuration → Device**.
|
||||
|
||||
On **Settings → LoRa**.
|
||||
|
||||
Setting | Deskripsyon | Default |
|
||||
------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Rejyon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power | Transmission power (dBm); 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
Setting | Deskripsyon | Default |
|
||||
--------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------- |
|
||||
Rejyon | Regulatory region for frequency bands. You must set this before transmitting. On firmware 2.8 or newer, the first region set also creates the node's identity key and gives it a new node number | Unset (must configure) |
|
||||
Presets | Speed/range tradeoff | LongFast |
|
||||
Number of Hops | Maximum retransmit hops | 3 |
|
||||
Transmit Power (dBm) | Transmission power; 0 = max allowed for region | 0 (region max) |
|
||||
Frequency Override | Overrides the computed operating frequency outright (MHz). It doesn't offset the calculated value — leave at 0 unless you know you need a specific frequency | 0 (use calculated) |
|
||||
Use Preset | On by default. Turn it off to set Spread Factor, Coding Rate and Bandwidth by hand instead of taking them from the modem preset | On |
|
||||
Spread Factor | Manual mode only: 5–12. Higher spreads further but slower. On SX127x (RF95) radios the firmware doesn't accept 5 or 6 and uses 11 instead | From preset |
|
||||
Coding Rate | Manual mode only: 5–8. More redundancy costs airtime | From preset |
|
||||
Bandwidth | Manual mode only: the channel bandwidth in kHz, typed in directly. On the 2.4 GHz region the app offers a list of the bandwidths your node supports instead, and a stored value that isn't on that list shows as _Unsupported_ and blocks saving until you pick a supported one | From preset |
|
||||
Frequency Slot | Which slot within the region's band to use. 0 derives it from the primary channel name | 0 (automatic) |
|
||||
Transmit Enabled | Turning this off makes the node receive-only | On |
|
||||
Override Duty Cycle | Ignores the region's duty-cycle limit. Illegal in most regions; turn it on only where your license permits | Off |
|
||||
Ignore MQTT | Drop packets that arrived from MQTT rather than over the air. The firmware turns this on for you whenever you set a region that has a duty-cycle limit — the EU bands, Thailand, and Ukraine 433 | Off, until you set a duty-cycle-limited region |
|
||||
Ok to MQTT | Allow your packets to be forwarded to MQTT by gateways | Off |
|
||||
RX Boosted Gain | Extra receive gain on SX126x radios; costs a little current | Off |
|
||||
PA fan disabled | Turn off the power-amplifier fan on hardware that has one | Off |
|
||||
|
||||
The preset list is also filtered to what your region legally permits, so a preset allowed in one
|
||||
region doesn't appear in another. Changing region can therefore leave your current preset
|
||||
|
||||
@@ -161,7 +161,7 @@ The Neighbor Info module lets each node broadcast a list of the nodes it can **d
|
||||
|
||||
1. Navigate to **Settings → Module configuration → Neighbor Info**.
|
||||
2. Enable the module.
|
||||
3. Set **Update interval (seconds)**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
3. Set **Update Interval**. The app accepts whatever you type; the firmware enforces its own minimum and resets a value below it.
|
||||
4. Turn on **Transmit over LoRa**. Without it, your neighbor list goes only to MQTT and to this app, never over the air.
|
||||
|
||||
Once enabled and transmitting over LoRa, your node periodically broadcasts its neighbor list. Other nodes with Neighbor Info enabled do the same.
|
||||
|
||||
@@ -90,7 +90,7 @@ Configure your node to point to your private broker with appropriate credentials
|
||||
|
||||
When **Map reporting** is on, your node periodically publishes a map report to the broker. The report goes out unencrypted, whatever keys your channels use, and carries your node id, long and short name, approximate location, hardware model, role, firmware version, LoRa region, modem preset, and primary channel name.
|
||||
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map reporting interval (seconds)** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
Turning it on opens a consent card. Turn on **I agree.** and choose a **Map Publish Interval** of one hour or more — the screen will not save until you do. A slider sets the position precision, and the app shows the resulting accuracy as a ± distance, so you can publish an approximate location rather than an exact one.
|
||||
|
||||
Reports appear at [meshmap.net](https://meshmap.net) and similar community map services.
|
||||
|
||||
|
||||
@@ -51,11 +51,11 @@ Turning **Map reporting** on reveals a consent card headed _Consent to Share Une
|
||||
via MQTT_, with an **I agree.** switch under it. The rest of the card doesn't exist on screen
|
||||
until you agree:
|
||||
|
||||
Setting | Leírás |
|
||||
--------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Elfogadom. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Térképadat-jelentés intervalluma (másodperc) | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
Setting | Leírás |
|
||||
-------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Elfogadom. | Explicit consent to transmit your node data, including an approximate position, unencrypted. Map reporting doesn't start without it |
|
||||
Precision slider | The slider has no label of its own. It sets how coarsely your position is published, from 12 to 15; the line beneath reads _±_ the resulting distance, in your own units |
|
||||
Map Publish Interval | How often to report. A dropdown of fixed intervals from 1 hour to 72 hours — nothing shorter is offered |
|
||||
|
||||
See [MQTT](mqtt) for a detailed usage guide including encryption, privacy, and broker setup.
|
||||
|
||||
@@ -80,20 +80,20 @@ Controls buzzer, LED, or vibration alerts on your node hardware. Useful for devi
|
||||
There are two independent triggers — an incoming **message**, and a received **bell** character —
|
||||
and each can drive the LED, the buzzer and the vibration motor separately, giving six toggles.
|
||||
|
||||
Setting | Leírás |
|
||||
--------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
|
||||
Külső értesítés engedélyezve | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Kimeneti LED (GPIO) | Pin the LED is wired to |
|
||||
Kimeneti LED aktív magas szint | Whether the LED pin is active high or low |
|
||||
Kimeneti csipogó (GPIO) | Pin the buzzer is wired to |
|
||||
Kimeneti rezgő (GPIO) | Pin the vibration motor is wired to |
|
||||
PWM csipogó használata | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
I2S használata csipogóként | Send the alert through an I2S audio output instead |
|
||||
Kimeneti időtartam (ezredmásodperc) | How long a single alert lasts |
|
||||
Ismétlő riasztás időkorlát (másodperc) | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Csengőhang | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
Setting | Leírás |
|
||||
------------------------------------------ | --------------------------------------------------------------------------------------------------- |
|
||||
Külső értesítés engedélyezve | Master toggle for the module |
|
||||
Alert message LED / buzzer / vibra | Which outputs fire on an incoming message |
|
||||
Alert bell LED / buzzer / vibra | Which outputs fire on a received bell character |
|
||||
Kimeneti LED (GPIO) | Pin the LED is wired to |
|
||||
Kimeneti LED aktív magas szint | Whether the LED pin is active high or low |
|
||||
Kimeneti csipogó (GPIO) | Pin the buzzer is wired to |
|
||||
Kimeneti rezgő (GPIO) | Pin the vibration motor is wired to |
|
||||
PWM csipogó használata | Drive the buzzer with PWM, which allows tones rather than a single pitch |
|
||||
I2S használata csipogóként | Send the alert through an I2S audio output instead |
|
||||
GPIO Output Duration | How long a single alert lasts |
|
||||
Nag Timeout | Keep repeating the alert for this long until it is acknowledged. 0 disables nagging |
|
||||
Csengőhang | The tone played on a PWM buzzer, in RTTTL. Can be imported from a file |
|
||||
|
||||
### Store & Forward module
|
||||
|
||||
@@ -122,7 +122,7 @@ Automated range testing tool for evaluating link quality between nodes. When ena
|
||||
Setting | Leírás |
|
||||
------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- |
|
||||
Hatótáv-teszt engedélyezve | Activate range testing |
|
||||
Küldési üzenetintervallum (másodperc) | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
Sender Interval | Time between test transmissions, chosen from a dropdown of fixed intervals |
|
||||
.CSV mentése a tárhelyre (csak ESP32) | Log received test data to the node's own filesystem. ESP32 hardware only |
|
||||
|
||||
### Telemetry module
|
||||
@@ -195,11 +195,11 @@ GPIO control over the mesh network. Allows a remote node to read or write GPIO p
|
||||
|
||||
Broadcasts information about directly heard neighbors, enabling mesh topology mapping. Each enabled node periodically shares a list of the other nodes it can hear and their signal quality.
|
||||
|
||||
Setting | Leírás |
|
||||
----------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Szomszéd-információ engedélyezve | Activate neighbor broadcasting |
|
||||
Frissítési intervallum (másodperc) | How often to broadcast neighbor list |
|
||||
Továbbítás LoRa-n keresztül | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
Setting | Leírás |
|
||||
-------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
|
||||
Szomszéd-információ engedélyezve | Activate neighbor broadcasting |
|
||||
Frissítési időköz | How often to broadcast neighbor list |
|
||||
Továbbítás LoRa-n keresztül | Also broadcast neighbor info over LoRa, not just MQTT/phone. Unavailable on a channel using the default key and name |
|
||||
|
||||
See [Local Mesh Discovery](discovery) for how to use neighbor data for mesh topology exploration.
|
||||
|
||||
@@ -217,27 +217,27 @@ Controls onboard NeoPixel or other addressable RGB LEDs on supported hardware. C
|
||||
|
||||
Turns your node into a motion or door sensor alert system. When a GPIO pin detects a state change (motion detected, door opened), the node broadcasts an alert message over the mesh.
|
||||
|
||||
Setting | Leírás |
|
||||
------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Érzékelő szenzor engedélyezve | Activate detection sensor |
|
||||
Figyelt GPIO láb | GPIO pin connected to sensor |
|
||||
Érzékelési ravasztípus | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
INPUT_PULLUP mód használata | Enable the pin's internal pull-up resistor |
|
||||
Minimális sugárzási idő (másodperc) | Minimum time between alert broadcasts |
|
||||
Állapot-sugárzás (másodperc) | Periodic state broadcast interval |
|
||||
Harangjel küldése riasztási üzenettel | Include bell character in alerts |
|
||||
Barátságos név | Custom name for this sensor |
|
||||
Setting | Leírás |
|
||||
------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
|
||||
Érzékelő szenzor engedélyezve | Activate detection sensor |
|
||||
Figyelt GPIO láb | GPIO pin connected to sensor |
|
||||
Érzékelési ravasztípus | How the pin's state maps to a detection event (e.g. active high/low, edge-triggered) |
|
||||
INPUT_PULLUP mód használata | Enable the pin's internal pull-up resistor |
|
||||
Minimum time between detection broadcasts | Minimum time between alert broadcasts |
|
||||
State Broadcast Interval | Periodic state broadcast interval |
|
||||
Harangjel küldése riasztási üzenettel | Include bell character in alerts |
|
||||
Barátságos név | Custom name for this sensor |
|
||||
|
||||
### Paxcounter module
|
||||
|
||||
People counter using Wi-Fi and BLE probe requests. Counts nearby devices by passively listening for probe requests that phones and laptops emit when scanning for networks. Available only on ESP32 devices.
|
||||
|
||||
Setting | Leírás |
|
||||
----------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter engedélyezve | Activate people counting |
|
||||
Frissítési intervallum (másodperc) | How often to report counts |
|
||||
Wi-Fi RSSI threshold | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE RSSI threshold | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
Setting | Leírás |
|
||||
--------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
|
||||
Paxcounter engedélyezve | Activate people counting |
|
||||
Frissítési időköz | How often to report counts |
|
||||
WiFi Threshold (dBm) | Ignore Wi-Fi probes weaker than this, so distant devices aren't counted (defaults to −80 dBm) |
|
||||
BLE Threshold (dBm) | The same cut-off for BLE advertisements (defaults to −80 dBm) |
|
||||
|
||||
> 💡 **Tip:** Paxcounter is useful for estimating foot traffic at trailheads, event venues, or other locations. Counts are approximate — one person may carry multiple devices.
|
||||
|
||||
|
||||
Loaded 100 of 326 files, more files were not shown because too many files have changed in this diff.
Show more
Reference in new issue
Block a user