A smart lock gateway installation requirement is the set of electrical, network, radio, mechanical, environmental, account-provisioning, security, and

Đăng lúc: Th10 19, 2026

Smart Lock Gateway Installation Requirements

Smart Lock Gateway Installation Requirements

A smart lock gateway installation requirement is the set of electrical, network, radio, mechanical, environmental, account-provisioning, security, and acceptance-test clauses that a site has to satisfy before a gateway is allowed to relay lock traffic between the catalog's documented app platforms — TTLock / Tuya / Doodle (or a hotel PC software stack) — and the operator console. The requirement set is per-model: the catalog this site sells from carries 79 published models across 10 categories, and the gateway question for each of those models is check the model’s published specification. The requirements below read like an annotated datasheet: every line an installer is asked to sign against is dissected, and every figure that varies per model is routed to an open specification item the buyer fills in from the verified product page.

This article is the install-side companion to the lifecycle guide in Smart Lock Gateway Guide. Where that article organised the program into five stages — pre-survey → pilot placement → expansion → refresh → decommission — this one organises the physical and contractual clauses a buyer must resolve before a single gateway is mounted. For the upstream question of whether the site even needs always-on connectivity, see Smart Lock Offline vs Online; for the access-point analogy the supplier will inevitably lean on, Smart Lock Access Point Planning covers the planning lens and Smart Lock Network Requirements covers the network-architecture lens.

How to read this datasheet

The supplier's gateway-install checklist, whether it appears in a quotation, a project plan or a one-pager handed over at a sales meeting, is built from eight requirement families. The buyer has to read it line by line, in the order failures actually occur, because the typical install failure is downstream of a clause the buyer never read closely. The eight families, in failure order, are:

  1. Power — what reaches the wall outlet the gateway will live at.
  2. Uplink — what reaches the network port or Wi-Fi the gateway will terminate on.
  3. Radio coverage — what reaches the air between gateway and lock.
  4. Mechanical and environment — what the gateway is mounted to and what surrounds it.
  5. Capacity and concurrency — how many locks per gateway the catalog supports.
  6. Account and credential provisioning — who onboards the gateway and the lock it speaks to.
  7. Security and access controls — what the gateway will and will not expose.
  8. Acceptance testing — the clause the buyer signs against on day-one go-live.

Each family below gets a table whose rows are the requirements, columns are the constraints on that requirement, and blank cells are populated by check the model’s published specification for the chosen SKU. The first table (T1) is the umbrella matrix. Tables T2 through T8 are the per-family worksheets the reader copies into a project file.

Umbrella requirement matrix (T1)

The matrix below is the shape of the buyer's first-pass install-package review. Every row is a requirement. Every column is a constraint the buyer has to evaluate. The matrix is intentionally scannable as a one-page summary; the worksheet tables in the next sections show each family at the granularity a real RFQ review needs.

