RuView

Multi-purpose View the repo

RuView is a WiFi‑based sensing platform that captures Channel State Information from low‑cost ESP32 nodes to detect presence, occupancy, breathing, heart rate, activity, and camera‑free 17‑keypoint pose through walls, and exposes this data to major smart‑home ecosystems via MQTT and Matter. It runs entirely on edge hardware (ESP32 mesh with optional Cognitum Seed) and includes a suite of modular AI‑driven analytics and automation tools.

auto-summary

104720 stars · 13577 forksGitHub repo · as of 2026-11-21 11:07 UTC

Maintainer
ruvnet
License
MIT
Capabilities
wifi
Chip families
esp32-c5esp32-c6esp32-s3

Boards with a recipe, by trust tier

Unverified

  • ESP32-C6-DevKitC-1UnverifiedEspressif
    Flash ESP32-C6-DevKitC-1guidedread the caveat

    Unverified esp-atlas asserts this board↔firmware link at the shown trust tier — it does not guarantee your specific unit or the current firmware version. Flashing can erase keys/config and can brick the device. At your own risk.

    Caveat: The firmware's C6 support is first-party and well cited: `sdkconfig.defaults.esp32c6` sets `CONFIG_IDF_TARGET="esp32c6"` with `CONFIG_ESPTOOLPY_FLASHSIZE="4MB"`, the `v0.8.8-esp32` release ships `esp32-csi-node-v0.8.8-c6-4mb-flash-bundle.zip` ("Fresh ESP32-C6 installation using the supported 4 MB layout"), and the README calls the C6 its research target. What is NOT cited upstream is this exact board. RuView's root README hardware table lists its "ESP32-C6 research node" against a generic "ESP32-C6-DevKit ($6-10)", and its transport test notes say only "Two ESP32-C6 boards" — no model number anywhere. That generic name is ambiguous between the two C6 devkits this atlas catalogues, `esp32-c6-devkitc-1` and `esp32-c6-devkitm-1`; the DevKitC-1 is the fuller reference board and the likelier reading, but picking it is our inference, which is why the recipe stays `unverified`. Note also that this board record carries 8 MB of flash while RuView ships only a 4 MB C6 layout; the 4 MB bundle boots on an 8 MB part, it simply does not use the extra flash. No `flash` block is declared: the bundle is a four-file install (bootloader 0x0, partition-table 0x8000, otadata 0xf000, app 0x20000) and the bare `.bin` asset is the application image alone.

  • ESP32-S3-DevKitC-1UnverifiedEspressif
    Flash ESP32-S3-DevKitC-1guidedread the caveat

    Unverified esp-atlas asserts this board↔firmware link at the shown trust tier — it does not guarantee your specific unit or the current firmware version. Flashing can erase keys/config and can brick the device. At your own risk.

    Caveat: RuView's own README names this board twice: "Recommended boards | ESP32-S3-DevKitC-1, XIAO ESP32-S3", and a dedicated build note for "Display-less boards (ESP32-S3-DevKitC-1 and similar)" telling you to build with the `sdkconfig.defaults.devkitc` overlay, because the default build compiles display support in and its runtime panel probe false-positives on a board with no panel — which disables the MGMT+DATA CSI upgrade and collapses CSI yield to 0 pps. This board record carries 4 MB of flash, so the matching prebuilt package is `esp32-csi-node-v0.8.8-s3-4mb-flash-bundle.zip`; the `s3-8mb` bundle is for 8 MB S3 boards. No `flash` block is declared on purpose: the bundle is a four-file install (bootloader 0x0, partition-table 0x8000, otadata 0xf000, app 0x20000) and the bare `esp32-csi-node-v0.8.8-s3-4mb.bin` asset is the application image only, so it cannot be flashed at 0x0 as a single merged binary and must not be offered as a one-click in-browser flash. `unverified`: not yet run on real hardware here.