Google Assistant SDK(C++)广播命令故障求助：最新版本响应异常

I’ve run into similar command-specific breakages with the Google Assistant SDK after updates—let’s walk through targeted fixes for your broadcast issue:

Key Observations from Your Output #

Your request payload looks structurally sound, but the SDK isn’t returning detailed errors even with verbose mode on. Since other commands (like time queries) work, this is likely tied to broadcast-specific permissions, command formatting, or device registration changes in the latest SDK version.

Step-by-Step Fixes #

1. Validate Device Model/ID Configuration #

Using device_id: "default" and device_model_id: "default" might not cut it anymore—recent SDK updates often require properly registered device credentials linked to your Google account:

• Head to the Actions Console and confirm your device model is registered with a unique, valid ID.
• Run the assistant with explicit device parameters:

  ./run_assistant --text_input "Broadcast Dinner" --credentials_file ./credentials.json --device_model_id "YOUR_REGISTERED_MODEL_ID" --device_id "YOUR_UNIQUE_DEVICE_ID"
  

2. Adjust Broadcast Command Format #

Google’s command parsing may have gotten stricter. Test more explicit phrasing that matches natural language patterns the Assistant expects for broadcasts:

• Instead of Broadcast Dinner, try:
  • Broadcast that dinner is ready
  • Tell everyone dinner is served

3. Verify Home Group Permissions #

Broadcasts require your device to be linked to a Google Home group:

• Make sure the Google account tied to your credentials.json is part of a valid Home group.
• Check that your device is added to the group via the Google Home app.

4. Enable Granular Debug Logging #

Standard verbose mode might miss gRPC-level errors. Enable deeper logging to uncover hidden issues:

GRPC_VERBOSITY=DEBUG GRPC_TRACE=all ./run_assistant --text_input "Broadcast Dinner" --credentials_file ./credentials.json

This will show raw API traffic and could reveal authorization or payload problems that aren’t visible in standard logs.

5. Roll Back or Update the SDK #

If this is a regression in the latest release:

• Reinstall the previously working version of the Assistant SDK (check your package manager or GitHub release history).
• Alternatively, update to the latest pre-release version if available—there’s a chance the issue has already been patched.

Your Request Output for Reference #

$ ./run_assistant --text_input "Broadcast Dinner" --credentials_file ./credentials.json
Using locale en-US
assistant_sdk robots_pem: assistant_sdk CreateCustomChannel(embeddedassistant.googleapis.com:443, creds, arg)
assistant_sdk wrote first request:
config {
  audio_out_config {
    encoding: LINEAR16
    sample_rate_hertz: 16000
  }
  dialog_state_in {
    language_code: "en-US"
  }
  device_config {
    device_id: "default"
    device_model_id: "default"
  }
  text_query: "Broadcast Dinner"
}
assistant_sdk waiting for response ...
assistant_sdk Got a response
$

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