#Requirement familyWhat the supplier line usually saysWhat the line actually means (annotated)Common bluff to push back onValue to confirm
R1Power"Standard mains outlet"Whether mains, PoE or USB; what voltage tolerance; whether the gateway has a battery fallback; whether the cabinet shares a circuit with other loads"Standard outlet" with no mention of UPS, voltage tolerance, or shared-circuit behaviourCheck the model’s published specification — mains / PoE / USB; voltage tolerance; battery fallback
R2Uplink"Connects to your network"Whether Ethernet (RJ45), Wi-Fi as uplink, or both; whether DHCP or static; whether specific ports / DNS / NTP need to be opened; whether the gateway phones home across public internet or a regional cloud"Connects to your network" with no protocol, no port, no DNS list, no cloud-region detailCheck the model’s published specification — Ethernet / Wi-Fi; required ports; cloud region
R3Radio coverage"30-metre line-of-sight range"The radio family the lock exposes, the expected range through walls of stated materials, the antenna orientation, the gateway-on-each-floor rule, and what happens at the edge of coverageA single range figure with no wall/material attenuation, no antenna guidance, no edge-of-coverage ruleCheck the model’s published specification — radio family; expected range; antenna orientation
R4Mechanical + environment"Wall-mountable"Mounting pattern (keyhole, VESA, DIN), ingress protection, ambient temperature range, ambient humidity range, weight, dimensions, cabling clearance behind"Indoor use only" that quietly includes attics, plant rooms and parking decksCheck the model’s published specification — ingress rating; operating temperature; operating humidity
R5Capacity + concurrency"Up to N locks per gateway"The lock count the gateway is rated for under the operator's expected concurrent event load — not the absolute maximum under zero trafficThe absolute-max number with no concurrency caveat, no per-event-rate caveatCheck the model’s published specification — concurrent-lock rating; sustained event rate
R6Account + credential provisioning"Add the gateway in the app"Whether the gateway is provisioned by QR / PIN / Bluetooth-pairing, who can add a gateway, whether a gateway ships pre-bound to a tenant account, whether multi-admin is supported, whether the lock-gateway pairing happens in the same console or a separate one"Add the gateway in the app" with no role / tenant / pre-binding storyCheck the model’s published specification — provisioning mode; admin role policy; tenant binding
R7Security + access controls"Encrypted communication"The protocol between gateway and cloud, the credential-storage posture on the gateway, the admin-auth model on the gateway itself, the firmware-update signing posture, and what the gateway does with retained data after decommission"Encrypted communication" with no algorithm / no signature / no retention postureCheck the model’s published specification — transport cipher; signing posture; admin-auth model
R8Acceptance testing"Verified during commissioning"The test set the installer is required to run, the evidence the installer is required to leave behind, the gate at which the buyer signs the lock and gateway into service, and the ladder that escalates a partial pass"Verified during commissioning" with no test list, no evidence requirement, no partial-pass ruleCheck the model’s published specification — test list; evidence format; partial-pass rule

The matrix is read by taking one row at a time, transcribing the supplier's line into the leftmost column, annotating it line-by-line in the next column, then refusing to sign the row until the open specification item is filled from the product page (not from the sales deck).

R1 — Power: what reaches the wall outlet (T2)

The first failure a gateway install produces is almost always power, because the buyer's electrical provisions were specified against the wrong "standard outlet" line. Three clauses must be pinned down before any device ships.

Question the RFQ must askWhy the buyer needs the answerCommon bluff to refuseValue to confirm (per SKU)
Mains voltage and frequencySite electrical may be 110–120 V / 60 Hz (Americas, parts of Japan) or 220–240 V / 50 Hz (most of the rest of the world); wrong region means the gateway SKUs split"Multi-region PSU" with no SKU listCheck the model’s published specification — region SKU list
Mains vs PoE vs USBDetermines whether the gateway needs a power outlet, a PoE switch port, or only a USB source; PoE changes switch-port budgeting radically"Wall-mountable" without specifying which power pathCheck the model’s published specification — accepted power paths
Battery / supercapacitor fallbackSome gateways retain radio to locks during a short power loss; some go silent immediately; the lock-side offline-mode rule for the chosen lock only matters if you know the gateway-side behaviour"Operates during outages" with no durationCheck the model’s published specification — backup behaviour and duration
Circuit sharing constraintWhether the gateway can share a circuit with other low-voltage loads (door magnet, maglock, PoE camera, access reader) or needs a dedicated drop"Standard outlet" with no circuit-sharing ruleCheck the model’s published specification — circuit-sharing guidance
UPS / surge protection postureWhether the gateway requires local UPS, what VA class is acceptable, whether surge-protected PDU is required"Use a surge protector" with no ratingCheck the model’s published specification — UPS / surge guidance

The honest answer for every row above, for the catalog this site sells from, is check the model’s published specification. Filling the open specification items without that confirmation is exactly the path the supplier wants the buyer to walk down.

R2 — Uplink: what reaches the network port (T3)

The second failure, when the order of failures is reproduced, is uplink. Four clauses govern whether the gateway's cloud tunnel even comes up.

Question the RFQ must askWhy the buyer needs the answerCommon bluff to refuseValue to confirm (per SKU)
Physical uplink — Ethernet / Wi-Fi / bothDetermines whether the gateway needs a wired drop on every floor or only a Wi-Fi association"Connects to your Wi-Fi" without naming required bands, security mode or captive-portal postureCheck the model’s published specification — physical uplink options
Addressing — DHCP vs staticSome enterprise networks restrict DHCP, hand out addresses by MAC, or require static reservations"Use DHCP" with no static-option guidanceCheck the model’s published specification — addressing options
Outbound ports / DNS / NTPOutbound HTTPS, NTP, and platform-specific ports on the operator firewall must be open before commissioning; some enterprise networks proxy HTTPS but break the gateway's certificate pinning"Standard HTTPS" with no port listCheck the model’s published specification — required outbound ports, DNS, NTP
Cloud region and data-residency postureWhether the gateway phones home to a regional cloud or a single global cloud; whether tenant data is stored per-region or centralised"Cloud-managed" with no region detailCheck the model’s published specification — cloud region(s)

