This is a simple mqtt demo, that connects to WiFi AP first. This application has a dependency to esp_wifi_remote, so that if it's build and executed on a chipset without WiFI capabilities it redirects all wifi calls the remote target.
When running this example on a target that doesn't natively support WiFi, please make sure that the remote target (slave application) is connected to your chipset via the configured transport interface.
Connection to the slave device also depends on RPC library used. It is recommended to use esp_hosted. Alternatively you can use eppp_link.
Please note, that esp_hosted as a component is currently WIP, so the wifi_remote defaults to eppp, for now.
We currently support only UART transport, so the connection is very simple. You only need to connect Rx, Tx and GND with the remote target.
You need to configure these fields according to your connection:
The RPC mechanism between the host and the slave micro uses TLS with mutual authentication, so you would have to configure certificates and keys for both parties. This application -- host target -- is considered RPC client, so it needs client's certificate and key, as well as the CA certificate to validate the server (slave application). If self-signed certificates are acceptable, you can use generate_test_certs script to generate both the CA and the keys itself and convert them to the PEM format that's accepted by the EPPP RPC engine. You will have to configure these options:
You need to set up the connection and configuration in a similar way on the slave part (connection pins + certificates and keys). Please refer to the slave_application README for more information.
To create a project from this example, run:
idf.py create-project-from-example "espressif/esp_wifi_remote=0.8.2:mqtt"