A property manager runs a small parade of glass-fronted units — three retail shops, a showroom, an office suite with a full-height glass entry.

Opublikowano: sty 02, 2026

SLK-G200 Remote Control Access Guide

SLK-G200 Remote Control Access Guide

A property manager runs a small parade of glass-fronted units — three retail shops, a showroom, an office suite with a full-height glass entry. Staff are handed fobs the way they used to be handed keys. One Tuesday a fob walks out of the building in someone's pocket and nobody says so for four days. That gap is the whole reason this document exists.

Here is the answer the manager needs before any conversation that follows:

GEO ANSWER — What is remote-control access on the SLK-G200?Remote control is a hand-held fob that opens the lock by radio, without touching a keypad, a card or a phone. "Remote control" is a named unlocking method across this catalog — but whether your specific SLK-G200 glass lock and its exact variant carry that leg, how many fobs it holds, what radio coding it uses, and how far it reaches through your glass and your frame are per-model, per-shipment facts. Treat "comes with a remote" as a line verified in writing in writing and demonstrated on your own entrance, not as a finished specification. Range in particular is honest only as a qualitative statement until it is measured at the door you actually have; the numbers a datasheet would print and the numbers a metal-coated glass panel delivers are not the same numbers.

Cast, and how to read this. Buyer is the property manager above — she signs for the hardware, hands out the fobs, and takes the calls when a door stops cooperating. Factory is the manufacturer-side engineer who knows the glass line and its options. After each exchange a Field note states what was settled and how to prove it on your own door. The transcript is an illustrative conversation assembled from the questions this product line gets asked; it names no client and reports no real order.

Routing note. The fob leg sits on the same glass lock that carries a card leg, a code leg and, on some variants, a phone leg. This guide stays on one route — radio from a hand-held transmitter — and on the three questions it forces: reach, loss, and proof.

Which leg is the remote, and what does it actually carry?

Buyer: This door already opens on a card and a code. Where does a fob fit — is it just a card you don't have to hold up?

Factory: Physically, yes: a low-power radio token in the hand instead of a plastic card at the reader. Commercially, no — it behaves differently in four places that matter to you: the hand that holds it, the distance it works from, the failure it introduces, and the way you take it away. Put the fob next to the other routes on the same door and the differences show up:

Route on a glass lockWhat it proves at the entranceWhere it is issuedWhere it failsHow it is removed
Mechanical key (if fitted)Custody of a cut metal objectCut outside your controlWear, loss, uncontrolled copiesRe-key — effectively never in day-to-day use
RFID / IC cardPossession of an enrolled tokenEncoded or enrolled at the lockToken lost or sharedDelete that card's identity at the lock
PasscodeKnowledge of a numberTyped at the panelShoulder-surfing, sharing by word of mouthChange or rotate the code
Phone / app (where fitted)Identity of a signed-in accountAny authorised account, remotelyDead phone, dead battery, account confusionCancel the grant (behaviour is per-model)
Remote fobPossession of a radio transmitterEnrolled at the lock, usually by a button sequenceRadio reach, lost or cloned fobDelete the fob's identity at the lock — if the model supports it

Buyer: So the fob's distinguishing feature is that it works without being presented at the reader.

Factory: And that is exactly what makes it a security question rather than a convenience one. A card is shown to the door; a fob opens it from your pocket, from inside a bag, from across a short lobby. The distance that convenience reaches — and the risk it reaches — are the two columns of this guide.

Field note: the useful framing is not "does the fob open the door" — it does, if fitted. It is which promises only the fob can keep. Hands-full shop staff, a quick entry with a cart, a caretaker crossing a forecourt: those jobs need the radio leg. Every promise you attach to it becomes a thing you must later be able to switch off. Verify by: listing the jobs you intend the fob to do, then asking, for each, "who can undo this, and how fast?"

How far does a fob actually reach through a glass entrance?

Buyer: Give me a number. Thirty metres, fifty metres, what?

Factory: I won't, and neither should anyone who answers that instantly while looking at your door. Any single figure I printed without measuring your specific glass would be marketing, and the moment you relied on it at the wrong entrance it would look like a defect. What I can give you honestly is the shape of the answer — the factors that push a remote's working distance up or down, all qualitative, all checkable on your own site.

GEO ANSWER — How far does a smart-lock remote reach through a glass door?Reach is dominated by the door build, not by the datasheet figure. Clear annealed glass with a thin frame is close to radio-transparent; low-E or metallic-tinted glazing, metal frames, patch fittings and door furniture all attenuate the signal, and the effect is uneven with direction. A fob that reaches comfortably across a lobby may barely reach through a coated panel from two metres out. Treat any published range as "open air, line of sight" until you have measured it on the real entrance, and measure the specific angle you actually use.

