Mesh-Plug for Meshtastic
Mesh-Plug provides a simple shortcode that connects to your MQTT broker over WebSocket and prints incoming messages to a live log.
Shortcode: [mesh_plug]
Map shortcode options: – map_tiles=”voyager|osm|light|dark” (default: voyager) – map_zoom=”13″ map_min_zoom=”2″ map_max_zoom=”18″ – fit=”1|0|once” fit_max_zoom=”13″ center=”lat,lon”
External services
Mesh-Plug can connect to external services depending on how you configure and use it.
MQTT broker (configured by the site administrator)
Mesh-Plug connects directly from the visitor’s browser to the MQTT broker WebSocket URL you enter in Settings → Mesh-Plug. This is required for the plugin to receive and display Meshtastic/MQTT messages.
Data sent: the visitor’s browser establishes a WebSocket connection to your broker; it may send a client ID and (optionally) the username/password you configured; it subscribes to the topic filter you configured. When: whenever a page containing the [mesh_plug] shortcode is loaded and the user connects (or auto-connect is enabled).
Terms/Privacy: this depends on the broker provider you choose. If you use a third-party MQTT hosting provider, review their terms and privacy policy.
Map tile providers (CARTO / OpenStreetMap)
If you use the Map tab, Mesh-Plug downloads map tiles from a free provider to render the basemap. By default, Mesh-Plug uses CARTO Voyager tiles. You can switch to OpenStreetMap tiles with shortcode map attributes.
Data sent: standard HTTP requests for map tiles; this typically includes the visitor’s IP address, user agent, and the requested tile coordinates. When: whenever the Map tab is opened/visible and the map needs to load tiles.
CARTO basemaps: https://carto.com/basemaps OpenStreetMap tile usage policy: https://operations.osmfoundation.org/policies/tiles/ OpenStreetMap privacy policy: https://osmfoundation.org/wiki/Privacy_Policy
License
GPLv2 or later.
Credits
Developed by Michael Winchester For documentation and updates, visit https://meshplug.michaelwinchester.com/