Skip to content

CHANGELOG.md

Latest commit

 

History

History
108 lines (60 loc) · 7.81 KB

CHANGELOG.md

File metadata and controls

108 lines (60 loc) · 7.81 KB
Raw

Changelog

Notable changes to HaMBridge (this repository). Release history for packaging metadata remains in packaging/debian/changelog (Debian) and the RPM spec where required by those formats.

[0.5.3] — 2026-05-17

Fixed

  • CI / Debian builds — Makefile finds fcl-fpcunit under /usr/lib/*-linux-gnu/fpc/... so make test works on Ubuntu/Debian (GitHub Actions ubuntu-24.04).

Changed

  • HaMBridge branding — README, Specification, packaging text; clone paths use hambridge; README summary table covers VISCA over serial and UDP.
  • Config — removed pre-release legacy JSON mapping paths, flat serial bus fields, and /etc/hambridge/hambridge.yaml discovery (no external releases yet).

[0.5.2] — 2026-05-16

Added

  • GitHub Actions — .github/workflows/ci.yml runs make and make test on pull requests and main; verify-release-pins checks release-pins.json against the Makefile and RPM spec. .github/workflows/release.yml on tags v*.*.* verifies version alignment, builds hambridge-{version}-linux-x86_64.tar.gz + SHA256SUMS, Debian .deb (amd64 and arm64 runners), and Fedora RPM (fedora:42 container), then publishes a GitHub Release with CHANGELOG.md notes.

[0.5.1] — 2026-05-16

Added

  • MQTT TLS (optional) — bridge.mqtt.tls may be a boolean (legacy) or an object with enabled, caFile, caPath, clientCertFile, clientKeyFile, verifyPeer, serverName, minVersion, maxVersion, ciphers (see Specification.md §3.0). Trust anchors and verification are applied before the TLS handshake via a build-time patch on prof7bit/fpc-mqtt-client mqtt.pas (see patches/; zip pin unchanged for other units). Startup validates paths, warns on verifyPeer: false and on private keys readable by group/other, and warns once if minVersion / maxVersion are set (not enforced; use ciphers / OpenSSL defaults).

[0.5.0] — 2026-05-16

Added

  • Automated tests (FPCUnit) — make test builds and runs ./build/hambridge_tests (plain report). Fixtures live under tests/fixtures/: minimal hambridge.yaml slices for devicesconfig validation (duplicate slugs, UDP triple and cross-bus rules, missing UDP controller, duplicate VISCA controllers) and a small visca-min.yaml for viscamapping golden encode/decode (including a controller power/on frame aligned with common Sony VISCA / Bitfocus-style bytes per Specification §10.4).

[0.4.1] — 2026-05-09

Changed

  • Bus schema enforcement — buses.<id> requires transport + protocol, validates protocol_config (if present) is an object, and reads serial settings from transport_configuration.

[0.4.2] — 2026-05-09

Changed

  • Endpoints loader — VISCA devices are loaded from endpoints[] with match.endpoint_type: device, using match.bus and match.deviceID (replacing the legacy devices[] stanza). Evdev inputs are loaded as match.endpoint_type: controller with match.protocol: evdev and default publish topic controller/<slug>/event.

[0.4.3] — 2026-05-09

Changed

  • Evdev endpoints enforcement — Linux input is configured via an evdev bus (transport: none, protocol: evdev, protocol_config.enabled: true) and endpoints[] controller rows (match.protocol: evdev). Validation now enforces protocol_config.enabled: true for evdev buses.

[0.4.4] — 2026-05-09

Added

  • VISCA over UDP — buses may use transport: udp + protocol: visca with transport_configuration.bindHost/bindPort. Device endpoints resolve udpHost/udpPort (or bus defaultUdpHost/defaultUdpPort). Replies are correlated using (bus, remoteHost, remotePort, deviceID) with strict must-match semantics. Controller ingest publishes on controller/<slug>/event (one match.protocol: visca controller endpoint per UDP bus).

[0.4.0] — 2026-05-09

Changed

  • Unified YAML configuration — One file hambridge.yaml replaces bridge.json + devices.json. Top-level bridge holds MQTT and logging; device_mappings.visca points at the VISCA mapping file (paths relative to the main config directory). buses may use transport: serial and nested transport_configuration ( port, baud, rs485, …). --devices and BRIDGE_DEVICES are removed; pass the same path to --config / BRIDGE_CONFIG for everything.
  • Config discovery — Matches docs/user/ConfigurationGuide.md (no implicit ./config/ probe): CLI, BRIDGE_CONFIG, .local/etc/config/hambridge.yaml, /etc/hambridge/config/, /etc/hambridge/hambridge.yaml.
  • VISCA mapping — mappings/visca.yaml (and .yml) supported via in-tree minimal YAML parsing; .json mapping files still work.

[0.3.3] — 2026-05-02

Added

  • Device reply decode — device/<slug>/telemetry and lastReply on device/<slug>/status may include a decode object (generic VISCA: replyClass, socket, payload / code as applicable) via viscareplydecode.
  • controller/<bus>/status — JSON snapshot with lastController and lastDeviceReply (objects or null), published after controller/<bus>/event and after device replies on that bus.

[0.3.2] — 2026-05-02

Added

  • devices.json — devices[].scheduler.coalesce: array of first path segments (pan, tilt, zoom, …). Before enqueueing, older queued commands for the same device and segment are removed (the item waiting for ACK is not dropped).
  • Redundant VISCA skip — Per-device, per-command-path last successful wire cache (bridge ACK/completion and controller semantic re-encode). Matching MQTT control is answered with commandAck (reason: redundant, viscaKind: skipped) without enqueueing or sending; duplicates already queued are dropped at send time the same way.
  • device/<slug>/status — Optional state object with last JSON for pan, tilt, zoom, and preset-family commands, updated from bridge successes and controller decodes.

[0.3.1] — 2026-05-02

Added

  • VISCA command lifecycle (commandrouter): per-bus state machine — drain TX queue, wait for device ACK / completion / error (or scheduler.ackTimeoutMs timeout), commandRetryMax resends with retryBackoffMs. ackTimeoutMs: 0 skips wait and publishes commandAck with viscaKind immediate.
  • MQTT device/<slug>/commandAck: JSON with ok, reason, attempts, mqttTopic, command, viscaKind, viscaHex.
  • Serial (serialport): software TX queue (up to 8 KiB), PumpTransmit for partial write / EAGAIN; reopen with backoff after hard read/write errors; optional TIOCSRS485 from devices.json buses.<id>.rs485.
  • visca-mapping.json: template slots as string (one byte) or object slot + width (1..8); MQTT / variables value as integer (big-endian) or JSON array of bytes. Controller reverse-decode updated.

[0.3.0] — 2026-05-02

Added

  • Serial RX: non-blocking reads, VISCA frames terminated by 0xFF.
  • Controller traffic: reverse-map packets against visca-mapping.json; publish controller/<bus>/event (semantic or raw event).
  • Device replies: classify ACK / completion / error; publish device/<slug>/telemetry and merge lastController / lastReply into device/<slug>/status.

[0.2.1] — (mapping)

  • Framed VISCA encoding in visca-mapping.json (bytes + optional template / variables + MQTT JSON for slots).

[0.2.0] — (VISCA TX)

  • MQTT device/<slug>/<command> → visca-mapping.json → serial TX; per-bus queue and inter-command spacing.

[0.1.0] — (evdev)

  • Linux evdev → MQTT JSON; bridge.json / devices.json; MQTT reconnect, LWT/birth.