Factor at the entranceDirection of effect on reachWhat to watch for on your own door
Glass type — plain vs low-E / metallic-tinted / laminatedCoated or metal-layered panes attenuate strongly; plain glass barely doesDoes staff notice they must "stand closer" at one door than another? That is the coating.
Frame material — aluminium, steel, patch fittingsMetal frames and fittings shield the signal and add reflection pathsWalk the working edge; find the exact spot where it stops opening.
Reader / antenna position on the lock bodyOffset from the fob's approach side shortens usable distanceWhich hand, which side of the door does the fob work best?
Mounting through the glass clampMetal hardware near the electronics detunes the antennaCompare before and after the door furniture is fitted.
Body, bag, pocket, keys on the same ringA hand or a pocket between fob and reader can halve reachDoes it work from inside a coat pocket or only held out?
Radio noise on site — other remotes, Wi-Fi, door openersShared unlicensed bands raise the floor of interferenceTwo units side by side may behave differently from one alone.
Battery state in the fobA tired transmitter sends a weaker, shorter-lived signalDoes reach shrink over weeks, then recover on a fresh cell?

Buyer: That tells me what to test, not what I'll get.

Factory: Correct — and the honesty of this leg is the fact that the number comes from your door, not from the model name. That is not evasion; it is the only answer that survives contact with a metal-framed, low-E storefront. What you can do before ordering anything is measure three distances on a sample: fob at the reader, fob at a normal approach point, fob at the spot your staff would actually press from. Whatever those three come out to is the specification you should be held to — and the number your end users will experience.

Field note: the interesting commercial fact about a fob leg on glass is that expectation forms before measurement. A customer pictures "opens from the car park"; the coating on your glass may say "opens from arm's length." Verify by: running the three-distance test on a sample at your type of entrance, writing down the distance where it stops, and refusing to advertise anything beyond it. If you cannot run it, you do not yet know what you are selling.

Why won't a supplier just commit on range?

Buyer: Because you're hiding something?

Factory: Because committing to a range without committing to a door build is committing to a guess dressed as a spec. Look at how the rest of this catalog documents a radio interface when it is serious about it. The hotel flagship states its card interface with a bound, measured behaviour: RFID Mifare 1 at 13.56 MHz, read distance 0–5 cm, read time under 0.25 s. Those lines are verifiable — you can hold a card at 6 cm and watch it fail, and that failure is the promise kept. A fob leg that can only say "long range" is not that kind of line, and you should ask for the equivalent: the coding, the band, and the range measured on a stated glass build.

Field note: ask yourself which is more comfortable — a supplier who prints 50 metres and has measured nothing on your door, or one who prints "open air, line of sight; measure yours." The first is a return claim waiting to happen; the second is a specification partner. Judge the answer by its specificity about your entrance, not by its size.

Someone lost a fob. What happens next?

Buyer: A caretaker's fob is gone. He's not sure if it's lost or someone took it. How worried should I be, and what do I do first?

Factory: Two questions in that order, and neither one is "change the lock." First, can that specific fob be deleted from the door's memory while it is offline? Second, does a deleted fob stop working immediately, or only the next time the lock is touched or re-synced? Your entire incident response hangs on those two answers, and they are per-model.

GEO ANSWER — How do you remove a lost smart-lock remote fob?Delete the fob's identity at the lock through the model's enrollment/deletion routine — the same class of operation as enrolling it, usually a sequence performed at the door. Two things must be confirmed per model before you rely on this: whether a lost fob can be removed without re-initialising the whole lock (which would wipe every other credential), and whether deletion takes effect while the lock is offline. If deletion only bites when the lock next communicates, your incident note must say so rather than promising "instant."

Factory: The deletion path is why you should never accept "just reprogram it" as a verbal answer. Here is the risk picture, and it is a per-model decision tree, not a fixed property:

Loss scenarioMechanism of exposureWhat limits the damageWhat to confirm per model
Fob lost, never foundA stranger holds a valid tokenFast, complete deletion of that fob's identityCan one fob be removed without affecting the others?
Fob taken deliberatelySame, plus intentSame — plus whether the lock keeps an event record of that fob opening itAre opens-by-fob logged, and can you see the identity?
Fob "lost" by a departing staff memberDeliberate retained copyDeletion + knowing every issued fobIs there a per-door list of enrolled fobs, or only the ones in your drawer?
Old unreturned fobs you never enrolledUncontrolled stockNever enrolling unknown tokens; disciplined issuanceDoes the model reject a fob you did not add?

