Overview
This guide is for properties where dormakaba EVO LZ locks are commissioned in Online (Wi‑Fi) mode, but building Wi‑Fi will be unavailable for ~6 months or so (construction, network cutover, ISP delays, etc.). Refer to ButterflyMX Dormakaba Smart Lock - Property Manager Resources for information on our online or BLE integration.
During this offline window:
- The locks are still Online-mode locks (not offline/BLE mode).
- BLE syncing does not apply in this scenario.
- Your “no-hotspot” access fallback should be Access Codes on Demand (ACOD) and Bluetooth Tap to Unlock via the ButterflyMX mobile app.
Primary references:
- Dormakaba EVO LZ Smart Lock User Guide (can be shared property wide)
- How to Create dormakaba Access Codes on Demand (ACOD) from the ButterflyMX OS
- How to Sync Credentials to dormakaba EVO LZ Smart Lock via Temporary Hotspot
What to expect while locks are offline (no building Wi‑Fi)
Features that will not work (until hotspot/Wi‑Fi is restored)
- Swipe to Open
- Visitor Passes
- Any “live” updates from ButterflyMX OS to the lock (new PINs, removed PINs, new fobs, access group changes, etc.)
What will usually still work
- Existing tenant PINs / admin PIN / admin fobs that were already downloaded to the lock
- Bluetooth Tap to Unlock via the ButterflyMX mobile app
The recommended operating model for a ~6‑month offline period
1) Primary access methods (no hotspot required): Access Codes on Demand (ACOD)
If someone needs access and you don’t want to rely on the lock being online, ACOD is the best tool because:
- It’s generated in ButterflyMX OS by admins
- It does not require the lock to be online (lock just needs power)
- It’s ideal for lockouts, maintenance, vendors, and temporary access
How to generate ACOD (PM/admin workflow):
Practical use during the 6 months:
-
Use ACOD for:
- move-in day access if tenant PIN syncing is uncertain
- vendors/contractors with scheduled windows
- emergency/after-hours access
- lockouts when app-based unlock isn’t available
2) Primary access methods (no hotspot required): Bluetooth Tap to Unlock
If someone needs access and they’re physically at the unit door, Bluetooth Tap to Unlock is a great day-to-day option during an extended offline period because:
- It unlocks the door using a local Bluetooth connection between the user’s phone and the lock (no Wi‑Fi required at the door)
- It’s ideal for residents and staff who already have access assigned in ButterflyMX OS
Important notes:
- Bluetooth Tap to Unlock is an in-person unlock method only (you must be near the lock).
- It does not provide remote unlock, and it does not replace credential syncing. Any new/changed access (new tenant PINs, admin fobs, removals, etc.) still requires the lock to be brought online via hotspot to download updates.
- The lock must have power (dead batteries will prevent all electronic entry methods—use ELPS and replace batteries if needed).
Managing your specific credential types during the offline period
1) Admin PIN / Admin fob changes (adds/removals)
- If the lock is offline, any admin pin changes won’t reach the door until you run a hotspot session.
- For this reason, we strongly recommend sharing the admin pin with essential personnel only.
-
Recommendation:
- Keep your existing Admin PIN/fobs as-is during the offline window if possible.
- If you must rotate or change the admin access pin or fob for any reason, plan a hotspot credential sync session for all locks the same day.
2) Tenant PINs (adds/changes/removals)
- New tenant PINs created/changed in OS will not update at the lock until the lock gets internet again (hotspot).
- Removals are especially important: if you remove a tenant in OS while locks are offline, their old PIN may still work at the door until the next hotspot sync.
Recommendation for 6 months offline:
-
Treat tenant PIN updates as “batch updates”:
- Use ACOD for immediate access needs.
- Run scheduled hotspot sync sessions (example: weekly, biweekly, or monthly) to push accumulated tenant PIN changes to locks.
Manually checking battery levels (recommended cadence)
Best practice: Do a physical battery check on a schedule (e.g., monthly).
Ways to check battery health manually:
- Visual indicator on the lock: A long red LED is a strong indicator the batteries are very low / dead and should be replaced ASAP.
- Test battery level using **4# keypad command and confirming based on LED response:
- This is called out in the dormakaba user guide.
ButterflyMX OS battery level (if/when the lock reconnects): Battery level shown in OS may be stale while offline, but it’s still useful after you do a hotspot session and the lock checks in.
- General battery alert behavior and OS notes here.
Battery maintenance best practices (to prevent lockouts)
- Replace batteries proactively rather than waiting for failures—especially during this 6-month window.
- Keep a small onsite stock of the correct batteries so maintenance can respond quickly.
ELPS device (battery jump) — your backup when batteries are dead
If the lock’s batteries die completely and you can’t get in, dormakaba supports an ELPS battery backup/jump device to temporarily power the lock so you can enter and replace the batteries.
- Keep an ELPS device on-site during the offline period (ideally more than one for larger sites).
- Make sure the ELPS device itself has fresh batteries.
- ELPS is especially important in this scenario because you can’t fall back on remote unlock features while the lock is offline.
Official instructions: How to Use the ELPS Device on your dormakaba EVO Smart Lock
Hotspot workflow (when you need to push queued updates)
Any time you need admin fobs/PINs or tenant PIN updates to actually reach the door, use a temporary hotspot.
Use this step-by-step guide: How to Sync Credentials to dormakaba EVO LZ Smart Lock via Temporary Hotspot
Operational tips for a 6‑month plan
-
Build a repeatable process:
- Make access changes in ButterflyMX OS (admin + tenants)
- Do a “hotspot day” where staff brings a hotspot door-to-door
- Validate a sample of updated PINs at each door
- Consider keeping the hotspot SSID/password consistent for the whole project, so reconnects are easier.
What to do if a resident is locked out during the offline period
Because Swipe to Open and Visitor Passes won’t work while offline, your recommended order of operations should be:
- Try the resident’s existing PIN (if it was already on the lock before the offline period)
- Generate an Access Code on Demand (ACOD) as the primary “no-hotspot-required” access method
- If the lock shows long red LED / no response, use the ELPS device to power the lock temporarily and replace batteries
- After entry is restored, consider scheduling a hotspot sync session soon (to refresh status and apply queued access changes)
FAQ
Q: What’s the best way to grant access without using a hotspot?
A: Use Access Codes on Demand (ACOD). They’re generated in ButterflyMX OS and work at the lock without the lock needing internet. (Guide)
Q: Will Swipe to Open / Visitor Pass work?
A: Not while locks are offline. Those features require the lock to be connected.