Smart Electric Motorcycle Development Guide

This topic describes how to develop smart electric motorcycle products (including electric mopeds) on the Tuya Developer Platform. It targets hardware, embedded, and app developers.

Smart electric motorcycles share most of their solution with smart electric vehicles. This topic follows the same eight-step workflow from feature definition to product release. It also describes key differences for electric motorcycles, including national-standard classification, license plates, the Bluetooth Low Energy (Bluetooth LE) + X hardware architecture, and dashboard-app interaction.

Before you start: confirm the electric two-wheeler category

In China, electric two-wheelers fall into three categories under GB 17761-2024 and the Safety Specifications for Electric Motorcycles and Electric Mopeds. Each category has its own compliance, registration, license, product category, and panel requirements. Confirm the category before development.

Category	Maximum speed	Vehicle type	Driver’s license	License plate
Electric bicycle	≤ 25 km/h	Non-motor vehicle	Not required	Yellow (small)
Electric moped	≤ 50 km/h	Motor vehicle	F license	Blue
Electric motorcycle	> 50 km/h	Motor vehicle	E or D license	Yellow (large)

To develop a model with a maximum speed above 25 km/h (electric moped or electric motorcycle), follow the workflow in this topic. The same workflow applies to electric bicycles capped at 25 km/h. For electric bicycles, pay attention to data points (DPs) for overspeed power cutoff and tamper-proof during feature definition.

Mandatory requirements

The following GB 17761-2024 requirements affect development most:

• Overspeed power cutoff: For an electric bicycle capped at 25 km/h, the motor must cut power when the vehicle exceeds the speed limit.
• Three tamper-proof components: The battery, controller, and speed limiter must use strict validation, so simple modifications cannot bypass the speed limit.
• Plastic part ratio: Plastic parts must not exceed 5.5% of the vehicle mass to reduce fire risk.
• China Compulsory Certification (CCC): New CCC certificates must be based on GB 17761-2024.
• Positioning and safety monitoring for commercial vehicles: Commercial vehicles should support BeiDou positioning, communication, and status monitoring. The Tuya Developer Platform provides these core capabilities.

Key timeline

• From September 1, 2025, new vehicles must comply with GB 17761-2024.
• From December 1, 2025, vehicles that fail to meet GB 17761-2024 cannot be sold.

Create a product

Prerequisites

• You have registered an account on the Tuya Developer Platform.
• (Recommended) Verify your organization’s identity to unlock more features.

Procedure

Open the Tuya Developer Platform and click Create on the home page. Under Standard Category, select Outdoor Travel > Travel > Smart Electric Vehicle.

After you create the product, the platform generates a product ID (PID). Use this PID for all embedded, app, and cloud debugging.

Feature definition (DP)

Tuya abstracts hardware capabilities into DPs. DPs fall into three categories:

Type	Defined by	Application scenarios	Example
Standard features	Tuya platform	Common capabilities	Lock, unlock, battery level, speed, and positioning
Custom features	Developer	Standard features are not enough	Custom battery management system (BMS) fields and exclusive riding mode
Advanced features	Platform-enabled	Cross-device and cloud services	QR code pairing, NFC card management, route records, and password management

DPs support only the following six data types: Boolean (Bool), Value, Enum, Fault/Bitmap, String, and Raw.

Common DPs for electric motorcycles (excerpt)

The following table reflects actual values from the Tuya standard DP templates for smart electric vehicles and electric motorcycles. Use it as a minimum viable DP set for a new product, and select the corresponding DP IDs during development.

