Mesh-Plug provides a simple shortcode that connects to your MQTT broker over WebSocket and prints incoming messages to a live log.<\/p>\n\n
Shortcode: [mesh_plug]<\/p>\n\n
Map shortcode options:\n- map_tiles=\"voyager|osm|light|dark\" (default: voyager)\n- map_zoom=\"13\" map_min_zoom=\"2\" map_max_zoom=\"18\"\n- fit=\"1|0|once\" fit_max_zoom=\"13\" center=\"lat,lon\"<\/p>\n\n
Mesh-Plug can connect to external services depending on how you configure and use it.<\/p>\n\n
Mesh-Plug connects directly from the visitor's browser to the MQTT broker WebSocket URL you enter in Settings \u2192 Mesh-Plug.\nThis is required for the plugin to receive and display Meshtastic\/MQTT messages.<\/p>\n\n
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.\nWhen: whenever a page containing the [mesh_plug] shortcode is loaded and the user connects (or auto-connect is enabled).<\/p>\n\n
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.<\/p>\n\n
If you use the Map tab, Mesh-Plug downloads map tiles from a free provider to render the basemap.\nBy default, Mesh-Plug uses CARTO Voyager tiles. You can switch to OpenStreetMap tiles with shortcode map attributes.<\/p>\n\n
Data sent: standard HTTP requests for map tiles; this typically includes the visitor's IP address, user agent, and the requested tile coordinates.\nWhen: whenever the Map tab is opened\/visible and the map needs to load tiles.<\/p>\n\n
CARTO basemaps: https:\/\/carto.com\/basemaps\nOpenStreetMap tile usage policy: https:\/\/operations.osmfoundation.org\/policies\/tiles\/\nOpenStreetMap privacy policy: https:\/\/osmfoundation.org\/wiki\/Privacy_Policy<\/p>\n\n
GPLv2 or later.<\/p>\n\n