This sample demonstrates how to connect to Golioth and observe a LightDB path for changes.
- Golioth credentials
- Network connectivity
Configure the following Kconfig options based on your Golioth credentials:
- GOLIOTH_SYSTEM_CLIENT_PSK_ID - PSK ID of registered device
- GOLIOTH_SYSTEM_CLIENT_PSK - PSK of registered device
by adding these lines to configuration file (e.g. prj.conf
):
CONFIG_GOLIOTH_SYSTEM_CLIENT_PSK_ID="my-psk-id"
CONFIG_GOLIOTH_SYSTEM_CLIENT_PSK="my-psk"
This application has been built and tested with QEMU x86 (qemu_x86).
On your Linux host computer, open a terminal window, locate the source code
of this sample application (i.e., samples/lightdb/observe
) and type:
$ west build -b qemu_x86 samples/lightdb/observe
$ west build -t run
See Networking with QEMU on how to setup networking on host and configure NAT/masquerading to access Internet.
Configure the following Kconfig options based on your WiFi AP credentials:
- GOLIOTH_SAMPLE_WIFI_SSID - WiFi SSID
- GOLIOTH_SAMPLE_WIFI_PSK - WiFi PSK
by adding these lines to configuration file (e.g. prj.conf
or
board/esp32.conf
):
CONFIG_GOLIOTH_SAMPLE_WIFI_SSID="my-wifi"
CONFIG_GOLIOTH_SAMPLE_WIFI_PSK="my-psk"
On your host computer open a terminal window, locate the source code of this
sample application (i.e., samples/lightdb/observe
) and type:
$ west build -b esp32 samples/lightdb/observe
$ west flash
See ESP32 for details on how to use ESP32 board.
This subsection documents using nRF52840 DK running Zephyr with offloaded ESP-AT WiFi driver and ESP32-WROOM-32 module based board (such as ESP32 DevkitC rev. 4) running WiFi stack. See AT Binary Lists for links to ESP-AT binaries and details on how to flash ESP-AT image on ESP chip. Flash ESP chip with following command:
esptool.py write_flash --verify 0x0 PATH_TO_ESP_AT/factory/factory_WROOM-32.bin
Connect nRF52840 DK and ESP32-DevKitC V4 (or other ESP32-WROOM-32 based board) using wires:
nRF52840 DK | ESP32-WROOM-32 |
P1.01 (RX) | IO17 (TX) |
P1.02 (TX) | IO16 (RX) |
P1.03 (CTS) | IO14 (RTS) |
P1.04 (RTS) | IO15 (CTS) |
P1.05 | EN |
GND | GND |
Configure the following Kconfig options based on your WiFi AP credentials:
- GOLIOTH_SAMPLE_WIFI_SSID - WiFi SSID
- GOLIOTH_SAMPLE_WIFI_PSK - WiFi PSK
by adding these lines to configuration file (e.g. prj.conf
or
board/nrf52840dk_nrf52840.conf
):
CONFIG_GOLIOTH_SAMPLE_WIFI_SSID="my-wifi"
CONFIG_GOLIOTH_SAMPLE_WIFI_PSK="my-psk"
On your host computer open a terminal window, locate the source code of this
sample application (i.e., samples/lightdb/observe
) and type:
$ west build -b nrf52840dk_nrf52840 samples/lightdb/observe
$ west flash
On your host computer open a terminal window, locate the source code of this
sample application (i.e., samples/ligthdb/observe
) and type:
$ west build -b nrf9160dk_nrf9160_ns samples/lightdb/observe
$ west flash
This is the output from the serial console:
[00:00:00.000,000] <inf> golioth_system: Initializing
[00:00:00.000,000] <inf> net_config: Initializing network
[00:00:00.000,000] <inf> net_config: IPv4 address: 192.0.2.1
[00:00:00.000,000] <dbg> golioth_lightdb: main: Start LightDB observe sample
[00:00:00.000,000] <inf> golioth_system: Starting connect
[00:00:00.030,000] <inf> golioth_system: Client connected!
[00:00:00.030,000] <inf> golioth_lightdb: Counter
35 |5
[00:00:04.370,000] <inf> golioth_lightdb: Counter
31 30 |10
[00:00:06.120,000] <inf> golioth_lightdb: Counter
31 31 |11
[00:00:07.620,000] <inf> golioth_lightdb: Counter
31 32 |12
The device retrieves the value stored at /counter
in LightDB and then
retrieves it every time that it's updated. The value can be updates as such:
goliothctl lightdb set <device-name> /counter -b 5
goliothctl lightdb set <device-name> /counter -b 10
goliothctl lightdb set <device-name> /counter -b 11
goliothctl lightdb set <device-name> /counter -b 12