mirror of
https://github.com/meshtastic/meshtastic.git
synced 2025-01-13 06:48:10 -08:00
Merge branch 'master' into update-position
This commit is contained in:
rcarteraz
GitHub
commit
dfc5ff6270
|
|
@ -7,6 +7,8 @@ description: "Get involved with Meshtastic's open-source project. Contribute to
|
|||
---
|
||||
|
||||
import Link from "@docusaurus/Link"
|
||||
import ThemedImage from '@theme/ThemedImage';
|
||||
import useBaseUrl from '@docusaurus/useBaseUrl';
|
||||
|
||||
## Volunteer Based Development
|
||||
|
||||
|
|
@ -78,8 +80,49 @@ If direct development contribution is not feasible for you, financial support is
|
|||
|
||||
We're deeply thankful for the backing from the Open Collective, Open Source Collective, DigitalOcean, and Vercel, which has been instrumental in our project's sustainability and growth:
|
||||
|
||||
- **Open Collective & Open Source Collective**: Our collaboration with these organizations offers a robust fiscal management framework and banking solutions, supporting our project alongside over three thousand other open source initiatives. Open Collective's transparent framework lets everyone see our finances, including income, expenditures, and contributions on [Meshtastic's Open Collective page](https://opencollective.com/meshtastic). This transparency and support affirm that we're in excellent company.
|
||||
<div className="flex flex-wrap items-start">
|
||||
<div className="w-full sm:w-3/12 p-3">
|
||||
<ThemedImage
|
||||
alt="Open Collective"
|
||||
className="max-h-8"
|
||||
sources={{
|
||||
light: useBaseUrl("/img/Open_Collective_logo_2021.svg"),
|
||||
dark: useBaseUrl("/img/Open_Collective_logo_2021.svg"),
|
||||
}}
|
||||
/>
|
||||
</div>
|
||||
<div className="w-full sm:w-9/12 p-3">
|
||||
Our collaboration with Open Collective and Open Source Collective offers a robust fiscal management framework and banking solutions, supporting our project alongside over three thousand other open source initiatives. Open Collective's transparent framework lets everyone see our finances, including income, expenditures, and contributions on [Meshtastic's Open Collective page](https://opencollective.com/meshtastic). This transparency and support affirm that we're in excellent company.
|
||||
</div>
|
||||
</div>
|
||||
|
||||
- **DigitalOcean**: Champions of open source, DigitalOcean supports Meshtastic through credits, which significantly aid our development, infrastructure, and testing efforts. This contribution is part of their commitment to fostering innovation and collaboration within the open source ecosystem.
|
||||
|
||||
- **Vercel**: By covering our hosting costs, Vercel directly contributes to Meshtastic's growth, enhancing our web scalability and presence. Their sponsorship is crucial for our continued development and focus on creating a robust platform for decentralized communication.
|
||||
<div className="flex flex-wrap items-start">
|
||||
<div className="w-full sm:w-3/12 p-3">
|
||||
<ThemedImage
|
||||
alt="This project is supported by DigitalOcean"
|
||||
className="max-h-8"
|
||||
sources={{
|
||||
light: useBaseUrl('https://opensource.nyc3.cdn.digitaloceanspaces.com/attribution/assets/PoweredByDO/DO_Powered_by_Badge_blue.svg'),
|
||||
dark: useBaseUrl('https://opensource.nyc3.cdn.digitaloceanspaces.com/attribution/assets/PoweredByDO/DO_Powered_by_Badge_blue.svg'),
|
||||
}}
|
||||
/>
|
||||
</div>
|
||||
<div className="w-full sm:w-9/12 p-3">
|
||||
Champions of open source, DigitalOcean supports Meshtastic through credits, which significantly aid our development, infrastructure, and testing efforts. This contribution is part of their commitment to fostering innovation and collaboration within the open source ecosystem.
|
||||
</div>
|
||||
</div>
|
||||
<div className="flex flex-wrap items-start">
|
||||
<div className="w-full sm:w-3/12 p-3">
|
||||
<ThemedImage
|
||||
alt="Vercel"
|
||||
className="max-h-8"
|
||||
sources={{
|
||||
light: useBaseUrl('/img/vercel-logotype-dark.svg'),
|
||||
dark: useBaseUrl('/img/vercel-logotype-light.svg'),
|
||||
}}
|
||||
/>
|
||||
</div>
|
||||
<div className="w-full sm:w-9/12 p-3">
|
||||
By covering our hosting costs, Vercel directly contributes to Meshtastic's growth, enhancing our web scalability and presence. Their sponsorship is crucial for our continued development and focus on creating a robust platform for decentralized communication.
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -25,6 +25,14 @@ export const Faq = {
|
|||
title: "Can I update my node's firmware over the mesh?",
|
||||
content: `No, Meshtastic does not support OTA updates over LoRa. Please visit [Flash Firmware](/docs/getting-started/flashing-firmware/) for update options.`,
|
||||
},
|
||||
{
|
||||
title: "Which version of firmware should I use?",
|
||||
content: `Currently, there are two types of Meshtastic firmware releases, "Alpha" and "Beta". Firmware releases are labeled with the version number, commit hash and the type. Installing the latest beta release recommended for most cases. Alpha release are geared towards users interested in testing the new features, fixes or enhancements with the understanding there are additional risks and potential for instability compared to running a beta release.`,
|
||||
},
|
||||
{
|
||||
title: "How often should I update firmware?",
|
||||
content: `Firmware should be kept up to date. While it is not necessary to update whenever a new release comes out it's a good idea to follow the Discord Server and Forums linked in the [Introduction](/docs/introduction/#contributors) where developers may advise the community about important updates. The Meshtastic [firmware releases page](https://github.com/meshtastic/firmware/releases) on Github has a summary of what has changed in each release.`,
|
||||
},
|
||||
],
|
||||
"android": [
|
||||
{
|
||||
|
|
|
|||
|
|
@ -7,6 +7,19 @@ sidebar_position: 3
|
|||
description: "Understand Meshtastic's encryption: optional network-wide AES256 security for off-grid communication, ensuring confidentiality against passive eavesdropping."
|
||||
---
|
||||
|
||||
## Explanation
|
||||
|
||||
Meshtastic provides AES256 encryption for the payload of each packet when sending via LoRa, with a different key for each [channel](/docs/configuration/radio/channels/). The [packet header](/docs/overview/mesh-algo/#layer-1-unreliable-zero-hop-messaging) is always sent unencrypted, which allows nodes to relay packets they can't decrypt as well. One can disable this by setting a different [rebroadcast mode](/docs/configuration/radio/device#rebroadcast-mode).
|
||||
|
||||
By default you have one primary channel which is encrypted with a simple known key ("AQ=="), so to use proper encryption you **must change** this key first, or create a new channel and share it with the ones you want to communicate with. However, if you don't have the default key, it means you will not be able to communicate with devices that don't have your key.
|
||||
|
||||
Direct messages to a specific node (e.g. text, traceroute or position requests) may use any channel you share with the recipient. Namely, the device will use the one where it most recently heard a NodeInfo packet from the recipient on. Client apps will not show messages directed to other nodes, but in principle they could be read by **anyone** who knows the used channel key. This means that if it uses the default key, you have to assume anyone could read your direct messages.
|
||||
|
||||
All periodic broadcasts (position, telemetry, etc.) the device sends out itself are sent over the primary channel and thus encrypted with that key.
|
||||
|
||||
The device will decrypt the payload before sending it to a client app via BLE, serial, Wi-Fi/Ethernet. For MQTT you can [specify](/docs/configuration/module/mqtt#encryption-enabled) whether you want to send an encrypted or unencrypted payload.
|
||||
|
||||
## Comments
|
||||
|
||||
Cryptography is tricky, so we've tried to 'simply' apply standard crypto solutions to our implementation. However, the project developers are not cryptography experts.
|
||||
|
||||
|
|
@ -33,7 +46,7 @@ Always keep in mind [xkcd's note on encryption](https://xkcd.com/538).
|
|||
- Consider our existing solution 'alpha' and probably fairly secure against a not particularly aggressive adversary (but we can't yet make a more confident statement).
|
||||
|
||||
|
||||
## Notes for reviewers
|
||||
### Notes for reviewers
|
||||
|
||||
If you are reviewing our implementation, this is a brief statement of our method.
|
||||
|
||||
|
|
@ -46,7 +59,7 @@ If you are reviewing our implementation, this is a brief statement of our method
|
|||
- Each 16 byte BLOCK for a packet has an incrementing COUNTER. COUNTER starts at zero for the first block of each packet.
|
||||
- The IV for each block is constructed by concatenating the NONCE as the upper 96 bits of the IV and the COUNTER as the bottom 32 bits. Since our packets are small counter portion will really never be higher than 32 (five bits).
|
||||
|
||||
## Comments from reviewer #1
|
||||
### Comments from reviewer #1
|
||||
|
||||
This reviewer is a cryptography professional, but would like to remain anonymous. We thank them for their comments ;-):
|
||||
|
||||
|
|
|
|||
|
|
@ -37,7 +37,7 @@ This layer is conventional non-reliable LoRa packet transmission. A packet gener
|
|||
| 0x08 | 4 bytes | Integer | Packet Header: The sending node's unique packet ID for this packet. |
|
||||
| 0x0C | 1 byte | Bits | Packet Header: Flags. See the [header flags](#packet-header-flags) for usage. |
|
||||
| 0x0D | 1 byte | Bits | Packet Header: Channel hash. Used as hint for decryption for the receiver. |
|
||||
| 0x0E | 2 bytes | Bytes | Packet Header: Padding for memory alignment. |
|
||||
| 0x0E | 2 bytes | Bytes | Packet Header: Reserved for future use. |
|
||||
| 0x10 | Max. 237 bytes (excl. protobuf overhead) | Bytes | Actual packet data. Unused bytes are not transmitted. |
|
||||
|
||||
#### Packet Header Flags
|
||||
|
|
@ -47,7 +47,7 @@ This layer is conventional non-reliable LoRa packet transmission. A packet gener
|
|||
| 0 | 3 | HopLimit (see note in Layer 3) |
|
||||
| 3 | 1 | WantAck |
|
||||
| 4 | 1 | ViaMQTT (packet came via MQTT) |
|
||||
| 5 .. 7 | 3 | Currently unused |
|
||||
| 5 | 3 | HopStart (original HopLimit) |
|
||||
|
||||
#### Usage Details
|
||||
|
||||
|
|
|
|||
|
|
@ -31,7 +31,7 @@ The maximum power allowed for Europe is +10 dBm ERP ([Effective Radiated Power](
|
|||
|
||||
The band range is from 433 to 434 MHz.
|
||||
|
||||
There are four channels defined with the standard radio preset `LongFast`. After factory reset the radio will be set to channel 4 with a center frequency of 433.875 MHz.
|
||||
There are four frequendy slots defined with the standard radio preset `LongFast`. After factory reset the radio will be set to frequency slot 4 with a center frequency of 433.875 MHz.
|
||||
|
||||
### 868 MHz
|
||||
|
||||
|
|
@ -39,7 +39,7 @@ The maximum power allowed for Europe is +27 dBm ERP ([Effective Radiated Power](
|
|||
|
||||
The band range is from 869.40 to 869.65 MHz. This is less than the 863–870 MHz range defined as SRD Band, but allows for a higher ERP and a duty cycle of 10%.
|
||||
|
||||
There is one channel defined with the standard radio preset `LongFast`. After factory reset the radio will be set to channel 1 with a center frequency of 869.525 MHz.
|
||||
There is one frequency slot defined with the standard radio preset `LongFast`. After factory reset the radio will be set to frequency slot 1 with a center frequency of 869.525 MHz.
|
||||
|
||||
## North America Frequency Bands
|
||||
|
||||
|
|
@ -49,13 +49,13 @@ The maximum output power for North America is +30 dBm ERP ([Effective Radiated P
|
|||
|
||||
The band range is from 902 to 928 MHz.
|
||||
|
||||
There are 104 channels defined with the standard radio preset `LongFast`. After factory reset the radio will be set to channel 20 with a center frequency of 906.875 MHz.
|
||||
There are 104 frequency slots defined with the standard radio preset `LongFast`. After factory reset the radio will be set to frequency slot 20 with a center frequency of 906.875 MHz.
|
||||
|
||||
## Data Rates
|
||||
|
||||
### Considerations
|
||||
|
||||
Various data-rate options are available when configuring a channel and are inversely proportional to the theoretical range of the devices.
|
||||
Various data-rate options are available when configuring a frequency slot and are inversely proportional to the theoretical range of the devices.
|
||||
|
||||
- **Spreading Factor (SF)** - How much we "spread" our data over time.
|
||||
- Each step up in Spreading Factor doubles the airtime to transmit.
|
||||
|
|
@ -112,7 +112,7 @@ Some example settings:
|
|||
|
||||
The link budget used by these calculations assumes a transmit power of 17dBm and an antenna with 0dB gain. Adjust your link budget assumptions based on your actual devices.
|
||||
|
||||
These channel settings may not have been tested. Use at your own discretion. Share on https://meshtastic.discourse.group with your successes or failure.
|
||||
These frequency slot settings may not have been tested. Use at your own discretion. Share on https://meshtastic.discourse.group with your successes or failure.
|
||||
|
||||
## Cryptography
|
||||
|
||||
|
|
|
|||
|
|
@ -1,24 +1,24 @@
|
|||
| Region Code | Description |
|
||||
|:-----------:|:-----------------------:|
|
||||
| `UNSET` | Unset |
|
||||
| `US` | United States |
|
||||
| `EU_433` | European Union 433MHz |
|
||||
| `EU_868` | European Union 868MHz |
|
||||
| `CN` | China |
|
||||
| `JP` | Japan |
|
||||
| `ANZ` | Australia & New Zealand |
|
||||
| `KR` | Korea |
|
||||
| `TW` | Taiwan |
|
||||
| `RU` | Russia |
|
||||
| `IN` | India |
|
||||
| `NZ_865` | New Zealand 865MHz |
|
||||
| `TH` | Thailand |
|
||||
| `UA_433` | Ukraine 433MHz |
|
||||
| `UA_868` | Ukraine 868MHz |
|
||||
| `MY_433` | Malaysia 433MHz |
|
||||
| `MY_919` | Malaysia 919MHz |
|
||||
| `SG_923` | Singapore 923MHz |
|
||||
| `LORA_24` | 2.4 GHz band worldwide |
|
||||
| Region Code | Description | Frequency Range (MHz) | Duty Cycle (%) | Power Limit (dBm) |
|
||||
|:-----------:|:-----------------------:|:---------------------:|:--------------:|:-----------------:|
|
||||
| `UNSET` | Unset | N/A | N/A | N/A |
|
||||
| `US` | United States | 902.0 - 928.0 | 100 | 30 |
|
||||
| `EU_433` | European Union 433MHz | 433.0 - 434.0 | 10 | 12 |
|
||||
| `EU_868` | European Union 868MHz | 869.4 - 869.65 | 10 | 27 |
|
||||
| `CN` | China | 470.0 - 510.0 | 100 | 19 |
|
||||
| `JP` | Japan | 920.8 - 927.8 | 100 | 16 |
|
||||
| `ANZ` | Australia & New Zealand | 915.0 - 928.0 | 100 | 30 |
|
||||
| `KR` | Korea | 920.0 - 923.0 | 100 | |
|
||||
| `TW` | Taiwan | 920.0 - 925.0 | 100 | 27 |
|
||||
| `RU` | Russia | 868.7 - 869.2 | 100 | 20 |
|
||||
| `IN` | India | 865.0 - 867.0 | 100 | 30 |
|
||||
| `NZ_865` | New Zealand 865MHz | 864.0 - 868.0 | 100 | 36 |
|
||||
| `TH` | Thailand | 920.0 - 925.0 | 100 | 16 |
|
||||
| `UA_433` | Ukraine 433MHz | 433.0 - 434.7 | 10 | 10 |
|
||||
| `UA_868` | Ukraine 868MHz | 868.0 - 868.6 | 1 | 14 |
|
||||
| `MY_433` | Malaysia 433MHz | 433.0 - 435.0 | 100 | 20 |
|
||||
| `MY_919` | Malaysia 919MHz | 919.0 - 924.0 | 100 | 27 |
|
||||
| `SG_923` | Singapore 923MHz | 917.0 - 925.0 | 100 | 20 |
|
||||
| `LORA_24` | 2.4 GHz band worldwide | 2400.0 - 2483.5 | 100 | 10 |
|
||||
|
||||
:::info
|
||||
EU_433 and EU_868 have to adhere to an hourly duty cycle limitation of 10%. Your device will stop transmitting if you reach it, until it is allowed again.
|
||||
|
|
|
|||
|
|
@ -12,7 +12,12 @@ import Tropho from "/img/enclosures/3dp-tropho-heltec32.webp";
|
|||
|
||||
### Heltec LoRa32 v2.1+ Case
|
||||
|
||||
Download from [Printables](https://www.printables.com/model/118750-heltec-lora-32-case-for-meshtastic) or purchase from the creator's [Etsy Store](https://www.etsy.com/listing/1170868625/meshtastic-heltec-lora-32-case).
|
||||
Download from [Printables](https://www.printables.com/model/118750-heltec-lora-32-case-for-meshtastic) or purchase an already printed case below.
|
||||
|
||||
- US
|
||||
- [QuantumShadow3D](https://www.etsy.com/listing/1170868625/meshtastic-heltec-lora-32-case).
|
||||
- UK/EU
|
||||
- [3DChicken](https://3dchicken.co.uk/)
|
||||
|
||||
#### Required Hardware
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,10 @@ sidebar_position: 1
|
|||
|
||||
### Solar Base Station
|
||||
|
||||
Download from [Printables](https://www.printables.com/model/297089-meshtastic-solar-base-station-node-enclosure-for-3) or purchase from the creator's [Etsy Store](https://www.etsy.com/listing/1312727008/meshtastic-solar-base-station-off-grid).
|
||||
Download from [Printables](https://www.printables.com/model/297089-meshtastic-solar-base-station-node-enclosure-for-3) or purchase an already printed case below.
|
||||
|
||||
- International
|
||||
- [VoltaicEnclosures](https://www.etsy.com/listing/1312727008/meshtastic-solar-base-station-off-grid)
|
||||
|
||||
|
||||
|
||||
|
|
@ -18,25 +21,45 @@ Download from [Printables](https://www.printables.com/model/297089-meshtastic-so
|
|||
|
||||
### RAK5005 Case
|
||||
|
||||
Download from [Printables](https://www.printables.com/model/286651-rak5005-case-for-meshtastic) or purchase from the creator's [Etsy Store](https://www.etsy.com/listing/1158237722/meshtastic-rak5005-case).
|
||||
Download from [Printables](https://www.printables.com/model/286651-rak5005-case-for-meshtastic) or purchase an already printed case below.
|
||||
|
||||
- US
|
||||
- [QuantumShadow3D](https://www.etsy.com/listing/1158237722/meshtastic-rak5005-case).
|
||||
- UK/EU
|
||||
- [3DChicken](https://3dchicken.co.uk/)
|
||||
|
||||
|
||||
|
||||
### RAK19007 Case
|
||||
|
||||
Download from [Printables](https://www.printables.com/model/286657-rak19007-case-for-meshtastic) or purchase from the creator's [Etsy Store](https://www.etsy.com/listing/1302265084/meshtastic-rak19007-case).
|
||||
Download from [Printables](https://www.printables.com/model/286657-rak19007-case-for-meshtastic) or purchase an already printed case below.
|
||||
|
||||
- US
|
||||
- [QuantumShadow3D](https://www.etsy.com/listing/1302265084/meshtastic-rak19007-case).
|
||||
- UK/EU
|
||||
- [3DChicken](https://3dchicken.co.uk/)
|
||||
|
||||
|
||||
|
||||
### RAK19003 Case
|
||||
|
||||
Download from [Printables](https://www.printables.com/model/286662-rak19003-case-for-meshtastic) or purchase from the creator's [Etsy Store](https://www.etsy.com/listing/1316287559/meshtastic-rak19003-case).
|
||||
Download from [Printables](https://www.printables.com/model/286662-rak19003-case-for-meshtastic) or purchase an already printed case below.
|
||||
|
||||
- US
|
||||
- [QuantumShadow3D](https://www.etsy.com/listing/1316287559/meshtastic-rak19003-case).
|
||||
- UK/EU
|
||||
- [3DChicken](https://3dchicken.co.uk/)
|
||||
|
||||
|
||||
|
||||
### RAK19003 (Micro) Case
|
||||
|
||||
Download from [Printables](https://www.printables.com/model/286664-rak19003-micro-case-for-meshtastic) or purchase from the creator's [Etsy Store](https://www.etsy.com/listing/1302260756/meshtastic-rak19003-micro-case).
|
||||
Download from [Printables](https://www.printables.com/model/286664-rak19003-micro-case-for-meshtastic) or purchase an already printed case below.
|
||||
|
||||
- US
|
||||
- [Etsy Store](https://www.etsy.com/listing/1302260756/meshtastic-rak19003-micro-case).
|
||||
- UK/EU
|
||||
- [3DChicken](https://3dchicken.co.uk/)
|
||||
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -10,7 +10,13 @@ sidebar_position: 2
|
|||
|
||||
### T-Beam V5 Case
|
||||
|
||||
Download from [Printables](https://www.printables.com/model/127253-t-beam-case-for-meshtastic-v5) or purchase from the creator's [Etsy Store](https://www.etsy.com/listing/1173559418/meshtastic-t-beam-case-for-neo-m8n).
|
||||
Download from [Printables](https://www.printables.com/model/127253-t-beam-case-for-meshtastic-v5) or purchase an already printed case below.
|
||||
|
||||
Purchase Links:
|
||||
- US
|
||||
- [QuantumShadow3D](https://www.etsy.com/listing/1173559418/meshtastic-t-beam-case-for-neo-m8n)
|
||||
- UK/EU
|
||||
- [3DChicken](https://3dchicken.co.uk/)
|
||||
|
||||
#### Required Hardware
|
||||
|
||||
|
|
|
|||
|
|
@ -16,10 +16,40 @@ them for assistance in getting started or if you're interested in contributing t
|
|||
organizer with an online presence and wish to be included in this list, please edit this page directly or reach out to
|
||||
us on [Discord](https://discord.com/invite/ktMAKGBnBs) to add your group.
|
||||
|
||||
## Australia
|
||||
### Tasmania
|
||||
- [Meshtastic User Group Tasmania](https://www.facebook.com/groups/1556630645195649)
|
||||
|
||||
## Canada
|
||||
### Alberta
|
||||
- [YYC Mesh](https://yycmesh.com/)
|
||||
- [Mesht Calgary](https://t.me/meshtcalgary)
|
||||
- [Mesht Alberta](https://t.me/meshtAlta)
|
||||
|
||||
### British Columbia
|
||||
- [Meshtastic BC users group](https://t.me/Mesh_BC)
|
||||
- [Meshtastic Dawson Creek BC users group](https://t.me/Mesh_BC_Dawson_Creek)
|
||||
|
||||
### Manitoba
|
||||
- [Mesht Manitoba](https://t.me/MeshtManitoba)
|
||||
|
||||
### New Brunswick
|
||||
- [Mesht New Brunswick](https://t.me/MeshtNB)
|
||||
### Newfoundland
|
||||
- [Mesht Newfoundland](https://t.me/MeshtNewfoundland)
|
||||
|
||||
### Northwest Territories
|
||||
- [Mesht Northwest Territories](https://t.me/MeshtNWT)
|
||||
|
||||
### Nova Scotia
|
||||
- [Mesht Nova Scotia](https://t.me/MeshtNovaScotia)
|
||||
|
||||
### Prince Edward Island
|
||||
- [Mesht PEI](https://t.me/MeshtPEI)
|
||||
|
||||
### Saskatchewan
|
||||
- [Mesht Saskatchewan](https://t.me/MeshtSaska)
|
||||
##
|
||||
## United States
|
||||
|
||||
### Arkansas
|
||||
|
|
@ -29,10 +59,12 @@ us on [Discord](https://discord.com/invite/ktMAKGBnBs) to add your group.
|
|||
- [SoCal Mesh](https://socalmesh.org)
|
||||
- [Laguna Mesh](https://lagunamesh.com)
|
||||
- [Mission Viejo Mesh](https://missionviejomesh.org/)
|
||||
- [Bay Area Mesh](https://canvis.app/z2k8a8)
|
||||
- [Meshtastic Bay Area Group](https://discord.gg/u2gxYu7RYQ)
|
||||
- [San Diego Mesh](https://discord.gg/k8RputgWgD)
|
||||
- [Antelope Valley Mesh](https://www.avmesh.org/)
|
||||
- [AltaMesh](https://altamesh.net/)
|
||||
- [Central Valley](https://centralvalleymesh.net/)
|
||||
- [Sac Valley Mesh](http://www.sacvalleymesh.com)
|
||||
|
||||
### Colorado
|
||||
- [Denver Mesh](https://denvermesh.org)
|
||||
|
|
@ -49,9 +81,24 @@ us on [Discord](https://discord.com/invite/ktMAKGBnBs) to add your group.
|
|||
### Michigan
|
||||
- [Michigan Meshtastic Network](https://discord.gg/3A5RREcBcc)
|
||||
|
||||
### Oklahoma
|
||||
- [Oklahoma Meshtastic Group](https://www.facebook.com/groups/942404880478488)
|
||||
|
||||
### Tennessee
|
||||
- [Nashville Meshville](https://meshville.org/)
|
||||
|
||||
### Texas
|
||||
- [Austin Mesh](https://austinmesh.org/)
|
||||
|
||||
## Germany
|
||||
- [Meshtastic Users D-A-CH](https://t.me/meshtasticgermany) for technical chat
|
||||
|
||||
## Italy
|
||||
- [Meshtastic Italia](https://t.me/meshtastic_italia)
|
||||
|
||||
## Lithuania
|
||||
- [Meshtastic Lietuva](https://www.facebook.com/groups/1122509422249414)
|
||||
|
||||
## Poland
|
||||
- [Meshtastic Poland Matrix Space](https://matrix.to/#/#meshtasticpl:matrix.org)
|
||||
|
||||
|
|
|
|||
|
|
@ -11,5 +11,7 @@ Current community projects:
|
|||
|
||||
- [Meshtasticator (Simulator)](/docs/community/software/community-meshtasticator) - Meshtasticator is a discrete-event and interactive simulator that mimics the radio section of the device software.
|
||||
- [Meshtastic Web API](/docs/community/software/meshtastic-web-api) - Meshtastic Web API provides a RESTful interface to interact with a Meshtastic node via a serial connection.
|
||||
- [Mesh-metrics](/docs/community/software/community-mesh-metrics) - Meshtastic repeater metrics scraper using meshtastic-cli to be ingested by node_exporter for use in Prometheus or Victoria Metrics Time series DB with a Grafana dashboard and sample alerting rules.
|
||||
|
||||
Support for these projects should be sought from their respective authors.
|
||||
|
||||
|
|
|
|||
16
docs/community/software/mesh-metrics.mdx
Normal file
16
docs/community/software/mesh-metrics.mdx
Normal file
|
|
@ -0,0 +1,16 @@
|
|||
---
|
||||
id: community-mesh-metrics
|
||||
title: Mesh-metrics
|
||||
sidebar_label: Mesh-metrics
|
||||
sidebar_position: 3
|
||||
---
|
||||
|
||||
:::note
|
||||
|
||||
This is a community project maintained by @cordelster.
|
||||
Development can be followed on [GitHub](https://github.com/cordelster/mesh-metrics).
|
||||
Support should be sought from the respective authors.
|
||||
|
||||
:::
|
||||
|
||||
Mesh-metrics is a script that uses the meshtastic-cli and a device connected by usb to send metrics-requests from a list of devices and output the results in a format to be ingested by node_exporter to populate a Prometheus/Victoria Metrics Time series DB. Along with the script, a Grafana dashboard and some alert examples are included. Mesh-metrics was created and is maintained by cordel and more information on its use and setup can be found on the [Mesh-metrics Github page](https://github.com/cordelster/mesh-metrics)
|
||||
|
|
@ -37,6 +37,8 @@ MQTT password to use (most useful for a custom MQTT server). If using a custom s
|
|||
|
||||
Whether to send encrypted or unencrypted packets to MQTT. This parameter is only honored if you also set server (the default official mqtt.meshtastic.org server can handle encrypted packets). Unencrypted packets may be useful for external systems that want to consume meshtastic packets.
|
||||
|
||||
Note: All messages are sent to the MQTT broker unencrypted if this option is not enabled, even when your uplink channels have encryption keys set.
|
||||
|
||||
### JSON Enabled
|
||||
|
||||
:::note
|
||||
|
|
|
|||
|
|
@ -8,11 +8,15 @@ description: This module allows you to send information about your immediate(0 h
|
|||
import Tabs from "@theme/Tabs";
|
||||
import TabItem from "@theme/TabItem";
|
||||
|
||||
The Neighbor Info Module is for sending information on each node's 0-hop neighbors to the mesh. Config options are: Enabled and Update Interval.
|
||||
The Neighbor Info Module is for sending information on each node's 0-hop neighbors to the mesh. Config options are: Enabled and Update Interval.
|
||||
|
||||
:::info
|
||||
Neighbor Info is informative only and does not affect the routing behavior of the mesh network. It is therefore optional and disabled by default.
|
||||
:::
|
||||
|
||||
In order to save bandwidth, Meshtastic does not keep track of the route a packet is taking to get to the destination, except when using Traceroute. When enabling this module, your node will periodically send out a packet with a list of its direct neighbors and the quality (SNR) of the corresponding link. If you enable this on all nodes, you can build up a graph of the full network to see how it is connected. At the time of writing, there are no clients visualizing it for you, but you can use e.g. MQTT to gather all the data.
|
||||
|
||||
In order to use it, make sure your devices use firmware version 2.2.0 or higher.
|
||||
In order to use it, make sure your devices use firmware version 2.2.0 or higher. From 2.3.2 on, the module can detect neighbors even if other nodes do not have the module enabled.
|
||||
|
||||
## Neighbor Info Module Config Values
|
||||
|
||||
|
|
|
|||
|
|
@ -15,7 +15,7 @@ This module allows you to test the range of your Meshtastic nodes. It requires t
|
|||
|
||||
Nodes are in range as long as the sequential packets can be received.
|
||||
|
||||
The receiving node can be used to save the messages along with the GPS coordinates at which they were received into a .csv file. This .csv file can then be integrated into [Google Earth](https://earth.google.com), [Google Maps - My Maps](https://mymaps.google.com), or any other program capable of processing .csv files. This can enable you to visualize your mesh.
|
||||
The receiving node can be used to save the messages along with the GPS coordinates at which they were received into a .csv file. This .csv file can then be integrated into [Google Earth](https://earth.google.com), [Google Maps - My Maps](https://mymaps.google.com), or any other program capable of processing .csv files. This can enable you to visualize your mesh. Ensure you have [position precision](https://meshtastic.org/docs/configuration/radio/channels/#position-precision) in the default channel set to high, otherwise the collected data will not record your true location.
|
||||
|
||||
:::info
|
||||
|
||||
|
|
@ -29,7 +29,7 @@ The range test module config options are: Enabled, Sender, and Save. Range Test
|
|||
|
||||
### Enabled
|
||||
|
||||
Enables the range test module. **Both Sender and Receiver must have the module enabled.**
|
||||
Enables the range test module. **Both Sender and Receiver must have the module enabled.** On the Apple and Android apps to receive any range test messages the module must be enabled. The device screen may continue to show range test packets from older firmware versions even if the module is disabled.
|
||||
|
||||
### Sender Interval
|
||||
|
||||
|
|
|
|||
|
|
@ -96,21 +96,29 @@ The result of reading a GPIO or notifications of GPIO changes will also be sent
|
|||
|
||||
You can get the latest python tool/library with `pip3 install --upgrade meshtastic` on Windows/Linux/OS-X. See the [python section](/docs/software/python/cli/installation) for more details.
|
||||
|
||||
To prevent access from untrusted users, you must first make a `gpio` channel that is used for authenticated access to this feature. You'll need to install this channel on both the local and remote node.
|
||||
To prevent access from untrusted users, you must first make a `gpio` channel that is used for authenticated access to this feature. You'll need to install this channel on both the local and remote node. Furthermore, you need to enable the module on both units.
|
||||
|
||||
The procedure using the python command line tool is:
|
||||
|
||||
1. Connect local device via USB
|
||||
2. Create a GPIO channel:
|
||||
2. Enable the Remote Hardware module:
|
||||
```shell
|
||||
meshtastic --set remote_hardware.enabled true
|
||||
```
|
||||
3. Create a GPIO channel:
|
||||
```shell
|
||||
meshtastic --ch-add gpio
|
||||
```
|
||||
3. Check the channel has been created and copy the long "Complete URL" that contains all the channels on that device:
|
||||
4. Check the channel has been created and copy the long "Complete URL" that contains all the channels on that device:
|
||||
```shell
|
||||
meshtastic --info
|
||||
```
|
||||
4. Connect the remote device via USB (or use the [remote admin](/docs/configuration/remote-admin) feature to reach it through the mesh)
|
||||
5. Set it to join the gpio channel you created:
|
||||
5. Connect the remote device via USB (or use the [remote admin](/docs/configuration/remote-admin) feature to reach it through the mesh)
|
||||
6. Enable the Remote Hardware module:
|
||||
```shell
|
||||
meshtastic --set remote_hardware.enabled true
|
||||
```
|
||||
7. Set it to join the gpio channel you created:
|
||||
```shell
|
||||
meshtastic --seturl theurlyoucopiedinstep3
|
||||
```
|
||||
|
|
|
|||
|
|
@ -189,7 +189,7 @@ meshtastic --set store_forward.records 100
|
|||
#### Web
|
||||
|
||||
:::info
|
||||
Store and Forward configuration is not currently available via the web client.
|
||||
All Store & Forward module config options are available in the Web UI at Config > Module Config > S&F.
|
||||
:::
|
||||
|
||||
</TabItem>
|
||||
|
|
|
|||
|
|
@ -163,6 +163,9 @@ Tap the Channel Name (or the pen icon) to access the Channel Menu:
|
|||
1. Add, remove, or modify secondary channels
|
||||
2. Create or modify encryption keys
|
||||
3. Enable uplink and downlink for individual channels
|
||||
4. Set the position precision value
|
||||
|
||||
|
||||
|
||||
</TabItem>
|
||||
|
||||
|
|
|
|||
|
|
@ -21,7 +21,7 @@ The device config options are: Role, Serial Output, and Debug Log. Device config
|
|||
| TRACKER | Broadcasts GPS position packets as priority. | Tracking the location of individuals or assets, especially in scenarios where timely and efficient location updates are critical. |
|
||||
| LOST_AND_FOUND | Broadcasts location as message to default channel regularly for to assist with device recovery. | Used for recovery efforts of a lost device. |
|
||||
| SENSOR | Broadcasts telemetry packets as priority. | Deploying in scenarios where gathering environmental or other sensor data is crucial, with efficient power usage and frequent updates. |
|
||||
| TAK | Optimized for ATAK system communication, reduces routine broadcasts. | Integration with ATAK systems (via the Mesthastic ATAK Plugin) for communication in tactical or coordinated operations. |
|
||||
| TAK | Optimized for ATAK system communication, reduces routine broadcasts. | Integration with ATAK systems (via the Meshtastic ATAK Plugin) for communication in tactical or coordinated operations. |
|
||||
| TAK_TRACKER | Enables automatic TAK PLI broadcasts and reduces routine broadcasts. | Standalone PLI integration with ATAK systems for communication in tactical or coordinated operations. |
|
||||
| REPEATER | Infrastructure node for extending network coverage by relaying messages with minimal overhead. Not visible in Nodes list. | Best positioned in strategic locations to maximize the network's overall coverage. Device is not shown in topology. |
|
||||
| ROUTER | Infrastructure node for extending network coverage by relaying messages. Visible in Nodes list. | Best positioned in strategic locations to maximize the network's overall coverage. Device is shown in topology. |
|
||||
|
|
|
|||
|
|
@ -70,7 +70,7 @@ The heading can be hard to read when 'INVERTED' or 'TWOCOLOR' display mode is us
|
|||
|
||||
### Wake on Tap or Motion
|
||||
|
||||
This option enables the ability to wake the device screen when motion, such as a tap on the device, is detected via an attached accelerometer.
|
||||
This option enables the ability to wake the device screen when motion, such as a tap on the device, is detected via an attached accelerometer, or a capacitive touch button.
|
||||
|
||||
## Display Config Client Availability
|
||||
|
||||
|
|
|
|||
|
|
@ -30,6 +30,9 @@ When activated, this feature disables Bluetooth, Serial, WiFi, and the device's
|
|||
|
||||
Automatically shut down a device after a defined time period if power is lost.
|
||||
|
||||
Before setting this, ensure your board correctly detects when it is connected to external power (the "🔌" icon in the app). Otherwise, your device could shut down even when power is present.
|
||||
Many devices detect power status correctly, however for some devices, you will need to modify the ADC Multiplier (below).
|
||||
|
||||
### ADC Multiplier Override
|
||||
|
||||
Ratio of voltage divider for battery pin e.g. 3.20 (R1=100k, R2=220k)
|
||||
|
|
|
|||
182
docs/configuration/region-by-country.mdx
Normal file
182
docs/configuration/region-by-country.mdx
Normal file
|
|
@ -0,0 +1,182 @@
|
|||
---
|
||||
id: region-by-country
|
||||
title: LoRa Region by Country
|
||||
description: List countries associated to their respective LoRa Region settings.
|
||||
sidebar_label: LoRa Region by Country
|
||||
sidebar_position: 5
|
||||
---
|
||||
|
||||
This table provides a summary of LoRa regions used for each country.
|
||||
|
||||
If you'd like to contribute information for your country, click the "Edit this page" link at the bottom.
|
||||
|
||||
### A
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Albania | EU_868<br />EU_433 | |
|
||||
| Australia | ANZ | |
|
||||
| Austria | EU_868<br />EU_433 | |
|
||||
|
||||
### B
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Belgium | EU_868<br />EU_433 | |
|
||||
| Bosnia-Herzegowina | EU_868<br />EU_433 | |
|
||||
| Brazil | ANZ | https://www.gov.br/anatel/pt-br/regulado/radiofrequencia/radiacao-restrita |
|
||||
| Bulgaria | EU_868<br />EU_433 | |
|
||||
|
||||
|
||||
### C
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Canada | US | |
|
||||
| China | CN | |
|
||||
| Cyprus | EU_868<br />EU_433 | |
|
||||
| Czech Republic | EU_868<br />EU_433 | |
|
||||
|
||||
### D
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Denmark | EU_868<br />EU_433 | |
|
||||
|
||||
### E
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Estonia | EU_868<br />EU_433 | |
|
||||
|
||||
### F
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| France | EU_868<br />EU_433 | |
|
||||
| Finland | EU_868<br />EU_433 | |
|
||||
|
||||
### G
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Germany | EU_868<br />EU_433 | |
|
||||
| Greece | EU_868<br />EU_433 | |
|
||||
|
||||
### H
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Hungary | EU_868<br />EU_433 | |
|
||||
|
||||
### I
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| India | IN | |
|
||||
| Ireland | EU_868<br />EU_433 | |
|
||||
| Italy | EU_868<br />EU_433 | |
|
||||
|
||||
### J
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Japan | JP | |
|
||||
|
||||
### K
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Korea | KR | |
|
||||
| Kroatia | EU_868<br />EU_433 | |
|
||||
|
||||
### L
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Latvia | EU_868<br />EU_433 | |
|
||||
| Lithauania | EU_868<br />EU_433 | |
|
||||
| Luxembourg | EU_868<br />EU_433 | |
|
||||
|
||||
### M
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Malaysia | MY_919<br />MY_433 | |
|
||||
| Montenegro | EU_868<br />EU_433 | |
|
||||
|
||||
### N
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Netherlands | EU_868<br />EU_433 | |
|
||||
| New Zealand | ANZ<br />NZ_865 | |
|
||||
| North Macedonia | EU_868<br />EU_433 | |
|
||||
| Norway | EU_868<br />EU_433 | |
|
||||
|
||||
### O
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
|
||||
### P
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Poland | EU_868<br />EU_433 | |
|
||||
| Portugal | EU_868<br />EU_433 | |
|
||||
|
||||
### Q
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
|
||||
### R
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Romania | EU_868<br />EU_433 | |
|
||||
| Russia | RU | |
|
||||
|
||||
### S
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Serbia | EU_868<br />EU_433 | |
|
||||
| Singapore | SG_923 | |
|
||||
| Slowakia | EU_868<br />EU_433 | |
|
||||
| Slowenia | EU_868<br />EU_433 | |
|
||||
| Spain | EU_868<br />EU_433 | |
|
||||
| Sweden | EU_868<br />EU_433 | |
|
||||
| Switzerland | EU_868<br />EU_433 | |
|
||||
|
||||
### T
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Taiwan | TW | |
|
||||
| Thailand | TH | |
|
||||
|
||||
### U
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Ukraine | UA_868<br />UA_433 | |
|
||||
| United Kingdom (UK) | EU_868<br />EU_433 | |
|
||||
| United States of America (USA) | US | |
|
||||
|
||||
### V
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
| Vatican City | EU_868<br />EU_433 | |
|
||||
|
||||
### Y
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
|
||||
### Z
|
||||
|
||||
| Country | LoRa Region | Regulatory document |
|
||||
| --- | --- | --- |
|
||||
|
|
@ -39,7 +39,6 @@ values={[
|
|||
|
||||
- [Android App](/docs/category/android-app)
|
||||
- [Web Client](https://client.meshtastic.org)
|
||||
- [iOS/iPadOS/macOS App](/docs/category/apple-apps)
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="network">
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
id: antenna-reports
|
||||
title: LoRa Antenna Testing Reports
|
||||
description: Community created Antenna Testing Reports for Meshtastic radios
|
||||
sidebar_label: Testing Reports
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
|
@ -11,4 +12,4 @@ The Meshtastic Antenna Reports repository started as a project by [RicInNewMexic
|
|||
|
||||
These users have gone through the effort of testing and providing their opinions on whether specific antennas perform optimally with Meshtastic devices.
|
||||
|
||||
If you wish to contribute a testing report or evaluation, please review the contribution guidelines in the [Meshtastic Antenna Reports](https://github.com/meshtastic/antenna-reports) Github repository.
|
||||
If you wish to contribute a testing report or evaluation, please review the contribution guidelines in the [Meshtastic Antenna Reports](https://github.com/meshtastic/antenna-reports) Github repository.
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
id: antennas
|
||||
title: LoRa Antennas
|
||||
description: Community favorites, testing teports, general considerations, and other resources for antennas for Meshtastic devices
|
||||
sidebar_label: Antennas
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
id: resources
|
||||
title: LoRa Antenna Resources
|
||||
description: Resources for creating coverage maps, RF calculations, and antenna designs for Meshtastic
|
||||
sidebar_label: Resources
|
||||
sidebar_position: 4
|
||||
---
|
||||
|
|
|
|||
|
|
@ -1,6 +1,7 @@
|
|||
---
|
||||
id: antenna-testing
|
||||
title: Antenna Testing
|
||||
description: Explore Meshtastic antenna testing to improve device range. Learn simple to advanced techniques for selecting the right antenna, ensuring effective and cost-efficient communication.
|
||||
sidebar_label: Testing
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
|
|
|||
41
docs/hardware/devices/canary/index.mdx
Normal file
41
docs/hardware/devices/canary/index.mdx
Normal file
|
|
@ -0,0 +1,41 @@
|
|||
---
|
||||
id: canaryone
|
||||
title: CanaryOne
|
||||
sidebar_label: Canary
|
||||
sidebar_position: 12
|
||||
---
|
||||
|
||||
|
||||
The CanaryOne was built by Canary Radio Company from the ground up to run Meshtastic in austere environments as an affordable tactical networking solution.
|
||||
|
||||
CanaryOne custom PCB and case were designed and are assembled and manufactured in the United States.
|
||||
|
||||
The custom PCB board supports jlink debugging, with intelligent electrical components sourced from the United States and Western Europe.
|
||||
|
||||
|
||||
|
||||
## Specifications
|
||||
|
||||
- **MCU**
|
||||
- NRF52840 (Bluetooth)
|
||||
- Bluetooth 5.0
|
||||
- **LoRa Transceiver**
|
||||
- Semtech SX1262
|
||||
- **Frequency options**
|
||||
- All Meshtastic options.
|
||||
- **Navigation Module**
|
||||
- ATGM336H-5N-71 (Supports GPS, BDS and GLONASS)
|
||||
- **Antenna**
|
||||
- SMA Socket
|
||||
- **Connectors**
|
||||
- USB-C
|
||||
|
||||
## Resources
|
||||
|
||||
- Firmware file: `canary-one-X.X.X.xxxxxxx.bin`
|
||||
- Purchase Link: [canaryradio.io](https://canaryradio.io/products/canaryone)
|
||||
|
||||
## Perspective Photos
|
||||
|
||||
|
||||
|
||||
|
|
@ -17,11 +17,12 @@ values={[
|
|||
{label: 'LoRa32 V3/V3.1', value:'v3'},
|
||||
{label: 'Wireless Stick Lite V3', value:'Wireless Stick Lite V3'},
|
||||
{label: 'Wireless Tracker', value: 'tracker'},
|
||||
{label: 'Wireless Paper', value: 'paper'}
|
||||
{label: 'Wireless Paper v1.0', value: 'paper-v1.0'},
|
||||
{label: 'Wireless Paper v1.1', value: 'paper-v1.1'}
|
||||
]}>
|
||||
<TabItem value="v2.1">
|
||||
|
||||
## HELTEC v2.1
|
||||
## V2.1
|
||||
|
||||
:::warning
|
||||
Not recommended because of design issues! Support is being phased out. Use V3 in new projects.
|
||||
|
|
@ -54,7 +55,7 @@ Not recommended because of design issues! Support is being phased out. Use V3 in
|
|||
|
||||
<TabItem value="v3">
|
||||
|
||||
## HELTEC v3/v3.1
|
||||
## V3/V3.1
|
||||
|
||||
:::info
|
||||
This device may have issues charging a connected battery if utilizing a USB-C to USB-C cable. It's recommended to use a USB-A to USB-C cable.
|
||||
|
|
@ -110,7 +111,7 @@ Image Source: [Heltec](<https://resource.heltec.cn/download/WiFi_LoRa32_V3/HTIT-
|
|||
|
||||
<TabItem value="Wireless Stick Lite V3">
|
||||
|
||||
## HELTEC Wireless Stick Lite V3
|
||||
## Wireless Stick Lite V3
|
||||
|
||||
:::info
|
||||
This device may have issues charging a connected battery if utilizing a USB-C to USB-C cable. It's recommended to use a USB-A to USB-C cable.
|
||||
|
|
@ -161,7 +162,7 @@ Image Source: [Heltec](https://resource.heltec.cn/download/Wireless_Stick_Lite_V
|
|||
|
||||
<TabItem value="tracker">
|
||||
|
||||
## HELTEC Tracker
|
||||
## Wireless Tracker
|
||||
|
||||
:::info
|
||||
This device may have issues charging a connected battery if utilizing a USB-C to USB-C cable. It's recommended to use a USB-A to USB-C cable.
|
||||
|
|
@ -221,16 +222,56 @@ Image Source: [Heltec](https://heltec.org/project/wireless-tracker/)
|
|||
|
||||
</TabItem>
|
||||
|
||||
<TabItem value="paper">
|
||||
<TabItem value="paper-v1.0">
|
||||
|
||||
## HELTEC Paper
|
||||
## Wireless Paper V1.0
|
||||
|
||||
:::caution
|
||||
|
||||
Currently the display is only supported in devices labeled v1.1.
|
||||
:::info
|
||||
**The Wireless Paper V1.0 is listed as "Wireless Paper V1.0" in the firmware files and on the web flasher.**
|
||||
|
||||
This device may have issues charging a connected battery if utilizing a USB-C to USB-C cable. It's recommended to use a USB-A to USB-C cable.
|
||||
:::
|
||||
|
||||
|
||||
|
||||
- **MCU:**
|
||||
- ESP32-S3FN8 (WiFi & Bluetooth)
|
||||
- **LoRa Transceiver:**
|
||||
- Semtech SX1262
|
||||
- **Frequency Options:**
|
||||
- 433 MHz
|
||||
- 470 - 510 MHz
|
||||
- 863 - 870 MHz
|
||||
- 902 - 928 MHz
|
||||
- **Connectors:**
|
||||
- USB-C
|
||||
- Antenna:
|
||||
- U.FL/IPEX antenna connector for LoRa
|
||||
- Integrated 2.4 GHz PCB antenna
|
||||
|
||||
### Features
|
||||
|
||||
- Onboard 2.13-inch black and white E-Ink display screen
|
||||
- User and Reset switches
|
||||
- No GPS
|
||||
|
||||
### Resources
|
||||
|
||||
- Firmware file: `firmware-heltec-wireless-paper-v1_0-X.X.X.xxxxxxx.bin`
|
||||
- Purchase Links:
|
||||
- International
|
||||
- [Heltec](https://heltec.org/project/wireless-paper/)
|
||||
- [AliExpress](https://www.aliexpress.us/item/3256805461611876.html)
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="paper-v1.1">
|
||||
|
||||
## Wireless Paper V1.1
|
||||
|
||||
:::info
|
||||
**The Wireless Paper V1.1 is listed as "Wireless Paper" in the firmware files and on the web flasher.**
|
||||
|
||||
This device may have issues charging a connected battery if utilizing a USB-C to USB-C cable. It's recommended to use a USB-A to USB-C cable.
|
||||
:::
|
||||
|
||||
|
||||
|
|
@ -239,6 +280,7 @@ This device may have issues charging a connected battery if utilizing a USB-C to
|
|||
- **LoRa Transceiver:**
|
||||
- Semtech SX1262
|
||||
- **Frequency Options:**
|
||||
- 433 MHz
|
||||
- 470 - 510 MHz
|
||||
- 863 - 870 MHz
|
||||
- 902 - 928 MHz
|
||||
|
|
|
|||
|
|
@ -51,7 +51,7 @@ Modular hardware system with Base, Core and Peripheral modules including the low
|
|||
[RAK18001](./rak/peripherals?rakmodules=Buzzer) Buzzer<br/>
|
||||
[RAK13002](./rak/peripherals?rakmodules=IO) IO<br/>
|
||||
RAK14001 RGB LED<br/>
|
||||
RAK12002 RTC<br/>
|
||||
[RAK12002](./rak/peripherals?rakmodules=RTC) RTC<br/>
|
||||
[RAK1901](./rak/peripherals?rakmodules=Sensors&sensors=RAK1901) Temperature and Humidity Sensor<br/>
|
||||
[RAK1902](./rak/peripherals?rakmodules=Sensors&sensors=RAK1902) Barometric Pressure Sensor<br/>
|
||||
[RAK1906](./rak/peripherals?rakmodules=Sensors&sensors=RAK1906) Environment Sensor<br/>
|
||||
|
|
@ -107,7 +107,7 @@ Inexpensive basic ESP32-based boards.
|
|||
| Name | MCU | Radio | WiFi | BT | GPS |
|
||||
|:------------------------------------------------------------------|:------------|:-------|:------------:|:---:|:---:|
|
||||
| [LoRa32 V2.1](./heltec/?heltec=v2.1) | ESP32 | SX127x | 2.4GHz b/g/n | 4.2 | NO |
|
||||
| [LoRa32 V3/3.1](./heltec/?heltec=v23) | ESP32-S3FN8 | SX1262 | 2.4GHz b/g/n | 5.0 | NO |
|
||||
| [LoRa32 V3/3.1](./heltec/?heltec=v23) | ESP32-S3FN8 | SX1262 | 2.4GHz b/g/n | 5.0 | NO |
|
||||
| [Wireless Stick Lite V3](./heltec/?heltec=Wireless+Stick+Lite+V3) | ESP32-S3FN8 | SX1262 | 2.4GHz b/g/n | 5.0 | NO |
|
||||
| [Wireless Tracker](./heltec/?heltec=tracker) | ESP32-S3FN8 | SX1262 | 2.4GHz b/g/n | 5.0 | YES |
|
||||
| [Wireless Paper](./heltec/?heltec=paper) | ESP32-S3FN8 | SX1262 | 2.4GHz b/g/n | 5.0 | NO |
|
||||
|
|
@ -139,3 +139,10 @@ Fast versatile boards using the RP2040.
|
|||
SSD1306 OLED Display<br/>
|
||||
SH1106 OLED Display<br/>
|
||||
CardKB Keyboard<br/>
|
||||
|
||||
### [CanaryOne](./canary)
|
||||
Complete solution with battery, screen, case, and antenna. Ships pre-flashed with latest Meshtastic firmware.
|
||||
|
||||
| Name | MCU | Radio | WiFi | BT | GPS |
|
||||
|:----------------------|:---------|:-------|:----:|:---:|:---:|
|
||||
| [CanaryOne](./canary) | nRF52840 | SX1262 | NO | 5.0 | YES |
|
||||
|
|
|
|||
|
|
@ -21,9 +21,13 @@ Before proceeding with the setup, ensure the device meets the following requirem
|
|||
[^2]: **Limited Functionality with CH341-SX1262 Device:** Please be aware that the CH341-SX1262 device is currently experiencing partial functionality issues. For reasons yet to be determined, this device struggles with sending packets larger than a few bytes.
|
||||
|
||||
### Hardware Compatibility
|
||||
- Tested radios include Waveshare SX126X, Adafruit RFM9x, and Elecrow Lora RFM95 IOT.
|
||||
|
||||
:::caution Warning
|
||||
UART HATs and SX1302/SX1303 chip-based HATs are not supported. Only hats that use a SPI radio can work with Meshtastic.
|
||||
:::
|
||||
|
||||
- Tested radios include the Waveshare SX126X (SPI version), Adafruit RFM9x, and Elecrow Lora RFM95 IOT.
|
||||
- Support for I2C displays, SPI displays, and keyboard input has been confirmed. It is necessary to be aware of potential pin conflicts when stacking hats.
|
||||
- UART HATs and SX1302/SX1303 chip-based HATs are not supported.
|
||||
|
||||
### System Requirements
|
||||
- The Meshtastic binary, `meshtasticd`, necessitates root access or a user with permissions to access GPIO, SPI, and other interfaces.
|
||||
|
|
|
|||
|
|
@ -22,8 +22,11 @@ Please see the RAK documentation for the correct way to connect your hardware to
|
|||
|
||||
- RAK's Wisblock [Documentation Center](https://docs.rakwireless.com/Product-Categories/WisBlock)
|
||||
- RAK's [GitHub Page](https://github.com/RAKWireless/WisBlock) for the WisBlock
|
||||
- RAK's [WisBlock IO Pin Mapping Tool](https://docs.rakwireless.com/Knowledge-Hub/Pin-Mapper/).
|
||||
- This tool helps properly map your WisBlock modules by identifying the compatible pins and their possible conflicts. Be sure to reference the RAK4631 [variant.h](https://github.com/meshtastic/firmware/blob/master/variants/rak4631/variant.h) to cross-reference potential conflicts to Meshtastic's firmware pin definitions.
|
||||
- Purchase links
|
||||
- See purchase links under specific base boards, core modules, and peripherals
|
||||
- China RAK Direct [RAK Wireless Starter Kit w/ Gen2 Base board](https://store.rakwireless.com/products/wisblock-meshtastic-starter-kit)
|
||||
- US Distributor Rokland [RAK Wireless Starter Kit w/ Gen2 Base board](https://store.rokland.com/products/rak-wireless-wisblock-meshtastic-starter-kit)
|
||||
- US Distributor Rokland [RAK Wireless Starter Kit w/ Gen1 Base board](https://store.rokland.com/products/rakwireless-meshtastic-starter-kit-alternative-with-rak5005-o-base)
|
||||
- UK/EU Distributor ConnectedThings [RAK Wireless Starter Kit w/ Gen2 Base board](https://connectedthings.store/gb/meshtastic/rak-wisblock-meshtastic-starter-kit.html)
|
||||
|
|
|
|||
|
|
@ -16,7 +16,8 @@ values={[
|
|||
{label: 'GPS Module', value: 'GPS'},
|
||||
{label: 'Buzzer', value: 'Buzzer'},
|
||||
{label: 'I/O Module', value: 'IO'},
|
||||
{label: 'Environmental Sensors', value:'Sensors'}
|
||||
{label: 'Environmental Sensors', value:'Sensors'},
|
||||
{label: 'RTC Module', value:'RTC'}
|
||||
]}>
|
||||
<TabItem value="GPS">
|
||||
|
||||
|
|
@ -33,6 +34,7 @@ The RAK12500 is supported on the following base boards & slots:
|
|||
|
||||
- RAK19007 on slot A
|
||||
- RAK19003 on slot C
|
||||
- RAK19001 on slot F
|
||||
|
||||
### RAK1910
|
||||
|
||||
|
|
@ -46,6 +48,7 @@ The RAK1910 is supported on the following base boards & slots:
|
|||
- RAK5005-0 on slot A
|
||||
- RAK19007 on slot A
|
||||
- RAK19003 on slot C
|
||||
- RAK19001 on slot F
|
||||
|
||||
### Resources
|
||||
- RAK Documentation Center
|
||||
|
|
@ -142,5 +145,19 @@ The [RAK1906 Environment Sensor](https://store.rakwireless.com/products/rak1906-
|
|||
- [RAK Wireless RAK1906](https://store.rakwireless.com/products/rak1906-bme680-environment-sensor)
|
||||
|
||||
</TabItem>
|
||||
<TabItem value="RTC">
|
||||
|
||||
## RTC Module
|
||||
|
||||
The [RAK12002 WisBlock RTC Module](https://store.rakwireless.com/products/rtc-module-rak12002) is a real-time-clock with a supercapacitor backup, allowing a node to maintain the correct time across reboots and for up to seven days without power. It operates on a crystal oscilator and communicates via the i2c interface. The module can be inserted into slots A, B or C (some users have reported issues with slot D) and is plug and play - no settings are required.
|
||||
|
||||
### Resources
|
||||
- [RAK Documentation Center RAK12002](https://docs.rakwireless.com/Product-Categories/WisBlock/RAK12002/Overview/)
|
||||
- Purchase Links:
|
||||
- US
|
||||
- [Rokland](https://store.rokland.com/products/rak-wireless-rak12002-rtc-module-micro-crystal-rv-3028-c7-pid-100032)
|
||||
- International
|
||||
- [RAK Wireless](https://store.rakwireless.com/products/rtc-module-rak12002)
|
||||
|
||||
</TabItem>
|
||||
</Tabs>
|
||||
|
|
|
|||
|
|
@ -7,14 +7,22 @@ sidebar_position: 1
|
|||
|
||||
## Functionality
|
||||
|
||||
- **Capacitive Touch Button (Top):**
|
||||
- **Short press:** Updates the e-ink display.
|
||||
- **Capacitive Touch Button (Top):**<br />
|
||||
*If "Wake on Tap or Motion" setting enabled:*
|
||||
- **Touch:**
|
||||
- Update the display
|
||||
- *(at screensaver)* Wake the display.
|
||||
- **Reset Button (Button 1):**
|
||||
- **Single press:** Resets the device.
|
||||
- **Double press:** Puts the device into bootloader mode which allows you to update the firmware.
|
||||
- **Program/Power Button (Button 2):**
|
||||
- **Single press:** Changes the information page displayed on the device's screen.
|
||||
- **Double press:** Turns the screen backlight on/off and sends an adhoc ping of the device's position to the network.
|
||||
- **Long press:** Signals the device to shutdown after 5 seconds.
|
||||
- **Single press:** Power-on / reboot.
|
||||
- **Double press:** Enter bootloader mode, for firmware update.
|
||||
- **Program Button (Button 2):**
|
||||
- **Single press:**
|
||||
- Display next page of information.
|
||||
- *(at screensaver)* Wake the display.
|
||||
- *(when off)* Enter bootloader mode, for firmware update.
|
||||
- **Double press:** Send an "adhoc ping": announce device to network.
|
||||
- ** 3x press:** Enable / disable GPS.
|
||||
- ** 4x press:** Enable / disable display's backlight.
|
||||
- **Hold:** Shutdown.
|
||||
|
||||
|
||||
|
|
|
|||
|
|
@ -2,6 +2,7 @@
|
|||
id: privacy
|
||||
title: Meshtastic privacy policy
|
||||
sidebar_label: Privacy
|
||||
custom_edit_url: null
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
|
|
@ -9,8 +10,6 @@ We don't collect any personal identifying information. We never capture username
|
|||
|
||||
If you opt-in to analytics on the Android app (thank you - that helps us know what things we need to improve), we will receive anonymized information about user behavior. This includes crash reports, screens used in the app, etc... Analytics is provided by [Firebase Crashlytics](https://firebase.google.com/products/crashlytics).
|
||||
|
||||
Maps provided by Mapbox require analytics to work. For more information about what they collect, please see the [Mapbox privacy policy](https://www.mapbox.com/legal/privacy).
|
||||
|
||||
The search engine for this website is provided by Algolia, please see their [privacy policy](https://www.algolia.com/policies/privacy) for details of what information they collect.
|
||||
|
||||
This is an open-source project run by hobbyists, and we try to be completely transparent. If you have questions on this policy, please post on the forum, and we'll reply/clarify/correct.
|
||||
|
|
|
|||
|
|
@ -14,21 +14,18 @@ The minimum Android version is 5.0 (Lollipop 2014, first BLE support), however A
|
|||
### Install with F-Droid
|
||||
|
||||
<p float="center">
|
||||
<a href="https://apt.izzysoft.de/fdroid/repo">
|
||||
<a href="https://f-droid.org/packages/com.geeksville.mesh/">
|
||||
<img
|
||||
alt="Get it on F-Droid"
|
||||
src="https://gitlab.com/IzzyOnDroid/repo/-/raw/master/assets/IzzyOnDroid.png"
|
||||
src="https://fdroid.gitlab.io/artwork/badge/get-it-on.png"
|
||||
width="49%"
|
||||
/>
|
||||
</a>
|
||||
</p>
|
||||
|
||||
1. Download and Install the F-Droid app from [f-droid.org](https://f-droid.org/)
|
||||
2. Open the F-Droid app and navigate to `Settings > Repositories`.
|
||||
3. Click on the `+` icon to add a new repo.
|
||||
4. Enter the Meshtastic repo address as follows: `https://apt.izzysoft.de/fdroid/repo/` as repository address and `3BF0D6ABFEAE2F401707B6D966BE743BF0EEE49C2561B9BA39073711F628937A` as fingerprint
|
||||
5. Navigate to the `Categories` page and refresh (scroll down).
|
||||
6. Search for and install the `Meshtastic` App.
|
||||
2. Navigate to the `Categories` page and refresh (scroll down).
|
||||
3. Search for and install the `Meshtastic` App.
|
||||
|
||||
### Install from Play Store
|
||||
|
||||
|
|
|
|||
|
|
@ -101,6 +101,20 @@ You can test changing channels with the QR code shown below.
|
|||
|
||||
|
||||
|
||||
### Adjust a channel
|
||||
|
||||
You can change the following settings by tapping on the name of an existing channel:
|
||||
1. MQTT Uplink
|
||||
2. MQTT Downlink
|
||||
3. Position precision value
|
||||
|
||||
#### Position Precision
|
||||
The precision levels currently used in the app correspond to the following values:
|
||||
- HIGH_PRECISION (32), full precision
|
||||
- MED_PRECISION (16), around ±350 meters
|
||||
- LOW_PRECISION (11), around ±11 kilometers
|
||||
- DISABLED (0), location data is never sent over the given channel
|
||||
|
||||
### Send a message
|
||||
|
||||
[](/img/android/android-messages.webp)
|
||||
|
|
|
|||
|
|
@ -63,17 +63,9 @@ First, some environment variables need to be set up with command:
|
|||
|
||||
`. ~/.platformio/penv/bin/activate`
|
||||
|
||||
You also want to make some adjustments in the bin/build-all.sh to conform the amd64 build:
|
||||
|
||||
```shell
|
||||
sed -i 's/^BOARDS_ESP32.*/BOARDS_ESP32=""/' bin/build-all.sh
|
||||
sed -i 's/^BOARDS_NRF52.*/BOARDS_NRF52=""/' bin/build-all.sh
|
||||
sed -i 's/echo "Building SPIFFS.*/exit/' bin/build-all.sh
|
||||
```
|
||||
|
||||
You can build amd64 image with command
|
||||
|
||||
`bin/build-all.sh`
|
||||
`./bin/build-native.sh`
|
||||
|
||||
### Executing the application interactively
|
||||
|
||||
|
|
|
|||
|
|
@ -3621,8 +3621,8 @@ packages:
|
|||
resolution: {integrity: sha512-jDctJ/IVQbZoJykoeHbhXpOlNBqGNcwXJKJog42E5HDPUwQTSdjCHdihjj0DlnheQ7blbT6dHOafNAiS8ooQKA==}
|
||||
engines: {node: '>=8'}
|
||||
|
||||
/body-parser@1.20.1:
|
||||
resolution: {integrity: sha512-jWi7abTbYwajOytWCQc37VulmWiRae5RyTpaCyDcS5/lMdtwSz5lOpDE67srw/HYe35f1z3fDQw+3txg7gNtWw==}
|
||||
/body-parser@1.20.2:
|
||||
resolution: {integrity: sha512-ml9pReCu3M61kGlqoTm2umSXTlRTuGTx0bfYj+uIUKKYycG5NtSbeetV3faSU6R7ajOPw0g/J1PvK4qNy7s5bA==}
|
||||
engines: {node: '>= 0.8', npm: 1.2.8000 || >= 1.4.16}
|
||||
dependencies:
|
||||
bytes: 3.1.2
|
||||
|
|
@ -3634,7 +3634,7 @@ packages:
|
|||
iconv-lite: 0.4.24
|
||||
on-finished: 2.4.1
|
||||
qs: 6.11.0
|
||||
raw-body: 2.5.1
|
||||
raw-body: 2.5.2
|
||||
type-is: 1.6.18
|
||||
unpipe: 1.0.0
|
||||
transitivePeerDependencies:
|
||||
|
|
@ -4095,8 +4095,8 @@ packages:
|
|||
resolution: {integrity: sha512-QADzlaHc8icV8I7vbaJXJwod9HWYp8uCqf1xa4OfNu1T7JVxQIrUgOWtHdNDtPiywmFbiS12VjotIXLrKM3orQ==}
|
||||
dev: false
|
||||
|
||||
/cookie@0.5.0:
|
||||
resolution: {integrity: sha512-YZ3GUyn/o8gfKJlnlX7g7xq4gyO6OSuhGPKaaGssGB2qgDUS0gPgtTvoyZLTt9Ab6dC4hfc9dV5arkvc/OCmrw==}
|
||||
/cookie@0.6.0:
|
||||
resolution: {integrity: sha512-U71cyTamuh1CRNCfpGY6to28lxvNwPG4Guz/EVjgf3Jmzv0vlDp1atT9eS5dDjMYHucpHbWns6Lwf3BKz6svdw==}
|
||||
engines: {node: '>= 0.6'}
|
||||
dev: false
|
||||
|
||||
|
|
@ -5220,16 +5220,16 @@ packages:
|
|||
strip-final-newline: 2.0.0
|
||||
dev: false
|
||||
|
||||
/express@4.18.2:
|
||||
resolution: {integrity: sha512-5/PsL6iGPdfQ/lKM1UuielYgv3BUoJfz1aUwU9vHZ+J7gyvwdQXFEBIEIaxeGf0GIcreATNyBExtalisDbuMqQ==}
|
||||
/express@4.19.2:
|
||||
resolution: {integrity: sha512-5T6nhjsT+EOMzuck8JjBHARTHfMht0POzlA60WV2pMD3gyXw2LZnZ+ueGdNxG+0calOJcWKbpFcuzLZ91YWq9Q==}
|
||||
engines: {node: '>= 0.10.0'}
|
||||
dependencies:
|
||||
accepts: 1.3.8
|
||||
array-flatten: 1.1.1
|
||||
body-parser: 1.20.1
|
||||
body-parser: 1.20.2
|
||||
content-disposition: 0.5.4
|
||||
content-type: 1.0.5
|
||||
cookie: 0.5.0
|
||||
cookie: 0.6.0
|
||||
cookie-signature: 1.0.6
|
||||
debug: 2.6.9
|
||||
depd: 2.0.0
|
||||
|
|
@ -5724,18 +5724,11 @@ packages:
|
|||
engines: {node: ^12.20.0 || ^14.13.1 || >=16.0.0}
|
||||
dev: false
|
||||
|
||||
/hasown@2.0.0:
|
||||
resolution: {integrity: sha512-vUptKVTpIJhcczKBbgnS+RtcuYMB8+oNzPK2/Hp3hanz8JmpATdmmgLgSaadVREkDm+e2giHwY3ZRkyjSIDDFA==}
|
||||
engines: {node: '>= 0.4'}
|
||||
dependencies:
|
||||
function-bind: 1.1.2
|
||||
|
||||
/hasown@2.0.1:
|
||||
resolution: {integrity: sha512-1/th4MHjnwncwXsIW6QMzlvYL9kG5e/CpVvLRZe4XPa8TOUNbCELqmvhDmnkNsAjwaG4+I8gJJL0JBvTTLO9qA==}
|
||||
engines: {node: '>= 0.4'}
|
||||
dependencies:
|
||||
function-bind: 1.1.2
|
||||
dev: false
|
||||
|
||||
/hast-util-from-parse5@8.0.1:
|
||||
resolution: {integrity: sha512-Er/Iixbc7IEa7r/XLtuG52zoqn/b3Xng/w6aZQ0xGVxzhw5xUFxcRqdPzP6yFi/4HBYRaifaI5fQ1RH8n0ZeOQ==}
|
||||
|
|
@ -6223,7 +6216,7 @@ packages:
|
|||
/is-core-module@2.13.1:
|
||||
resolution: {integrity: sha512-hHrIjvZsftOsvKSn2TRYl63zvxsgE0K+0mYMoH6gD4omR5IWB2KynivBQczo3+wF1cCkjzvptnI9Q0sPU66ilw==}
|
||||
dependencies:
|
||||
hasown: 2.0.0
|
||||
hasown: 2.0.1
|
||||
|
||||
/is-decimal@2.0.1:
|
||||
resolution: {integrity: sha512-AAB9hiomQs5DXWcRB1rqsxGUstbRroFOPPVAomNk/3XHR5JyEZChOyTWe2oayKnsSsr/kcGqF+z6yuH6HHpN0A==}
|
||||
|
|
@ -8587,8 +8580,8 @@ packages:
|
|||
engines: {node: '>= 0.6'}
|
||||
dev: false
|
||||
|
||||
/raw-body@2.5.1:
|
||||
resolution: {integrity: sha512-qqJBtEyVgS0ZmPGdCFPWJ3FreoqvG4MVQln/kCgF7Olq95IbOp0/BWyMwbdtn4VTvkM8Y7khCQ2Xgk/tcrCXig==}
|
||||
/raw-body@2.5.2:
|
||||
resolution: {integrity: sha512-8zGqypfENjCIqGhgXToC8aB2r7YrBX+AQAfIPs/Mlk+BtPTztOvTS01NRW/3Eh60J+a48lt8qsCzirQ6loCVfA==}
|
||||
engines: {node: '>= 0.8'}
|
||||
dependencies:
|
||||
bytes: 3.1.2
|
||||
|
|
@ -10206,7 +10199,7 @@ packages:
|
|||
compression: 1.7.4
|
||||
connect-history-api-fallback: 2.0.0
|
||||
default-gateway: 6.0.3
|
||||
express: 4.18.2
|
||||
express: 4.19.2
|
||||
graceful-fs: 4.2.11
|
||||
html-entities: 2.4.0
|
||||
http-proxy-middleware: 2.0.6(@types/express@4.17.21)
|
||||
|
|
|
|||
|
|
@ -31,7 +31,12 @@ export default function NotFoundContent({ className }) {
|
|||
original URL and let them know their link is broken.
|
||||
</Translate>
|
||||
</p>
|
||||
<img src="/design/chirpy.png" alt="Chirpy" />
|
||||
<img
|
||||
src="/design/chirpy/chirpy.png"
|
||||
alt="Chirpy"
|
||||
className={clsx("col col--6 col--offset-3")}
|
||||
style={{ maxWidth: "300px" }}
|
||||
/>
|
||||
</div>
|
||||
</div>
|
||||
</main>
|
||||
|
|
|
|||
|
|
@ -1 +1 @@
|
|||
Subproject commit 2865a55d39dea5f6d9f2c09ac1ec485666a833da
|
||||
Subproject commit eeddd10c108f1516e6e0c878fbaa8ed40a4d279d
|
||||
1
static/img/Open_Collective_logo_2021.svg
Normal file
1
static/img/Open_Collective_logo_2021.svg
Normal file
|
|
@ -0,0 +1 @@
|
|||
<svg width="457" height="60" xmlns="http://www.w3.org/2000/svg"><g fill="none" fill-rule="evenodd"><path d="M34.62 18.179C36.75 21.249 38 24.979 38 29s-1.25 7.75-3.38 10.821L29.697 34.9A12.16 12.16 0 0 0 31.214 29c0-2.14-.55-4.15-1.516-5.9l4.921-4.921ZM29.82 13.38 24.9 18.302A12.16 12.16 0 0 0 19 16.786c-6.746 0-12.214 5.468-12.214 12.214S12.254 41.214 19 41.214c2.14 0 4.15-.55 5.9-1.516l4.921 4.921A18.912 18.912 0 0 1 19 48C8.507 48 0 39.493 0 29s8.507-19 19-19c4.021 0 7.75 1.25 10.821 3.38Z" fill="#7FADF2"/><path d="M34.62 18.179C36.75 21.249 38 24.979 38 29s-1.25 7.75-3.38 10.821L29.697 34.9A12.16 12.16 0 0 0 31.214 29c0-2.14-.55-4.15-1.516-5.9l4.921-4.921Z" fill="#B8D3F4"/><g fill="#515F71"><path d="M110.7 13.6c-3.7 0-7.2 1.4-9.8 3.6v-2.3c0-.6-.5-1-1-1h-3.4c-.6 0-1 .5-1 1v43.7c0 .5.4 1 1 1h3.5c.5 0 1-.4 1-1V40.3c2.6 2.2 6.1 3.6 9.8 3.6 8.4 0 15.2-6.8 15.2-15.2-.2-8.4-7-15.1-15.3-15.1Zm0 24.8c-5.4 0-9.7-4.4-9.7-9.7 0-5.4 4.4-9.7 9.7-9.7 5.4 0 9.7 4.4 9.7 9.7 0 5.4-4.4 9.7-9.7 9.7ZM176.6 13.6c-3.7 0-7.1 1.3-9.7 3.5v-1.3c0-1.1-.9-2-2-2h-1.5c-1.1 0-2 .9-2 2v26.3c0 .8.7 1.5 1.5 1.5h2.5c.8 0 1.5-.7 1.5-1.5V29.6c0-5.4 4.4-10.6 9.7-10.6 3.5 0 9.7 1.9 9.7 10.6v12.5c0 .8.7 1.5 1.5 1.5h2.5c.8 0 1.5-.7 1.5-1.5V29.5c0-13.2-10.4-15.9-15.2-15.9ZM158.2 25.5c-1.5-7.1-8-12.3-15.6-11.9-7.6.4-13.8 6.4-14.3 14-.6 8.9 6.4 16.3 15.1 16.3 5.9 0 11-3.3 13.5-8.2.4-.7-.1-1.6-.9-1.8l-3-.6c-.5-.1-1 .1-1.3.6-1.7 2.7-4.8 4.6-8.2 4.6-3 0-5.7-1.4-7.5-3.5l17.2-7.2 5-2.3Zm-24.4 4.4c0-.4-.1-.8-.1-1.2 0-5.4 4.4-9.7 9.7-9.7 3 0 5.8 1.4 7.5 3.6l-17.1 7.3ZM77.3 13.4c-8.4 0-15.2 6.8-15.2 15.2 0 8.4 6.8 15.2 15.2 15.2 8.4 0 15.2-6.8 15.2-15.2 0-8.4-6.8-15.2-15.2-15.2Zm0 24.9c-5.4 0-9.7-4.4-9.7-9.7 0-5.4 4.4-9.7 9.7-9.7 5.4 0 9.7 4.4 9.7 9.7.1 5.3-4.3 9.7-9.7 9.7ZM258.7 13.3c-8.4 0-15.2 6.8-15.2 15.2 0 8.4 6.8 15.2 15.2 15.2 8.4 0 15.2-6.8 15.2-15.2 0-8.4-6.8-15.2-15.2-15.2Zm0 24.9c-5.4 0-9.7-4.4-9.7-9.7 0-5.4 4.4-9.7 9.7-9.7 5.4 0 9.7 4.4 9.7 9.7 0 5.3-4.3 9.7-9.7 9.7ZM390.6 4.3h-3.1c-.7 0-1.2.5-1.2 1.2v3.1c0 .7.5 1.2 1.2 1.2h3.1c.7 0 1.2-.5 1.2-1.2V5.5c0-.7-.6-1.2-1.2-1.2ZM454.5 33.7l-3.6-.7c-.4-.1-.8.1-1 .5-1.7 2.8-4.8 4.7-8.3 4.7-3 0-5.7-1.4-7.5-3.5l17.2-7.2 5.2-2.2c-1.5-7.1-8-12.3-15.6-11.9-7.6.4-13.8 6.5-14.3 14.1-.6 8.9 6.4 16.3 15.1 16.3 6 0 11.2-3.5 13.6-8.5.2-.8-.2-1.5-.8-1.6Zm-22.7-5.3c0-5.4 4.4-9.7 9.7-9.7 3 0 5.8 1.4 7.5 3.6l-17.2 7.3v-1.2ZM332 25.2c-1.5-7.1-8-12.3-15.6-11.9-7.6.4-13.8 6.5-14.3 14.1-.6 8.9 6.4 16.3 15.1 16.3 6 0 11.2-3.5 13.7-8.6.3-.6-.1-1.3-.7-1.4l-3.6-.7c-.4-.1-.8.1-1 .5-1.7 2.8-4.8 4.7-8.3 4.7-3 0-5.7-1.4-7.5-3.5l17.2-7.2 5-2.3Zm-24.5 4.4c0-.4-.1-.8-.1-1.2 0-5.4 4.4-9.7 9.7-9.7 3 0 5.8 1.4 7.5 3.6l-17.1 7.3ZM283.2.7h-3.6c-.5 0-.9.4-.9.9v40.7c0 .5.4 1 1 1h3.5c.5 0 1-.4 1-1V1.6c0-.5-.5-.9-1-.9ZM295.5.7h-3.6c-.5 0-.9.4-.9.9v40.7c0 .5.4 1 1 1h3.5c.5 0 1-.4 1-1V1.6c-.1-.5-.5-.9-1-.9ZM390.6 13.4h-3.1c-.7 0-1.2.5-1.2 1.2v27.6c0 .7.5 1.2 1.2 1.2h3.1c.7 0 1.2-.5 1.2-1.2V14.5c0-.6-.6-1.1-1.2-1.1ZM380.4 13.4h-3.9c-.4 0-.8-.4-.8-.8V1.5c0-.4-.4-.8-.8-.8H371c-.4 0-.8.4-.8.8v11.1c0 .4-.4.8-.8.8h-3.9c-.4 0-.8.4-.8.8V18c0 .4.4.8.8.8h3.9c.4 0 .8.4.8.8v22.7c0 .6.5 1 1 1h3.4c.6 0 1-.5 1-1V19.6c0-.4.4-.8.8-.8h3.9c.4 0 .8-.4.8-.8v-3.9c.1-.4-.2-.7-.7-.7ZM358.8 35.5c-.4-.4-1.1-.4-1.5 0-1.8 1.7-4.1 2.7-6.8 2.7-5.7 0-10.3-5-9.7-10.8.5-4.5 4.2-8.1 8.7-8.6 2.8-.3 5.5.7 7.4 2.4.6.5 1.5.5 2.1-.1l1.7-1.7c.6-.6.6-1.6 0-2.2-2.9-2.7-6.9-4.2-11.2-3.9-7.7.5-13.9 6.9-14.2 14.7-.3 8.6 6.6 15.6 15.2 15.6 4.1 0 7.9-1.6 10.6-4.3.4-.4.4-1.1 0-1.5l-2.3-2.3ZM239.1 35.5c-.4-.4-1.1-.4-1.5 0-1.8 1.7-4.1 2.7-6.8 2.7-5.7 0-10.3-5-9.7-10.8.5-4.5 4.2-8.1 8.7-8.6 2.8-.3 5.5.7 7.4 2.4.6.5 1.5.5 2.1-.1l1.7-1.7c.6-.6.6-1.6 0-2.2-2.9-2.7-6.9-4.2-11.2-3.9-7.7.5-13.9 6.9-14.2 14.7-.3 8.6 6.6 15.6 15.2 15.6 4.1 0 7.9-1.6 10.6-4.3.4-.4.4-1.1 0-1.5l-2.3-2.3ZM424 13.7h-4.9c-.1 0-.2.1-.2.2l-8 23.5c-.1.2-.4.2-.4 0l-8-23.5c0-.1-.1-.2-.2-.2h-4.9c-.2 0-.3.2-.2.3l9.9 29.1c0 .1.1.2.2.2h6.8c.1 0 .2-.1.2-.2l9.9-29.1c.1-.1 0-.3-.2-.3Z"/></g></g></svg>
|
||||
|
After Width: | Height: | Size: 3.9 KiB |
BIN
static/img/hardware/canary-one/dos.webp
Normal file
BIN
static/img/hardware/canary-one/dos.webp
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 481 KiB |
BIN
static/img/hardware/canary-one/front.webp
Normal file
BIN
static/img/hardware/canary-one/front.webp
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 139 KiB |
BIN
static/img/hardware/canary-one/perspective.webp
Normal file
BIN
static/img/hardware/canary-one/perspective.webp
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 80 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 44 KiB After Width: | Height: | Size: 16 KiB |
3
static/img/vercel-logotype-dark.svg
Normal file
3
static/img/vercel-logotype-dark.svg
Normal file
|
|
@ -0,0 +1,3 @@
|
|||
<svg width="4438" height="1000" viewBox="0 0 4438 1000" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<path d="M2223.75 250C2051.25 250 1926.87 362.5 1926.87 531.25C1926.87 700 2066.72 812.5 2239.38 812.5C2343.59 812.5 2435.47 771.25 2492.34 701.719L2372.81 632.656C2341.25 667.188 2293.28 687.344 2239.38 687.344C2164.53 687.344 2100.94 648.281 2077.34 585.781H2515.16C2518.59 568.281 2520.63 550.156 2520.63 531.094C2520.63 362.5 2396.41 250 2223.75 250ZM2076.09 476.562C2095.62 414.219 2149.06 375 2223.75 375C2298.59 375 2352.03 414.219 2371.41 476.562H2076.09ZM2040.78 78.125L1607.81 828.125L1174.69 78.125H1337.03L1607.66 546.875L1878.28 78.125H2040.78ZM577.344 0L1154.69 1000H0L577.344 0ZM3148.75 531.25C3148.75 625 3210 687.5 3305 687.5C3369.38 687.5 3417.66 658.281 3442.5 610.625L3562.5 679.844C3512.81 762.656 3419.69 812.5 3305 812.5C3132.34 812.5 3008.13 700 3008.13 531.25C3008.13 362.5 3132.5 250 3305 250C3419.69 250 3512.66 299.844 3562.5 382.656L3442.5 451.875C3417.66 404.219 3369.38 375 3305 375C3210.16 375 3148.75 437.5 3148.75 531.25ZM4437.5 78.125V796.875H4296.88V78.125H4437.5ZM3906.25 250C3733.75 250 3609.38 362.5 3609.38 531.25C3609.38 700 3749.38 812.5 3921.88 812.5C4026.09 812.5 4117.97 771.25 4174.84 701.719L4055.31 632.656C4023.75 667.188 3975.78 687.344 3921.88 687.344C3847.03 687.344 3783.44 648.281 3759.84 585.781H4197.66C4201.09 568.281 4203.12 550.156 4203.12 531.094C4203.12 362.5 4078.91 250 3906.25 250ZM3758.59 476.562C3778.13 414.219 3831.41 375 3906.25 375C3981.09 375 4034.53 414.219 4053.91 476.562H3758.59ZM2961.25 265.625V417.031C2945.63 412.5 2929.06 409.375 2911.25 409.375C2820.47 409.375 2755 471.875 2755 565.625V796.875H2614.38V265.625H2755V409.375C2755 330 2847.34 265.625 2961.25 265.625Z" fill="black"/>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 1.7 KiB |
3
static/img/vercel-logotype-light.svg
Normal file
3
static/img/vercel-logotype-light.svg
Normal file
|
|
@ -0,0 +1,3 @@
|
|||
<svg width="4438" height="1000" viewBox="0 0 4438 1000" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<path d="M2223.75 250C2051.25 250 1926.87 362.5 1926.87 531.25C1926.87 700 2066.72 812.5 2239.38 812.5C2343.59 812.5 2435.47 771.25 2492.34 701.719L2372.81 632.656C2341.25 667.188 2293.28 687.344 2239.38 687.344C2164.53 687.344 2100.94 648.281 2077.34 585.781H2515.16C2518.59 568.281 2520.63 550.156 2520.63 531.094C2520.63 362.5 2396.41 250 2223.75 250ZM2076.09 476.562C2095.62 414.219 2149.06 375 2223.75 375C2298.59 375 2352.03 414.219 2371.41 476.562H2076.09ZM2040.78 78.125L1607.81 828.125L1174.69 78.125H1337.03L1607.66 546.875L1878.28 78.125H2040.78ZM577.344 0L1154.69 1000H0L577.344 0ZM3148.75 531.25C3148.75 625 3210 687.5 3305 687.5C3369.38 687.5 3417.66 658.281 3442.5 610.625L3562.5 679.844C3512.81 762.656 3419.69 812.5 3305 812.5C3132.34 812.5 3008.13 700 3008.13 531.25C3008.13 362.5 3132.5 250 3305 250C3419.69 250 3512.66 299.844 3562.5 382.656L3442.5 451.875C3417.66 404.219 3369.38 375 3305 375C3210.16 375 3148.75 437.5 3148.75 531.25ZM4437.5 78.125V796.875H4296.88V78.125H4437.5ZM3906.25 250C3733.75 250 3609.38 362.5 3609.38 531.25C3609.38 700 3749.38 812.5 3921.88 812.5C4026.09 812.5 4117.97 771.25 4174.84 701.719L4055.31 632.656C4023.75 667.188 3975.78 687.344 3921.88 687.344C3847.03 687.344 3783.44 648.281 3759.84 585.781H4197.66C4201.09 568.281 4203.12 550.156 4203.12 531.094C4203.12 362.5 4078.91 250 3906.25 250ZM3758.59 476.562C3778.13 414.219 3831.41 375 3906.25 375C3981.09 375 4034.53 414.219 4053.91 476.562H3758.59ZM2961.25 265.625V417.031C2945.63 412.5 2929.06 409.375 2911.25 409.375C2820.47 409.375 2755 471.875 2755 565.625V796.875H2614.38V265.625H2755V409.375C2755 330 2847.34 265.625 2961.25 265.625Z" fill="white"/>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 1.7 KiB |
|
|
@ -2,8 +2,8 @@ import typography from "@tailwindcss/typography";
|
|||
import type { Config } from "tailwindcss";
|
||||
|
||||
export default {
|
||||
content: ["./src/**/*.{js,jsx,ts,tsx}"],
|
||||
darkMode: "class",
|
||||
content: ["./src/**/*.{js,jsx,ts,tsx,md,mdx}", "./docs/**/*.{md,mdx}"],
|
||||
darkMode: ["class", '[data-theme="dark"]'],
|
||||
theme: {
|
||||
extend: {
|
||||
colors: {
|
||||
|
|
|
|||
Loading…
Reference in a new issue