DP ID	Feature	Identifier (ID)	Type	Read/write	Description
1	Anti-theft switch	blelock_switch	Bool	rw	Arm or disarm the Bluetooth anti-theft device.
2	Start	start	Bool	rw	Power on or start the vehicle.
3	Battery level	battery_percentage	Value	ro	Main battery level percentage, from 0 to 100.
4	GPS position	gps_position	String	ro	Latitude and longitude string. See the vehicle positioning protocol.
5	Speed	speed	Value	ro	Vehicle speed in km/h, from 0 to 250. Report it at 1 Hz or higher.
6	Ride time	ridetime_once	Value	ro	Total ride time in seconds since startup.
11	Unit setup	unit_set	Enum	rw	km or mile, shown on the dashboard and the app.
12	Total mileage	mileage_total	Value	ro	Total mileage in km. Accumulated and retained across power cycles.
13	Estimated range	endurance_mileage	Value	ro	Estimated range that the vehicle calculates from the current battery level.
14	Current ride mileage	mileage_once	Value	ro	Current ride mileage in km after startup.
18	Riding mode	level	Enum	rw	eco, normal, sport, and more. Electric motorcycles usually support three or more levels.
19	Find vehicle	search	Bool	rw	Trigger a beep or flash from the app to locate the vehicle.
24	GPS	gps_signal_strength	Value	ro	GPS signal strength level.
25	4G	4g_signal_strength	Value	ro	4G signal strength.
26	Fault detection	fault_detection	Bool	rw	Trigger a vehicle self-check from the app.
27	Status	status	Enum	ro	Vehicle state machine, such as standby, riding, charging, and fault.
29	Power system	power_system	Fault	ro	Fault Bitmap for the motor, controller, speed limiter, and more.
30	Smart system	smart_system	Fault	ro	Fault Bitmap for the central control, communication, positioning, and more.
31	Electronic system	electronic_system	Fault	ro	Fault Bitmap for the dashboard, lights, horn, and more.
32	Lithium battery system	lithium_battery_system	Fault	ro	Fault Bitmap for the battery and BMS.
45	Geofence	geofence_switch	Bool	rw	Geofence switch. It takes effect after you enable the advanced geofence feature on the platform.
58	Battery 1 information	battery_info	String	ro	Detailed main battery fields, such as voltage, temperature, and cycle count.
60	ICCID	iccid	String	ro	ICCID of the 4G SIM card. Used for positioning, billing, and SIM management integration.

Bitmap design example for Fault DPs

Split electric motorcycle faults into four fault DPs: power_system, smart_system, electronic_system, and lithium_battery_system. In each DP, define one fault source for each bit according to the vehicle fault list.

   power_system                      smart_system                  electronic_system              lithium_battery_system
bit0  Motor overheat              bit0  4G comm loss              bit0  Dashboard comm loss        bit0  Low battery
bit1  Motor Hall fault            bit1 Bluetooth LE comm loss     bit1  Dashboard light fault      bit1  Battery overheat
bit2  Controller overheat         bit2 GPS fix lost               bit2  Headlight fault            bit2  Battery under-voltage
bit3  Controller overcurrent      bit3 Cloud auth fail            bit3  Turn-light fault           bit3  Battery over-voltage
bit4  Speed limiter fault         bit4 OTA interrupted            bit4  Horn fault                 bit4  Cell imbalance alert
bit5  Power under-voltage         ...                             ...                              bit5  BMS comms fault
...                                                                                                ...

Recommendation: Always use a Fault DP with a Bitmap. Do not create a separate Bool DP for each fault. Splitting faults by subsystem makes app-side alerts easier to categorize and easier to extend later.

When to use custom DPs

Add a custom DP when the standard DP table does not cover a capability you need. For example:

• For raw cell voltages from a custom BMS, use a RAW DP and define the byte protocol.
• For an exclusive commute mode voice prompt switch, use a Bool DP named commute_voice_enable.

Advanced features (enable as needed)

Advanced features used often on electric motorcycles include:

• QR code pairing: Users scan the QR code on the vehicle with the app to bind the device, without entering the PID.
• NFC card management: Users can replace a physical key with an NFC card.
• Route records: The cloud stores ride routes, and the app replays them.
• Password management: Users can unlock the vehicle with a local four-to-six-digit password.
• Bluetooth keepalive: The vehicle unlocks when the phone is close and locks when the phone moves away.
• Direct-to-cloud connection: A 4G version connects to the cloud directly without a phone.

Configure the panel

Select a ride app

Smart electric vehicles and electric motorcycles must use Tuya’s dedicated ride apps, not the SmartLife app. Select the app by sales region:

Sales territory	Control app	App store keywords
Mainland China	涂鸦出行	涂鸦出行
Overseas	Tuya Ride	Tuya Ride

Electric vehicle all-in-one panel

