Tag Archives: Meshtastic

General, Personal

New Meshtastic Eliza for communication testing

Setup a new channel with auto responding feature using Eliza chatbot.
This is to facilitate users who want to test receive and response text over meshtastic.

Channel Name = Eliza
Node shortname = RF30
No encryption key

The channel will respond automatically to messages via Eliza. If a message is sent directly to the node, Eliza will also respond.

Hope this provides more interaction, especially to new users.

PS: Someone asked to integrate /eliza as the trigger word at the start of line in the LongFast channel. This has been implemented.

General

Singapore Meshtastic SG_923 ATIS broadcast

I’m (for now) providing a Singapore Meshtastic ATIS broadcast so as to allow new users in Singapore to be able to tune into something useful.

To begin with, some notes

  • Leave your primary channel (i.e. channel 0) to your default. Or whatever you want your primary channel to be.
  • Set the ATIS channel to whatever secondary channel you wish. In my case, it is channel 1. Use the settings provided below.
  • Below are my MQTT settings.
  • Server: mqtt.meshtastic.org mqtt.lucifernet.com
  • Username: meshdev
  • Password: large4cats

Below are the ATIS settings to tune into.

  • Name: ATIS
  • Encryption: unencrypted – fill in “AQ==” without quotes if required
  • uplinkEnabled: True
  • downlinkEnabled: True
  • positionPrecision: 12 (put in any thing you wish)
  • isMuted: false

Below is the strings / format of my ATIS broadcast which includes

  1. Timestamp:
    [MMDD:HHmm:MsgCount:RETRY]
    MM == Month
    DD == Day
    HH == Hour
    mm == Minutes
    Retry == retry set number. The max retry is currently set to 5. The ATIS message will keep trying until a positive ACK is recieved. i.e. meshtastic command exists correctly.
  2. HELO message, Weather or Traffic
    HELO message = Good morning, afternoon or evening
    WEATHER = WX SGP
    TRAFFIC = TRF SGP
  3. Actual message – Weather
    [Condition] [Temperature] FeelsLike [Temperature] [Humidity] [Windspeed] [Rain mm] [Pressure hPa]

    Weather Condition abbreviation:-
    • “Sunny”: “SUN”,
    • “Clear”: “CLR”,
    • “Partly cloudy”: “PTCLD”,
    • “Cloudy”: “CLD”,
    • “Overcast”: “OVC”,
    • “Mist”: “MIST”,
    • “Patchy rain possible”: “RN?”,
    • “Rain”: “RAIN”,
    • “Light rain”: “L-RAIN”,
    • “Heavy rain”: “H-RAIN”,
    • “Thunderstorm”: “TSTM”,

      Note that if a field cannot be provided due to source timeouts it will be presented by a “-“
  4. Actual message – Traffic (information summarized from LTA Datamall)
    [Sections experiencing delays +X minutes] [Average travel time on Expressway segments] [Standard deviation of the travel time]

    This should be enough to know if driving times are normal and how long it might take for each major expressway leg. Highlighting any sections with out of normal delays

If set up right, you should hear the broadcast over your meshtastic node!

Linux, Personal

Meshtastic Setup notes for uConsole

Finally managed to get some stability in using Meshtastic on the uConsole.

  1. Managed to get the GPS device to be available to Meshtasticd without having to shutdown GPSD. Updated write up below.
  2. Managed to get my Meshtastic node to join the local Singapore mesh network. Given that i can have Meshtasticd now running as a daemon most of the time, it finally makes sense to keep the node running and perhaps contribute to the density of the LoRa network here (?). The notes and learnings below. Mainly congestion optimisation.