|
| 1 | +# Matter Wi-Fi + AWS Component |
| 2 | + |
| 3 | +- Matter+AWS is a silabs only feature to connect matter devices to proprietary |
| 4 | + cloud solutions(AWS,GCP,APPLE ...) directly.As such, a Matter Wi-Fi device |
| 5 | + must support connecting locally on the Matter Fabric, via IPv6, and |
| 6 | + connecting to the Internet via IPv4. |
| 7 | +- Matter devices can be controlled by chip-tool or controller and the |
| 8 | + respective status of the attribute modified will be published to the cloud. |
| 9 | +- Remote user can install the cloud specific application to get the |
| 10 | + notification on the attribute status. |
| 11 | + |
| 12 | +## Matter + AWS Feature Diagram |
| 13 | + |
| 14 | +1. Below diagram gives end-to-end flow about Direct Internet Connectivity. |
| 15 | + |
| 16 | + |
| 17 | + |
| 18 | +## Prerequisites |
| 19 | + |
| 20 | +### Hardware Requirements |
| 21 | + |
| 22 | +- Hardware required for Matter + AWS feature to run on Silicon Labs Platform, |
| 23 | + refer [Hardware Requirements](#hardware-requirements) |
| 24 | + |
| 25 | +### Software Requirements |
| 26 | + |
| 27 | +- MQTT Explorer http://mqtt-explorer.com/ |
| 28 | +- Software required for Matter + AWS feature, refer |
| 29 | + [Software Requirements](#software-requirements) |
| 30 | + |
| 31 | +## End-to-End Set-up bring up |
| 32 | + |
| 33 | +## Message Queuing Telemetry Transport (MQTT) |
| 34 | + |
| 35 | +- MQTT is an OASIS standard messaging protocol for the Internet of Things |
| 36 | + (IoT). It is designed as an extremely lightweight publish/subscribe |
| 37 | + messaging transport that is ideal for connecting remote devices with a small |
| 38 | + code footprint and minimal network bandwidth. Refer https://mqtt.org/ for |
| 39 | + more details |
| 40 | + |
| 41 | +### Building Matter Matter + AWS Application |
| 42 | + |
| 43 | +1. To Build Matter + AWS Application, refer |
| 44 | + [Building of Matter + AWS](./silabs_matter_aws_build_guide.md) |
| 45 | +2. Commission the Matter Device and confirm Matter + AWS connection is done from |
| 46 | + Device side logs. |
| 47 | + |
| 48 | +## End-to-End Test of Matter + AWS Application |
| 49 | + |
| 50 | +- **Sharing status of device to cloud** |
| 51 | + |
| 52 | + - Below diagram gives end-to-end flow for sharing status from matter |
| 53 | + device to cloud |
| 54 | + |
| 55 | +  |
| 56 | + |
| 57 | +**Note**: For reference, Lighting App commands given in the above image. |
| 58 | +Similarly other application commands also can be passed. - End-to-end command to |
| 59 | +be executed from chip-tool, refer |
| 60 | +[Running the Matter Demo](RUN_DEMO.md#demo-execution---commissioning-a-wi-fi-device-using-chip-tool-for-linux) - |
| 61 | +Below is the application specific attribute/s information or state shared to the |
| 62 | +cloud through Direct Internet Connectivity Solution - For Lighting App, On/Off |
| 63 | +Attributes - For Lock App, lock/unlock Attributes - For On/off Plug App, On/Off |
| 64 | +Attributes - For Windows App, lift/tilt Attributes - For Thermostat App, |
| 65 | +SystemMode/CurrentTemp/LocalTemperature/OccupiedCoolingSetpoint/OccupiedHeatingSetpoint |
| 66 | +Attributes - Application status would be updated on the mqtt_explorer UI, as |
| 67 | +shown in below image. |
| 68 | + |
| 69 | + |
| 70 | + |
| 71 | +- **Control of the device through cloud interface** |
| 72 | + - Below diagram gives end-to-end flow for Control of the matter device |
| 73 | + through cloud interface |
| 74 | +  |
| 75 | + |
| 76 | +**Note**: For reference, Lighting App commands given in the above image. |
| 77 | +Similarly other application commands also can be passed. |
| 78 | + |
| 79 | +- Make sure matter device is up and commissioned successfully, refer |
| 80 | + [Running the Matter Demo](RUN_DEMO.md#demo-execution---commissioning-a-wi-fi-device-using-chip-tool-for-linux) |
| 81 | +- For Controlling the device, set topic name and the commands to be executed |
| 82 | + in the mqtt_explorer for below applications. |
| 83 | + - Lighting App |
| 84 | + - Topic: command |
| 85 | + - Commands: |
| 86 | + - toggle |
| 87 | + - on |
| 88 | + - off |
| 89 | + - Onoff-plug App |
| 90 | + - Topic: command |
| 91 | + - Commands: |
| 92 | + - toggle |
| 93 | + - on |
| 94 | + - off |
| 95 | + - Lock App |
| 96 | + - Topic: command |
| 97 | + - Commands: |
| 98 | + - lock |
| 99 | + - unlock |
| 100 | + - Thermostat App |
| 101 | + - Topic: command |
| 102 | + - Commands: |
| 103 | + - SetMode/value(value need to provide 1,2,3,4 ex:SetMode/1) |
| 104 | + - Heating/value(value need to provide 2500,2600 |
| 105 | + ex:HeatingSetPoint/2500) |
| 106 | + - Cooling/value(value need to provide 2500,2600 |
| 107 | + ex:CoolingSetPoint/2500) |
| 108 | + - Window App |
| 109 | + - Topic: command |
| 110 | + - Commands: |
| 111 | + - Lift/value(value need to provide in range 1000 to 10000 ex: |
| 112 | + Lift/2500) |
| 113 | + - Tilt/value(value need to provide in range 1000 to 10000 ex: |
| 114 | + Tilt/2500) |
| 115 | +- Then click `publish` button to execute the command. |
| 116 | + |
| 117 | +  |
0 commit comments