涂鸦出行 and Tuya Ride include an electric vehicle all-in-one panel. Most electric motorcycle customers can use it out of the box without customization. The following image shows the all-in-one panel: a 3D vehicle model, battery level, range, speed, communication signals, one-tap lock, modes, unlock methods, lights, and sound shortcuts.

The all-in-one panel covers the following capabilities:

• Home: 3D vehicle status card with battery level, range, speed, 4G, GPS, and Bluetooth signals.
• Control: One-tap lock and unlock, mode switching, and find vehicle.
• Settings: Unlock methods, lights, sound effects, speed limit, anti-theft sensitivity, NFC card management, and password management.
• Services: Inspection report, route playback, and geofence.

Role split between phone and dashboard

Electric motorcycles ride at higher speeds, and checking a phone while riding is unsafe. Design smart electric motorcycles differently from electric bicycles:

• The dashboard is the primary surface during a ride: Show navigation turns, incoming calls, messages, and vehicle alerts on the dashboard.
• The phone covers non-riding scenarios: Support remote vehicle inspection, parameter configuration, route analysis, and alert push.

Example: When a rider receives a phone call, the dashboard shows the caller’s information. The rider answers or hangs up with a handlebar button, without taking out the phone. This is the standard interaction pattern for smart electric motorcycles, and is rare on electric bicycles.

The following image shows the role split in smart electric motorcycle automation between the dashboard and phone. During riding, the dashboard takes priority. The phone focuses on remote capabilities.

Design hardware

The following image shows the overall system architecture for a smart electric motorcycle. Solid lines show regular paths, and dotted lines show the 4G direct-to-cloud path.

Tuya offers two hardware integration paths for electric motorcycles. Choose one based on the compute capacity of your main controller and your cost target:

Solution	Microcontroller	Module	Best for	Difficulty
MCU SDK	Your MCU	Tuya Bluetooth or 4G module	The mainstream option, used most often	Low
TuyaOS	Module runs the business logic	TuyaOS-compatible module	Sufficient resources and cross-platform goals	Medium

Select a communication protocol

Scenario	Recommendation
Standard-configuration electric motorcycle, mainly controlled by phone	Bluetooth LE.
Commercial operation, fleet, or large model	Bluetooth + 4G dual mode.
Overseas or export model	Use Bluetooth first, and add 4G when required.

Bluetooth serves as the primary communication protocol for electric motorcycles because it:

• Consumes low power and does not affect vehicle standby current.
• Works with almost all phones without extra user cost.
• Supports passive unlock when you enable Tuya’s advanced Bluetooth keepalive capability.

Select a hardware form factor

By feature granularity and cost, electric motorcycle smart features come in three typical form factors. All three form factors use the Bluetooth LE + X hardware architecture, so you can upgrade smoothly.

Form factor	Communication capabilities	Typical features	Application scenarios	Installation
Bluetooth anti-theft device	Bluetooth LE only	One-tap start and stop, find vehicle, Bluetooth proximity unlock, and alarm on arming	Entry-level electric motorcycle and local control only (no remote features)	Standalone module with one power line
4G smart control unit	Bluetooth LE, 4G, and GPS	Remote positioning, remote control, seat lock, analog sensing, and control	Mid-to-high-end electric motorcycles, operations, and fleets	Standalone central control box that can work across models
4G dashboard	Integrated Bluetooth LE, 4G, and GPS	Dashboard display and all remote capabilities (the most integrated option)	Integrated vehicle design, BOM reduction	Built into the dashboard with no extra parts

Selection recommendation:

• Entry-level consumer model: Bluetooth anti-theft device.
• Operations, fleets, and high-end vehicles: 4G smart control unit.
• New custom model with a planned dashboard upgrade: 4G dashboard.

Bluetooth LE + X hardware architecture

The Bluetooth LE + X architecture uses the Bluetooth LE module as the system hub. The module connects to the vehicle MCU and the 4G Category 1 (CAT.1) module through UART. Bluetooth LE handles local control, low-power keepalive, and power management. 4G provides remote capabilities. The MCU runs vehicle business logic. Connect a standalone GPS module directly to the MCU through UART. The MCU parses NMEA data and reports it as needed.

                           ┌─────────────────┐
                  ┌──UART──┤ 4G CAT.1 module │── ✈ Cloud
                  │        └─────────────────┘
            ┌─────┴───────────────┐
            │ Bluetooth LE module │── 📱 Direct Bluetooth LE ── 涂鸦出行 / Tuya Ride app
            │ (BF6H-M)            │
            │ System hub          │
            │ + Power management. │
            └─────┬───────────────┘
                  │ UART
                  │
            ┌─────┴────────────┐         ┌───────────────────────┐
            │   MCU            │── UART──┤ Standalone GPS module │── Satellite
            │ Vehicle business │         │ GB600/610 and more    │
            └──────────────────┘         └───────────────────────┘

