- Newest
- Most votes
- Most comments
Thanks for reaching out. If you are using the sample template from Github README, it says DeviceConfiguration is empty. (very end of README. file)
"DeviceConfiguration": {}
If you are planning on sending data back to the device, you need to define DeviceConfiguration parameters. The values can be provided by the Lambda function. For example, I would like to send ServerUrl
to device, then I define something like,
"DeviceConfiguration": {
"ServerUrl": {"Ref": "ServerUrl"}
}
My Lambda function will return the value for ServerUrl through parameterOverrides.
def lambda_handler(event, context):
return {
"allowProvisioning": True,
"parameterOverrides" : {
"ServerUrl": "https://amazon.com/devices" // dummy URL
}
}
Lambda function does supply the values for the parameters you defined in DeviceConfiguration. This way, customer knows what parameters are going to device by looking at the provisioning template.
Hope this helps,
Ranga
Great! It now works :)
One thing that could be improved in the docs as a follow-up is having in the examples something like a you described to reference "Parameter" values, i.e. having
"DeviceConfiguration": {
"SomeConfig": {"Ref": "SomeParameter"}
}
Because from my side I interpreted (wrongly) that simply adding something to "parameterOverrides" would already add to "deviceConfiguration" configuration. At least from this quote in the doc:
"parameterOverrides" will be added to "deviceConfiguration" parameter in RegisterThing response payload.
Nevertheless, your answer solved my issue, thank you very much!
Glad it worked. Yes, we are working on fixing the documentation. Thanks for pointing it out.
Thanks,
Ranga
Relevant content
- asked a year ago
- Accepted Answerasked 8 months ago
- asked 9 months ago
- AWS OFFICIALUpdated a month ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated 2 years ago