BETA — Open to testers. Tell us what to fix on @vomehome or via a tester code.

Local keys for LEDVANCE, SYLVANIA and other brands

Devices that show up on your network but not in your Tuya account are usually Tuya hardware sold under another brand. Here is how to reach them.

Updated 16 August 2026 tuyaledvancelocal-control


If a device appears on your network as a Tuya device but your Smart Life account has never heard of it, the usual explanation is that it is Tuya hardware sold under another brand. It pairs only in that brand's own app, which is a white-label build of Tuya's app with its own account system.

The device is fine. Your account is fine. They simply live in different places.

Why the obvious fixes do not work

Re-pairing it to Smart Life. Some brands have moved off the Tuya platform entirely — LEDVANCE among them — so their devices refuse to pair with the standard Tuya apps at all. This is not a pairing technique you have yet to discover.

Sharing the device to your Smart Life account. Tuya's white-label apps are separate data containers. A share link from the LEDVANCE app can only reach another LEDVANCE account.

What does work

Those apps talk to an older Tuya API that returns local keys for an email and password:

tuya-local-bridge vendor ledvance --email you@example.com

It asks for your password for that brand's app, uses it once, and never stores it. You get every device on that account with its local key:

7 devices on the LEDVANCE SMART+ account

name                         device id                local key            online
gold light 1                 bf1ca00f…               wK9…mZZ              yes
gold light 2                 bfb11c43…               O$3…d9J              yes
...

Then fold those keys into the normal reconciliation:

tuya-local-bridge status --include-stored

Devices that were unexplained should now be ready to convert. From there, follow Move Tuya devices to local control as usual.

Currently supported: LEDVANCE SMART+ (ledvance) and SYLVANIA Smart (sylvania). Other brands need their app's credentials adding — tell us which brand and we will look.

Once it works

You can stop using the brand's app day to day, along with anything you were chaining through it. The devices run on your network and answer to Home Assistant directly.

You cannot uninstall it for good, though. Pairing a replacement bulb, or factory-resetting an existing one, still goes through that app — and a reset rotates the local key, which will silently break the tuya-local entry. tuya-local-bridge heal finds and repairs that.

When it goes wrong

USER_PASSWD_WRONG. The protocol is working and the credentials are not. Check you are using the brand's app account, not your Tuya or Home Assistant login.

No devices listed, but the login succeeded. The account may be registered in another region. Try --region us (or cn, in), and set --country-code to your dialling code.

A device is listed but never appears on the network. It is offline or out of range. Keys stay valid, so convert it whenever it comes back.

Rather not do this alone?
The Vome assistant will walk you through this guide a step at a time, and can do some of it for you.
Sign in for AI help

Something wrong or missing here? Tell us — these pages are written from real work, so corrections are welcome.