* rebased to master
* Update bin/config.d/lora-ZebraHat_2W.yaml
Co-authored-by: Austin <vidplace7@gmail.com>
* Update bin/config.d/lora-ZebraHat_1W.yaml
Co-authored-by: Austin <vidplace7@gmail.com>
* Update bin/config.d/lora-NebraHat_2W.yaml
Co-authored-by: Austin <vidplace7@gmail.com>
* Update bin/config.d/lora-NebraHat_1W.yaml
Co-authored-by: Austin <vidplace7@gmail.com>
* Remove TX_GAIN_LORA configuration line
* Remove TX_GAIN_LORA configuration line
* Comment out TX_GAIN_LORA configuration
* Comment out TX_GAIN_LORA configuration
* Update lora-ok3506-RAK6421-13300-slot1.yaml
* Update lora-ok3506-RAK6421-13300-slot2.yaml
* Update lora-RAK6421-13300-slot1.yaml
* Update lora-RAK6421-13300-slot2.yaml
---------
Co-authored-by: Austin <vidplace7@gmail.com>
(cherry picked from commit a49729eb89)
meshtasticd configuration files
This directory contains YAML configuration files for meshtasticd. Each file describes a specific hardware configuration, including the LoRa module and pin assignments. These configurations are used by meshtasticd to correctly interface with the hardware.
Metadata structure
Each configuration file includes a Meta section that provides information about the configuration.
This configuration is consumed by configuration-selection tools.
Meta:
name: MeshAdv-Pi E22-900M30S # A unique identifier for this configuration.
support: community # community, official, or deprecated; determined by Meshtastic Leads.
compatible: # A list of compatible products or platforms.
- raspberry-pi
name: A unique identifier for the configuration, typically reflecting the hardware it supports.
support: Indicates the level of support for this configuration. It can be one of the following:
community: Supported by the Meshtastic community. Meshtastic Members may not possess, or have not tested this configuration.official: Fully supported by Meshtastic. Meshtastic Members have tested and verified this configuration.deprecated: No longer recommended for deployment by Meshtastic.
compatible: A list of compatible products or platforms that can use this configuration.
This will vary depending on the intended use case / platform.
Multiple compatible entries can be included. E.g. Armbian BOARD value or OpenWrt TARGET value.
These tags can be consumed by different configuration-selection tools, filtering based upon their platform/etc.