是否计划扩展Registry Manager CreateQuery及IoT Hub作业以支持模块目标定位？

Great question—this is a super common scenario for managing fleets with shared modules across diverse devices, so let’s break this down for you:

First, to directly answer your core question: As of now, the Registry Manager's CreateQuery function doesn't natively support filtering by module, and IoT Hub Jobs don't have built-in options to target modules specifically. That said, the Azure IoT team is aware of this gap for bulk module management, and this feature is on the product roadmap. You can track updates through Azure's official IoT feedback channels to stay in the loop.

Now, since you need to update that temperature sensor module across 2000 devices right away, here are three practical workarounds that let you achieve your goal today:

Workaround 1: Use Device Twin Tags + IoT Hub Jobs to Update Module Properties #

This leverages existing IoT Hub job capabilities by tagging devices that have your target module, then updating the module's desired properties via the job:

• Step 1: Tag relevant devices
  Add a consistent tag (like "moduleType": "TemperatureSensor") to the device twin of every device that includes your temperature sensor module. For bulk operations, use the Azure CLI with a script to loop through devices:

  az iot hub device-twin update --hub-name {YourHubName} --device-id {DeviceId} --tags '{"moduleType": "TemperatureSensor"}'
  

  If you have a list of device IDs, you can automate this with a bash/PowerShell script to avoid manual updates.
• Step 2: Create a targeted IoT Hub Job
  When setting up the job, filter devices using the tag you added. Then, in the twin update payload, specify the module's desired property change directly:

  {
    "properties.desired.modules.TemperatureSensor.image": "your-new-module-image:v2"
  }
  

  The job will run across all tagged devices, and the module will pick up the new image URL from the device twin.

Workaround 2: Build a Custom Script with Azure IoT SDKs #

For more control over filtering and module targeting, use the Azure IoT SDKs (Python, .NET, etc.) to write a script that batches updates:

• Here’s a quick Python example that iterates through all devices, finds the temperature sensor module, and updates its image property:

  from azure.iot.hub import IoTHubRegistryManager
  
  # Replace with your IoT Hub connection string and module details
  IOT_HUB_CONN_STRING = "{YourIoTHubConnectionString}"
  TARGET_MODULE_ID = "TemperatureSensor"
  NEW_IMAGE_URI = "your-updated-image:v2"
  
  registry_manager = IoTHubRegistryManager(IOT_HUB_CONN_STRING)
  all_devices = registry_manager.get_devices()
  
  for device in all_devices:
      # Get all modules for the current device
      device_modules = registry_manager.get_modules(device.device_id)
      for module in device_modules:
          if module.module_id == TARGET_MODULE_ID:
              # Update the module twin's desired property
              module.module_twin.properties.desired["image"] = NEW_IMAGE_URI
              registry_manager.update_module_twin(device.device_id, module.module_id, module.module_twin)
              print(f"Updated module {TARGET_MODULE_ID} for device {device.device_id}")
  

  This script can be modified to add additional filters (like device type) if you need to narrow down the target set further.

Workaround 3: Bulk Updates via IoT Hub REST API #

If you prefer working with APIs, you can use the IoT Hub REST API to fetch devices, retrieve module twins, and update properties in bulk. Tools like Postman or curl scripts can help automate this workflow—just use the Get Devices endpoint to list devices, then the Get Module Twin and Update Module Twin endpoints for each target module.

Finally, if native module-targeted queries and jobs are critical for your long-term workflow, I’d recommend submitting a feature request to the Azure IoT feedback portal. The team prioritizes features based on user demand, so your input will help push this capability forward.

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