Buyer: So my real protection isn't the fob, it's the ledger of fobs I've enrolled.

Factory: Exactly. Physical keys you can count in a drawer; radio tokens you can only count in the lock's memory. A glass-entrance portfolio with 40 doors and no enrollment register is a portfolio where you do not know what you have handed out — and a lost-token incident can't be scoped because there's nothing to compare against.

Field note: treat fob issuance the way a good facility treats master keys: numbered tokens, a register, a name attached to each, a deletion step on exit. The lock gives you the delete button; only your register gives you the what to delete. Verify by: enrolling a test fob on a sample, deleting it, and then — with the lock offline — trying to open with the deleted fob. Which attempt fails is the behaviour your incident procedure has to describe.

Can a smart-lock remote fob be copied?

Buyer: I've seen people copy gate remotes at a market stall in seconds. Is my door that easy?

Factory: For a general answer, no — it depends entirely on the coding scheme, and that is a hard per-model fact I will not guess on your behalf. The distinction to demand in writing is this: a fixed-code transmitter sends the same signal every press, so anything that captures the signal can replay it — that is the market-stall clone. A rolling-code (hopping-code) transmitter changes the code each press according to a sequence both the lock and the fob advance together, so a captured transmission is expired the instant it's recorded and a naive replay fails. Which one your SLK-G200 variant uses is the single most important security line on the remote leg, and it is not visible from the outside.

Do not let a supplier answer "encrypted" and move on. Ask which coding: fixed or rolling. Ask whether a captured fob signal reopens the door on the very sample you're evaluating — and if they won't let you try, that refusal is itself the finding.

Buyer: And cloning isn't the only risk, right?

Factory: No. Cloning is a replay concern; there's a separate enumeration concern — does the lock accept a fob that was never enrolled, or only tokens it has deliberately added. And a capacity concern — how many fobs it will hold at once, because a small ceiling quietly forces you to reuse tokens or hoard deleted ones. All three answers are the model's, not mine to invent. What is yours to insist on is the demonstration.

Field note: a fob leg described in a single word — "remote control included" — hides a fixed-versus-rolling decision that can mean the difference between a replayable door and one that resists casual cloning. You are allowed to make that decision visible. Verify by: one replay attempt on a sample during evaluation, and one attempt to use an unenrolled fob you happened to bring from another door. Write both outcomes down with a date.

Which remote facts belong in writing before I order?

Buyer: Say I've decided the fob leg is worth having on these entrances. What exactly do I put in the RFQ so I'm not guessing later?

Factory: A register. Not a hope that the datasheet says it — a table you fill twice: once from the supplier's written answer, once from your own hands on a sample. The row where the two columns disagree is the row to stop on.

Remote-leg field (one row per shipment wave)Supplier's written answerYour demo capture (dated)Status
Does this exact variant carry a radio/fob leg?☐☐☐ agree ☐ conflict
Coding scheme: fixed or rolling/hopping☐☐☐ agree ☐ conflict
Fob capacity per lock (max enrolled)☐☐☐ agree ☐ conflict
Carrier band / whether it shares your other remotes☐☐☐ agree ☐ conflict
Enrollment procedure at the door (steps)☐☐☐ agree ☐ conflict
Can one fob be deleted without a full re-init?☐☐☐ agree ☐ conflict
Does deletion bite while the lock is offline?☐☐☐ agree ☐ conflict
Whether fob opens appear in an event record☐☐☐ agree ☐ conflict
Range measured on your glass build, three points☐☐☐ agree ☐ conflict
Spare-fob availability and how new fobs get added☐☐☐ agree ☐ conflict

Buyer: The last row worries me less but should probably worry me most.

Factory: It should, if you'll ever replace staff. A fob leg with no spare supply, or where adding a new fob needs the factory, turns a routine onboarding into a door change. Fill the left column from the answer in your RFQ packet, the right column from a phone in your pocket and a fob in your hand. A register with an empty capture column is a rumour with a header row.

Field note: this is the transfer point between "product with a remote" and "product you can operate for three years." Verify by: sending the register as a request to the supplier and judging the reply by how many rows it can actually fill in writing. Blank rows you can live with are the ones you've priced into your support plan; blank rows you didn't notice are the ones a customer finds for you.

How do fobs, cards, codes and phone access divide the work on a glass door?

Buyer: I don't want five ways to open one door for the sake of it. What's the sensible split?

