Compatibility Guide
Hafele Dialock Hotel Key Cards
Compatibility Guide
Quick answer
Procurement-grade compatibility reference for Hafele Dialock hotel and serviced-apartment estates. Maps the DT 100 to DT 750 door terminals, the WT and FT wall and furniture terminals, and the EFL and LL lockers to the chip families they accept (Tag-it HF-I, MIFARE Classic EV1, MIFARE DESFire EV2, LEGIC), walks the Dialock Software Generation 2 stack (SW 200 / SW 300 / SW 400), covers the Dialock Smartphone Key BLE module, and explains why Hafele's single-credential door + furniture + locker integration is the genuine differentiator versus Saflok and VingCard.
- Identify the door terminal model and the reader-head chip set first. DT 510, DT 700, DT 710 and DT 750 ship with a multi-chip reader that accepts Tag-it HF-I (ISO/IEC 15693), MIFARE Classic EV1 and MIFARE DESFire EV2 on the same antenna.
- Match the back-end (Dialock Software Generation 2 — SW 200 Control / SW 300 Hotel / SW 400 Professional) and the encoder (ES 110 encoding station + MDU 110 Mobile Data Unit) to the chip family and operational model rather than the other way around.
- Hafele has no public CVE in NVD as of May 2026 — a quotable trust signal when the wider hospitality lock category has high-profile disclosures (Saflok / Unsaflok in 2024). Treat that as a procurement-narrative advantage, not a reason to skip security validation.
- Prove opening, encoder round-trip and PMS extend/replace/cancel on the actual door terminal model before scaling artwork or premium materials. Hafele's furniture-lock integration means a single Dialock card SKU usually has to work on door, locker and minibar locks simultaneously.
At a glance
Use these short answers to decide whether this page matches the project before moving into the detail.
Best fit
Hotels and serviced apartments running Hafele Dialock door + furniture + locker locks on one credential. European retrofit programmes using DT 510 / DT 510 B Europrofile...
What to send
Door terminal model (DT 100 / DT 200 / DT 510 / DT 700 / DT 710 / DT 750), furniture terminal model (FT 120 / FT 200 / FT 200 CAP) and locker model (EFL 1/3/6/30/50/51 o...
Next step
Ready to move forward? Start your inquiry to get specific answers for this project.
Check Dialock card compatibility- Testing checklist
-
- Validate opening on the door terminal AND on at least one furniture or locker terminal before approving a card SKU for the estate.
- Confirm encoder round-trip (issue, extend, replace, cancel) on a live PMS reservation through the Dialock HMS connector.
- Log the door terminal firmware and the Dialock Software build for every tested unit before going to production.
- If LEGIC stock is in play (common in Europe), validate the LEGIC chip independently because Hafele's spec language documents LEGIC as sensitive to moisture and wetness.
Hafele Dialock terminal taxonomy — DT, WT, FT, EFL and LL
Hafele's Dialock platform is engineered in Nagold, Germany, and covers four distinct device categories under one credential: door terminals (DT series), wall terminals (WT series), furniture terminals (FT series) and electronic furniture locks (EFL) plus locker locks (LL). A Dialock card or key fob can be programmed to work across all of them simultaneously, which is the single largest functional differentiator versus Saflok, VingCard, SALTO and Onity — all of which are predominantly door-only.
Procurement teams refreshing a Dialock card stack therefore need to understand the full terminal mix at the property, not just the room-door model. A property with DT 700 room doors plus FT 120 minibar locks plus EFL 50 staff lockers plus LL 300 spa lockers needs every card SKU to work on all four. The good news: in practice, the same MIFARE DESFire EV2 (or Tag-it HF-I, or LEGIC) inlay covers the entire ecosystem once the encoder is configured correctly.
The table below maps the most common Dialock terminals to their default credential set and recommended encoder pairing. Verify the door terminal firmware before locking in a chip — DT 510 / 700 / 710 / 750 reader heads have been re-spun to extend chip support without a model-name change.
| Dialock terminal | Category | Native credentials | Typical encoder / programmer | Notes |
|---|---|---|---|---|
| DT 100 / DT 200 | Door terminal (entry) | Tag-it HF-I + MIFARE Classic EV1 | MDU 100 / MDU 110 + PK | Earlier escutcheon-style door terminals. |
| DT 400 | Door terminal (back-of-house, fire-door variant) | MIFARE Classic EV1 (+ optional LEGIC) | MDU 110 + PK + ES 110 | Common on back-of-house doors and 20-minute fire doors when paired with DT 750 escutcheons. |
| DT 510 / DT 510 B / DT 510 D-DZ | Door terminal (Europrofile cylinder retrofit) | Tag-it HF-I + MIFARE Classic EV1 + MIFARE DESFire EV2 | MDU 110 + ES 110 | European retrofit cylinder. D-DZ = double-cylinder; FH suffix = without thumbturn. Strong fit for serviced apartments. |
| DT 600 | Door terminal (intermediate hospitality) | Tag-it HF-I + MIFARE Classic EV1 + DESFire EV2 | MDU 110 + ES 110 | Hospitality predecessor to DT 700; multi-chip reader head. |
| DT 700 / DT 710 | Door terminal (hospitality flagship) | Tag-it HF-I + MIFARE Classic EV1 + MIFARE DESFire EV2 + optional Dialock Smartphone Key (BLE module add-on) | MDU 110 + ES 110 | 1,000 user keys and 1,000 audit-trail entries per lock; real-time clock; BLE retrofit via SPK module (DT 710 SPK variant ships with BLE). |
| DT 750 | Door terminal (premium / fire-rated) | Tag-it HF-I + MIFARE Classic EV1 + DESFire EV2 + Dialock Smartphone Key | MDU 110 + ES 110 | Approved for 20-minute fire doors. Premium hotel and assisted-living deployments. |
| WT 100 / WT 200 / WT 210 | Wall terminal (online wall reader) | Same multi-chip reader as the door terminals | MDU 110 + ES 110 | Used for elevator dispatch, pool, gym, parking and other zone access. |
| FT 120 / FT 200 / FT 200 CAP | Furniture terminal (minibar, drawer, safe) | MIFARE Classic EV1 + Tag-it HF-I | MDU 110 + ES 110 | Up to 228 keys per terminal. CAP variant has an energy-storage capacitor for ~6-day RTC retention through a power loss. |
| EFL 1 / EFL 3 / EFL 6 / EFL 30 / EFL 50 / EFL 51 | Electronic furniture lock | MIFARE Classic EV1 + Tag-it HF-I | MDU 110 + ES 110 | Cabinet, locker and drawer locks. Same credential as the door terminal — single-card programme across all four device families. |
| LL 300 LockerLock | Locker lock (gym, spa, staff) | MIFARE Classic EV1 + Tag-it HF-I | MDU 110 + ES 110 | Wellness-area and staff locker variant. Common pairing in serviced apartments and gyms. |
Chip-family compatibility per generation
Dialock's multi-chip reader heads accept three concurrent chip families on the same antenna: Tag-it HF-I (ISO/IEC 15693), MIFARE Classic EV1 and MIFARE DESFire EV2. LEGIC support is available on European installs as a separate reader-head order option. This section summarises which chip drops in cleanly for which terminal generation.
- Tag-it HF-I (ISO/IEC 15693, 13.56 MHz vicinity standard) — the historical Dialock credential, originated by Texas Instruments. 64x32-bit blocks of memory, 64-bit UID. Still in active use across DT 700 / 710 / 750 reader heads and across FT, EFL and LL terminals.
- MIFARE Classic EV1 (ISO/IEC 14443A, 13.56 MHz) — added to the multi-chip reader for properties moving away from Tag-it. 1 KB memory, 16 sectors. Crypto-1 is broken industry-wide so Classic is positioned as a migration step, not a long-term target.
- MIFARE DESFire EV2 — the recommended target for new Dialock estates. AES-128 authenticated sessions, multi-application memory layout, supported on DT 510, DT 600, DT 700, DT 710 and DT 750. DESFire EV3 stock is also wire-compatible thanks to NXP's EV2/EV1 backwards-compatible default configuration.
- LEGIC (advant / prime) — common on Hafele installs in Germany, Switzerland, Austria and other DACH-region serviced apartments. Hafele's spec language flags LEGIC inlays as more sensitive to moisture and wetness than MIFARE-family inlays; verify the use environment before specifying LEGIC for poolside or outdoor terminals.
- Magstripe — not native on Dialock. The Dialock platform is RFID-only; properties migrating from a magstripe predecessor should not expect a dual-interface card option.
- 125 kHz proximity (HID Prox / EM4100) — not native on Dialock hospitality terminals. Appears only on hybrid access-control integrations that pair Dialock with a separate HID reader head.
Dialock Software Generation 2 and the encoder stack
Hafele packages its back-end as Dialock Software Generation 2 in three SKUs. Picking the right tier is a procurement decision driven by property size and the number of access points; it does not affect card-stack chip selection. The encoder hardware is the same across all three software tiers.
- SW 200 Control — entry-tier back-end. Up to a handful of access points; suitable for small serviced-apartment buildings or short-stay properties.
- SW 300 Hotel — the hospitality tier with PMS connector support, audit trails, guest-key issuance workflow and full multi-device (door + furniture + locker) credential management.
- SW 400 Professional — the largest tier; suits multi-property operators or large estates with extensive online wall-terminal networks.
- ES 110 Encoding Station — the desktop encoder. USB to the front-desk PC; writes Tag-it, MIFARE Classic and DESFire credentials onto cards or key fobs.
- MDU 100 / MDU 110 Mobile Data Unit — handheld programmer used by engineering staff to commission terminals and transfer the locking plan to the lock. LCD interface, five-language UI, USB and IR. The MDU 110 supersedes the MDU 100.
- PK (Programming Key) — a configuration credential used to enable engineering operations on individual terminals (open-time configuration, access-list refresh).
- Dialock HMS — the PMS-side connector that bridges Dialock Software Generation 2 to OPERA, Mews and other PMS platforms. Runs on the same PC as the PMS client and the ES 110 encoder.
Mobile Access — Dialock Smartphone Key and BLE retrofit
Dialock's mobile-access track is more conservative than Saflok or SALTO. Hafele relies on BLE add-on modules retrofitted into existing door terminals plus a first-party smartphone app, with named partner integrations rather than native Apple Wallet or Google Wallet support.
- Dialock Smartphone Key — Hafele's BLE mobile-key offering. Implemented as an add-on BLE module retrofitted into DT 700 / 710 / 750 terminals (the DT 710 SPK variant ships with the BLE module already installed).
- My Dialock Manager — the Android commissioning app (package id `de.sphinxelectronics.terminalsetup`). Used by engineering staff for on-site provisioning of door terminals.
- hotelbird — a named third-party mobile check-in partner. Real-world deployments include IntercityHotel Brunswick, IntercityHotel Duisburg and Steigenberger Munich.
- straiv — hotel-tech integration partner, paired with Dialock in some IntercityHotel and Steigenberger deployments for mobile check-in and key issuance.
- Apple Wallet and Google Wallet — not natively supported on Dialock as of May 2026 per the publicly available material. Properties wanting wallet keys should confirm directly with Hafele before committing; this is the one area where Saflok and VingCard currently have a clearer mobile track.
- Mobile-only operating models still need a card-stack baseline. ADA accessibility, mobile-device failures, walk-in guests and front-desk overrides all require a backup physical card.
PMS integration — OPERA, Mews, Apaleo, Protel via Dialock HMS
Dialock integrates with hospitality PMS platforms through the Dialock HMS connector application, which sits between the PMS and the Dialock Software Generation 2 + ES 110 encoder. Compatibility is driven by the HMS connector version, not by card chip; the card payload structure is fixed once the HMS is configured.
- Oracle OPERA — supported via OHIP for OPERA Cloud and via the legacy serial interface for OPERA 5 on-premise. The Dialock HMS must be installed alongside the PMS client.
- Mews — Mews documents the Hafele Dialock integration as a verified pairing. Staff cut keys directly in Mews Operations once Dialock HMS and the Mews Open API are co-installed on the front-desk PC.
- Apaleo — listed on the Apaleo Store as an integrated partner; common pairing for cloud-native independents.
- Protel — supported through Dialock HMS on protel.I/O.
- Cloud-based PMS platforms rely on the Dialock HMS connector running locally on the front-desk PC to bridge the cloud PMS to the USB encoder. The connector must run on the same workstation as the encoder.
Common field failure modes
Field failures on Dialock estates follow a predictable pattern. Understanding where the break usually happens shortens the troubleshooting cycle and prevents unnecessary card replacements.
- FT 120 / FT 200 furniture terminal not opening after a guest check-in. Usually traces to the credential not being provisioned for the minibar / safe device class — re-issue the card through Dialock HMS with the correct device-class flag set.
- DT 700 / 710 reader head accepts MIFARE Classic but not DESFire EV2 stock. The reader head is on a pre-2017 firmware line that pre-dates DESFire support; firmware update via MDU 110 rather than card change.
- LEGIC card intermittent reads after pool exposure. LEGIC inlays are sensitive to moisture; replace with a sealed PVC card or switch to MIFARE DESFire EV2 for poolside terminals.
- Encoder ES 110 enumerates but Dialock Software rejects card writes. Dialock HMS connector and Software Generation 2 build are out of sync; reinstall HMS to match the Software build.
- FT 200 (without CAP) loses real-time clock after a long power outage. Specify FT 200 CAP for properties that need RTC survival through outages of more than 24 hours.
- Tag-it HF-I cards from one batch read on DT 700 but not on FT 120 furniture terminals. Verify the FT 120 is on a firmware build that recognises the Tag-it AFI / DSFID fields used by the property; an MDU 110 firmware push usually resolves it.
Card material and thickness constraints
Dialock reader heads tolerate standard hotel card stock without surprises. The constraints to plan around are mostly material-related rather than thickness-related.
- Standard ISO/IEC 7810 ID-1 thickness (0.76 mm ± 0.08 mm) is the safe default across DT, WT, FT, EFL and LL terminals.
- Thicker cards (1.0–1.2 mm) — premium PVC or wood-effect cards — read reliably on the multi-chip reader heads. Pilot a production-thickness sample before committing to a full order.
- Wood and bamboo cards with a MIFARE DESFire EV2 inlay read well on DT 600, DT 700 / 710 / 750. Less validated on the legacy DT 100 / 200 reader heads.
- Metal-edge or anti-metal cards are not recommended for Dialock; the shielding detunes the antenna and produces intermittent reads on the multi-chip reader head.
- LEGIC inlays should be specified in sealed PVC bodies for poolside, spa or outdoor terminal use — Hafele's spec language documents LEGIC as more moisture-sensitive than MIFARE.
- Key fobs (KT key tag, 917.64.093 in Hafele's catalog) are common for EFL 50 / 51 furniture locks; the form factor reads on the same multi-chip reader as the cards.
What to validate before scaling
A Dialock pilot should exercise both the hardware path (chip, antenna, reader on door AND furniture AND locker terminals) and the operational path (encoder, Dialock HMS connector, PMS, front-desk workflow). Scaling before both paths are proven is the most common source of pilot regret.
- Test one baseline card on the door terminal, one furniture terminal and one locker terminal before approving a card SKU for the estate. Dialock's single-credential ecosystem is its biggest advantage — also its biggest test surface.
- Run a full check-in, extend, re-encode and cancel cycle on a live PMS reservation through Dialock HMS to surface connector edge cases.
- Log the door terminal firmware (via MDU 110), the Dialock Software Generation 2 build and the Dialock HMS connector version for every tested unit.
- If LEGIC stock is in scope, validate it against pool, spa or outdoor terminals if any exist in the property.
- Plan a small (100–200 card) first production batch before scaling to the full property order; most field failures show up in the first 30 days of live issuance.
Useful next pages
Use these linked product, guide and comparison pages to keep the next click specific and practical.
Card products that ship on Dialock
Hotel card SKUs that the Dialock multi-chip reader heads accept. MIFARE DESFire EV2 / EV3 for new estates; Tag-it HF-I or MIFARE Classic on legacy estates with a documented migration plan.
Related guides and comparisons
Deeper reading for the chip-family, encoding and material decisions that usually follow the Dialock compatibility question.
Related editorial
Background reading for teams that want to understand the Dialock ecosystem before the first sample conversation.
Platform references
Hafele Dialock product references that anchor the platform discussion before a sample request is submitted.
FAQ
How do I identify the Hafele Dialock terminal model before ordering cards?
Three indicators usually settle it: the visible model badge on the door terminal (DT 700, DT 710 or DT 750 = current hospitality flagships with multi-chip readers; DT 510 = European cylinder retrofit; DT 100 / 200 = earlier escutcheons), the Dialock Software Generation 2 tier installed at the property (SW 200 / 300 / 400), and the firmware build that the MDU 110 reads from any individual terminal. If all three are unclear, send a current guest card sample to the supplier for an inspection read before committing to a production chip.
Can I put MIFARE DESFire EV3 cards on a Dialock estate that has DT 510 / 600 / 700 terminals specified for DESFire EV2?
Yes. DESFire EV3 ships in a factory default that is wire-compatible with EV2 and EV1, per the NXP MF3D(H)x3 datasheet, so an EV3 stock can serve an estate originally specified for EV2. Validate the round-trip on a small sample before committing to bulk orders, especially on older DT 700 firmware lines that were originally written for EV1.
Does Hafele Dialock have any public security disclosures or CVEs?
As of May 2026, the NIST National Vulnerability Database has no public CVE entry for Hafele Dialock. That is a favourable trust signal — particularly when compared to the dormakaba Saflok platform, which had a high-profile disclosure in 2024 (Unsaflok / CVE-2024-29916). However: no public CVE is not the same as no vulnerability. Properties should still follow standard procurement diligence — confirm the Dialock Software Generation 2 build is current, verify door terminal firmware via MDU 110, and migrate any legacy MIFARE Classic stock to DESFire EV2 / EV3 to retire the industry-wide Crypto-1 surface.
What is the difference between SW 200 Control, SW 300 Hotel and SW 400 Professional?
SW 200 Control is the entry tier (small properties, limited access points). SW 300 Hotel adds the hospitality workflow — PMS connector support, guest-key issuance, audit trails, full multi-device credential management across door, furniture and locker terminals. SW 400 Professional is the largest tier (multi-property operators, large estates with extensive WT online wall-terminal networks). The card-stack assumptions (chip family, encoder model, PMS pairing) are the same across all three tiers; only the operating scale differs.
What is the difference between MDU 100 and MDU 110?
The MDU (Mobile Data Unit) is Hafele's handheld programmer used by engineering staff to commission terminals and push the locking plan to individual locks. The MDU 110 supersedes the MDU 100, with an updated LCD interface, five-language UI and USB / IR connectivity. Properties on current Dialock Software Generation 2 builds should standardise on the MDU 110. The encoder hardware (ES 110) and the card stock are unaffected by the MDU revision.
Will premium-material cards (1.0 mm wood or bamboo) read reliably on Dialock?
On DT 600, DT 700, DT 710 and DT 750 multi-chip reader heads, yes — they are tuned for card stacks up to roughly 1.2 mm. On older DT 100 / 200 reader heads, premium thickness is less validated; pilot a production-thickness sample on the actual door terminal model before ordering a full batch.
Does Dialock support Apple Wallet and Google Wallet keys?
Not natively as of May 2026 based on the publicly available material. Hafele's mobile-access track centres on Dialock Smartphone Key (BLE module add-on; the DT 710 SPK variant ships with BLE) plus partner integrations such as hotelbird and straiv. Confirm wallet support directly with Hafele if it is a hard procurement requirement; this is the area where Saflok and VingCard currently have a clearer mobile track.
What PMS systems are certified on Dialock?
Oracle OPERA (5 and Cloud via OHIP), Mews, Apaleo, Protel and a tail of regional PMS platforms are integrated against Dialock Software Generation 2 through the Dialock HMS connector. Mews specifically requires Dialock HMS and the Mews Open API co-installed on the front-desk PC to allow key-cutting directly from Mews Operations. The limiting factor is usually the Dialock HMS connector version, not the PMS itself.
Sources & references
Primary standards, OEM datasheets and regulatory documents cited by this article. All URLs were verified on the access date shown below.
- Hafele Dialock Access Control Systems (official hub)
Authoritative product-line reference; touchless RFID + BLE positioning.
- Hafele Dialock FAQs (official)
Source for the supported card-tech list — 'Legic, MIFARE Classic EV1, Tag-it-ISO' — and PMS-integration claims.
- Hafele Dialock RFID Access Management brochure (PDF)
Component overview — MDU, PK, ES 110 roles; multi-chip reader head.
- Hafele DT 700 mounting and operating manual
Source for DT 700 capacity numbers — 1,000 user keys, 1,000 audit-trail entries, real-time clock.
- Hafele DT 510 B electronic profile cylinder spec
Confirms DT 510 B supports Tag-it HF-I + MIFARE Classic EV1 + MIFARE DESFire EV2 simultaneously on the same cylinder.
- Hafele DT 750 product page (GoKeyless)
DT 750 fire-rated approval (20-minute fire door) and chip support.
- Hafele Dialock Software Generation 2 (SW 200 / SW 300 / SW 400)
Three software tiers and access-point / encoder licensing model.
- Hafele Dialock CONTROL software manual (PDF)
Software architecture and PMS-side connector role.
- Hafele MDU 110 Mobile Data Unit (product page)
Confirms MDU 110 role, five-language UI, USB and IR connectivity.
- Hafele ES 110 Encoding Station (product page)
Encoder model and USB interface to front-desk PC.
- Hafele Smartphone Hotel Key (BLE)
Dialock Smartphone Key BLE retrofit and hotelbird integration.
- My Dialock Manager (Android app)
Commissioning app package id.
- Mews — Hafele Dialock integration article
Mews integration requires Dialock HMS and Mews Open API co-installed on the same PC.
- Apaleo Store — Hafele Dialock app listing
PMS integration partner listing.
- Hafele IntercityHotel 2.0 case study (Brunswick)
Real-world deployments — IntercityHotel Brunswick / Duisburg / Steigenberger Munich with hotelbird mobile check-in.
- Texas Instruments Tag-it HF-I IC datasheet
Authoritative reference for Tag-it HF-I — ISO/IEC 15693, 13.56 MHz, 64x32-bit memory blocks, 64-bit UID.
- NXP MIFARE DESFire EV3 datasheet (MF3D(H)x3)
EV3 air interface (ISO/IEC 14443-4); AES-128 authenticated sessions; EV2/EV1 backwards-compatible default.
- NXP MIFARE Classic EV1 1K datasheet (MF1S50YYX_V1)
Classic 1K sector/block layout used in Dialock multi-chip reader heads.
- NIST National Vulnerability Database — Hafele Dialock search (verification)
Verifies no public CVE for Hafele Dialock as of May 2026.
- RIBA Journal — Dialock for hotel and leisure
UK A&D trade-press positioning for hospitality and leisure-sector specifications.
Proud Tek is a Shenzhen-based RFID & NFC manufacturer supplying hotel chains, transit operators, event venues and retail brands worldwide. Every order includes free samples, RF testing and dedicated project support.
Get a Quick Quote
Tell us about your project and we'll respond within one business day. Fields marked (asterisk) are required.