Android Studio向Google Cloud IoT Core收发数据及Android Things项目云连接问题

Hey there! Let's work through why your accelerometer data isn't making it to Google Cloud IoT Core. Since you've already got the sensor up and running smoothly, we can focus on troubleshooting the MQTT/cloud integration pieces.

1. Double-Check MQTT Client Initialization #

First, confirm your MQTT client is set up with the right credentials and endpoint details—small mistakes here are super common:

• Your clientId must follow the exact format: projects/[PROJECT_ID]/locations/[REGION]/registries/[REGISTRY_ID]/devices/[DEVICE_ID]
• Ensure you're using TLS on port 8883 (Google IoT Core requires this for secure MQTT connections)
• Verify your JWT token is generated correctly and hasn't expired (they're only valid for a max of 24 hours; 1 hour is safer for testing)

Here's a quick snippet to validate your JWT setup:

private String generateJwtToken() {
    long currentTime = System.currentTimeMillis();
    return Jwts.builder()
        .setIssuedAt(new Date(currentTime))
        .setExpiration(new Date(currentTime + 3600000)) // 1-hour expiry
        .setAudience(YOUR_PROJECT_ID)
        .signWith(SignatureAlgorithm.RS256, yourPrivateKey)
        .compact();
}

2. Validate the Publish Method Implementation #

When calling your publish method, make sure you're targeting the correct IoT Core telemetry topic: /devices/[DEVICE_ID]/events
Also, format your accelerometer data into a structured payload (JSON is ideal for readability):

private void sendAccelerometerData(float x, float y, float z) {
    String telemetryTopic = String.format("/devices/%s/events", YOUR_DEVICE_ID);
    JSONObject payload = new JSONObject();
    try {
        payload.put("timestamp", System.currentTimeMillis());
        payload.put("accel_x", x);
        payload.put("accel_y", y);
        payload.put("accel_z", z);
        
        // Publish with QoS 1 (ensures message delivery)
        mqttClient.publish(telemetryTopic, payload.toString().getBytes(), 1, false);
    } catch (JSONException | MqttException e) {
        Log.e(TAG, "Failed to send accelerometer data", e);
    }
}

Don't skip exception handling here—stack traces will tell you exactly what's breaking (e.g., lost connection, invalid topic, auth failure).

3. Track Connection State #

Add an MQTT callback to confirm your client is connected and messages are being delivered:

mqttClient.setCallback(new MqttCallback() {
    @Override
    public void connectionLost(Throwable cause) {
        Log.w(TAG, "MQTT connection lost", cause);
        // Add reconnection logic here if needed
    }

    @Override
    public void messageArrived(String topic, MqttMessage message) throws Exception {
        // Handle any incoming commands from IoT Core if required
    }

    @Override
    public void deliveryComplete(IMqttDeliveryToken token) {
        Log.d(TAG, "Accelerometer data delivered successfully!");
    }
});

The deliveryComplete method will confirm your message was sent, while connectionLost will alert you if the client drops the link unexpectedly.

4. Verify Cloud-Side Configuration #

Don't overlook the IoT Core dashboard:

• Ensure your device is registered with the correct public key (it must match the private key you're using for JWT)
• Check that your registry has the right permissions set (the device needs permission to publish events)
• Dig into the IoT Core logs in the Google Cloud Console—this is often the fastest way to spot auth errors or invalid topic issues

5. Test with a Standalone MQTT Client #

If you're still stuck, test your credentials and topic with a tool like Mosquitto. If that works, the issue is in your Android code; if not, it's a cloud configuration problem.

内容的提问来源于stack exchange，提问作者Alkhalil