This wiring assigns GPS management to the MCU and provides the following benefits:

• Releases Bluetooth LE module I/O resources for communication.
• Gives the vehicle logic direct access to raw positioning data, which improves route filtering and geofence checks.
• Aligns GPS power-on sequence with the ignition and startup state machine.

Key pins of the Bluetooth module (BF6H-M)

Pin (silk screen)	I/O	Direction	Feature
TXD0 / RXD0	PD7 to PD6	OUT / IN	UART with 4G module.
TXD1 / RXD1	PA3 to PA2	OUT / IN	UART with MCU.
PWM1	PA7	IN	Cellular module wakes up Bluetooth (low level ≥ 60 ms)
PWM0	PA6	IN	Cellular module presence detection (active low, used across PCBs)
PWM5	PA5	OUT	Bluetooth controls 4G power (active high to power on)
PWM4	PA4	OUT	Power control for an optional peripheral (active high to power on); use as needed
PA1	PA1	OUT	Bluetooth wakes up the MCU (drive high ≥ 20 ms before sending data)
PA0	PA0	IN	MCU wakes up Bluetooth (drive high ≥ 50 ms before sending data)

Vehicle sleep and wake-up: Bluetooth LE acts as the system power manager. During standby, it disconnects power to the 4G module to save power. When a remote command arrives, the 4G module wakes Bluetooth LE through PWM1, and Bluetooth LE then wakes the MCU. The MCU manages GPS power according to the ignition and startup state machine.

Key handshake timing

• Cellular module wakes Bluetooth: Before sending UART data, the 4G module outputs a low level on PWM1 for at least 60 ms to make sure Bluetooth LE exits sleep.
• Bluetooth wakes MCU: Pull up PA1 for at least 20 ms before sending UART data. The MCU wakes through an I/O interrupt.
• MCU wakes Bluetooth: Pull up PA0 for at least 50 ms before sending UART data to prevent byte loss.
• Return to low after data transmission: After data transfer ends, pull the wake line low to enter low-power state. Adjust the duration through serial commands.

Level matching

The UART between the Bluetooth module at 3.3 V and the 4G module at 1.8 V must use level shifting to prevent port damage and unstable communication. Tuya recommends two solutions:

Solution	Component	Strength	Best for
Bidirectional level translator	TXS010X or SN74LVC series	Few components, strong anti-interference capability, and automatic bidirectional translation	Mass production
Discrete NPN inverter	S8050 with 10 KΩ and 1 KΩ pull-up resistors	Lowest cost	Minimal or low-cost design

Connect a standalone GPS module

Connect the standalone GPS module to the vehicle MCU through UART. The MCU parses NMEA messages and reports location, speed, satellite count, and other results as DPs. This wiring keeps the Bluetooth LE UART free, and the MCU controls the power-on sequence directly.

Recommended GPS module	Manufacturer	Frequency bands	Application scenarios
GB600	Tuya	L1 single frequency, five-system multimode: GPS, BDS, Galileo, QZSS, and GLONASS	Preferred for entry-level and low-cost mass production. Uses the Beken BK1661 SoC and offers a compact and low power design.
GB610	Tuya	L1 + L5 dual-frequency, multimode and multifrequency positioning, including BDS B2A/B2B/B2I and Galileo E5A	High-accuracy scenarios. Uses Beken BK1662 SoC, supports 120 tracking channels, cold start time of about 28 seconds, and tracking sensitivity of -165 dBm.

You can find complete datasheets and sample code for both modules in Tuya Developer Platform > GNSS Module. For a new design with no special requirements, choose GB600 first. Choose GB610 for accuracy-sensitive cases, such as fleet deployments or dense urban canyon scenarios.

