mirror of
https://github.com/meshtastic/meshtastic.git
synced 2024-11-09 23:24:10 -08:00
abstract configuration to settings pages
This commit is contained in:
Foster Irwin
parent
874f044790
commit
a0a4e47acc
|
|
@ -13,43 +13,8 @@ The ExternalNotification Module will allow you to connect a speaker, LED or othe
|
|||
|
||||
## Configuration
|
||||
|
||||
<PluginModule name="ext_notification_plugin" rename="ext_notification_module" />
|
||||
|
||||
These are the settings that can be configured.
|
||||
|
||||
ext_notification_module_enabled
|
||||
Is the module enabled?
|
||||
|
||||
0 = Disabled (Default)
|
||||
1 = Enabled
|
||||
|
||||
ext_notification_module_active
|
||||
Is your external circuit triggered when our GPIO is low or high?
|
||||
|
||||
0 = Active Low (Default)
|
||||
1 = Active High
|
||||
|
||||
ext_notification_module_alert_message
|
||||
Do you want to be notified on an incoming message?
|
||||
|
||||
0 = Disabled (Default)
|
||||
1 = Alert when a text message comes
|
||||
|
||||
ext_notification_module_alert_bell
|
||||
Do you want to be notified on an incoming bell?
|
||||
|
||||
0 = Disabled (Default)
|
||||
1 = Alert when the bell character is received
|
||||
|
||||
ext_notification_module_output
|
||||
What GPIO is your external circuit attached?
|
||||
|
||||
GPIO of the output. (Default = 13)
|
||||
|
||||
ext_notification_module_output_ms
|
||||
How long do you want us to trigger your external circuit?
|
||||
|
||||
Amount of time in ms for the alert. Default is 1000.
|
||||
Configuration details are available on the [Device Settings](/docs/settings) pages. Configuring the External Notification Module requires configuring the following modules:
|
||||
- [External Notification Module](/docs/settings/modules/external-notification-module)
|
||||
|
||||
## Usage Notes
|
||||
|
||||
|
|
|
|||
|
|
@ -11,29 +11,8 @@ This module allows you to test the range of your Meshtastic nodes. It uses two n
|
|||
|
||||
## Configuration
|
||||
|
||||
<PluginModule name="range_test_module_" rename="range_test_plugin_" />
|
||||
|
||||
These are the settings that can be configured.
|
||||
|
||||
range_test_module_enabled
|
||||
Is the Module enabled?
|
||||
|
||||
0 = Disabled (Default)
|
||||
1 = Enabled
|
||||
|
||||
range_test_module_save
|
||||
If enabled, we will save a log of all received messages to /static/rangetest.csv which you can access from the webserver. We will abort
|
||||
writing if there is less than 50k of space on the filesystem to prevent filling up the storage.
|
||||
|
||||
0 = Disabled (Default)
|
||||
1 = Enabled
|
||||
|
||||
range_test_module_sender
|
||||
Number of seconds to wait between sending packets. Using the long_slow channel configuration, it's best not to go more frequent than once every 60 seconds. You can be more agressive with faster settings. 0 is default which disables sending messages.
|
||||
|
||||
:::note
|
||||
The device must be restarted after the settings have been changed for the module to take effect.
|
||||
:::
|
||||
Configuration details are available on the [Device Settings](/docs/settings) pages. Configuring the Range Test Module requires configuring the following modules:
|
||||
- [Range Test Module](/docs/settings/modules/range-test-module)
|
||||
|
||||
### Usage Notes
|
||||
|
||||
|
|
|
|||
|
|
@ -17,57 +17,8 @@ The preferred setup is using I2C, so the `telemetry_module_sensor_pin` may not b
|
|||
|
||||
## Configuration
|
||||
|
||||
These are the settings that can be configured.
|
||||
|
||||
telemetry_module_enabled
|
||||
Is the module enabled?
|
||||
|
||||
0 = Disabled (Default)
|
||||
1 = Enabled
|
||||
|
||||
telemetry_module_screen_enabled
|
||||
Show received sensor readings on device screen.
|
||||
|
||||
0 = Disabled (Default)
|
||||
1 = Enabled
|
||||
|
||||
telemetry_module_read_error_count_threshold
|
||||
Error count threshold for failed sensor readings.
|
||||
|
||||
Default = 0
|
||||
|
||||
preferences.telemetry_module_update_interval
|
||||
How often (in seconds) should sensor readings be broadcasted?
|
||||
|
||||
Default = 0
|
||||
|
||||
telemetry_module_recovery_interval
|
||||
For how long should we wait (in seconds) before trying to read sensors again upon exceeded error threshold?
|
||||
|
||||
Default = 0
|
||||
|
||||
telemetry_module_display_fahrenheit
|
||||
Should temperature readings be converted to fahrenheit?
|
||||
|
||||
0 = Disabled (Default)
|
||||
1 = Enabled
|
||||
|
||||
telemetry_module_sensor_type
|
||||
What sensor is connected?
|
||||
|
||||
0 = DHT11 (Default)
|
||||
1 = Dallas 1-wire DS18B20
|
||||
2 = DHT12
|
||||
3 = DHT21
|
||||
4 = DHT22
|
||||
5 = BME280
|
||||
6 = BME680
|
||||
7 = MCP9808
|
||||
|
||||
telemetry_module_sensor_pin
|
||||
Which pin is the sensor connected to?
|
||||
|
||||
Default = 0
|
||||
Configuration details are available on the [Device Settings](/docs/settings) pages. Configuring the Telemetry Module requires configuring the following modules:
|
||||
- [Telemetry Module](/docs/settings/modules/telemetry-module)
|
||||
|
||||
## Usage Notes
|
||||
|
||||
|
|
|
|||
Loading…
Reference in a new issue