Add notes about public MQTT server having a lot of traffic #901
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@GUVWAF is attempting to deploy a commit to the Meshtastic Team on Vercel. A member of the Team first needs to authorize it. |
pdxlocations
approved these changes
Dec 24, 2023
mr-tbot
added a commit
to mr-tbot/mesh-ai
that referenced
this pull request
Mar 14, 2025
Finally found this article: meshtastic/meshtastic#901 Which finally explains why my node has been disconnecting from the script - it wasn't my script! It was MQTT overwhelming my node! Make sure to leave MQTT features completely disabled on any device you use this script with! Signed-off-by: TBOT <[email protected]>
mr-tbot
added a commit
to mr-tbot/mesh-ai
that referenced
this pull request
Mar 14, 2025
…mproved Ollama Support
### New Updates in v0.4.0 → v0.4.1
- **Error Handling (ongoing):**
- Trying a new method to handle WinError exceptions - which though much improved in v0.4.0 - still occur under the right connection circumstances - especially over Wi-Fi.
(**UPDATE: My WinError issues were being caused by a combination of low solar power, and MQTT being enabled on my node. MQTT - especially using LongFast is very intense on a node, and can cause abrupt connection restarts as noted here: meshtastic/meshtastic#901 - but - now the script is super robust regardless for handling errors!)**
- **Emergency Email Subject:**
- Email Subject now includes the long name, short name & Node ID of the sending node, rather than just the Node ID.
- **Docker Support**
- Thanks @clendaniel - Who was kind enough to generate a Dockerfile & docker-compose.yaml for the project!
### New Updates in v0.4.1 → v0.4.2
- **Initial Ubuntu & Ollama Unidecode Support: -**
- User @milo_o - Thank you so much! I have merged your idea into the main branch - hoping this works as expected for users - please report any problems! - #19
- **Emergency Email Google Maps Link:**
- Emergency email now includes a Google Maps link to the sender's location, rather than just coordinates. - Great call, @nlantz79! (Remember - this is only as accurate as the sender node's location precision allows!)
Signed-off-by: TBOT <[email protected]>
Snail3D
pushed a commit
to Snail3D/Mesh-Master
that referenced
this pull request
Oct 19, 2025
Finally found this article: meshtastic/meshtastic#901 Which finally explains why my node has been disconnecting from the script - it wasn't my script! It was MQTT overwhelming my node! Make sure to leave MQTT features completely disabled on any device you use this script with! Signed-off-by: TBOT <[email protected]>
Snail3D
pushed a commit
to Snail3D/Mesh-Master
that referenced
this pull request
Oct 19, 2025
…mproved Ollama Support
### New Updates in v0.4.0 → v0.4.1
- **Error Handling (ongoing):**
- Trying a new method to handle WinError exceptions - which though much improved in v0.4.0 - still occur under the right connection circumstances - especially over Wi-Fi.
(**UPDATE: My WinError issues were being caused by a combination of low solar power, and MQTT being enabled on my node. MQTT - especially using LongFast is very intense on a node, and can cause abrupt connection restarts as noted here: meshtastic/meshtastic#901 - but - now the script is super robust regardless for handling errors!)**
- **Emergency Email Subject:**
- Email Subject now includes the long name, short name & Node ID of the sending node, rather than just the Node ID.
- **Docker Support**
- Thanks @clendaniel - Who was kind enough to generate a Dockerfile & docker-compose.yaml for the project!
### New Updates in v0.4.1 → v0.4.2
- **Initial Ubuntu & Ollama Unidecode Support: -**
- User @milo_o - Thank you so much! I have merged your idea into the main branch - hoping this works as expected for users - please report any problems! - mr-tbot/mesh-ai#19
- **Emergency Email Google Maps Link:**
- Emergency email now includes a Google Maps link to the sender's location, rather than just coordinates. - Great call, @nlantz79! (Remember - this is only as accurate as the sender node's location precision allows!)
Signed-off-by: TBOT <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Several people have experienced various issues (not receiving messages, not being able to connect to the WebUI, not being able to change settings, etc.) when using the default channel on the public MQTT server, which has a lot of traffic. Since there isn't much we can do about it at this point, I think it's good to warn users about this.