How ritabrata777/aura works
This is an ESP32 health-monitoring device and web platform. Sensors collect vitals and ECG; firmware sends readings over MQTT, the API validates and routes them to account-specific storage, and dashboards receive live updates or request history. Provisioning and pairing associate devices with patient or individual-user accounts, while the clinical platform also supports doctor relationships, prescriptions, and video consultations. The README documents the system flow; unsampled implementation links are omitted where their callers are not established.
Main entry points: api.ts API client · esp32-health-device.c Firmware application · mqtt.ingestion.service.ts MQTT ingestion · app Health dashboards
Components 22
Device firmware
- Vital sensors
main/max30102.c - ECG capture
main/ecg_ad8232.c - Wi-Fi manager
main/wifi_manager.c - Device messaging
main/device_comm.c - Firmware application
main/esp32-health-device.c
API platform
- MQTT ingestion
web-platform/apps/api/src/mqtt/mqtt.ingestion.service.ts - Accounts and auth
web-platform/apps/api/src/auth/auth.service.ts - Device provisioning
web-platform/apps/api/src/devices - Measurements
web-platform/apps/api/src/measurements - Doctor relationships
web-platform/apps/api/src/doctors/doctors.service.ts - Prescriptions
web-platform/apps/api/src/prescriptions - Video consultations
web-platform/apps/api/src/video - AI companion
web-platform/apps/api/src/ai/ai.service.ts - Wellness accounts
web-platform/apps/api/src/individual-users/individual-users.service.ts - Live updates
web-platform/apps/api/src/websocket
Web experience
- Health dashboards
web-platform/apps/web/app - API client
web-platform/apps/web/lib/api.ts - Live client
web-platform/apps/web/lib/live.ts
Data and messaging
- PostgreSQL
- MQTT broker
- Shared protocol
web-platform/packages/protocol/src/index.ts
Other components
- Patient or user
Connections 25
- Patient or user → Health dashboards: uses
- Health dashboards → API client: requests
- API client → Accounts and auth: authenticates
- API client → Device provisioning: provisions and pairs
- API client → Measurements: fetches history
- API client → Doctor relationships: manages care
- API client → Prescriptions: manages prescriptions
- API client → Video consultations: requests tokens
- API client → AI companion: sends chat
- Health dashboards → Live client: receives updates
- Live client → Live updates: connects by Socket.IO
- Firmware application → Vital sensors: reads sensors
- Firmware application → ECG capture: captures ECG
- Firmware application → Wi-Fi manager: connects network
- Firmware application → Device messaging: sends device messages
- Device messaging → MQTT broker: publishes and subscribes
- MQTT broker → MQTT ingestion: delivers device traffic
- MQTT ingestion → Shared protocol: validates payloads
web-platform/apps/api/src/mqtt/mqtt.ingestion.service.ts - MQTT ingestion → PostgreSQL: persists readings
- MQTT ingestion → Live updates: broadcasts events
web-platform/apps/api/src/mqtt/mqtt.ingestion.service.ts - Device provisioning → PostgreSQL: stores device records
web-platform/apps/api/src/devices/devices.service.ts - Accounts and auth → PostgreSQL: stores account data
web-platform/apps/api/src/auth/auth.service.ts - Doctor relationships → PostgreSQL: stores relationships
web-platform/apps/api/src/doctors/doctors.service.ts - Wellness accounts → PostgreSQL: stores wellness data
web-platform/apps/api/src/individual-users/individual-users.service.ts - Patient or user → Firmware application: is monitored