智能家居集成SYNC阶段异常：助手向Fulfillment发送错误数据

Hey there, since your OAuth flow is working smoothly (great job getting that part sorted!), let’s dig into why the action.devices.SYNC intent is sending wonky data to your Fulfillment. I’ve run into this exact issue before, so here’s what to check:

First, Know What a Valid SYNC Request Should Look Like #

Before troubleshooting, let’s confirm the baseline. A proper SYNC request from Google Assistant should have this structure (key fields highlighted):

{
  "requestId": "some-unique-string",
  "inputs": [
    {
      "intent": "action.devices.SYNC",
      "payload": {}
    }
  ],
  "user": {
    "userId": "your-oauth-linked-user-id",
    "locale": "en-US"
  },
  "devices": []
}

If your incoming request is missing user.userId, has extra unexpected fields, or the intent isn’t even action.devices.SYNC, that’s where we start.

Common Culprits & Fixes #

• OAuth Token Claims Are Missing: Even if login works, your OAuth token needs to include the openid scope and a valid sub (subject) claim. Google uses this to tie the user to your system—if sub is missing or invalid, the SYNC request might send garbage user data. Double-check your token response in a tool like jwt.io to verify these claims.
• Fulfillment Endpoint Isn’t Parsing JSON Correctly: Make sure your endpoint is set to accept POST requests with application/json content type. If your server is expecting form data instead, it’ll misparse the payload and make it look like Google is sending wrong data. Add a log to capture the raw request body so you can see exactly what’s coming in. For example, in Python/Flask:

  @app.route('/fulfillment', methods=['POST'])
  def handle_fulfillment():
      raw_request = request.get_data(as_text=True)
      print(f"Raw SYNC Request: {raw_request}")
      # Rest of your logic
  

• Project Configuration Glitch: Head to the Actions Console and double-check your smart home project settings. Ensure you’re using the correct device registration mode (automatic vs manual) and that your OAuth client ID/secret are properly linked. Sometimes beta features or misconfigured account linking settings can alter the intent structure.
• Intent Handler Mix-Up: It’s easy to accidentally route SYNC requests to a handler meant for QUERY or EXECUTE intents. If your code is expecting a different intent’s payload, the data will look incorrect. Verify that your routing logic is correctly matching the action.devices.SYNC intent before processing.
• Test with the Actions Console Tool: Use the "Test" tab in the Actions Console to send a manual SYNC request. Compare that request to what you’re getting from your test device. If the manual request is valid but the device’s isn’t, the issue might be tied to the device’s Google Assistant version or account settings.

One Last Thing #

If you’re still stuck, share the raw request log (redact any sensitive user IDs!)—that’ll make it way easier to spot exactly what’s off.

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