Apsardzes apgaismojuma automatizācija ar KNX: trauksmes GA → DALI aina un CCTV koordinācija

KNX trauksmes GA shēma — perimetra apsardzes zonas

Zone 1 — Garden perimeter (north):
  Alarm GA: 11/0/0   DPT 1.005   Alarm bit
  Source:   Binary input I1 ← PIR Optex BX-80N dry contact
  Actions on GA 11/0/0 = 1 (alarm):
    → DALI Group 1 → Scene 8 (100% brightness)
    → BewO email: "Zone 1 Garden alarm activated"
    → CCTV PTZ Camera 1 → Preset 3 (north garden view)
    → 15-minute hold timer start (GA 11/0/0 remains 1)

Zone 2 — Entrance gate:
  Alarm GA: 11/0/1   DPT 1.005
  Source:   Binary input I2 ← gate PIR or CCTV motion relay
  Actions on GA 11/0/1 = 1:
    → DALI Group 3 → Scene 8 (100% brightness)
    → BewO email: "Zone 2 Entrance alarm activated"
    → CCTV PTZ Camera 2 → Preset 1 (entrance gate view)

Zone 3 — Parking area (south):
  Alarm GA: 11/0/2   DPT 1.005
  Source:   Binary input I3 ← parking PIR coverage
  Actions on GA 11/0/2 = 1:
    → DALI Group 2 → Scene 8 (100% brightness)
    → BewO email: "Zone 3 Parking alarm activated"
    → CCTV PTZ Camera 3 → Preset 2 (parking area view)

CCTV PTZ iepriekš iestatīta komanda caur Home Assistant KNX tiltu

Integration path:
  KNX Alarm GA → Home Assistant KNX integration → HA automation
  HA automation → ONVIF service call → PTZ camera preset

Home Assistant automation (simplified):
  trigger:
    - platform: state
      entity_id: binary_sensor.knx_alarm_zone1
      to: "on"
  action:
    - service: onvif.ptz
      target:
        entity_id: camera.perimeter_ptz_1
      data:
        preset: "3"   # Preset 3 = North garden view

Alternative: ARISTO BewO HTTP action on alarm GA
  BewO alarm object GA 11/0/0:
    On alarm trigger: HTTP GET
    URL: http://<camera-IP>/cgi-bin/ptz.cgi?action=goto&preset=3
    Method: GET (no authentication for internal network)

PTZ preset programming (HIKVISION example):
  Camera webUI → Configuration → PTZ → Patrol Settings
  Preset 1: Entrance gate coverage (pan 0°, tilt -15°, zoom 2×)
  Preset 2: Parking area wide (pan 90°, tilt -20°, zoom 1×)
  Preset 3: North garden (pan 180°, tilt -10°, zoom 1.5×)

ARISTO BewO trauksmes konfigurācija

BewO Alarm Module → Add alarm object:

Object name:    "Zone 1 – Garden perimeter"
Group address:  11/0/0
DPT:            DPT 1.005
Alarm value:    1 (alarm active when GA = 1)
Priority:       High (immediate notification)

Notification settings:
  Email to:     security@building.com, fm@building.com
  SMS to:       +44 7xxx xxx xxx (if SMS gateway configured)
  Subject:      "ALARM: Zone 1 – Garden perimeter activated"
  Body:         "KNX security alarm triggered at [timestamp].
                 Zone: Garden perimeter (north façade).
                 DALI floodlights activated at 100%.
                 Please verify via CCTV camera 1, preset 3."

Acknowledgement: BewO requires email reply or BewO app
  acknowledgement to clear alarm log entry.
  Alarm remains active in log until acknowledged.

Alarm history: BewO stores 12-month alarm log with timestamp,
  zone name, and acknowledgement record for security audit trail.

KNX apsardzes grafiks un manuāla vadība

KNX time controller (MDT SCN-TC8.01):
  Armed GA: 11/5/0   DPT 1.001   (1=armed, 0=disarmed)

Automatic schedule:
  Monday–Friday:
    07:45  → GA 11/5/0 = 0 (disarm, staff arriving)
    18:30  → GA 11/5/0 = 1 (arm, office closing)
  Saturday–Sunday:
    00:00  → GA 11/5/0 = 1 (armed all day)

Alarm logic gate (MDT Logic Module):
  Input 1: GA 11/5/0 (Armed = 1)
  Input 2: GA 11/0/x (Zone alarm bit)
  Output:  AND gate → alarm action (DALI + email + PTZ)

  When disarmed (GA 11/5/0 = 0):
    → AND output = 0 regardless of PIR state
    → No alarm actions triggered
    → PIR binary inputs still visible in ETS6 Group Monitor

KNX keypad override (Gira 2-fold push-button):
  Button 1 long press: GA 11/5/0 = 0 (manual disarm, 1-hour override)
  Button 2 long press: GA 11/5/0 = 1 (manual arm ahead of schedule)

Drošs pret atteici: DALI un KNX barošanas zuduma projektēšana

DALI driver system failure level (SFL) programming:
  Configure via DALI commissioning tool (DaliConnect or Osram OPTOTRONIC):
  Goto 254 (100%) on DALI bus fail  → security zone drivers
  Goto 51  (20%)  on DALI bus fail  → non-security zones (energy saving)

  DALI bus fail = no valid DALI commands for >500ms
  → driver reverts to programmed SFL automatically

KNX power-loss protection for security zone supply:
  Security zone floodlights: fed from dedicated MCB
  UPS backup: 48VDC UPS → 230VAC inverter → security zone MCB
  Autonomy: 2 hours at 100% load (size UPS to total floodlight W)

Thermal actuator fail-safe (for non-DALI zones):
  Use NC (normally closed) thermal actuator for security circuits
  KNX actuator deenergised = contacts closed = lights ON
  → On KNX power loss: lights turn ON automatically
  → Normal operation: KNX commands actuator open (lights OFF)
  → Inverted logic: KNX sends 0 to switch lights ON (NC actuator)

Note: This design is counterintuitive for programmers —
  document clearly in ETS6 project: "Security Zone Output:
  KNX 0 = Light ON, KNX 1 = Light OFF (NC actuator logic)"