Error Codes

Last Updated on : 2025-09-17 03:01:31Copy for LLMView as MarkdownDownload PDF

This topic describes error codes related to robot vacuum services.

Tuya Tied Things (TTT) plugin

Error code	Definition	Remark
6	`userId` is empty `albumName` is empty `filePath` is empty	Parameter format is incorrect.
20001	`DeviceId` is invalid	Parameter format is incorrect.
20021	`IThingP2P` is null	Cannot find service.
70001	P2P connection in progress	-
70002	P2P connection failed	-
70003	P2P is not connected	-
70101	Other files are being uploaded	-
70102	File upload cancellation failed	uploadFile invoke failed.
70110	On querying file	-
70111	File query failed	-
70112	Other files are being downloaded	-
70113	File download failed	-
70114	File download cancellation failed	-

RN plugin

Error code	Description
-9000	The data of `deviceBean` is missing.
-9001	The required P2P SDK is not integrated.
-9002	The P2P connection is being created.
-9003	The specified device is offline.
-9005	No map files are found.
-9006	The P2P connection is closed.

File transfer

Error code	Definition	Remark
-1	A common error has occurred.	-
-10002	The session is invalid.	An expired session or invalid session ID is used.
-10003	Timeout.	The P2P connection timed out, or the device did not respond.
-10004	The connection is canceled.	-
-10006	The device is offline.	-
-10008	A device exception has occurred.	-
-20001	The command is invalid.	An exception has occurred during the function call, such as downloading without a P2P connection.
-20002	The parameter is invalid.	-
-20006	This app version does not support the specified device.	Update the app.
-30060	An error is returned by the device.	-
-30061	An error has occurred while transferring the file.	-
-30062	The file does not exist.	-
-30063	Failed to create a file.	Check whether the path exists or whether you have permission to write the file.
-30064	Too many files to download.	The number of files to download exceeds 40 or is 0.
-30065	The name of the file being uploaded is too long.	-

P2P connection

Error code	Description
-1	Not initialized.
-3	A timeout has occurred.
-4	The ID is invalid.
-5	The parameter is invalid.
-11	The session is invalid.
-12	The session is closed by the peer end.
-13	The session has been closed.
-14	The session is closed by the device.
-16	The listener is interrupted.
-19	The connection is interrupted.
-23	The maximum number of sessions has been reached.
-24	The preconnection is invalid.
-25	The preconnection is closed.
-26	The preconnection is activated.
-29	The system has run out of memory.
-30	The HTTP API request failed.
-31	The preconnection is not supported.
-32	DTLS handshake failed due to fingerprint verification failure.
-33	Token acquisition timed out (App ATOP API failed, or the system time of TUTK or Shangyun device/app has been changed).
-34	WebRTC verification failed.
-35	Failed to initialize Mbed TLS.
-36	Heartbeat timeout occurred.
-37	DTLS handshake failed.
-38	DTLS handshake timed out.
-39	The peer did not respond, which might be due to pre-link pending or activation.
-40	Pre-link reservation timed out.
-41	The P2P library is reset.
-42	Failed to initialize the timer.
-43	Failed to initialize the SDP.
-44	Failed to add media in SDP.
-45	Failed to add codec in SDP.
-46	Failed to initialize the channel.
-47	The AES key is invalid.
-48	Failed to set the AES key in SDP.
-49	The token is invalid.
-50	Answer reception timed out.
-51	Local network exception occurred, possibly because no local address was collected.
-52	Local network exception occurred.
-53	Peer network exception occurred.
-54	TCP relay service did not respond, potentially due to verification failure or incorrect device ID.
-55	The token has expired.
-56	The token is invalid due to device ID mismatch.
-57	Failed to verify the token.
-58	The MQTT message sending failed.
-100	The peer end is closed, but the reason for the closure is not explained.
-102	The listener for sessions is triggered. However, the device runs in privacy mode, so the requested session is closed.
-103	Failed to create a data sending thread. The requested session is closed.
-104	The maximum number of sessions has been reached. The requested session is closed.
-105	The authentication failed. The requested session is closed.
-106	The session has been closed as expected.
-108	No data communication occurs in a period of more than 20 minutes. The session is closed forcibly.
-109	You have called the open API to manually close a session, for example, during a firmware over-the-air (OTA) update.
-110	You have called the open API to exit the P2P module.
-111	You have called the open API to make the device run in privacy mode.
-113	The device is processing a call.
-114	Failed to request application resources.
-115	The device is in a restricted streaming state.
-300	WebRTC session exited.

Prev DocChangelog

Next DocSample Code