{"id":128,"date":"2026-01-11T22:59:42","date_gmt":"2026-01-11T22:59:42","guid":{"rendered":"https:\/\/michaelwinchester.com\/mesh-plug\/?page_id=128"},"modified":"2026-01-11T22:59:43","modified_gmt":"2026-01-11T22:59:43","slug":"connectivity-checklist","status":"publish","type":"page","link":"https:\/\/michaelwinchester.com\/mesh-plug\/connectivity-checklist\/","title":{"rendered":"Connectivity Checklist"},"content":{"rendered":"\n

Mesh-Plug Connectivity Checklist<\/h1>\n\n\n\n

(Meshtastic + MQTT + WordPress)<\/em><\/p>\n\n\n\n

This checklist verifies that Meshtastic devices<\/strong>, your MQTT broker<\/strong>, and Mesh-Plug<\/strong> are all connected using the correct transport<\/em>.<\/p>\n\n\n\n

\n

Key rule:<\/strong>
Devices\/apps use MQTT over TLS (8883)<\/strong>; browsers use MQTT over WebSockets (9001)<\/strong>.<\/p>\n<\/blockquote>\n\n\n\n

\n\n\n\n

1. Port & Transport Map (Read This First)<\/h2>\n\n\n\n
Component<\/th>Port<\/th>Transport<\/th>Why<\/th><\/tr><\/thead>
Meshtastic Android<\/td>8883<\/strong><\/td>MQTT over TLS<\/td>Native MQTT client<\/td><\/tr>
Meshtastic Devices<\/td>8883<\/strong><\/td>MQTT over TLS<\/td>Standard IoT transport<\/td><\/tr>
Mesh-Plug (WordPress)<\/td>9001<\/strong><\/td>MQTT over WebSockets (WSS)<\/td>Required by browsers<\/td><\/tr>
mosquitto_sub\/pub<\/code><\/td>8883 only<\/strong><\/td>MQTT over TLS<\/td>CLI does not<\/strong> support WSS<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

\u26a0\ufe0f mosquitto_sub<\/code> will never work<\/strong> on port 9001; protocol errors are expected.<\/p>\n\n\n\n

\n\n\n\n

2. Android Meshtastic Settings (Publisher)<\/h2>\n\n\n\n

MQTT Settings<\/strong><\/p>\n\n\n\n

    \n
  • Host: mqtt.your-domain.com<\/code><\/li>\n\n\n\n
  • Port: 8883<\/strong><\/li>\n\n\n\n
  • TLS: ON<\/strong><\/li>\n\n\n\n
  • Username \/ Password: (your broker creds)<\/em><\/li>\n\n\n\n
  • Root topic: msh<\/code><\/li>\n\n\n\n
  • JSON output: ON<\/strong><\/li>\n<\/ul>\n\n\n\n

    After changing settings<\/strong><\/p>\n\n\n\n

      \n
    • Toggle MQTT OFF \u2192 ON<\/strong><\/li>\n\n\n\n
    • Send:\n
        \n
      • Exchange User Info<\/li>\n\n\n\n
      • Send Position<\/li>\n\n\n\n
      • Chat message<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n\n\n\n
        \n\n\n\n

        3. Mesh-Plug Settings (Subscriber)<\/h2>\n\n\n\n

        Broker<\/strong><\/p>\n\n\n\n

          \n
        • URL: wss:\/\/mqtt.your-domain.com:9001\/mqtt<\/code><\/li>\n<\/ul>\n\n\n\n

          Topics<\/strong><\/p>\n\n\n\n

            \n
          • Subscribe topic: msh\/#<\/code><\/li>\n\n\n\n
          • Publish prefix (if enabled): msh<\/code><\/li>\n<\/ul>\n\n\n\n

            Important stability setting<\/strong><\/p>\n\n\n\n

              \n
            • Gateway Hex:<\/strong>
              Set this explicitly (example: !b2a7c7a8<\/code>)
              Do not<\/strong> rely on auto-learn once your system is stable.<\/li>\n<\/ul>\n\n\n\n
              \n\n\n\n

              4. Broker Sanity Checks (Server)<\/h2>\n\n\n\n

              Confirm ports are listening<\/h3>\n\n\n\n
              nc -vz mqtt.your-domain.com 8883\nnc -vz mqtt.your-domain.com 9001\n<\/code><\/pre>\n\n\n\n
              Both should succeed.<\/p>\n\n\n\n
              \n\n\n\n
              Confirm 9001 is WebSockets<\/h3>\n\n\n\n
              curl -i -k --http1.1 \\\n  -H \"Connection: Upgrade\" \\\n  -H \"Upgrade: websocket\" \\\n  https://mqtt.your-domain.com:9001\/mqtt\n<\/code><\/pre>\n\n\n\n
              Expected:<\/p>\n\n\n\n
              HTTP\/1.1 101 Switching Protocols\n<\/code><\/pre>\n\n\n\n
              \n\n\n\n
              5. Verify Meshtastic Traffic (CLI Test)<\/h2>\n\n\n\n
              Run this before<\/strong> checking WordPress:<\/p>\n\n\n\n
              mosquitto_sub -v \\\n  -h mqtt.your-domain.com \\\n  -p 8883 \\\n  --cafile \/etc\/ssl\/certs\/ca-certificates.crt \\\n  -u YOUR_USER \\\n  -P 'YOUR_PASSWORD' \\\n  -t 'msh\/#'\n<\/code><\/pre>\n\n\n\n
              Then trigger actions in the Android app.<\/p>\n\n\n\n
              You should see messages like:<\/h3>\n\n\n\n
              msh\/2\/json\/... {\"type\":\"nodeinfo\"...}\nmsh\/2\/json\/... {\"type\":\"position\"...}\nmsh\/2\/json\/... {\"payload\":{\"text\":\"hello\"}}\n<\/code><\/pre>\n\n\n\n
              If you see traffic here but not<\/strong> in Mesh-Plug, the issue is browser\/WSS config.
              If you see nothing<\/strong>, Android is not publishing.<\/p>\n\n\n\n
              \n\n\n\n
              6. Common Failure Modes (and Fixes)<\/h2>\n\n\n\n
              \u274c No data anywhere<\/h3>\n\n\n\n
                \n
              • Android accidentally set to 9001<\/strong><\/li>\n\n\n\n
              • Root topic doubled (msh\/msh<\/code>)<\/li>\n\n\n\n
              • MQTT toggled on but never reconnected<\/li>\n<\/ul>\n\n\n\n
                Fix:<\/strong> Android \u2192 port 8883<\/strong>, toggle MQTT off\/on.<\/p>\n\n\n\n
                \n\n\n\n
                \u274c Mesh-Plug connected but no chat or nodes<\/h3>\n\n\n\n
                  \n
                • Gateway Hex auto-learn polluted by client swapping<\/li>\n<\/ul>\n\n\n\n
                  Fix:<\/strong> Set Gateway Hex explicitly and reload dashboard.<\/p>\n\n\n\n
                  \n\n\n\n
                  \u274c mosquitto_sub<\/code> protocol error<\/h3>\n\n\n\n
                    \n
                  • Attempting to test 9001<\/strong><\/li>\n<\/ul>\n\n\n\n
                    Fix:<\/strong> Use 8883 only<\/strong> for CLI testing.<\/p>\n\n\n\n
                    \n\n\n\n
                    7. Golden Rule (Pin This)<\/h2>\n\n\n\n
                    \n
                    Devices publish on 8883.
                    Browsers subscribe on 9001.
                    Same broker. Same topics. Different transports.<\/strong><\/p>\n<\/blockquote>\n","protected":false},"excerpt":{"rendered":"
                    Mesh-Plug Connectivity Checklist (Meshtastic + MQTT + WordPress) This checklist verifies that Meshtastic devices, your MQTT broker, and Mesh-Plug are all connected using the correct transport. Key rule:Devices\/apps use MQTT over TLS (8883); browsers use MQTT over WebSockets (9001). 1. Port & Transport Map (Read This First) Component Port Transport Why Meshtastic Android 8883 MQTT […]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-128","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/michaelwinchester.com\/mesh-plug\/wp-json\/wp\/v2\/pages\/128","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/michaelwinchester.com\/mesh-plug\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/michaelwinchester.com\/mesh-plug\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/michaelwinchester.com\/mesh-plug\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/michaelwinchester.com\/mesh-plug\/wp-json\/wp\/v2\/comments?post=128"}],"version-history":[{"count":1,"href":"https:\/\/michaelwinchester.com\/mesh-plug\/wp-json\/wp\/v2\/pages\/128\/revisions"}],"predecessor-version":[{"id":129,"href":"https:\/\/michaelwinchester.com\/mesh-plug\/wp-json\/wp\/v2\/pages\/128\/revisions\/129"}],"wp:attachment":[{"href":"https:\/\/michaelwinchester.com\/mesh-plug\/wp-json\/wp\/v2\/media?parent=128"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}