如何通过AWS Lambda提取DynamoDB温度数据并实现MQTT阈值控制

Got it, let's walk through how to add the temperature threshold check and MQTT command publishing to your existing setup. Assuming your Lambda is triggered by DynamoDB Streams (since you're reacting to new data entries), here's a practical, code-driven approach tailored to your workflow:

1. Prep Work First #

Before diving into code, make sure you have these sorted:

• Lambda Permissions: Add an IoT Core policy to your Lambda execution role that allows the iot:Publish action on your target MQTT topic (e.g., home/heating/control).
• Configurable Thresholds: Decide on your upper/lower temperature limits (e.g., 25°C as the upper threshold—above this send 'off', below send 'on'). Store these as Lambda environment variables instead of hardcoding for easy adjustments later.
• Target MQTT Topic: Confirm the exact topic you want to send the 'on'/'off' commands to (e.g., devices/heater/command).

2. Modify Your Lambda Code (Python Example) #

Here's how to update your existing function to include the threshold logic and MQTT publishing:

import boto3
import os

# Initialize AWS IoT Data client for MQTT publishing
iot_client = boto3.client('iot-data')

# Pull configs from Lambda environment variables (flexible, no code redeploys needed)
LOW_THRESHOLD = int(os.environ.get('LOW_THRESHOLD', 20))
HIGH_THRESHOLD = int(os.environ.get('HIGH_THRESHOLD', 25))
TARGET_MQTT_TOPIC = os.environ.get('TARGET_MQTT_TOPIC', 'devices/heater/command')

def lambda_handler(event, context):
    # Process each new DynamoDB record from the stream
    for record in event['Records']:
        try:
            # Extract the new temperature entry from DynamoDB's NewImage
            new_data = record['dynamodb']['NewImage']
            # Adjust the key below to match your actual DynamoDB temperature attribute name
            temp_raw = new_data['temperature']['S']  # Use 'N' instead if stored as a number
            
            # Convert temperature to integer (handle conversion errors gracefully)
            temp_int = int(temp_raw)
            
            # Determine which command to send based on thresholds
            if temp_int > HIGH_THRESHOLD:
                command = 'off'
                print(f"Temp {temp_int}°C exceeds upper limit. Sending 'off' command.")
            elif temp_int < LOW_THRESHOLD:
                command = 'on'
                print(f"Temp {temp_int}°C is below lower limit. Sending 'on' command.")
            else:
                print(f"Temp {temp_int}°C is within range. No command sent.")
                continue  # Skip publishing if temperature is in the safe zone
            
            # Publish the command to your target MQTT topic
            publish_response = iot_client.publish(
                topic=TARGET_MQTT_TOPIC,
                qos=1,  # Adjust QoS to 0 (fire-and-forget) or 2 (exactly-once) as needed
                payload=command
            )
            print(f"Successfully published '{command}' to {TARGET_MQTT_TOPIC}")
            
        except KeyError as e:
            print(f"Missing expected attribute in DynamoDB record: {str(e)}")
        except ValueError as e:
            print(f"Failed to convert temperature to integer: {str(e)}")
        except Exception as e:
            print(f"Unexpected error processing record: {str(e)}")
    
    return {
        'statusCode': 200,
        'body': 'Completed processing all new temperature records'
    }

3. Key Notes & Best Practices #

• Environment Variables: Using os.environ lets you tweak thresholds or target topics without redeploying code—just update the values in the AWS Lambda Console.
• Error Handling: The try/except blocks ensure your Lambda doesn't crash if a DynamoDB record is malformed or the temperature value is invalid (e.g., a non-numeric string).
• QoS Levels: Adjust the qos parameter in the publish() call based on your reliability needs: QoS 0 is fast but unconfirmed, QoS 1 guarantees at-least-once delivery, QoS 2 guarantees exactly-once.
• Testing: Use the Lambda Console's test feature with sample DynamoDB stream events to verify the logic works before deploying to production.

4. Verify the Setup #

After deploying the updated Lambda:

1. Send a test temperature reading from your Raspberry Pi that's above the high threshold—check if the 'off' command appears on your target MQTT topic.
2. Send a reading below the low threshold to confirm the 'on' command is published.
3. Check Lambda's CloudWatch Logs if something doesn't work—they'll show detailed error messages or print statements to help debug.

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