Skip to content

fix-medium: send API v2 alarms to the monitor's own server - #56

Merged
SteveGilvarry merged 1 commit into
ZoneMinder:mainfrom
nabbi:fix/v2-alarm-own-server
Oct 25, 2026
Merged

SteveGilvarry merged 1 commit into
ZoneMinder:mainfrom
nabbi:fix/v2-alarm-own-server

Conversation

@nabbi

@nabbi nabbi commented Oct 24, 2026

Copy link
Copy Markdown
Contributor

Impact: fix-medium (alarms on cameras recorded by another server failed in multi-server setups)

Automated PR, tested in a zm-holodeck sandbox. An AI agent (Claude Opus 5.5) reproduced the bug against a disposable
lab (ZoneMinder upstream master 1bdccda40 as two servers on one database, with its CakePHP API v2; simulated
HikVision, Dahua, Axis, Reolink and ONVIF cameras on both), wrote this fix and ran the checks there. Minimal human
review before opening: please review it as you would any contributor's PR.

TL;DR

Fixes #55

🤖 Generated with Claude Code

In a multi-server setup, forcing or cancelling an alarm on a camera that
another server records always went to the server the client logs in to.
ZoneMinder runs zmu there, which can't reach that camera's capture daemon,
so the alarm failed (zmu exit 255) and no event was recorded. Streams and
PTZ already go to each camera's own server; alarms now go to that server's
API too, from the PathToApi the servers list gives.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@SteveGilvarry
SteveGilvarry merged commit 1cf756a into ZoneMinder:main Oct 25, 2026
3 checks passed
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 25, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

API v2: alarms on a camera recorded by another server fail in a multi-server setup

2 participants