For per-model app-platform binding, the catalog as documented is TTLock / Tuya / Doodle at the consumer-tier, and hotel PC software at the hotel-tier. The mapping between lock SKU and app platform is check the model’s published specification. The supplier's RFQ-peddled "any platform, any lock" line is a bluff.

R3 — Radio coverage: what reaches the air between gateway and lock (T4)

The third failure — the one that quietly escapes commissioning for the first six to twelve months — is radio coverage. The buyer's pilot site says "fine"; the expansion site is built; an edge door stops responding. Three clauses govern radio coverage.

Question the RFQ must askWhy the buyer needs the answerCommon bluff to refuseValue to confirm (per SKU)
Radio family exposed by the lockSmart lock radio is per-lock-model and not configurable by the buyer; only documented on the product page"Works with any BLE gateway" with no radio-generation detailCheck the model’s published specification — lock radio family / generation
Gateway-to-lock expected rangeDifferent ranges apply for different radio families; range is degraded by concrete, steel, metallic film, and mirrored glass"30-metre range" with no wall-material attenuationCheck the model’s published specification — expected range
Antenna orientation and gateway-on-each-floor ruleA gateway in a basement does not serve a tenth-floor door; a gateway inside a metal cabinet does not serve the corridor outside"Place anywhere" without orientation or floor-rule guidanceCheck the model’s published specification — antenna orientation; per-floor guidance
Edge-of-coverage behaviourWhat the lock does at the edge — retry, drop to offline-only, queue events, page the operator"Always online" with no edge behaviourCheck the model’s published specification — edge-of-coverage behaviour

A common assemble error on the buyer side is to assume that the same radio rules that govern a Wi-Fi access point apply to a gateway. They do not. Wi-Fi radios and gateway-to-lock radios are different physical layers, different power budgets, different wall-attenuation characteristics, and different edge-of-coverage failure modes. The catalog's app-platform boundary is TTLock / Tuya / Doodle at the lock side; the radio side is whatever the chosen lock exposes. Check the model’s published specification for every shortlisted SKU.

R4 — Mechanical and environment: what the gateway is mounted to (T5)

The fourth failure sits at the installer's hands-on day. Five clauses belong to the rack / wall / ceiling the gateway will live on.

Question the RFQ must askWhy the buyer needs the answerCommon bluff to refuseValue to confirm (per SKU)
Mounting patternKeyhole, VESA, DIN-rail, ceiling tile — affects what hardware the installer brings"Wall-mountable" without a patternCheck the model’s published specification — mounting pattern
Dimensions and weightWhether the chosen mounting surface accepts the device; whether ceiling-tile suspension is allowed"Compact" without a numberCheck the model’s published specification — dimensions; weight
Ambient temperatureOperating envelope in the chosen mounting location; plant rooms, parking decks and attic plant rooms can be outside the envelope"Indoor use" without a temperature windowCheck the model’s published specification — operating-temperature window
Ambient humidityBathrooms, indoor pools, plant rooms, basement dehumidifier-rooms; humidity envelope excludes these"Indoor use" without a humidity windowCheck the model’s published specification — operating-humidity window
Ingress / dust protectionParking decks, plant rooms and loading bays may need a dust- or splash-rated enclosure even if the gateway itself is indoor-only"Indoor use" without an IP ratingCheck the model’s published specification — IP rating (or "indoor only — no IP rating asserted")

The honest reading of "indoor use only" is "the gateway does not carry an ingress-protection rating sufficient for the target environment, regardless of whether the target environment seems benign." Plant rooms are not benign. Loading bays are not benign. Attic plant rooms above boiler plant are not benign. None of this is asserted for any specific SKU — it is the buyer's own environmental judgement, with the open specification item confirming what the product page says.

R5 — Capacity and concurrency (T6)

