Smart Home

Tuya Universal— RTI XP Driver

Control your Tuya and Smart Life Wi-Fi devices from RTI, directly over your own network.

Version
v2.1.0
Updated
Aug 20, 2026
Licensing
Per-processor

About this driver

Two-way RTI control for Tuya and Smart Life Wi-Fi devices: plugs, switches, multi-gang power strips, bulbs and LED strips, fans, and IR/RF blasters. If your Smart Life app already controls something through a blaster, the driver can learn that code again and send it from an RTI button. The driver talks straight to each device over your own network. Once it is set up it makes no calls to Tuya at all, so there is no account allowance to run out, nothing that expires, and nothing to keep an eye on. It keeps working with the internet down. Setup is one click: paste your Tuya Access ID and Secret into Integration Designer, click Import from Tuya Account, and the driver fills in every device's name, ID, key and type for you. You never look up a device key by hand. It then finds each device's address on your network by itself, and keeps following a device if your router later gives it a different one. Up to 24 devices on a single driver instance. Add more instances for more devices, all covered by one license.

What's included

  • Direct control over your own network. After setup the driver makes no calls to Tuya, so nothing expires and nothing needs monitoring. It works with your internet down.
  • One-click setup. Import from Tuya Account fills in every device's name, ID, local key and type from your Tuya account, so you never hunt for a device key by hand.
  • Finds your devices on the network and keeps up with them. No IP address to type in, and a device that moves to a new address is followed instead of going offline.
  • Tells you when a device has been re-paired. Re-pairing a device in the Smart Life app changes its key, which is the most common reason one stops responding. The driver recognizes exactly that, and one click picks up the new key.
  • Plugs, switches, multi-gang power strips, bulbs and LED strips, fans, and raw data-point access for anything else.
  • Anything your blaster already controls, controlled from RTI. If the Smart Life app can work a device through your IR or RF blaster, the driver can learn that code again and send it locally, from an RTI button: TVs, air conditioners, fans, roller shutters, gates. Codes are learned and stored in the driver, 50 slots for them.
  • Speaks all three Tuya local protocols (3.3, 3.4 and 3.5) and works out which one each device uses on its own.
  • Up to 24 devices per instance, unlimited instances, one license per processor covers them all.
  • 120-minute trial locked to your processor, so you can prove it on your own system first.

What you should know before buying

  • Wi-Fi, mains-powered devices only. Zigbee, Bluetooth and battery devices have no network address of their own and cannot be reached over the LAN by anything, this driver included.
  • Devices that sit inside a hub, and the virtual remotes inside an IR/RF blaster, have no key of their own, so they cannot be addressed directly. Blaster remotes still work, sent through the blaster itself.
  • A rolling-code RF handset cannot be learned. Tuya's RF learning handles fixed-code remotes only, and that is the blaster's limit, not the driver's. The simple test: if your Smart Life app already works the device through the blaster, it is fixed-code, and our driver can learn it too.
  • Setup needs a free Tuya developer account once, to read your device keys. That is a one-time step done on your computer in Integration Designer. The running driver never contacts Tuya.
  • One instance per processor runs LAN discovery. The processor hands the discovery port to whichever instance claims it first, so a second instance works normally, it just needs its device addresses typed in.
  • Adding a second instance is a memory question, and the memory belongs to your processor, not to us. On our bench one instance driving 24 devices peaked at 5.6 MB, and a second instance costs about the same again. Devices on Tuya protocol 3.5 cost roughly twice a 3.4 device, and their firmware decides which one they speak. Whether your processor has room depends on the processor and on every other driver already installed on it, so do not assume it does. If you want an answer before you buy, ask us and we will give you the figures we have measured.
  • Local encryption is done by the processor itself. How much processor time that costs depends on how many devices you run and which protocol they use. If you are planning a large system, ask us and we will measure your combination on our bench.

How licensing works

  1. Download the driver (free — button on the right), install it in Integration Designer, and load to your processor. It runs unlocked for 120 minutes per session for compatibility testing.
  2. Buy a license here, then sign in and enter your processor's MAC address on your account page. We issue a signed license key bound to that MAC.
  3. Paste the key into the driver's configuration. The trial wall goes away and the driver runs unlocked indefinitely.
Need a custom driver? Suggest one or email [email protected].