# CT Mesh MeshCore Resources

# MeshCore Resources

## Community-run Web Tools

These tools use data reported to our MQTT server by nodes across the state.

- MeshCore Map NEW! - live map showing MeshCore nodes
- MeshCore Wardriving Map NEW! - coverage maps for MeshCore. Note: a new app is in testing and may supersede this.
- Wardrive Contribution - upload your wardrive data to improve coverage maps

## Official Links

meshcore.co.uk

flasher.meshcore.co.uk

Note: the flasher requires WebSerial or Web Bluetooth support in your browser.

## MQTT

Our MQTT broker is uplink-only and designed for fixed nodes across the state to serve as gateway nodes. Its purpose is not to bridge gaps or extend mesh coverage, but to report local traffic to our own web-based tools for analytical data and metrics to assess the mesh's performance. This role is best suited for stable, well-placed nodes with reliable coverage.

MeshCore MQTT uplink uses meshcoretomqtt on a Raspberry Pi or similar Linux computer with the service installed. This configuration stanza goes in your `.env.local` file after the first two MQTT servers that upload to analyzer.letsmesh.net. This also requires a custom firmware. See custom repeater firmware setup.

    # MQTT Broker 3 - CT Mesh
    MCTOMQTT_MQTT3_ENABLED=true
    MCTOMQTT_MQTT3_SERVER=mqtt.ctmesh.org
    MCTOMQTT_MQTT3_PORT=1883
    MCTOMQTT_MQTT3_USE_TLS=false
    MCTOMQTT_MQTT3_USERNAME=meshdev
    MCTOMQTT_MQTT3_PASSWORD=large4cats

← Back to CT Mesh