The fifth failure surfaces only after go-live, when the operator notices the gateway at the busy floor starts losing events during peak hours. Three clauses govern capacity.

Question the RFQ must askWhy the buyer needs the answerCommon bluff to refuseValue to confirm (per SKU)
Concurrent-lock ratingThe lock count the gateway can hold in its table at one timeThe "supports N locks" line without concurrent-event-rate contextCheck the model’s published specification — concurrent-lock rating
Sustained event rateHow many lock events per minute the gateway is rated for under sustained load (unlock, audit-pull, credential issue, firmware-polling)A single concurrent-lock figure with no event-rate contextCheck the model’s published specification — sustained event rate
Failure-mode under overloadWhether the gateway drops events, queues them, or falls back to local-only"Scalable" with no overload ruleCheck the model’s published specification — overload behaviour

The honest reading of "up to N locks per gateway" is "up to N locks under zero traffic" — the supplier sells the number, the buyer needs the sustained figure. The sustained figure is check the model’s published specification.

R6 — Account and credential provisioning (T7)

The sixth failure is the one that surfaces the first time the buyer tries to add a junior administrator to the console and cannot. Five clauses govern provisioning.

Question the RFQ must askWhy the buyer needs the answerCommon bluff to refuseValue to confirm (per SKU)
Provisioning channelQR / Bluetooth-pairing / PIN-entry / pre-bound — determines the install-day workflow"Add the gateway in the app" without the channelCheck the model’s published specification — provisioning channel
Admin role policyWho can add a gateway; how many admins per tenant; how role-promotion works; what an auditor can read"Multi-admin" without naming the role-policyCheck the model’s published specification — admin role policy
Tenant binding postureWhether the gateway is bound to one tenant at the factory or on first boot; whether re-tenanting is supported"Multi-tenant" without naming the binding modelCheck the model’s published specification — tenant binding posture
Credential-issuance channelWhether credentials are issued from the lock side, the gateway side, or both; whether an issued credential fans out through the gateway to the lock on next handshake"Issue credentials in the app" without the fan-out modelCheck the model’s published specification — credential-issuance channel
Audit-log retention postureWhere audit events are stored, for how long, who can read them, what is purged on decommission"Audit log included" without retention or purging numbersCheck the model’s published specification — audit-log retention

The honest reading of "easy to add" is "easy to add the first time, for the first tenant, with the default admin". Everything past first-tenant is a separate clause that has to be written into the order.

R7 — Security and access controls (T8)

The seventh failure is the one that surfaces when the buyer's IT / compliance function refuses to let the gateway onto the network because the supplier cannot answer the cryptographically precise questions. Four clauses govern security.

Question the RFQ must askWhy the buyer needs the answerCommon bluff to refuseValue to confirm (per SKU)
Transport cipherThe cipher and protocol between gateway and cloud; the cipher between gateway and lock; whether one or both are pinned to a specific algorithm"Encrypted" without naming the cipher or the pinning policyCheck the model’s published specification — transport cipher(s)
Firmware-update signing postureWhether firmware updates are signed and whether the gateway refuses unsigned updates; whether the buyer can pin to a known firmware"Signed firmware" without a key-rotation / fail-closed ruleCheck the model’s published specification — signing / fail-closed rule
Admin-auth modelWhether admin authentication uses a password, a hardware key, an SSO bridge, or two of the above"Secure admin" without naming the modelCheck the model’s published specification — admin-auth model
Decommission data-purge postureWhat is wiped from the gateway on decommission, what is wiped from the cloud tenant on deletion, what is left behind (and where) for regulator or audit purposes"Data wiped on decommission" without itemising what is wiped whereCheck the model’s published specification — data-purge policy

The honest reading of "encrypted" is "encrypted with a specific algorithm that the buyer can read in the product page". "Encrypted" with no further detail is a refusal to answer.

R8 — Acceptance testing (T9)

The eighth and final failure is the one that escapes a partial-day commissioning: the gateway goes live, the lock responds once, the buyer signs, and three months later the operator finds that two doors at the edge of coverage silently drop. Five clauses govern acceptance.

