diff --git a/docs/community/local-groups.mdx b/docs/community/local-groups.mdx index cd85a77a..3b198f48 100644 --- a/docs/community/local-groups.mdx +++ b/docs/community/local-groups.mdx @@ -59,7 +59,7 @@ 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/) diff --git a/docs/community/software/index.mdx b/docs/community/software/index.mdx index 9a4865fd..0f5bdc1a 100644 --- a/docs/community/software/index.mdx +++ b/docs/community/software/index.mdx @@ -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. + diff --git a/docs/community/software/mesh-metrics.mdx b/docs/community/software/mesh-metrics.mdx new file mode 100644 index 00000000..fe1bd5bd --- /dev/null +++ b/docs/community/software/mesh-metrics.mdx @@ -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) diff --git a/docs/configuration/module/remote-hardware.mdx b/docs/configuration/module/remote-hardware.mdx index 20eb8245..db6ebfcc 100644 --- a/docs/configuration/module/remote-hardware.mdx +++ b/docs/configuration/module/remote-hardware.mdx @@ -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 ``` diff --git a/docs/getting-started/initial-config.mdx b/docs/getting-started/initial-config.mdx index 13fe5740..24ba92da 100644 --- a/docs/getting-started/initial-config.mdx +++ b/docs/getting-started/initial-config.mdx @@ -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) diff --git a/docs/hardware/devices/rak/peripherals.mdx b/docs/hardware/devices/rak/peripherals.mdx index 385c686d..3ccbf07d 100644 --- a/docs/hardware/devices/rak/peripherals.mdx +++ b/docs/hardware/devices/rak/peripherals.mdx @@ -34,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 @@ -47,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 diff --git a/docs/legal/privacy.mdx b/docs/legal/privacy.mdx index d79010ff..06d9beb1 100644 --- a/docs/legal/privacy.mdx +++ b/docs/legal/privacy.mdx @@ -10,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.