Phase 1 (B500 + Tuya SDK) validates the product concept. Phase 2 proves the cloud-free path is viable — a custom BLE device triggering an SOS event in the phone app without routing through Tuya Cloud. This removes the PRC jurisdiction, account termination risk, and GDPR Chinese data routing issues identified in the legal review.
Two workstreams run in parallel so neither waits on the other. Both feed the same decision at the end: which hardware path goes to launch.
Hardware: KKM B500 (sent by Aaron)
Stack: Tuya IoT App SDK — Development Edition, registered May 2026
Proves: Full Tuya flow — BLE → Tuya Cloud → app → SOS action. Does the SDK integration work? Is latency acceptable?
Hardware: Seeed Studio XIAO ESP32S3 Sense (~£11)
Stack: Espressif ESP-IDF + phone BLE library. No Tuya SDK. No cloud.
Proves: Direct BLE → phone → SOS without any cloud in the middle. Aaron owns the full stack. Removes every legal flag from the Tuya compliance review.
Amazon UK → · Seeed Studio direct (Germany warehouse)
| Dimensions | 21 × 17.8mm — postage stamp footprint |
| Chip | ESP32-S3 dual-core Xtensa LX7 at 240MHz |
| BLE | Bluetooth 5.0 / Bluetooth Mesh |
| Deep sleep | 14–34 μA — months on a coin cell in sleep |
| Battery | Built-in LiPo charge management (3.7V) |
| Microphone | Built-in digital mic — no external hardware needed for voiceprint |
| AI / NN | Hardware neural network acceleration — runs ESP-Skainet keyword spotting on-device |
| Price | $13.90 / ~£11 · 10+ units: $12.70 each |
| TuyaOpen | Supported (ESP32-S3 board definition in repo) — can run either TuyaOpen or native ESP-IDF |
| Full BOM | + 500mAh LiPo (~£4) + tactile button (~£1) + LED = ~£16 total prototype cost |
The device is a BLE Peripheral — normally in deep sleep, wakes on button interrupt, broadcasts a custom advertisement packet (device ID + event type), then sleeps again. No Wi-Fi, no cloud, no Tuya SDK on the device. The phone is the internet gateway. BLE libraries are mature on both Flutter (flutter_blue_plus) and React Native (react-native-ble-plx).
The XIAO ESP32S3 Sense has a built-in microphone and hardware neural network acceleration. This directly supports the silent keyword trigger Aaron described — and does it in a way that eliminates the Tuya biometric consent requirements entirely.
Why it's cleaner than Tuya's voiceprint: ESP-Skainet runs the keyword detection model on the device itself. The voiceprint never leaves the hardware — no upload to any cloud, no biometric data in transit, no consent flow complexity. GDPR position is simple: the data never exists as a record anywhere.
What to test in Phase 2:
Won't be production-ready in Phase 2, but will confirm whether the feature is viable at this hardware cost point before committing to custom PCB design.
| Test | Pass condition |
|---|---|
| BLE trigger → phone | SOS event received within 3 seconds of button hold completing |
| Battery life | Device runs >30 days on 500mAh LiPo in normal sleep/wake pattern |
| Accidental trigger rejection | Single press (<2s) does not trigger SOS — meets Tuya Compliance §I.4 standard |
| Range | BLE maintained at 10m through one internal wall |
| Keyword detection (stretch) | >85% detection rate in quiet room, <5% false positive rate |
| Track A comparison | Both flows documented — latency, reliability, UX differences noted |
| Item | Source | Price | Delivery |
|---|---|---|---|
| XIAO ESP32S3 Sense | Amazon UK · Seeed Studio (Germany warehouse) | ~£11–14 | 1–5 days |
| 500mAh LiPo battery | Pimoroni / Amazon UK | ~£4 | 1–2 days |
| Tactile button assortment | Amazon UK | ~£3 | 1–2 days |
| Breadboard + jumper wires | Amazon UK / already have | ~£3 | 1–2 days |
| Total | ~£21 |
Also: chase Aaron on B500 dispatch for Track A. Both likely arrive on similar timelines — run in parallel rather than sequentially.
ESP32-S3 (with mic) or ESP32-C3 (cheaper, no mic) PCB design. Espressif-ecosystem ODM factories — well-trodden path. Target unit cost £3–6 at 1,000+ units. No Tuya dependency. No GDPR exposure from hardware layer.
Fall back to Track A (Tuya SDK) for commercial launch with documented migration plan. Phase 1 legal mitigations still apply — GDPR opinion, account termination contingency, voiceprint consent flow.