Rawmesh

Rawmesh

The IoT mesh for student devices and live labs.

Secure HTTPS endpoints on iot.r4xn.com — stream sensors, drive relays, and watch state update in real time.

Connect a device See the flow

Rawmesh is the cloud side of your board.

Built by R4XN for polytechnic projects, campus labs, and small device fleets that need a clean path from GPIO to the browser.

Every team gets a username directory on iot.r4xn.com. Firmware posts over TLS. Dashboards read the same state. No local IP juggling once the device is online.

Transport HTTPS
Device method POST
Auth API key
Host iot.r4xn.com

What the mesh gives you.

One host, many project paths — sensors in, commands out, status always current.

Sensor ingest

ESP32 posts LDR and other ADC readings on a short loop. Rawmesh stores the value, marks the device online, and can return actuator commands in the same response.

Actuator control

Lamp, fan, and relay states live in the database. Toggle from the dashboard; the next device poll applies the change on the pins.

Live dashboard

Login-protected UI shows light/dark status, online heartbeat, and ON/OFF controls without exposing the API key in the browser.

Isolated project paths

Each username is its own folder — API, config, and dashboard — so class projects stay separated on the same cloud.

From board to cloud in four steps.

Claim a path, flash firmware, post readings, control from the browser.

01

Claim a project path

Your workspace sits at a dedicated directory. Example: adamjohan maps to its own API and dashboard.

https://iot.r4xn.com/<username>/
02

Flash with the secure base URL

Point SERVER_BASE at your path. Use WiFiClientSecure and send the API key on every request.

https://iot.r4xn.com/adamjohan
03

POST sensor data

ESP32 sends LDR readings and heartbeats. The cloud stores state and can return lamp / fan commands in JSON.

POST /api/sensor.php
04

Control from the dashboard

Toggle outputs in the browser. The next device poll applies the new state over HTTPS.

POST /api/control.php

Your path on the mesh.

Everything for a project lives under one username directory.

Project root https://iot.r4xn.com/<username>/
Login / dashboard /login.php · /dashboard.php
Device ingest /api/sensor.php · /api/get_status.php
Browser control /api/control.php · /api/status.php

API surface.

Device routes require POST, HTTPS, and a valid API key. Dashboard routes use a login session.

POST

/api/sensor.php

ESP32 uploads api_key + ldr_value. Returns lamp, fan, and light/dark status.

POST

/api/get_status.php

ESP32 polls desired actuator state and refreshes the online heartbeat.

POST

/api/control.php

Logged-in user sets device (lamp|fan) and value (0|1).

GET

/api/status.php

Dashboard live poll for lamp, fan, LDR, and ESP online state.

Built for labs that ship.

Rawmesh keeps classroom IoT practical — one host, clear paths, secure posts.

Polytechnic students

Finish ESP32 coursework with a real cloud endpoint instead of fragile LAN demos.

Lecturers & lab techs

Give each student a username folder. Review dashboards without touching device firmware mid-class.

Prototype teams

Stand up sensor + relay demos fast, then keep the same HTTPS contract when you scale pins.

Point firmware at Rawmesh.

Use WiFiClientSecure, POST form fields, and send the API key on every request to your project path.

Talk to R4XN Read the API 
const char* SERVER_BASE =
  "https://iot.r4xn.com/adamjohan";

const char* API_KEY =
  "your-project-key";

// POST /api/sensor.php
// api_key + ldr_value → lamp, fan

// POST /api/get_status.php
// api_key → apply GPIO from DB

Quick answers.

Common questions when wiring the first board.

Why HTTPS only?

Device APIs reject plain HTTP outside localhost. Keys and sensor payloads stay on TLS between ESP32 and iot.r4xn.com.

Where does my project live?

Under https://iot.r4xn.com/<username>/. That folder holds the PHP API, dashboard, and config for your device.

What boards work?

Anything that can POST over TLS — ESP32 is the reference stack with WiFiClientSecure + HTTPClient.

How do I get a path?

Contact R4XN for a Rawmesh username directory and API key, then flash your sketch with the secure base URL.

Ready to join the mesh?

Deploy your project folder, set WiFi in firmware, and start posting.

Start connecting r4xn.com