使用GL865 V3与Paho MQTT连接Adafruit Broker时连接异常断开求助

Hey there, since you’ve confirmed your connect packet bytes look correct and Adafruit’s dashboard shows a brief "GSMModule45 connected" message, the initial handshake is working—but the broker is dropping the connection right after. Let’s break down the most likely culprits:

1. MQTT Protocol Version Mismatch #

Your connect packet starts with 0x00,0x04 followed by MQTT—that’s MQTT 3.1.1, which Adafruit IO supports. But double-check your GL865 V3’s Paho configuration to make sure it’s explicitly set to 3.1.1. Some modules default to MQTT 3.1 (which uses the MQIsdp protocol name), and even a small mismatch here can trigger an immediate disconnect.

2. Keep Alive Interval Issues #

The Keep Alive field (two bytes in your connect packet) tells the broker how long to wait for a ping from your module before dropping the connection. If this is set to 0, the broker assumes your client won’t send heartbeats and will disconnect you immediately. If it’s set too low (like 1 second), your module might not send a PINGREQ fast enough.

Check bytes 10-11 in your connect packet (zero-indexed) to confirm the value—aim for 30-60 seconds (e.g., 0x00,0x3C for 60 seconds) and make sure your module is configured to send PINGREQ packets on schedule.

3. Incorrect Connect Flags #

The connect flag byte (9th byte in your packet) has critical bits that Adafruit IO requires:

• Username Flag (bit 7): Must be 1 (Adafruit requires your username for authentication)
• Password Flag (bit 6): Must be 1 (You need to send your Adafruit IO key as the password)
• Clean Session (bit 1): Try setting to 1 first—this tells the broker to discard old sessions, which can resolve conflicts if a previous session was left hanging
• Will Flag (bit 2): Set to 0 if you haven’t configured a last will and testament; leaving this as 1 will make the broker wait for a will packet, and it’ll disconnect you if it doesn’t arrive in time

If any of these bits are misconfigured, the broker will accept the initial connection then drop it immediately.

4. Username/Password Encoding & Length Mismatches #

Adafruit IO expects your username (Adafruit account name) and IO key (password) to be sent as valid UTF-8 strings, with accurate 2-byte length prefixes. Even a single byte mismatch between the length field and the actual string length will cause the broker to reject the session.

For example, if your username is GSMModule45 (11 characters), the length prefix should be 0x00,0x0B followed by the UTF-8 bytes of the username. Double-check that these lengths match exactly for both username and password fields in your connect packet.

5. GL865 V3 Module-Specific Checks #

• Stable TCP Connection: First verify that the module can maintain a raw TCP connection to io.adafruit.com:1883 without dropping. Some GSM modules automatically close idle TCP connections, so if your MQTT client isn’t sending data quickly enough, the underlying TCP link might die.
• Paho Library Configuration: Ensure the Paho library is set up to handle CONNACK responses properly. If your module tries to publish/subscribe before receiving the CONNACK from the broker, that can trigger an immediate disconnect. Also, check if auto-reconnect is enabled—though that won’t fix the root cause, it can help with testing.
• Serial Port Settings: Mismatched baud rates or missing flow control can cause partial packet loss. Even if the initial connect packet gets through, subsequent ACKs or pings might be corrupted, leading the broker to drop the connection.

6. Test with a Minimal Connect Packet #

Try sending a stripped-down connect packet with only mandatory fields to eliminate variables. Here’s an example structure (replace placeholders with your actual credentials):

// Fixed header: CONNECT packet, remaining length adjusted to match your content
0x10, 0x3F,
// Protocol name (MQTT 3.1.1)
0x00, 0x04, 0x4D, 0x51, 0x54, 0x54,
// Protocol level (3.1.1 = 0x04)
0x04,
// Connect flags: Username=1, Password=1, Clean Session=1 → 0xC2
0xC2,
// Keep Alive: 60 seconds
0x00, 0x3C,
// Client ID: "GSMModule45" (length 11)
0x00, 0x0B, 0x47, 0x53, 0x4D, 0x4D, 0x6F, 0x64, 0x75, 0x6C, 0x65, 0x34, 0x35,
// Your Adafruit username (replace with your length and bytes)
0x00, 0x08, 0x79, 0x6F, 0x75, 0x72, 0x55, 0x73, 0x65, 0x72,
// Your Adafruit IO key (replace with your length and bytes)
0x00, 0x20, 0xXX, 0xXX, 0xXX, ...

If the connection still drops, try capturing the TCP traffic between your module and the broker to see what CONNACK code the broker sends. A CONNACK with return code 0x00 means success, while codes like 0x04 (bad username/password) or 0x05 (not authorized) will tell you exactly what’s wrong.

内容的提问来源于stack exchange，提问作者Burak İlçim