coderluii/channelwatch

By coderluii

Updated 1 day ago

ChannelWatch monitors Channels DVR logs and sends Pushover notifications. Minimal resource usage.

Image
Networking
Internet of things
Monitoring & observability
1

10K+

coderluii/channelwatch repository overview

ChannelWatch

ChannelWatch is a self-hosted monitoring and notification dashboard for Channels DVR.

It watches DVR activity, recording events, VOD playback, disk space, and service health from a single container. The v0.9 release adds multi-DVR setup, first-run discovery, per-DVR status, notification routing, delivery history, backup and restore, health checks, metrics, an in-app Update Center, and a maintained Unraid template.

Images

  • Docker Hub: coderluii/channelwatch
  • GHCR: ghcr.io/coderluii/channelwatch

Recommended tags:

  • latest for the newest stable image
  • 0.9 for the current compatible v0.9 release
  • 0.9.17 for the v0.9.17 release

Quick Start

services:
  channelwatch:
    image: coderluii/channelwatch:latest
    container_name: channelwatch
    ports:
      - "8501:8501"
    volumes:
      - ./config:/config
    environment:
      TZ: America/Los_Angeles
      CHANNELWATCH_SECRET_STORAGE_KEY: "${CHANNELWATCH_SECRET_STORAGE_KEY:?set a unique value of at least 32 characters}"
      PUID: "1000"
      PGID: "1000"
    restart: unless-stopped

Open http://localhost:8501 after the container starts.

Updating

Use v0.9.17, 0.9, or latest for the current v0.9 release. It provides an actionable blocked state when a required deployment key is missing, makes notification tests reflect real delivery, preserves report drafts, separates restart recovery from DVR readiness, and accepts safely resolved LAN and Tailscale DVR hostnames.

After installing a version with Update Center support through Docker, Unraid, Compose, or Helm, compatible app-only releases can be checked, verified, backed up, applied, and rolled back from Settings > Updates.

v0.9.17 requires a normal container image update. Pull and recreate the container because missing-key recovery must work before the core monitor starts; the Update Center intentionally reports this release as container image update required.

Releases that change the container runtime still require a normal image update. ChannelWatch will show container image update required when that is the safe path.

Configuration

ChannelWatch stores its settings, logs, database, backups, and encryption key under /config. Set CHANNELWATCH_SECRET_STORAGE_KEY to a unique value of at least 32 characters so new local secret files are written with envelope encryption.

The external Project One-Click template currently omits that variable. If a fresh one-click install shows Runtime setup required, generate a stable value with openssl rand -base64 48, add it to the stack as CHANNELWATCH_SECRET_STORAGE_KEY, and recreate the container without deleting its /config volume. Preserve the same value across upgrades and restores; ChannelWatch cannot recover it if it is lost.

DVR setup is easiest through the web UI. For bootstrap-only deployments, CHANNELS_DVR_SERVERS supports comma-separated Name@host:port entries.

License and release verification

ChannelWatch is MIT-licensed. The image carries the project license, notice, third-party inventory, complete applicable copyleft license texts, and the exact corresponding-source/rebuild map under /licenses/channelwatch. Exact amd64 and arm64 SPDX/CycloneDX SBOMs and a checksum manifest covering every other attached artifact are included with the corresponding GitHub Release.

Tag summary

Content type

Image

Digest

sha256:136806b19

Size

68.9 MB

Last updated

1 day ago

docker pull coderluii/channelwatch