Why will my Bluetooth remote not pair with SmartLife?

SmartLife is Tuya's app and it only adopts hardware the manufacturer built as a Tuya device. It is not a general Bluetooth tool. If your remote, bed, desk or light strip was not made as a Tuya product, there is nothing to pair, and no setting or firmware on your side changes that.

What is a Tuya local key?

It is the encryption key a Tuya device uses to accept commands without going through the cloud. You need it, plus the device id, to talk to a Tuya device directly. It is issued when the device is provisioned to an account, and the documented ways of retrieving it all go through a Tuya IoT developer project and their cloud API.

Is the Tuya local key the same for every device of the same model?

No. It is unique to each physical unit. Two identical light strips bought together have different keys. TinyTuya's own documentation also states that the local key changes every time a device is removed and re-added to the app, and resets if the device is reset or re-paired.

Can Tuya Bluetooth devices be controlled locally without the cloud?

Yes, once you have the device id and local key. Several open source Home Assistant integrations drive Tuya BLE devices entirely over Bluetooth with no cloud contact at runtime. The unavoidable part is getting the key in the first place, which needs a Tuya IoT developer account.

What controls Bluetooth devices without an account?

Devices that speak ordinary Bluetooth GATT with no vendor key can be driven directly from a phone or a browser. Adjustable beds, recliners and lift chairs, standing desks, and many LED strip controllers fall into this group. READYWARE talks to them straight over Bluetooth with no account, no hub and no bridge.

SmartLife, Tuya and the Local Key — Why Your Bluetooth Remote Will Not Pair

Q: Can someone share their local key so it works for everyone?

No. Because the key belongs to one physical unit and resets when that unit is re-paired, a shared key is useless to anyone else and stops working for its owner the moment they re-pair. This is the opposite of infrared and radio remotes, where one capture solves every remote built on that chip, permanently.

The short version

SmartLife is Tuya's app. It only adopts hardware the manufacturer built as a Tuya device. It is not a general Bluetooth tool.
If your remote is not a Tuya product, there is nothing to pair. No setting on your side changes that.
Tuya Bluetooth gear can run fully local once you have its device id and local key. Several open source projects do exactly that.
Getting that key needs a Tuya developer account. There is no published way to pull it off the air or out of the device.
The key belongs to one physical unit and resets when that unit is re-paired. Nobody can share one that works for you.
Plenty of Bluetooth gear needs none of this and can be driven straight from a phone or a browser.

What SmartLife actually is

SmartLife is the consumer app for Tuya, a platform manufacturers build on top of. A company that wants a connected product can ship Tuya's module and firmware instead of writing their own app and cloud. That is why hundreds of unrelated brands all tell you to download the same two apps.

The important consequence: a device appears in SmartLife only if its maker built it as a Tuya device. The app is not scanning for Bluetooth things and adopting them. It is signing in to an account and listing hardware that already belongs to that ecosystem.

So if your Bluetooth remote will not pair with SmartLife, it is almost certainly not faulty and you have not missed a step. It was never a Tuya device. There is nothing on your side to fix.

What a local key is, and why it matters

Normally a Tuya device takes orders from Tuya's cloud. Your phone talks to the cloud, the cloud talks to the device. That is the part people dislike: an internet round trip to turn on a light in the same room, and a product that stops working the day the service does.

Tuya devices can also be driven directly, with no cloud in the loop. To do that you need two things from the device:

What	What it is
device id	Tuya's internal identifier for that one unit
local key	The encryption key that unit will accept commands under

With those in hand, the cloud is no longer needed. Several open source projects prove it, and say so plainly in their own documentation.

Project	What it demonstrates
ha-tuya-ble	"never contacts the Tuya cloud at runtime"; account credentials "used once and never stored"
Tuya-BLE	"No cloud round-trip for commands once the device credentials are obtained"
ha_tuya_ble	Same family of work, Bluetooth devices driven locally

So the protocol itself is not the obstacle. It is understood, it is implemented, and it works offline.

The catch, stated honestly

Every documented way of getting the local key goes through Tuya's cloud. The usual route is to create a Tuya IoT developer project, generate an access id and access key, and query their API with the official SDK. That is what tuya-local-key-extractor does, and it is what TinyTuya does.

We went looking specifically for a way around it: reading the key out of the pairing exchange, capturing it off the air, pulling it from the phone app. If a method exists, it is not public.

Worth being clear about what that means. The gear can be freed from the cloud, but only by asking the cloud for permission once, through a developer account most owners will never create. The device is local-capable and still gated.

Why a shared key would not help you