Question the RFQ must askWhy the buyer needs the answerCommon bluff to refuseValue to confirm (per SKU)
Installer test listThe exact set of tests the installer runs at commissioning — door-by-door, gateway-by-gateway"Verified during commissioning" without the test listCheck the model’s published specification — installer test list
Evidence required to leave behindScreenshot of admin page, signal-strength reading per door, event-arrival proof per door, sign-off page per door"Evidence provided" without itemising the formatCheck the model’s published specification — evidence format
Partial-pass escalation ruleWhether one failing door blocks the entire commissioning, whether failing doors are remediated the same day, whether the buyer can take possession of completed-doors-only"Go-live pending fix" without a partial-pass ruleCheck the model’s published specification — partial-pass rule
Day-one go-live gateThe conditions under which the buyer signs the gateway (and the locks behind it) into service"Go-live at end of day" without naming the gateCheck the model’s published specification — go-live gate
Re-test cadence during warranty-periodWhether the installer returns for periodic re-tests, at what interval, and at whose cost"Periodic re-test" without cadence or cost-sideCheck the model’s published specification — re-test cadence

The honest reading of "verified during commissioning" is "the installer verifies whatever the installer considers sufficient to declare working". That is not a contract-grade acceptance test.

What to demand from the supplier (the RFQ clauses)

The clauses below are what the buyer writes into the RFQ and refuses to release the deposit until each one is signed. They are not sales-driven clauses; they are contract-driven clauses.

"Power. Supplier shall state, per gateway SKU, accepted mains voltage, accepted PoE class if any, USB input if any, fallback behaviour during power loss, and circuit-sharing guidance. Supplier shall not assert a 'standard outlet' line without the four items above."

"Uplink. Supplier shall state physical uplink options, addressing options, outbound ports / DNS / NTP, and the cloud region(s) the gateway phones home to. Supplier shall not assert 'connects to your network' without the four items above."

"Radio. Supplier shall state the lock radio family and generation, expected gateway-to-lock range, antenna-orientation guidance, and the edge-of-coverage behaviour of the lock when the gateway link is lost."

"Mechanical + environment. Supplier shall state mounting pattern, dimensions, weight, operating-temperature window, operating-humidity window, and ingress rating (or 'indoor only — no IP rating asserted')."

"Capacity. Supplier shall state concurrent-lock rating under sustained event load, and the failure-mode under overload. Supplier shall not assert a maximum figure without the sustained-load caveat."

"Provisioning + security. Supplier shall state provisioning channel, admin role policy, tenant binding posture, transport cipher(s), firmware-signing posture, admin-auth model, and decommission data-purge policy."

"Acceptance. Supplier shall provide the installer test list, the evidence format, the partial-pass escalation rule, the day-one go-live gate, and the re-test cadence during the warranty period. Each item shall be itemised, not summarised."

The honest annotation is that every clause the buyer refuses to release is one the supplier would prefer not to write down. Catalog-side application of these clauses is straightforward: the app-platform boundary is TTLock / Tuya / Doodle (with hotel PC software for hotel-class SKUs), and per-model gateway support is check the model’s published specification.

What is a bluff (anti-claims to push back on)

A handful of lines recur in supplier RFQs and have to be refused on receipt, not negotiated later. They belong in the buyer's "anti-claims" cheat sheet alongside the matrix above.

  • "Works with any of our locks." It does not. The catalog app-platform mapping is per-SKU and is check the model’s published specification.
  • "Standard outlet." A power line with no mains-voltage list, no PoE-class list, no circuit-sharing rule, and no UPS guidance is a refusal to specify.
  • "Connects to your network." An uplink line with no protocol, port, DNS or cloud-region list is a refusal to specify.
  • "30-metre range." A radio-coverage line with no wall-attenuation and no antenna guidance is a refusal to specify.
  • "Up to N locks." A capacity line without a sustained-event-rate caveat is the maximum-under-zero-traffic number; refuse it.
  • "Secure by design." A security line without naming cipher, signing, admin-auth and data-purge items is a refusal to specify.
  • "Matter / Zigbee / Apple Home Key ready." None of those protocols are in the catalog. Any supplier line that mentions them for a catalog SKU is a misread of the product page.

The cost-side and the lead-time-side are deliberately excluded from this article: per the site-wide fact discipline, those are routed to /request-a-quote and are not asserted here.

Illustrative project scenario

