- Initial setup for Pressac EnOcean gateway.
- An AWS account with permissions to create and manage AWS IoT resources.
- Understand how to setup AWS IoT connection. External link here
Note: For detailed instructions on how to set up the AWS connection on your Pressac gateway, please refer to the AWS guide. This guide provides a step-by-step walkthrough on creating the necessary resources. To access the instructions, simply navigate to Page 406, where you will find steps on how to create the required resources, including:
- AWS IoT thing
- AWS IoT policy
- AWS IoT root CA certificate
Navigate to the AWS IoT Core connection page by clicking “- AWS IoT” in the Connections sub-menu on the Pressac EnOcean gateway web-interface.
Then change the AWS IoT connection from “OFF” to “ON”.
Once you have switched “ON” the connection, input the client ID, root topic and endpoint, upload your certificates and set your message type.
|Connection to AWS IoT can be enabled or disabled from here.
|This is the client identifier the gateway will use when publishing to AWS IoT. This value will be used to identify the gateway to the AWS IoT MQTT server. It must be unique among devices across your AWS account.
|Device data will be sent to AWS IoT Core using only the standard defined topics.
|Device data will be sent to AWS IoT Core using the device shadow service for AWS IoT. To learn more go to AWS Device Shadows.
|Standard and device shadow
|Device data will be sent to both standard topics and to the AWS device shadow service.
|You can find the endpoint of your AWS IoT Thing in the management screen of your AWS IoT Thing. By default, the endpoint of an AWS IoT Thing looks like: xxxxxxxxxxxxxxxxx.iot.region.amazonaws.com.
|Certificate for your AWS IoT Thing this is generated/created when creating your AWS IoT Thing on AWS IoT.
|Private key certificate of your AWS IoT Thing. This is generated/created when creating your AWS IoT Thing on AWS IoT.
|Server/certificate authority certificates allow the gateway to verify they’re communicating with AWS IoT and not another server impersonating AWS IoT. The default preloaded certificate is ‘RSA 2048 bit key: Amazon Root CA 1.’ If necessary, this can be changed from here.
After inputting your connection details and uploading your certificates, select which data you would like to be included in the payload and click “Save”. The AWS IoT connection status will now change to “Connected”.
The data contained in the payload sent is optional. From here, you can select the data you would like to include.
|The time the gateway received a message from a physical device.
|Name assigned to the physical device sending data to the gateway. This can be found in your device lists.
|Device ID (device identification) associated with a physical device e.g. ‘01882050’. Device IDs can be found in your device lists.
|Type of EnOcean device as found on the devices page. e.g. CO2, temperature and humidity.
|Gateway name assigned in the System > General screen.
|Location of a device assigned on the edit device screen e.g. mainoffice.
|Values received by the gateway from a physical device such as temperature, humidity, current etc.
|Device value unit
|Unit the device value is measured in if available e.g. °C.
|Signal strength (dBm)
|Signal strength between the device and gateway in dBm.