This is the question we get asked most, and the answer is the interesting part.

The local key is unique to one physical unit. Two identical light strips bought in the same packet have different keys. Worse, TinyTuya's own documentation states that the key changes every time a device is removed and re-added to the app, and resets if the unit is reset or re-paired.

So a key someone posts online is worth nothing to anybody else, and stops working for its owner the moment they re-pair. There is nothing to collect and nothing to build on.

That is the exact opposite of how infrared and radio remotes work, and it is worth understanding the difference:

	IR & RF remotes	Tuya Bluetooth
One capture covers	Every remote built on that chip	One physical unit
Still valid tomorrow	Yes, permanently	Until it is re-paired
Can be shared	Yes, that is the whole point	No
Needs an account	No	Yes, once, a developer one

A ceiling fan remote captured once by one person in 2026 will still open that entire family of fans for everybody in 2036. A Tuya key is a rental that expires when its owner touches the app.

What works with no account at all

Plenty of Bluetooth hardware speaks ordinary GATT with no vendor key, no pairing to a cloud and no bridge. Your phone connects to the device and sends the command. That is it.

Things that generally work this way:

Adjustable beds, recliners and lift chairsThe motor controller inside is usually one of a handful of makes, whatever the badge on the headboard says.
Standing and sit-stand desksHeight presets and memory positions, straight over Bluetooth.
Many LED strip controllersThe cheap generic ones in particular.
Relays, switches, blinds and shadesWhere the maker did not build a cloud into them.

READYWARE talks to these directly: no account, no hub, no bridge, nothing to sign up for. Over 75 Bluetooth device families across more than 200 brands, and it runs in a browser as well as in the app. If the controller inside your bed is one it knows, it builds you the remote and you use it.

On top of that, infrared and radio are where this approach really pays, because those signals belong to nobody. Over 40 fixed-code radio families covering garage and gate openers, ceiling fans, blinds, outlets and doorbells, and an infrared database in the millions of codes. None of it asks who you are.

If you have already done the developer-account dance and you are holding device ids and local keys for Home Assistant, tell us. If enough people are in that position we would look at a paste-your-own-key path. We are not going to pretend it is a feature for everybody, because it is not.

Questions people actually ask

My light is in SmartLife but I want it off the cloud. Can I?

Usually yes, with the device id and local key, using one of the open source projects linked above. Expect to create a Tuya IoT developer project to get them. It is a genuine amount of work for one light, and much more reasonable if you are doing a whole house at once.

Is there any way to get the key without a developer account?

Nothing published that we could find. We looked for a way to read it from the pairing exchange, capture it off the air, or extract it from the phone app, and came up empty. If that changes we will update this page.

Why does my device need the internet to talk to something in the same room?

Because the manufacturer chose a platform where the account is the product. It is cheaper to ship than building your own app, and it keeps the customer attached. The hardware is almost always capable of working locally; the firmware simply is not set up to let it.

Will my Tuya device keep working if the service goes away?

Scenes, schedules and remote access would stop. Whether anything local survives depends entirely on the product. This is the usual reason people go looking for local keys in the first place, and it is a fair reason.

Can READYWARE control my Tuya Bluetooth device?

Not today, and we are not going to claim otherwise. The honest reason is on this page: it would be the only thing in the app that requires a developer account, and the key would stop working the next time you re-paired the device. If that changes at Tuya's end, or enough people turn up already holding keys, we will revisit it.

What about Tuya infrared blasters?

Different situation, and a better one. Infrared codes are just timings, so they convert cleanly. Our Signal Editor reads and writes Tuya IR alongside Pronto, Flipper, LIRC, Global Caché, BroadLink, ESPHome and more, and you can move a whole remote between formats in one go.

Free, no sign-up, runs in your browser

Nothing here needs an account. Open it and use it.

🛠️ Signal Editor Read, convert and repair IR & RF codes in the browser. Pronto, Flipper .ir/.sub, LIRC, Global Caché, BroadLink, Tuya IR, ESPHome, Home Assistant SmartIR and more. Build a working remote from your brand with the wizards, including a Bluetooth builder that needs no account. 🚚 Signal Transporter Move a whole remote between formats and hardware without hand-editing a single hex blob. 🎛️ Online Remote Builder Lay out a remote in your browser, then load it onto your phone, tablet or TV. 📱 The READYWARE app Android, iOS and Android TV. IR, RF, WiFi, network, Bluetooth and smart home on one canvas.

▶ Play Store 🍎 App Store 🛠️ Open the Signal Editor

SmartLife, Tuya and the local key