Consider a 240-key new-build hotel on a single campus, five floors, two wings per floor, two stairwell cores, one back-of-house corridor per floor, one loading-bay entry, one pool-deck door. The lock family under consideration includes hotel-class SKUs on the guest-room doors (the SLK-9936S family is the available anchor for documentation granularity — see RFID Hotel Card Door Lock, Satin Finish — but the exact SKU must be check the model’s published specification for the buyer-side selection) and a residential-class multi-function lock family on the back-of-house and amenity doors. The app-platform boundary documented in this catalog is TTLock / Tuya / Doodle / hotel PC software; the buyer is on the hotel PC software side for the guest-room doors and is therefore navigating the hotel-tier stack, with the residential-class locks on a consumer-tier app platform on the amenity doors. Wi-Fi, Matter, Zigbee, Apple Home Key and the rest of the radio families are not in scope per the catalog.

The install-side requirements table for this project runs as follows:

  • Power. One wiring-closet drop per floor, dedicated breaker, local UPS sized for sustained-outage coverage of the gateway fleet, surge-protected PDU. Vendor to verify in writing per-gateway SKU.
  • Uplink. Each gateway terminates on a dedicated switch port on the floor's wiring-closet switch; outbound HTTPS, NTP, and platform-specific ports opened; static addressing reserved on the operator DHCP server. Vendor to verify in writing per-gateway SKU.
  • Radio. One gateway per floor, antenna orientation vertical, mounted at corridor-ceiling height, away from the elevator-lobby concrete shear walls. Edge-of-coverage test on every stairwell-core door before the floor is signed into service.
  • Mechanical + environment. Mounting on corridor walls inside wiring closets, not on the plant-room wall (humidity envelope on the plant-room door set falls outside the residential-class SKU operating window — that door is excluded from the gateway fleet and re-scoped to standalone operation).
  • Capacity. Vendor confirms the gateway's per-event-rate ceiling under the hotel's expected 0.6 events per lock per minute during the morning check-out window. Pilot site signs off this ceiling before the fifth gateway is ordered.
  • Provisioning + security. Single tenant, two-admin role model (operator admin, auditor read-only), transport cipher itemised, firmware-signing fail-closed rule itemised, decommission data-purge policy itemised.
  • Acceptance. Day-one gate is "every guest-room door responds within 250 ms at the edge of coverage during the morning check-out window". Partial-pass rule: one failing door blocks the entire floor; failing doors are remediated the same day or rolled back to standalone mode overnight.

The scenario is illustrative, not a case study. It exists to anchor the eight requirement families to a reader's familiar shape — a 240-key new-build — and to make clear which questions the buyer must answer from the product page, not from the supplier's sales collateral.

Closing CTA and further reading

A gateway installation is what the supplier wants it to look like, unless the buyer has read every line of the supplier's checklist against the eight requirement families above. The buyer-side posture across all eight families is the same: per-model figures routed to to verify in writing, filled from the product page, never from the sales deck. The catalog-side posture is the same across all eight families: app-platform families are TTLock / Tuya / Doodle (with hotel PC software for hotel-class SKUs), and per-model binding is check the model’s published specification.

For the broader connectivity landscape, the lifecycle from pre-survey through decommission is the Smart Lock Gateway Guide. For the upstream reach question, Smart Lock Access Point Planning and Smart Lock Network Requirements frame the access-point analogy; the architectural ladder is in Smart Lock Network Architecture; the upstream layer is in Smart Lock Communication Architecture; the comparison-without-on-prem-relay is in Smart Lock Hub Guide; the broader panorama is in Connected Smart Locks: Complete B2B Guide. The off-premise service-side of all of this is in Smart Lock Cloud Management, and the install-day tooling is in Smart Lock Installation Tools.

To take the matrix above into the build phase, order the shortlisted SKUs as samples first via the order-samples page and have the installer run the R8 acceptance test against the R1–R7 clauses on the day of arrival. Then send the populated worksheet — with every open specification item resolved against the product page — through the quote workflow at Request a quote, and order-catalog details can be requested from Request the catalog. Neither path asserts pricing, MOQ, lead time, warranty or certification; both routes return itemised answers per the published routing policy.

Giỏ hàng của bạn
Trải nghiệm của bạn trên trang web này sẽ được cải thiện bằng cách cho phép cookie Chính sách cookie
Chat on WhatsApp