Internet of Things

Hi, I am working through general LoRaWAN functions and applications as part of a larger IoT project. I'm having trouble connecting my gateway (Multitech Conduit) to AWS. I've gone through all the steps provided in the AWS help documentation and documentation from the manufacturer, including creating new Gateway Cert Manager permissions/roles (AWS steps here https://docs.aws.amazon.com/iot/latest/developerguide/connect-iot-lorawan-rfregion-permissions.html). Still, when I try to add my gateway I get an error message saying that I do not have the correct permissions set to add a gateway. Has anyone run into this? Is there a way to associate the role/permission with my IAM account? or should it be set for the root account?

Environment : **GreenGrassV2**, Deployed on : **Raspberry Pi Version 3** , Operating system :** Raspbian GNU/Linux 10** We want to start and stop raspberry pi operating system's service from lambda function. Lambda function is deployed under green grass container. Service can be start and stop without sudo / root privileges. We have configured polkit service to start/stop service without sudo. To start and stop service we tried with "exec" , "spawn" and "spawnSync" but we are getting error as under ``` {"err":{"killed":false, "code":1,"signal":null,"cmd":"systemctl stop wpa_supplicant@wlan0.service"}} ``` We also tried to execute command using .sh file but that also giving above error. Purpose to start/stop service is, we want to change Raspberry pi AP mode to station mode and vise versa.

I have the following mqtt message: ``` { "sensors": [ { "lsid": 412618, "data": [ { "temp_in": 72.3, "heat_index_in": 72, "dew_point_in": 55.9, "ts": 1652785241, "hum_in": 56.3 } ], "sensor_type": 243, "data_structure_type": 12 }, { "lsid": 421195, } ``` I can get the "sensors,0.lsid" value and the entire "data" array using this query: ``` select get(sensors,0).lsid as ls, get(sensors, 0).data as data1 from "topic" ``` but what I really need is to get "temp_in:72.3" , i.e. the values from the second level array I've tried using this :[https://docs.aws.amazon.com/iot/latest/developerguide/iot-sql-nested-queries.html](), but unless i'm not following it correctly, it doesnt seem to work. Any help would be greatly appreciated

Hello community, especially those more experienced in IoT via LoRaWAN: As you can see in the attached image, so far I have only been able to visualize the MQTT broadcast from Helium (label "red485-00)" in the "test client" by subscribing to all the topics of the object "DRAGINO-RS485LN-00" (type "Helium-Things"). Said object is sending the "payload" corresponding to some sensors (temperatures and CO2 in only 9 bytes) Please, I need your help to learn how to program the necessary (and cheapest possible) AWS service/s to decode that payload and represent its values ​​in graphs (historical, last value, etc.). To begin with, I would like to know which AWS services to use, in which language (JSON, JavaScripts, Python, etc.) and in which place to leave that written programming. Thank you very much to those who can give me a hand. [220517-102036_red485FromHeliumToAWS](https://drive.google.com/file/d/1LoAJueLRbJ8-o8omkus5eLlwYC1VU4vR/view?usp=sharing)

I have an OPC server that has nodes with arrays as values. For example I have a node called "Temperatures" which has values [33, 29, 30, 19] in the array. **Is it possible to set single items of this array as properties into SiteWise assets with aliases** like */Temperatures/1*, */Temperatures/2*, */Temperatures/3*, etc.?

Hi, the framework given by AWS for ESP32-DevkitC based OTA MQTT is crashing when internet disconnects. During crash, 6 out of 5 retry for TLS attempts is seen in serial log. Please suggest how to overcome this. If any other info required please let me know.

HI, I have followed the instructions from : https://aws.amazon.com/premiumsupport/knowledge-center/aws-iot-core-jitp-setup/, and i have created a thing in the AWS IoT Core. But there is no shadow created in the Device Shadows -- Device Shadows (0)Info. How i can create also the Device Shadow with JITP Provision? Thanks.

I have a Greengrass Lambda component subscribed to the `aws.greengrass.SNS` output topic `sns/message/status` using the `aws.greengrass.LegacySubscriptionRouter` component with the following configuration: ``` { "subscriptions": { "GreengrassSnsOutput": { "id": "GreengrassSnsOutput", "source": "component:aws.greengrass.SNS", "subject": "sns/message/status", "target": f"component:MyComponentName", } } } ``` That works as expected, but if I update the Lambda corresponding to `MyComponentName`, I get the following error message in the main Greengrass log file: ``` com.aws.greengrass.lambdamanager.LambdaNotFoundException: Lambda arn:aws:lambda:region:account:function:my-function-name:# does not exist ``` The [developer guide](https://docs.aws.amazon.com/greengrass/v2/developerguide/legacy-subscription-router-component.html#legacy-subscription-router-component-configuration) suggests that v2.1.0... >Adds support to specify component names instead of ARNs for source and target. If you specify a component name for a subscription, you don't need to reconfigure the subscription each time the version of the Lambda function changes. I took that to mean nothing needs to happen with respect to the subscription after a new component version with the same name but a new Lambda ARN is deployed. Is that right or is there something else that needs to be done? I'm using the following component versions: ``` "aws.greengrass.LegacySubscriptionRouter": { "componentVersion": "2.1.4" }, "aws.greengrass.Nucleus": { "componentVersion": "2.5.5" }, "aws.greengrass.SNS": { "componentVersion": "2.1.0" }, ```

I have generated a timestream database and table, but am struggling to write data to the table. The data comes from an mqtt topic, and can be seen in the cloudwatch log, so I know my select statement is sound. I think i have given the IAM role the correct permissions. This answer [https://repost.aws/questions/QUmWAjLqG7RwGHCSL2tMrXvw/iot-core-rules-to-map-timestamp-to-timestream#COMoUviJP_TGCAgZvcltBQUw](by @Greg_b) describes how to enter the 'timestamp value' but does not say what is needed in the 'timestamp unit' field. I am a complete newcomer to AWS so apologies if my question is not worded correctly. I would really appreciate some help with this! One further question, why, after i have deactiveted a rule, does it still appear in the cloudwatch logs?

We have: - an AWS transfer family server with FTPS protocol - a custom hostname and a valid ACM certificate which is attached to the FTP server - a Lambda for the Identity provider The client is using: - EXPLICIT AUTH TLS - our custom hostname - port 21 The problem is: the client can connect, the authentication is successfully (see below for the auth test result), but during the communication with the FTP server a TLS_RESUME_FAILURE occurs. The error in the customer client is "522 Data connection must use cached TLS session", and the error in the CloudWatch LogGroup of the transfer server is just "TLS_RESUME_FAILURE" I have no clue why this is happen. Any ideas? Here is the auth test result ``` { "Response": "{\"HomeDirectoryDetails\":\"[{\\\"Entry\\\":\\\"/\\\",\\\"Target\\\":\\\"/xxx/new\\\"}]\",\"HomeDirectoryType\":\"LOGICAL\",\"Role\":\"arn:aws:iam::123456789:role/ftp-s3-access-role\",\"Policy\":\"{\"Version\": \"2012-10-17\", \"Statement\": [{\"Sid\": \"AllowListAccessToBucket\", \"Action\": [\"s3:ListBucket\"], \"Effect\": \"Allow\", \"Resource\": [\"arn:aws:s3:::xxx-prod\"]}, {\"Sid\": \"TransferDataBucketAccess\", \"Effect\": \"Allow\", \"Action\": [\"s3:PutObject\", \"s3:GetObject\", \"s3:GetObjectVersion\", \"s3:GetObjectACL\", \"s3:PutObjectACL\"], \"Resource\": [\"arn:aws:s3:::xxx-prod/xxx/new\", \"arn:aws:s3:::xxx-prod/xxx/new/*\"]}]}\",\"UserName\":\"test\",\"IdentityProviderType\":\"AWS_LAMBDA\"}", "StatusCode": 200, "Message": "" } ```

Hello, I generated an MQTT client certificate using create-keys-and-certificate. The issuer of this certificate is: issuer= /OU=Amazon Web Services O=Amazon.com Inc. L=Seattle ST=Washington C=US is there any way to access that intermediate certificate and any other intermediate ones in the chain? I've checked all the certificates here: https://www.amazontrust.com/repository/ but unfortunately none of them is that one. thank you!

I'm trying to create a Greengrass Lambda function that publishes to an IPC topic using the the IoT SDK. My Lambda code includes: ``` from awsiot import greengrasscoreipc # type: ignore from awsiot.greengrasscoreipc.model import ( # type: ignore JsonMessage, PublishMessage, PublishToTopicRequest, ) ipc_client = greengrasscoreipc.connect() ``` This leads to the following import error: ``` FATAL: lambda_runtime.py:426,Failed to initialize Lambda runtime due to exception: No module named '_awscrt'. ``` I can see that the Lambda artifact includes both `awscrt` and `awsiot` in `/greengrass/v2/packages/artifacts-unarchived/componentName/version/lambda-artifact/`, so I'm not sure why the import is failing. I'm using a non-pinned Python 3.8 Lambda in NoContainer mode with LambdaManager v2.2.3, LambdaLauncher v2.0.10, and LambdaRuntimes v2.0.8 I have been able to use `awsiot` to publish to IPC topics in a non-Lambda component. That component runs a `pip install -r requirements.txt` command to install `awsiotsdk` to the site-packages for `ggc_user` during the install lifecycle, whereas the Lambda component is delivered to the device with its package dependencies included. Any ideas what I need to do differently? I haven't seen this problem yet with other Lambdas that have different dependencies.

Hi All, We are working on ESP32C3 for OTA functionality using https://github.com/espressif/esp-aws-iot/tree/release/beta/examples/ota/ota_mqtt. We understood original C SDK from AWS side updated from ESP side to make it compatible to ESP32C3. As a part of testing, ESP32C3 is always connected to the Router over WiFi (Mobile Hotspot always ON). We are toggling the internet connection to the router.(**Mobile Data turned Off and ON**) We observed on every internet reconnection, there is memory leak of ~3KB. The memory leak used to get restored. But it take ~12 Min, ~17 Min, ~23Min. In one of the captured log, original free heap of 121828 get reduced to 118620 (~3K leak) after internet restore. After ~23 min, memory leak recovered to 121740. We are following with ESP for this issue. But we are getting little slow reply from ESP side. We have following observation, i) The AWS CSDK has WiFi disconnect event. But there is no event to handle Internet disconnect as we highlighted above - **Mobile Data turned Off and ON** ii) On WiFi disconnection and reconnection, memory leak not observed **Our queries/request:** i) If possible, we request AWS to replicate above testing on ESP32 device and share result. We are also trying to build code for ESP32 - mqtt OTA released from AWS side. We are getting some error. We are working on same. ii) Provide input from AWS side for memory leak observation. That will help to work on this issue further. **Did you came across the mentioned memory leak error in past? ** iii) Provide input on Internet disconnect event as we mentioned in observation 1 Thanks....

- I'm using Quectel modem BG95 with a host MCU to connect to AWS IoT core and publish to topics and subscribe to topics as well. - I used to get an error occasionally that closed the MQTT connection exactly while doing pub/sub operations and connection had to be re-established , but that was very rare. - However, since the last few days I have been running tests on multiple devices (using same IoT core endpoint) and have been getting this MQTT dis-connection on each pub or sub operation. I am attaching a log for review. - To me it seems a server side issue since I have tried it with multiple modems and previous versions of firmware. ``` [While publishing to topic] ;2022-05-08T02:29:41Z;28;-966233403;462863960;;RAK000121|-45,RAKTEST|-56 AT+QIDEACT=1 OK[ 2022-05-08T02:29:41Z ] [FARM_IP][INFO] MDM_SET_DEACTIVATE_PDP-else AT+QIACT=1 OK AT+QMTOPEN=0,"a5u9klmd2viw3z-ats.iot.us-west-1.amazonaws.com",8883 OK +QMTOPEN: 0,0 --- [Opening MQTT Connection] [ 2022-05-08T02:29:41Z ] [FARM_IP][INFO] Mqtt opened AT+QMTCONN=0,"0123qwer786" OK +QMTCONN: 0,0,0 --- [MQTT client connected] AT+QMTPUB=0,1,1,0,"fm/1011",72 --- [Publishing to the MQTT Topic] > ;2022-05-08T02:29:41Z;28;-966233403;462863960;;RAK000121|-45,RAKTEST|-56 OK +QMTSTAT: 0,1 --- [MQTT Connection Closed] ``` ``` [While Subscribing to topic] AT+QMTSUB=0,1,"imei/get_logs",0 --- [Subscribing to the MQTT Topic] OK +QMTSTAT: 0,1 --- [MQTT Connection Closed] [ ] [FARM_IP][INFO] Starting timer AT+QMTSUB=0,1,"imei/get_logs",0 --- [Subscribing to the MQTT Topic] OK +QMTSTAT: 0,1 --- [MQTT Connection Closed] ```

Are there plans to support ECC keys in IoT Greengrass V2 - So that security devices like the ATECC608A/B etc can be used to secure keys for Greengrass communications between devices and AWS cloud ? I believe that Greengrass V1 did support this, but support seems to have disappeared it doesn't seem to possible with the current V2 version. Is support for these devices dropped or is there a plan or roadmap for support ? https://devices.amazonaws.com/detail/a3G0L00000AAOCcUAP/ATECC608a-CryptoAuthentication-Secure-Element

As my understanding, there are two required steps. I think only 1) is ok. **Is this redundancy? ** 1) From AWS IoT core policies, grant access to cognito_identity_id ```shell aws iot attach-policy --policy-name 'myIoTPolicy' --target '<YOUR_COGNITO_IDENTITY_ID>' ``` 2) From Cognito side, attach AWSIoTDataAccess and AWSIoTConfigAccess to Cognito Authenticated Role

I would like to be able to perform local testing of my greengrass components before deployment. The issue is that my components normally use Greengrass IPC, meaning that I cannot perform local testing, as IPC messages cannot be sent/received as the local component test won't be happening in Greengrass. Is there a way to get around this ? Is there a method to mimic/test Greengrass IPC calls in a program, outside of a Greengrass deployment ?

Hello, I am sending data using MQTT test client in AWS IoT. The data is showing up properly when I subscribe to the topic. I then wanted to send the data to DynamoDB using a rule. I created the rule and double checked everything: made sure the topics were the same, the rule and MQTT were in the same location (ie: u-west-1), i tried creating different roles when the first didn't work, and i double checked to make sure the attributes were spelled correctly in the MQTT message and DynamoDB table. Any help or additional troubleshooting methods will be greatly appreciated. Thanks.