Wiring notes:

• MCU UART to GPS UART: Default baud rate 9,600 or 115,200, set per vendor configuration. RX and TX lines are sufficient. You can connect the PPS signal to an MCU interrupt pin for time synchronization.
• Power supply: GPS modules usually use a 3.3 V power supply. The MCU controls the switch through a GPIO or an LDO enable pin, and powers off GPS during vehicle sleep.
• Antenna: Electric motorcycles have many plastic parts and a metal tank that block signals. Place the antenna on top of the dashboard cover or near the rear handle. Avoid shielded areas and reserve a GND reflection area.
• Level: The MCU and GPS module usually use 3.3 V, so no level shifting is required. For a 1.8 V GPS module, see Level matching.

Tuya recommended modules

Tuya has verified the following modules in electric motorcycle scenarios. You can search all datasheets and SDK documents in the Tuya Developer Platform.

4G modules (by sales region)

Model	Sales territory	Frequency bands	Size	Resource link
L511C-Y6E	China	LTE FDD B1/3/5/8, TDD B34/38/39/40/41	17.7×15.8×2.3 mm	Datasheet MCU SDK
L511E-Y6E	Europe, Southeast Asia, Africa, Australia, Middle East, Hong Kong, Macau, and Taiwan	LTE FDD B1/3/5/7/8/20/28, TDD B38/40/41	Same as above	Same as the L511 series
L511A	North America	LTE FDD B2/4/5/12/13/14*/66/71	Same as above	Same as the L511 series
MG661-LA-19	Latin America	LTE FDD B2/3/4/5/7/8/28/66	N/A	N/A

Bluetooth module

Model	Sales territory	Frequency bands	Size	Resource link
BF6H-M	Global	2.4 GHz ISM band	19×15.5×2.5 mm	Datasheet MCU SDK

Pick the 4G module by sales region and use BF6H-M for Bluetooth. Other 4G modules (NL668-AM, MC665-EU, MA510-GL, and more) are integrated and remain available for existing inventory or special customer requests. For new designs, choose the L511 series first.

Embedded development

MCU SDK path (recommended)

Workflow:

Your MCU                    Tuya Bluetooth module                  Phone app / Cloud
┌────────────────┐ UART   ┌───────────────────────┐ Bluetooth LE/4G  ┌──────────────┐
│  Vehicle logic │<-----> │ Tuya standard protocol│<---------------> │ Tuya Ride    │
│  + MCU SDK     │  TX/RX │(Universal)            │                  │  + Tuya cloud│
└────────────────┘        └───────────────────────┘                  └──────────────┘

The MCU SDK helps you implement:

• Frame encapsulation and parsing. You only handle DP sending and receiving, not serial bytes.
• Heartbeat, state machine, and reconnection.
• OTA reception and verification.
• Time synchronization and pairing state machine.

You only need to implement two callbacks:

• dp_download_handle(): Handle control DPs sent from the app, such as locking the vehicle.
• dp_report(): Report current status DPs, such as speed and battery level.

TuyaOS path

The module runs the TuyaOS kernel. The vehicle host MCU completes integration through a simple communication interface. The benefit is that one business codebase runs across different chip platforms and protocols (Bluetooth and cellular). Select a module that supports TuyaOS.

Use TuyaOS when:

• One vehicle model needs both a Bluetooth version and a Bluetooth + 4G version.
• The vehicle MCU is short on resources, and you want the module to run the business logic.
• You want to use TuyaOS components directly, such as OTA, KV storage, and RPC.

Embedded development rules

• DP report frequency: Report high-rate DPs (speed, location) at 1 Hz or higher. Report low-rate DPs (battery level, mileage) on change. Avoid unnecessary data traffic.
• OTA slicing: Electric motorcycle firmware often reaches 1 MB or larger. Bluetooth OTA must support resumable download. For major 4G OTA updates, push them during charging to avoid consuming user data.
• Fault reporting: Report faults with Fault DPs and Bitmaps. Do not report 100 independent Bool DPs.
• Power loss protection: Write cumulative values, such as mileage and ride records, to flash memory so power loss does not erase them.
• GB 17761-2024 compliance: Expose DPs for speed limiting, overspeed power cutoff, and the status of the three tamper-proof components for easier audits.