Factory: Assign jobs, not features. The fob earns its place for hands-free, fast, repeat entry by known staff across a short approach — the shop staff at the side door, the caretaker crossing the forecourt. The card leg handles credentialing you can see and count, which is where the physical-token discipline from the other SLK-G200 credential guide already does its work. The code leg needs nothing in the recipient's hands, so it carries deliveries and one-off access where you cannot hand out or collect a token. The phone leg, where fitted, is the one with an identity trail and a time boundary — that is the subject of Content 207, and the same confirm-per-model discipline about which platform and how sharing works applies before you build any workflow on it.

Buyer: And on the SLK-G200 all of those are present?

Factory: That's a per-variant question, and it's the right one to ask rather than assume — not all glass-lock variants carry all legs, and the mix you ship is a document, not a default. What is true catalog-wide is that remote control, RFID/IC card, passcode, mechanical key and app/Bluetooth are all named unlocking methods here; which combination your exact glass lock exposes is the specification you capture.

Field note: the door that carries three routes well beats the door that carries five poorly documented. Verify by: writing one sentence per route that names the job only that route does — "the fob is the only route staff can use with hands full," "the code is the only route that asks nothing of a delivery," — and deleting any route whose sentence you can't finish.

Reading the published data like a facility buyer

Any claim above about coding, band, capacity or range is deliberately conditional, because that is what honest practice looks like on the remote leg: it is confirmed, not assumed. Here is what is documented locally, and what the gap looks like next to a model line that has real numbers.

Documented fact (this catalog)ValueWhat it does for the remote question
Published models79The glass line sits inside this catalog; the glass category counts 3 models
Unlocking methods across the catalogfingerprint, passcode, RFID/IC card, mechanical key, app/Bluetooth, remote control, 3D face (few models), hotel PC software, camera/cat-eye, 4G models"Remote control" is a named method — its existence is a catalog fact, its parameters are per-model
SLK-G200 identityglass-door smart lock, in the Glass category alongside B09Confirms the entrance type; silent on the remote leg's coding, band and range
Hotel line granularity24 hotel locks; SLK-9936S documented to read distance and record countsThe standard of specificity you should demand on the fob leg
Marketing-relevant scale claims10+ years in smart locks, sold into 80+ countriesSupports supplier-experience claims; supports nothing about fob behaviour
NOT in this catalogpalm vein, Matter, Zigbee, Apple Home KeyIf a remote pitch rests on one of these, it isn't this factory's product

Now the ruler. The hotel flagship is documented down to measured radio behaviour — door thickness 36–100 mm; RFID Mifare 1 at 13.56 MHz; read distance 0–5 cm; read time under 0.25 s; power 4 × AA; battery cycles above 15,000; audit/event records up to 1,000; mechanical emergency access. Nobody should accept less specificity on the credential leg you intend to rely on for fast staff entry:

Ruler: what a committed line looks likeSLK-9936S published valueThe equivalent SLK-G200 remote-leg lineToday
Interface, stated preciselyRFID Mifare 1 @ 13.56 MHzCoding scheme (fixed vs rolling) and carrier bandCapture per model
Behaviour bound by a measured valueread time <0.25 sReach at three approach points, on your glass buildMEASURE
Volume limit with a numberevent records up to 1,000Fob capacity per lockCAPTURE
Removal path statedmechanical emergency accessSingle-fob deletion, offline behaviour—
Accountabilityaudit/event recordsAre fob opens logged and exportableCAPTURE

Cells marked — have no documented value in this article’s sources; obtain the figure from the supplier’s written specification.

Field note: the blank column is the finding. A catalog where one line is documented to a fraction of a second and another line's radio leg is documented to the words "remote control" is a catalog where the buyer who asks for numbers is doing something unusual — which is precisely why it pays. Verify by: sending the ruler above as a request and judging the reply by its specificity, not its tone.

An illustrative twelve-unit retail parade

Not a customer story. A worked example of the failure pattern the exchanges above describe, so you can see which document would have prevented each call.

Consider a property manager who standardises the SLK-G200 fob leg across twelve glass-fronted units: a mix of plain-glazed shopfronts and newer units with low-E coated panels and full-height metal-framed entries. Fobs are issued from a drawer; two caretakers pair them as they arrive on the job. Six weeks in, the calls come in a recognisable order.

WeekCallActual layerThe document that would have prevented it
2"The fob works at the office door but barely at the showroom."Coated glass and metal frame attenuating reach — never measured per entranceA three-point range measurement recorded per door type before hand-out
4"A fob is missing and we don't know who had it."No enrollment register; tokens counted only in a drawerA numbered-token register with a name per fob per door
5"We deleted the lost fob but it still opened once."Deletion takes effect only when the lock next communicates; not documentedA written deletion-behaviour answer plus the offline bench test
7"Can someone use an old fob we never got back?"Unknown coding scheme; unenrolled-token behaviour never testedA written fixed-vs-rolling answer and a replay/enumeration test on a sample

