FirePanel¶

Overview¶

Fire alarm control panel function for panel-level EPS/FACP state: alarm summary, acknowledge, reset, day/night mode, alarm blocking, tests, service access, and external configuration.

Use FirePanel on the root panel or master node. Use FirePoint for per-address state and FireDetector for physical detector behavior.

Added in: PQ Framework 2.3
Namespace: Pq.Adapters.Framework

When to Use¶

Fire alarm control panels / EPS ustredny
Panel or master nodes that report summary alarm/trouble state
Panel-level reset, acknowledge, day/night mode, or service mode
Fire group test lifecycle reported by the panel

States¶

State	Status id	Description
`PanelDay`	`fire.panel.day` (hidden)	Panel is in day mode
`PanelNight`	`fire.panel.night`	Panel is in night mode
`Alarm`	`fire.alarm`	Fire alarm active
`AlarmGeneral`	`fire.alarm.general`	General fire alarm active
`AlarmSection`	`fire.alarm.section`	Section alarm active
`AlarmConditional`	`fire.alarm.conditional`	Conditional fire alarm active
`Prealarm`	`fire.prealarm`	Fire pre-alarm active
`Trouble`	`fire.trouble`	Fire trouble active
`AlarmBlocked`	`fire.alarm.blocked`	Alarm escalation/signaling blocked
`Test`	`fire.test`	Fire test active
`Maintenance`	`lifecycle.maintenance`	Service/configuration mode
`Disabled`	`fire.disabled`	Part of the installation is bypassed

PanelDay is the hidden default state: SetPanelDay(ct) publishes no status string, so a panel in day mode reports the function as cleared.

Disabled is status only. The disabled address publishes its own pq.event.fire.address.disabled, so FirePanel has no matching action.

Actions¶

Action	Target State	Event
`FirePanelGeneralAlarm(timestamp)`	`AlarmGeneral`	`pq.event.fire.alarm.general`
`FirePanelSectionAlarm(timestamp)`	`AlarmSection`	`pq.event.fire.alarm.section`
`FirePanelConditionalAlarm(timestamp)`	`AlarmConditional`	`pq.event.fire.alarm.conditional`
`FirePanelPreAlarm(timestamp)`	`Prealarm`	`pq.event.fire.prealarm`
`FirePanelTrouble(timestamp)`	`Trouble`	`pq.event.fire.trouble`
`FirePanelTroubleCleared(timestamp)`	no state change	`pq.event.fire.trouble.cleared`
`FirePanelAlarmAcknowledged(timestamp)`	no state change	`pq.event.fire.alarm.acknowledged`
`FirePanelAlarmBlocked(timestamp)`	`AlarmBlocked`	`pq.event.fire.alarm.blocked`
`FirePanelAlarmUnblocked(timestamp)`	no state change	`pq.event.fire.alarm.unblocked`
`FirePanelReset(timestamp)`	no state change	`pq.event.fire.panel.reset`
`FirePanelDayMode(timestamp)`	`PanelDay`	`pq.event.fire.panel.day_mode`
`FirePanelNightMode(timestamp)`	`PanelNight`	`pq.event.fire.panel.night_mode`
`FirePanelTestStarted(timestamp)`	`Test`	`pq.event.fire.test.started`
`FirePanelTestCompleted(timestamp)`	no state change	`pq.event.fire.test.completed`
`FirePanelExternalConfigurationStarted(timestamp)`	`Maintenance`	`pq.event.fire.panel.external_configuration.started`
`FirePanelExternalConfigurationCompleted(timestamp)`	no state change	`pq.event.fire.panel.external_configuration.completed`
`FirePanelServiceAccess(timestamp)`	`Maintenance`	`pq.event.fire.panel.service_access`

YAML Example¶

device_types:
  - type_id: FirePanel
    name: "Fire Panel"
    functions:
      FirePanel:
      ConnectionBase:
      Power:
      HistoryPoll:
      StatusPoll:

Notes¶

FirePanel is panel-level. Do not attach it to every detector.
For a vendor alarm-acknowledge event, call FirePanelAlarmAcknowledged.
Preserve vendor event codes as optional parameters when useful, e.g. rawEventNumber.