USB-C RF Receiver for Wireless Temperature/Humidity Sensors
A USB-C plug-in receiver that listens for inexpensive wireless remote temperature and humidity sensor transmissions and forwards the readings to a PC.
Intermediate Project
— This is an intermediate project because it combines USB device firmware with sub-1 GHz RF reception and likely protocol decoding, which requires careful RF layout, timing capture, and host-side data handling.
Assumptions:
- The remote sensors are common low-cost sub-1 GHz devices, likely using simple OOK/FSK or a proprietary protocol rather than WiFi/BLE.
- The device is a prototype dongle that will enumerate as a USB serial device or similar on the PC, so no separate display or storage is required.
- The user wants a practical build using readily available parts from major distributors, not a custom RF front end from scratch.
Bill of Materials
Compatibility Notes
- The ESP32-S3-DEVKITC-1 is a 3.3 V SPI device, so it pairs naturally with 3.3 V MCUs like ESP32-S3-DEVKITC-1 or STM32F072CBT6.
- If you use a dev board powered from USB-C, confirm it exposes a stable 3.3 V rail with enough current for the RF module and any external antenna front end.
- The RF module and MCU should share a common ground and short SPI traces; RF performance will suffer if the module is placed too close to the USB connector or noisy switching regulators.
- If the target sensors use 433 MHz or 868/915 MHz, the antenna and regional band choice must match the sensor protocol.
You'll Also Need
- A suitable antenna for the chosen sub-1 GHz band.
- USB-C cable and enclosure.
- Level shifting only if you choose a 5 V-only board, which is not recommended here.
- Firmware to decode the specific sensor protocol and format the data for the PC.
- Optional RF front-end passives such as matching network components, decoupling capacitors, and ESD protection.
Estimated BOM Cost: $15-35 (based on live distributor pricing)
Design Considerations
Protocol Uncertainty
The biggest risk is that the inexpensive sensors may use a proprietary OOK/FSK protocol rather than a standard one. Start with a flexible receiver like ESP32-S3-DEVKITC-1 and capture raw timing first, then decode the packet format in firmware. If the sensors turn out to be 433 MHz fixed-format devices, you can often get a working prototype quickly without needing a full protocol stack.
USB-C Simplicity
For a prototype, do not overcomplicate the USB-C side unless you need more than default 5 V power. A USB-powered MCU board is usually enough, and it avoids USB-PD negotiation bugs that can delay bring-up. If you later move to a custom PCB, then a controller like STUSB4500QTR becomes more relevant.
RF Layout and Antenna
ESP32-S3-DEVKITC-1 GHz reception is very sensitive to antenna placement and ground return quality. Keep the antenna away from the USB connector, MCU clock traces, and any switching regulators, and use the antenna recommended for the sensor band. Even a good receiver IC will perform poorly if the antenna is detuned by the enclosure or nearby copper.
Firmware Architecture
Use an interrupt-driven or DMA-assisted SPI receive path and a small state machine for packet capture, validation, and USB reporting. Add a watchdog and a timeout-based resync path because cheap remotes often transmit infrequently and with variable preambles. Logging raw RSSI and packet timing during development will make protocol reverse engineering much easier.
Power and Noise
USB bus power is convenient, but the PC's 5 V rail can be noisy. Use local decoupling near the RF module and keep the 3.3 V rail clean, especially if the dev board uses a switching regulator. If you see missed packets, check for supply ripple and ground bounce before assuming the RF protocol is the issue.
Validation Strategy
Test first with the sensor very close to the antenna, then move it through walls and at increasing distance to characterize link margin. Record raw captures from multiple sensor transmissions to confirm whether the device sends repeated frames, rolling IDs, or checksum fields. This will tell you whether the receiver is robust enough for real-world use or only works in ideal lab conditions.
Want to customize this project or build something different?
Try the Project Advisor