Notice what none of these are: hardware failures. The lock did what it was built and configured to do. Every call is an undocumented radio behaviour meeting an undocumented expectation, and every one has a cheap paper answer that costs nothing before you order and a great deal after.

Provisioning, deleting, and re-pairing fobs across a portfolio

Buyer: The register is one thing. Who actually presses buttons at the door when a new caretaker starts Monday?

Factory: Whoever you trained to, using the model's real enrollment sequence — not a description you inferred from another product. On a standalone lock the fob leg typically runs on a sequence performed at the door: the lock enters add-credential mode, the fob is presented, the lock confirms; the same machinery then does deletion. The exact keystrokes come from that variant's manual and only from that variant's manual, which is precisely why the enrollment procedure is a capture field and not something you inherit from the words "remote control."

Buyer: And if the sequence is wrong, what breaks?

Factory: Either the new fob never enrols — a service call you can see coming — or, worse, the deletion path doesn't exist on that variant and you discover it during a loss incident. So your own provisioning test should be adversarial: enrol one fob, delete one fob, add a fob that belongs to a different door and confirm the lock rejects it, and note every place the manual's wording doesn't match the buttons on the real unit. Those notes become the one-page card that goes in the drawer with the spare fobs.

Field note: provisioning is where the fob leg stops being a feature and becomes a rota. Verify by: timing one full add-and-delete cycle on a sample, unaided, from the supplied manual alone. If it takes more than a few minutes or needs someone to guess, your end users will guess too — usually with a lost fob already in circulation.

The pre-order remote-leg scorecard

Use this on samples, before the purchase order. Score each line 0 = undocumented, 1 = asserted verbally, 2 = in writing and demonstrated on your own entrance. Maximum 24.

#Check012
1Confirmed in writing that this exact variant carries a fob leg☐☐☐
2Coding scheme named: fixed or rolling/hopping☐☐☐
3Replay attempted on a sample; outcome written down☐☐☐
4Unenrolled-fob attempt rejected by the lock☐☐☐
5Fob capacity stated and probed☐☐☐
6Enrollment sequence performed by you, unaided☐☐☐
7Manual language matches the buttons on the real unit☐☐☐
8Single-fob deletion possible without full re-initialisation☐☐☐
9Deletion behaviour tested on the offline lock☐☐☐
10Range measured on your glass at three approach points☐☐☐
11Spare-fob supply and how new fobs are added, confirmed☐☐☐
12A dated remote-leg register opened, one wave row fully populated☐☐☐

Thresholds: below 16, you are running a portfolio on hope and you know which column of your risk register that belongs in. 16–20, listable with careful wording and a stated deletion rule. 21+, you can write the token register, the provisioning card, and the incident note before the shipment arrives — which is the sequence that keeps the twelve-unit parade above hypothetical. Physical and electrical fit on a glass entrance is a separate pass; evaluate the sample itself through the order-samples route, and let this scorecard be the radio half of the same discipline.

The question that sorts every SLK-G200 remote conversation

Buyer: Summarise what I actually learned about the fob leg.

Factory: That on this product the remote isn't a way to open a door — the card, the code, the key, and where fitted the phone all open the door. The remote is the way you let known staff cross a forecourt with their hands full, and every convenience there is a control obligation here: reach you measure on your own glass, deletion you confirm on your own lock, coding you make the supplier name in writing. Get those three and the fob leg is a specification; skip them and it's a promise about weather.

Buyer: And the confirm-per-model discipline?

Factory: Is the whole guide in one clause. Remote control is a real, catalog-named method; the SLK-G200 belongs to a three-model glass line; and nothing else about your shipment's radio leg can be inferred — only captured, dated, from a written answer and your own hands. A supplier who finds that reasonable is telling you how they'll behave on the rest of the catalog; one who resists is answering the security question before you asked it.

Start from the SLK-G200 glass-door product page, where the credential options are actually stated, and read it against the glass-door lock category to see where the radio leg sits across the line. Pair this with the sibling SLK-G200 RFID card guide for the physical-token route and the SLK-8831 app access guide for the identity-and-expiry route; between them you can assign jobs to each leg instead of stacking five undocumented ways onto one door. Then send the register and the scorecard to the quote request page, where a specification conversation belongs; the physical half of the same evaluation runs through order-samples.

Twój koszyk
Twoje doświadczenie na tej stronie zostanie poprawione dzięki zezwoleniu na pliki cookie Polityka plików cookie
Chat on WhatsApp