From Device to Cloud: The OTA Firmware Update Architecture of an AI Toy Module

2026-08-20 4 min read Nablai Technical Team

Illustration

One of the biggest differences between an AI toy and a conventional toy is that it keeps growing after it is sold. The technical name for that ability is OTA (over-the-air) update. This article takes the architecture apart: how firmware on an AI toy module travels safely from the device all the way up to the cloud.

The modules we build, and the dual-stack architecture

Nablai (Shenzhen Nablai Intelligent Technology Co., Ltd.) is an AI company whose main product is the AI module for smart toys. Built on three host platforms - Tuya T5E, Espressif ESP32S3 and PY32 - Nablai ships three AI toy module families, TY, LX and NT, on a dual-track module-plus-app model.

One architectural fact has to be cleared up first:Both TY002 (Tuya T5E) and LX002 (Espressif ESP32S3) run a dual-stack architecture: a local SDK plus a cloud API. The two are architecturally the same kind of thing; they differ only in which ecosystem they belong to and who holds brand sovereignty. This is emphatically not a side-by-side of TY equals cloud-only and LX equals local-only. NanoToy (PY32) is the genuine pure-UART command module: no AI, no cloud, no SDK and no support for remote updates.

  • TY002: on the device, TuyaOS handles device logic, networking, local interaction and the "Hello Tuya" wake word; in the cloud, Tuya IoT Cloud handles AI conversation, multiple languages, global data centers and OTA. App and accounts live inside the Tuya ecosystem and work out of the box, with brand sovereignty held by Tuya.
  • LX002: on the device, ESP-IDF handles local command parsing, camera preprocessing and a custom wake word; in the cloud, the Nablai private cloud handles AI conversation and the delivery of emotion expressions. The app, WeChat Mini Program, admin console, account system and dedicated LLM are all customizable as a package, so brand sovereignty stays intact.

How OTA responsibilities split across the two stacks

Table

The device side is responsible for a safe landing, the cloud side for smart scheduling, and the two coordinate through a shared version protocol.

The local layer: an update must never fail halfway

The local SDK has four hard jobs:

  1. Download and verification: firmware packages carry a signature, and if local verification fails the device simply will not flash.
  2. Resume from the breakpoint: a flaky network can pick up where it left off instead of starting over.
  3. Power-loss protection: writes use dual A/B partitions, so if power is lost mid-update the device boots from the old partition next time.
  4. Automatic rollback: two consecutive failed boots and it switches back to the previous stable version on its own.

LX002 also looks at battery state: below 20% charge it will not force an update, so the unit cannot be bricked by power dying mid-update. The protection logic that cuts charging above 45°C shares the same hardware monitoring as update safety.

The cloud layer: updates have to be smart

The cloud API is responsible for pushing the right version to the right devices at the right time:

  • Version management: every model keeps three states, stable, gray release and rollback.
  • Staged rollout: a new package goes to 5% of devices first, and only ramps up if the metrics look healthy.
  • Targeted delivery: devices can be selected by region, production batch or sales channel.

OTA for TY002 is orchestrated by Tuya IoT Cloud, so a toy company pushes from the Tuya console; OTA for LX002 is orchestrated by the Nablai private cloud together with the AMS vendor management platform, where the customer defines the version cadence and the rollout ratio and can even package under their own brand. That is what intact sovereignty means in engineering terms.

Differential updates and the experience

Update packages are differential: only what changed is transferred, which saves data and is faster. Progress sounds and expressions run through the whole update, so the user can feel it happening. We once helped a plush toy client push out a Goodnight Story Season pack, an English Practice pack and a Lunar New Year greeting expression set over OTA in the three months after launch, and the e-commerce reviews kept coming back to the same point: the toy still gets updates. That is the real differentiation OTA delivers.

Selection advice

If you are evaluating an AI toy module, treat OTA as a hard requirement: check whether it is dual-stack, whether it supports signing and rollback, whether it supports staged rollout, and whether you can set your own version cadence. Choose TY002 if you need to get overseas quickly; LX002 if you need brand sovereignty and deep customization; NanoToy (PY32) if you just want a low-cost way to test the water.

Our engineering practice

Internally we hold to a few hard rules for OTA: every package we push must be signed, and if local verification fails the device will not flash; update packages are differential and transfer only what changed; progress sounds and expressions run through the whole update; and two consecutive failures lock the device and report to the AMS console. Factory firmware is also covered by our 99%+ yield quality control, which cuts the odds of ever needing to fight fires in the first place.

FAQ

Q: Are OTA and cloud versus local the same question? A: No. TY002 and LX002 are both dual-stack; the difference lies in ecosystem ownership and brand sovereignty.

Q: Can NanoToy do OTA? A: No. It is a pure-UART command module with no remote update capability.

Q: Who steps in when an update fails? A: The device locks itself and reports to the console, and our technical team takes it from there.

About Nablai

Nablai is an AI company, and AI smart toys are the application area we focus on today. Our product is the AI smart toy module, and our goal is to give toy companies a product-level solution for bringing AI into their toys.

We have built three product families:

  • TY Series: built on Tuya T5E, 60+ languages, the fast lane into global markets
  • LX Series: built on Espressif ESP32S3, full brand ownership, deep customization
  • NT Series: built on PY32, a low-cost way to test the smart toy market
  • Website: https://www.nablai.com.cn
  • Phone: 15917703502
  • Slogan: Driven by gradients, optimized by intelligence. Powered by Nabla, Optimized by AI.

Shenzhen Nablai Intelligent Technology Co., Ltd. — AI module specialists for smart toys

📧 contact@nablai.com.cn    🌐 www.nablai.com.cn