Expand a gateway to see its alarms and assigned keypads. Choose Configure alarm to edit that alarm. Refresh reloads discovery without changing devices.

Users and PINs belong to one gateway. Adding an alarm does not automatically give existing users access or include it in Homebridge.

Review access by alarm, then choose Edit access to change a user’s grant. Identity and PIN are shared across the gateway; permissions and limits are specific to each alarm.

The use allowance is shared across that grant’s allowed keypads. API access is separate from physical-keypad access. Red marks disabled, exhausted or expired access. Green means an enabled grant can still be used; a weekly schedule closed right now stays green. A user is red when none of their alarm grants remains usable. Colors do not change the saved Enabled setting.

Select a user to edit their details. Name, PIN and Enabled apply across the gateway; disabling a user blocks their grants without deleting them.

Choose an alarm in the editor to set its permissions, keypads, schedule and shared use allowance. All day on a weekly row allows 00:00–24:00 for that day in the schedule’s timezone. Multiple windows on the same day are allowed; overlapping windows combine. Up to 28 windows per schedule. Re-enabling a user does not refill uses. Refresh beside Uses remaining reloads the user’s saved settings; you’ll be asked before unsaved edits are discarded. Red also marks exhausted or expired grants; a user is red when no alarm grant remains usable. Weekly schedules stay green between their permitted days. This does not change Enabled. Each alarm must retain an unrestricted owner.

Homebridge uses one selected user across its included alarms. The selected identity is shown below the editor. Saving a Homebridge user or PIN change opens a guided update, including any preparation and confirmation required by connected integrations.

Choose an alarm to edit its protection policy. Each keypad has its own failure counter, timer and escalation; different keypads do not add to one counter.

Failures count requests, not complete PIN-entry attempts. The tested keypad can send its first request at digit four and another for each later digit before its light goes out. With threshold six, nine wrong digits in one window can trigger lockout.

Requests while locked do not extend the timer. Reset clears counters and escalation for all keypads on the alarm without changing alarm state; REST/HomeKit requests do not use physical-keypad lockouts.

Set entry delay (time to disarm), exit delay (time to leave) and trigger duration for Stay, Night and Away. Use whole seconds from 0–255; zero removes that interval.

Save while disarmed and keep other alarm controls unused during saving. Timings apply on the next arming; saving does not arm, disarm or move anything.

State and countdown come from deCONZ. An alarm state does not prove a physical siren operated.

Newest entries appear first. Filter by gateway, alarm and source. Automatic refresh starts disabled. Enable refresh updates this view every three seconds; Disable refresh stops those updates. Background collection continues either way. Refresh now loads the latest collected events.

Keep activity for applies to all gateways. Clear logs clears the selected gateway/alarm, including hidden categories. Deleted records and connection gaps cannot be recovered.

Only real activity is recorded. Names identify the accepted credential, not the person; Unknown means a rejected request had no identified user. Submitted requests, deCONZ responses and extension results are separate stages, not separate entries of a PIN. Acceptance does not prove physical completion.

Shows up to 200 matching rows; each history retains at most 5,000 records within its retention period.

Digits alone request disarm. To arm, select Stay, Away or Night before entering a code. The first four digits submit together; later digits submit individually, even after acceptance.

Green light means the entry window is active, not that a code was accepted. It turns on with the first digit, and each digit restarts the five-second timer. When it goes out, the next digit starts a new entry. Fewer than four digits are discarded without sending a request. A/B have no assigned action.

Reset entry clears the digits and light, and selects Disarm for the next code. It sends no command and does not cancel queued or sent requests.

Try demo data uses fictional code 2323, simulated protection and no real requests. Results stay on this page.

Live mode uses REST permissions, not physical-keypad restrictions or lockouts. A valid Disarm PIN requests opening of the selected garage; a rejected PIN requests closing. One configured garage is selected automatically. With multiple garages, choose the garage on this page. Stale requests are dropped; uncertain results are not retried. Request results do not confirm physical completion.

Start capture, mark each intended attempt, then use the physical keypad. Stop and copy the output when finished. Markers do not send commands; browser-keypad REST requests are not captured here.

Capture includes timing, anonymous event labels and lockout details, without PINs, names, keys or device addresses. Different event IDs do not prove separate PIN entries; Zigbee sequence numbers are unavailable.

Capture stops after ten minutes and retains up to 200 rows in broker memory until cleared, replaced or restarted.