Getting Started

Getting Started

What you need

• An original Awair Element
• A CMSIS-DAP probe, such as a Raspberry Pi Pico running picoprobe
• Access to the test points on the back of the EMW3165 module

The probe is required for the initial installation and low-level recovery. For a closer look at the device itself, see Hardware Architecture.

Connect the probe

Connect the probe to the test points on the opposite side of the EMW3165 module:

• TP80 / TP81: SWD, required for flashing and recovery
• TP103 / TP104: debug UART, optional

Verify the pin direction and voltage before powering the target. The core workflow does not require the debug UART.

Install a precompiled release

Version tags publish complete firmware bundles on the Releases page. A bundle contains the STM32 bootloader and application, the external-flash lookup table and BCM43362A2 WLAN firmware, the SRAM SPI-flash loader, SHA-256 checksums, and manifest.json.

The normal installation preserves DCT and saved configuration. The separate rewair-default-dct.bin recovery asset erases saved configuration and includes a build-generated MAC address. Never install one unchanged DCT image on multiple devices.

For a source build and the exact flash commands, continue to Building and Flashing.

First boot

If no Wi-Fi credentials are saved, Rewair starts an open setup network named rewair-setup-<xxxx>, where <xxxx> is derived from the final two bytes of the Wi-Fi MAC address. Join it and open http://192.168.0.1/. The captive portal should normally open automatically.

Select a network and save its credentials. Rewair stores the network and switches from access-point mode to station mode. Once joined, open the device's LAN address to use the same portal.

See Networking and MQTT for fallback behavior and Home Assistant setup.

Recovering a device

If an experimental flash no longer boots, use the scripts and instructions in tools/recovery to restore the stock F411 firmware. Low-level SPI-flash details are covered in SPI Flash and Recovery.