1. Install
a) Same box (ZM and gateway together) One install, with the serve extra:
sudo /opt/zoneminder/venv/bin/pip install --force-reinstall --no-deps \
"pyzm[serve] @ git+https://github.com/ZoneMinder/pyzmNg.git@master"
b) Separate boxes ZM box — client only, no extra:
| {"ts": "2026-04-30T02:00:51Z", "level": "INFO", "method": "GET", "path": "/api/orders/1292", "status": 200, "latency_ms": 90, "ip": "10.0.2.185", "user_id": "u_1039", "user_agent": "Mozilla/5.0 (iPhone; CPU iPhone OS 17_2 like Mac OS X) Safari/604.1", "response_bytes": 991} | |
| {"ts": "2026-04-30T02:02:00Z", "level": "INFO", "method": "GET", "path": "/api/health", "status": 200, "latency_ms": 2, "ip": "10.0.3.64", "user_id": null, "user_agent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) Chrome/120.0.0.0", "response_bytes": 74} | |
| {"ts": "2026-04-30T02:03:34Z", "level": "INFO", "method": "GET", "path": "/api/products", "status": 200, "latency_ms": 49, "ip": "10.0.1.175", "user_id": "u_1024", "user_agent": "Mozilla/5.0 (iPhone; CPU iPhone OS 17_2 like Mac OS X) Safari/604.1", "response_bytes": 5214} | |
| {"ts": "2026-04-30T02:05:27Z", "level": "INFO", "method": "GET", "path": "/api/products/6066", "status": 200, "latency_ms": 55, "ip": "10.0.1.25", "user_id": "u_1017", "user_agent": "Mozilla/5.0 (Macintosh; Intel Mac OS X |
These are the things I did to get NVIDIA GeForce GTX 1050 Ti working on Ubuntu 24. Given its an older GPU card, I had to use a lower CUDA version and a lower gcc version. Your system may be different. Don't try and figure it out yourself. Easier to use claude CLI and debug together:
IMPORTANT: Don't copy paste - find out your GPU specs, and then download the right nvidia driver/CUDA/CuDNN/
wget https://developer.download.nvidia.com/compute/nvidia-driver/590.48.01/local_installers/nvidia-driver-local-repo-ubuntu2404-590.48.01_1.0-1_amd64.deb
sudo dpkg -i nvidia-driver-local-repo-ubuntu2404-590.48.01_1.0-1_amd64.deb
wget https://developer.download.nvidia.com/compute/cuda/11.8.0/local_installers/cuda_11.8.0_520.61.05_linux.run
/api/ with .json suffix on all endpoints?token=xxx)Monitor[Function]=Modect){ monitors: [{ Monitor: {...}, Monitor_Status: {...} }] }MonitorId, StartDateTime, CaptureFPS)
| import numpy as np | |
| import sys | |
| import cv2 | |
| import time | |
| import datetime | |
| import re | |
| from pyzm.helpers.Base import Base | |
| import portalocker | |
| import os |
| #!/bin/bash | |
| # claude-runner.sh - Runs Claude CLI with automatic rate-limit handling | |
| # Uses tmux to maintain proper terminal environment | |
| set -euo pipefail | |
| SESSION_NAME="claude-worker" | |
| RESUME_FILE="$HOME/.claude-session-id" | |
| STATE_FILE="$HOME/.claude-runner-state" |
| ## 👤 User | |
| Analyze agents.md to make sure its in great shape. One key issue I see is you implement things, run tests, say its all ok, but it breaks when I try. Are you generating/updating tests always? If not, how shoulD AGENTS.md be improved? I really want to follow a "test for everything" philosophy - when tests pass, it really should mean the app should work and all options/buttons/screens tested | |
| --- | |
| ## 🤖 Claude | |
| I'll analyze AGENTS.md and identify the testing gaps. Let me first check what tests currently exist: |
| ## 👤 User | |
| The full walkthrough tests are surfacial. If I want to write human readable instructions on the flow (I want it to go step by step into each screen and test functionality of items), and use that human redable instructions to generate code for e2e tests, what is the best approach? | |
| --- | |
| ## 🤖 Claude | |
| Great question! For human-readable test specifications that generate E2E tests, here are the best approaches for your Playwright setup: |
| --- | |
| ## 🤖 Claude | |
| Perfect! The build succeeds. Now let's commit this debug version so you can test it on iOS and see what the logs tell us: | |
| --- | |
| ## 🤖 Claude |