The Doors section shows every smart lock that is connected to LinArt through a LockHub gateway: state, battery, unlocking and locking, codes, cards and fingerprints, weekly schedules, guest codes from the rentals and the gateway's Wi-Fi networks. For owners, co-admins, family members and guests – everyone sees exactly the doors that have been shared with them.
A LockHub is the gateway that talks to the locks over Bluetooth (TTLock-compatible, e.g. LVD-11 or C001C) and is connected to the LinArt cloud over Wi-Fi. Everything you do to a door in LinArt goes through this gateway. How the gateway is set up and a lock is paired is described in the LockHub manual (DE) and in the product guide for the lock cylinder; this page describes the operation in the dashboard.
The Doors card shows a dial per lock with name, state and a hint line. The header carries the summary: “All doors locked”, “Open: …” or “No connection: …”. If two or more doors are open, Lock all appears.
| Shown | Meaning |
|---|---|
| Locked / Unlocked | The last state reported by the lock. After your own action the state is shown at once until the server catches up. |
| State unknown (question mark) | The gateway is offline, the lock has never reported, or the last state is older than 30 minutes. Tap = Check (query the status). |
| “as of 2 h ago” | The state is old (over 30 minutes) and is shown dimmed. |
| “Gateway offline · last 14:05” | The gateway has stopped reporting (LockHub 0.7.5 and later: 3 minutes without a heartbeat; older firmware: 15 minutes without an event). The dial is locked. See Gateway offline. |
| “Open for 12 min” | The door has been open for more than a minute; the ring fills up with time (up to 5 minutes). |
| “locks in 25 s” / “should lock now — waiting for the lock” | Auto-lock is active (see Auto-lock); the ring drains until the lock bolts itself. |
| Battery 18% | Appears from 25 % remaining charge, red from 10 %. In the gateway panel the battery is listed for every lock with the date of the last reading. Replacing batteries: guide “Batteries and power”. |
| Shield symbol next to the name | “Confirm unlocking (Face ID / code)” is switched on for this lock. |
| Badge “family” | The lock belongs to another home in which you are a member. |
| Last line, e.g. “Unlocked by phone · 3 min” | The lock's last event: via cloud, by phone, on the keypad, automatically, on the LAN, by cable – or “Unlocked at the door / Locked at the door”, “Locked automatically”. |
In the gateway panel below, the header shows “gateway offline” or “Add mode active”; members see “family access · owner …” there. Every lock has the buttons Unlock, Lock, Status and More.
In the gateway panel it also works via Unlock → dialog “Unlock “Front door”?” → Yes, unlock, as well as Lock and Status. A lock may be unlocked only once every 3 seconds (“Too fast, wait 3 s” / “One moment…”).
Who may unlock a lock in a home where they are not the owner is decided by the policy “Family members may unlock” and the door share under Familie (DE); otherwise “The owner has turned off your access” appears.
Owners and co-admins only. The hardware steps (fitting the cylinder, placing the gateway, setting up Wi-Fi) are in the LockHub manual (DE) and in the guide “Setting up with LinArt” and are not repeated here.
Rename: More → field “Name” → Save. If the gateway is offline at that moment, “name saved — the gateway gets it when it is online” appears.
Sync time: Sync time sets the lock's clock – important for time-limited codes. Members may do this too.
Remove: Remove lock safely resets the lock to factory settings: “… will be reset to factory settings: codes, cards and fingerprints stored in the lock are deleted. Stand near the lock and touch its keypad.” It always needs the second factor. Only for a broken or lost lock there is “Forget without reset (lock broken or lost)” – afterwards a hardware reset at the door is needed. Possible answers: “The lock is out of range. Touch its keypad and try again. Nothing changed.”, “Lock battery too low (under 15 %). Replace the batteries first. Nothing changed.”, “The lock was not changed. Try again next to the lock.”
Reset gateway: Reset gateway wipes Wi-Fi, local passwords, app keys, lock keys and LED settings; the gateway restarts in setup mode (blue), the cloud identity is kept. If locks are still paired, the dialog warns and offers Remove all locks first. See guide “Removing a lock or resetting the gateway”.
Everything stored in the lock is managed by owners and co-admins in the window “Data in the lock: <name>”.
Over the cloud, codes are shown masked (••••15). Only the owner of the home can reveal them for 60 seconds with Show full codes: “The codes are visible for 60 seconds and stored nowhere. Over the cloud the gateway shows only the last 2 digits.”
Error hints: “A code has 4 to 9 digits.”, “This code exists already.”, “The lock refused the code: it exists already or the memory is full.” (see Memory full), “The lock does not answer: it is at the edge of range …”, “The gateway is busy — try again in a few seconds.”
A weekly code is valid every week only on certain days and hours – for example for the cleaning “workdays 8–12”. The lock itself cannot store such a thing; the gateway keeps the code in the lock only for the current or next window and moves it on afterwards. Prerequisite: LockHub firmware 0.7.4 or later (capability “weekly-codes”) – otherwise the section is missing.
Every entry shows days and time and below it “in the lock now: 13.10.2026 08:00 - 13.10.2026 12:00” or “not in the lock yet (waiting for the window or the gateway)”. If the lock is not reachable at the moment: “Schedule saved; the lock is not reachable yet, the gateway retries every 5 minutes.” When deleting a schedule while the lock is not reachable: “Schedule deleted, but the lock is not reachable right now — the code in the lock stays valid until its window ends.”
Limits and errors: “At most 16 weekly codes per gateway.”, “Invalid days.”, “Invalid time.”, “This code exists already.”. If the gateway is off, the code expires with its window and does not stay valid (fail-closed). Child profiles with a schedule (Familie → Kinder (DE)) create exactly such codes.
If “The list was out of date — reloaded, please try again.” appears, the list in the lock has changed in the meantime; simply repeat the action. Guest codes of a booking are better changed in the booking with New door code (see Guest codes), a child's code with New code in the profile – then LinArt knows about the change.
“During these hours the lock does not lock — the door opens without a key.”
History in the gateway panel (More): “History” shows the events of the last 7 days (“No events in 7 days.”), “Who did what” the actions from LinArt with e-mail and result. Anyone who is not owner or co-admin sees only their own entries there – unless the owner has shared the door history for everyone under Familie → Datenschutz (DE).
The field appears only if the lock supports auto-lock and the gateway firmware reports the value.
Owners and co-admins only, in the gateway panel under More:
Which doors an individual member or guest gets is set under Familie → Mitglied → Türen (DE).
If a property under Rentals → Properties has doors assigned (“These locks get the guests' door code automatically.”), LinArt writes one door code to each of these doors for every confirmed booking – without you doing anything. You do not have to create the codes under “Data in the lock”.
| When | What happens |
|---|---|
| 48 hours before arrival | LinArt creates the code (6 digits by default, unique per door), syncs the lock's clock and writes the code as a time-limited code: valid from arrival (minus the property's lead time) until departure + 30 minutes. Afterwards the list is read to check that the code really is in the lock. Direct bookings with an open payment wait until they are marked as ✓ Paid. |
| Every 5 minutes | The reconciliation runs again. A failed attempt is repeated after 2, 4, 8, 16, 32 and then every 60 minutes until the code is in the lock. |
| 2 hours before arrival, code still missing | Push and e-mail to the host: “Door code missing: <property>” – “The guest's door code for the arrival … is not on the lock yet (…). Please check gateway and lock.” plus the backup-access line (key-safe code or the hint to set one up). |
| Departure + 30 minutes, cancellation, Guest has left | The code is deleted and the deletion is verified. The lock no longer accepts the code anyway because of the time window. 24 hours after the stay the plain-text code is deleted. |
| Deletion fails twice (gateway offline) | Notice to the team: “Code still in the lock: <property>” – “The old guest code could not be removed (gateway not reachable) — it still opens the door until … We keep trying; please check the gateway.” |
| Dates moved | The code is deleted and written again with the new window (“being rewritten”). |
| Cleaning | Every cleaning task gets its own code, valid only in the cleaning window; the cleaner receives it through their task link. |
Under Rentals → Today every arrival carries a chip: “Door code active” (on every door), “Door code scheduled” (still to be written), “Door code missing” (at least one door failed), “no door”, “Door code removed”. Under “Needs attention” you find “Door code not on the lock: <property> · <door> · error” and “Gateway offline: …”.
In the booking (Details) the card “Door code: 482915” shows the state per door: “on the lock”, “waiting”, “error”, “being rewritten”, “removed”, “removal failed”, the cause of the error in brackets, below it “valid … – …”. Before the time of writing: “The door code is written to the locks automatically <time>.”; without a door: “No door is assigned to this property yet.”
The guest sees their door code on the stay card from 24 hours before arrival; the message templates never contain the code (“The door code is not in it — the guest sees it on the card from 24 h before arrival.”). The guest's door code is visible only to hosts and co-admins – staff see only first names. Everything else about the host side: Rentals for hosts.
Owners and co-admins only, and only while the gateway is online (LockHub 0.6.1 or later). The gateway remembers up to 5 networks and switches to the strongest one by itself.
Passwords are never shown. To move to another Wi-Fi: first add the new network, then forget the old one. The gateway's status LED is tested and dimmed there as well (Test (~34 s), “brightness”, on/off; see “The gateway's indicator”).
While the state of all doors is unknown (gateway offline), Home shows only a compact line “Doors · ? No connection: …” with Check.
A code (guest code, child code, weekly schedule or created by hand) is stored in the lock only if the gateway is online and the lock is reachable over Bluetooth and there is room in the lock. Check in this order:
Guest codes and child codes are then written again by LinArt itself (guest codes on the next reconciliation, children with Write again). If a guest code is still missing 2 hours before arrival, the notice “Door code missing” is sent; the guest then needs a key safe or a mechanical key. Codes you created by hand you create again after fixing the cause.
The dials are locked (“Gateway offline · last 14:05”), lists cannot be read, and automatic codes wait. What keeps working: all codes, cards and fingerprints that are already in the lock (the lock checks them itself, time-limited ones too), the keypad on the lock and offline keys of the iPhone app (owners up to 24 hours, members 8 hours, guests 2 hours from the last fetch). Weekly codes expire with their window and are set again only when the gateway is back.
Check: power at the gateway, the router, then Refresh in the panel. If the gateway has had no network for more than 10 minutes, it shows blue and waits for set-up over Bluetooth (guide “Distance and signal”). Changing the Wi-Fi: Gateway Wi-Fi networks; setting up again: LockHub manual (DE).
The gateway has not heard the lock in the last minute. Touch the keypad to wake it and repeat – LinArt tries commands three times anyway. Permanently: place the gateway at most two walls away from the lock, ideally with a line of sight; metal and concrete dampen strongly. The link How to fix this → below the error message opens the matching section of the guide. Very weak batteries also show up as a range problem (Battery).
Message “The lock refused the code: it exists already or the memory is full.” (for guest codes the cause code_rejected). What to do: tab Codes → Read from the lock → remove old time-limited, one-time and no longer needed codes with Delete; likewise old cards and fingerprints. If the new code is already in the list, it is already valid. For weekly codes the limit of 16 per gateway applies as well.
From 25 % the dial shows “Battery 22%” underneath, red from 10 %. Below 15 % LinArt refuses removing/resetting (“Lock battery too low (under 15 %). Replace the batteries first. Nothing changed.”). Replace the batteries, then press Status. The battery level is also shown per event in the lock journal. Replacement and emergency power: “Batteries and power”.
Tap the dial = Check. If it stays that way: gateway online? Lock in range? A lock reports its state only while it is awake – a tap on the keypad helps.
Codes, cards, fingerprints and the admin code: “Confirmation” once per 24 hours. Removing, resetting, “Forget all networks” and relaxing a policy: always. Without a factor set up: “This action needs a second factor. Set up Face ID or an authenticator app: Settings → Security.” – see Konto & Sicherheit (DE).
For 14 days the panel shows “Gateway factory-reset on …: set up Wi-Fi and add the locks again. Offline keys were revoked.”; the owner gets a push notification and an e-mail. If this was not intended, someone had physical access. If another account tries to add the gateway, you are asked whether to release it or keep it (see Geräte (DE)).
Access through the cloud ends immediately, offline keys of the app are revoked (the gateway rejects them as soon as it is online). Codes, cards or fingerprints that this person had in the lock stay there – check “Data in the lock” and delete them if needed. Details: Familie → Mitglied entfernen (DE).
| Action | Owner | Co-admin | Family member | Guest | Viewer | Rentals: manager / staff with properties |
|---|---|---|---|---|---|---|
| See doors, unlock, lock, status, sync time | all | all | shared doors (default: all), as long as “Family members may unlock” is on | only the assigned doors, only until “Access until” | no doors | only the doors of their own properties |
| Add, rename, remove a lock, auto-lock, policies, LED, Wi-Fi, reset gateway | ✓ | ✓ | — | — | — | — |
| Codes, cards, fingerprints, passage mode, journal, sound/screen | ✓ | ✓ (codes masked) | — | — | — | — |
| “Show full codes”, the lock's admin code | ✓ | — | — | — | — | — |
| See a booking's door code, “New door code” | ✓ | ✓ | — | — | — | manager (co-admin with properties) ✓, staff — |
| History “Who did what” | everything | everything | own entries only (unless the door history is shared) | own only | — | own only |
| Offline key in the iPhone app valid | 24 h | 24 h | 8 h | 2 h, never beyond “Access until” | — | 8 h |
Plans: The Doors section is included in every plan as soon as a LockHub is in the home; there is no limit on locks other than the plan's device limit (see Tarif & Abrechnung (DE)). How many people and guests may be invited is under Familie → Rollen und Tarife (DE). Guest codes from the rentals need a property under Rentals (Rental plan, or 1 property in Family / Power / Unlimited) – see Rentals for hosts.
Over the cloud the gateway shows only the last two digits. Only the owner of the home can see all digits for 60 seconds with Show full codes; co-admins always see codes masked. Child codes are shown in plain text to owners and co-admins on the page Familie → Kinder (DE); guest door codes are in the booking under Rentals.
As a family member or guest you see only doors that have been shared with you under Family and for which “Family members may unlock” is on. Viewers see no doors at all. In the rentals, managers and staff see only the doors of their properties. As a guest the visibility ends with “Access until”. Ask the owner or use Ask for more access on Familie (DE).
Lists and the journal are fetched from the lock over Bluetooth – 5 to 30 seconds, the server waits up to 45 seconds. That is normal. If “The gateway got the command; the answer comes later” appears, simply press Refresh.
Yes. Permanent, time-limited and one-time codes, cards and fingerprints live in the lock and are checked there – the time window too. Only weekly codes need the gateway: without the gateway they expire with their current window. Unlocking doors remotely does not work without the gateway; the iPhone app unlocks over Bluetooth with an offline key (owners 24 h, members 8 h, guests 2 h).
“Confirm unlocking (Face ID / code)” is switched on for this lock (shield symbol). The owner or a co-admin can change that in the gateway panel under More. Anyone without a second factor yet sets it up under Settings → Security.
For fixed times every week: weekly code. For a period: time-limited code. For one visit: one-time code. If the person should unlock with their phone instead, invite them as a guest with “Access until” (Familie → einladen (DE)). In the rentals, cleaners get their code automatically per cleaning task.
Press Write now in the booking and read the state per door. If it says “error (gatewayUnreachable)”, the gateway is offline (Gateway offline); for “lock_out_of_range” wake the lock (Range); for “code_rejected” delete old codes (Memory full). If it does not work in time, tell the guest about the key safe or a mechanical key – or create a time-limited code by hand on site as soon as the lock is reachable.
Yes, with the passage mode: during the set hours the lock does not lock.
The last known state is older than 30 minutes. The lock reports only on events; with Check (tap on the dial) you fetch the current state.
Remove lock resets the lock: all codes, cards and fingerprints in the lock are deleted. Only “Forget without reset” leaves the lock unchanged – it then keeps an admin without keys and needs a hardware reset at the door.
While it is still online: add the network, then forget the old one. If it is already offline: set-up over Bluetooth as in the LockHub manual (DE) (the gateway shows blue after more than 10 minutes without a network).