Configure product

Go to Product Configuration on the Tuya Developer Platform. Select and configure the following items as needed:

Item	Focus for electric motorcycles
Firmware update	Support both Bluetooth and 4G. For major versions, push them during charging by default to save user data.
Multilingual support	Required: Chinese and English are the baseline. For overseas, add Spanish, Portuguese, Vietnamese, and Indonesian.
Pairing information	Select Bluetooth pairing. 4G versions do not need pairing.
Device information push	Send anti-theft alerts, low battery alerts, overspeed alerts, and geofence breach alerts through push channels.
Scene linkage	Electric motorcycles use this less often. You can leave it disabled at the start.
Shortcut switches	Add frequent actions, such as one-tap lock and find vehicle, to the app homepage.
Product manual	Use the electronic manual on the platform to reduce printing cost.

Pairing example (Bluetooth)

Electric motorcycles do not use Wi-Fi, so the only pairing channel is Bluetooth. Tuya recommends the following two Bluetooth pairing methods. Select one or use both based on production process and target users:

Solution	Trigger method	User operation	Application scenarios
A: Bluetooth-triggered pairing	The user performs a physical action on the vehicle, such as pressing and holding the anti-theft button for five seconds or turning the ignition on three times. The vehicle enters a discoverable broadcast state.	The Add Device page and other app pages discover the vehicle automatically.	Entry-level model, anti-theft device form factor, and no extra printing on the production line.
B: Bluetooth QR code pairing	A unique QR code (with PID, MAC, and a one-time binding token) is pre-printed on the vehicle or its package.	Tap Scan in the app to bind in one step.	Mid-to-high-end vehicles, 4G dashboard or smart control unit, smooth out-of-box experience.

Solution comparison

Dimension	A: Bluetooth-triggered pairing	B: Bluetooth QR code pairing
User experience	Average. Users read the manual to learn the trigger.	Smooth. Scan to bind, near zero learning cost.
Mispairing prevention	Weak. Several nearby vehicles broadcast the same name, and the user picks one.	Strong. The QR code carries a unique MAC and token, with one-to-one binding.
Production process	Simple. No need to generate or print a unique code.	Complex. The line generates, prints, and applies a QR code per vehicle.
After-sales code replacement	N/A	Users need customer service or a fallback flow after QR code loss.
Platform dependency	Standard Bluetooth pairing, supported by all Bluetooth devices by default.	Requires the QR code pairing advanced feature in product configuration.
Recommended group	Entry-level electric motorcycle or Bluetooth anti-theft device	4G smart control unit or 4G dashboard vehicles

Recommendation: For high-end models or complete vehicle shipments, use solution B first. Keep solution A as a fallback for QR code loss or damage.

Push examples

Trigger	Push content
Vibration above the threshold while the vehicle is still	"Your vehicle Scooter-26B detected abnormal vibration."
Battery at or below 20%	"Battery is low. Charge soon."
Outside the geofence	"Your vehicle has left the home area."
OTA complete	"New firmware is ready. Restart the vehicle to apply."

Flash firmware and authorize module

Flash the firmware and the license to the device, or the device cannot connect to the cloud.

For the complete solution, flashing tool downloads, pin wiring for different modules such as Bluetooth and 4G, and production test processes, see Flashing and Authorization.

Three official Tuya solutions

Tuya classifies flashing and authorization into three solution types based on chip type and production system:

Official solution	Best for	Description
Flashing and authorization combined	Tuya standard module	Ship after Tuya burns the firmware. Or use the Tuya Cloud Module Burning Authorization tool yourself.
Flashing and authorization separated	Debug stage or non-Tuya standard modules	Authorize only. Burn the firmware with the chip vendor’s tool.
Production test integration	A complete in-house production system	Connect to your production line through the Tuya standard interface and run burning and authorization in-house.

For solution selection and the production test interface specification, see Flashing and Authorization.

Mass production for electric motorcycles

Mass production for electric motorcycles uses one of four common methods by scale. Each maps to an official solution above:

Method	Best for	Official solution	Description
Online flashing	Sample stage	Flashing and authorization combined	Device connects directly to Tuya cloud for authorization.
Offline flashing	Factory mass production	Flashing and authorization combined	Send the authorization package in advance.
End-of-line authorization	One-time write during end-of-line vehicle testing	Separate flashing and authorization, or production test integration	Recommended. Merge into the end-of-line station workflow.
MCU self-flashing	MCU executes the authorization process independently	Production test integration	MCU SDK solution only.

Production recommendations

• Use one license per PID. Do not reuse codes.
• Add "power-on and power-off test + Bluetooth connection test" to the end-of-line test items to prevent missed flashing.
• Different modules, such as Bluetooth and 4G, use different flashing pins, writers, and drivers. See the corresponding sections in Flashing and Authorization.

Test the product

Before release, prepare a test report through one of the following methods:

• Self-test: Download test cases from Testing Service, run the tests, and upload the report.
• Tuya Cloud Test app: Run test cases directly with the cloud test app.
• Tuya test service: Pay the Tuya test team to run tests for you.

Pay extra attention to the following electric motorcycle test items:

• Bluetooth stability at high and low to medium speeds, including bumps and distance from the phone.
• DP state recovery after a 4G outage.
• Battery DP reporting accuracy at extreme temperatures.
• Recovery after power loss during OTA.
• GB 17761-2024 compliance, including DP and alert flows after speed limit power cutoff and tamper prevention triggers.

Release and certify the product

Release

After the test report passes, release the product on the Tuya Developer Platform. After release, use the PID for mass production authorization.

Required certifications

Certification	Mainland China	Overseas (typical)
Vehicle	CCC (GB 17761-2024)	E-mark, European Economic Community (EEC), and Department of Transportation (DOT)
Bluetooth module	State Radio Regulation of China (SRRC)	Federal Communications Commission (FCC), Conformite Europeenne Radio Equipment Directive (CE-RED), Korea Certification (KC), and Telecom Engineering Center (TELEC)
4G module	China Type Approval (CTA) + SRRC	FCC, CE-RED, and Global Certification Forum (GCF)
Battery	GB 31241	UN38.3 and IEC 62133

Appendix: Differences between electric motorcycles and electric bicycles

Dimension	Electric bicycle	Electric motorcycle
Speed limit	25 km/h or lower (forced power-cut)	50 km/h or unlimited
Main controller compute	Standard	Mid to high, supports a dashboard SoC
Dashboard	Mostly segment LCD	Thin-film transistor (TFT) color screen, supports interaction
Rider attention	Low speed allows phone use	High speed forbids phone reliance
Pairing protocol	Bluetooth	Bluetooth first, 4G optional
Tamper-proof	Three components (mandatory)	Vehicle level
Typical DP count	30 to 50	50 to 100
Price range	CNY1,500 to CNY5,000	CNY8,000 to CNY50,000
Smart feature potential	Limited	High, including navigation, advanced driver assistance systems (ADAS), calls, and screen mirroring

FAQ

How many PIDs do I need for both electric bicycle and electric motorcycle models?

At least two. Electric bicycles and electric motorcycles differ greatly in DPs, panel layout, and GB 17761-2024 compliance. Mixing them under one PID raises maintenance and management costs sharply.

Which hardware form factor should I choose for my electric motorcycle (Bluetooth anti-theft, 4G smart control unit, 4G dashboard)?

• Consumer entry-level, cost-sensitive, near-field control and anti-theft only: Bluetooth anti-theft device.
• Operations or fleet, with remote location and remote control: 4G smart control unit (the standalone central control box can be reused across models).
• New vehicle in design with a dashboard upgrade: 4G dashboard (the most integrated, no extra parts).

All three form factors use the same Bluetooth LE + X architecture and support smooth upgrades. For more information, see Select a hardware form factor and Bluetooth LE + X hardware architecture.

Do I need to add a voice assistant to my electric motorcycle?

Build the dashboard display and handlebar button interactions first. Wind noise and helmets reduce recognition accuracy during riding. Voice works as an enhancement, not a required feature.

Which app should I use for overseas vehicles?

Use Tuya Ride for overseas sales. Use 涂鸦出行 for the Chinese mainland. Both apps provide the same panel capabilities. Select the app by sales region. For overseas development, focus on multilingual support, regional compliance such as General Data Protection Regulation (GDPR) and California Consumer Privacy Act (CCPA), and 4G band adaptation.