How to Place a First Smart Lock Order Without Wasting a Quarter
The sequence that turns a first order into a repeat programme.
Read the article →Integrators place more orders than any other buyer group we serve. What ends the relationship is almost never the hardware. It is a lock that does not behave the way the ecosystem promised, discovered in front of a customer.
There are two ecosystems on our smart locks: Tuya and TTLock. Both open the lock actively from the phone. The choice decides the app, the gateway and how much control the end user gets.
Swipe the table sideways to see the full specification →
| Tuya | Wider consumer recognition and a large device ecosystem |
|---|---|
| TTLock | Finer access-control features such as timed e-keys and access history |
| Both | Open actively from the phone |
| Mixing them | Not possible on one gateway; a Tuya gateway does not manage a TTLock lock |
This is the version check that matters most. Tuya Bluetooth and TTLock open actively from the phone. The older Tuya Wi-Fi generation is request-based, where the lock is pressed first and the app confirms.
It belongs on the quotation as a written line, not as an assumption from a model name. If the app is the reason the end user chose the product, this is the specification that decides whether it works.
Swipe the table sideways to see the full specification →
| What it is | A development project, not a product option |
|---|---|
| What we can do | Confirm what the platform supports, in writing |
| What we cannot do | Promise an app or an integration the platform does not allow |
| Who to involve | Engineer to engineer, so the question reaches the platform |
A gateway is ecosystem specific. One gateway normally manages several locks in range, and the count depends on the layout rather than on the lock count. It belongs in the quotation rather than in the commissioning phase.
Test the sample in your own environment before demonstrating it, then record what you tested. An update that changes behaviour should not be discovered at a customer site.
Swipe the table sideways to see the full specification →
| Firmware version | Read from the app, written down, kept with the sample |
|---|---|
| App version | Version number and platform |
| Gateway model | The exact gateway the validation used |
| Configuration | Any setting that changed the behaviour |
The most expensive mistake in this buyer group is buying the request-based version by accident. It is prevented by one written line on the quotation.
Three questions this guide usually raises.
On this topic
Tuya has wider consumer recognition; TTLock has finer access-control features such as timed e-keys and access history. Both open actively from the phone.
White-label apps exist in both ecosystems under commercial terms we do not control, so we confirm what the platform allows rather than promise an app.
No. One gateway normally manages several locks in range. The count follows the layout and belongs in the quotation.
The sequence that turns a first order into a repeat programme.
Read the article →Five photos and three numbers are usually enough to confirm the fit.
Read the article →The packaging is the part buyers underestimate, and the part that cannot be changed once it is printed.
Read the article →