Firmware 1.0.0

The first release, for the M5Stack ATOM Lite. It's the same firmware as
1.0.0-rc2, tested with KISS TNC apps and a real radio.

Added

• A bridge from a Kenwood TH-D74 or TH-D75 over Bluetooth Classic to up to
  two phones running KISS TNC apps over the BLE KISS API, as B.B. Link
  does. The radio's TNC is put into KISS mode at every connect, and the
  link reconnects every 15 s while the radio is off or out of range.
• Pairing a radio with a double press, or over USB.
• The LED shows the radio link, phones, pairing, authorization mode and
  errors, in bright, dim, breathe or dark mode.
• Reset: hold the button while plugging in.
• The control API over USB serial: status, events, settings, Bluetooth
  scan and pairing, the radio's TNC model, holding the radio link, and the
  authorization code.
• The device's key and authorization code, made on first start.
• Signed images in two app partitions with rollback, ready for updates
  over BLE.

Management apps over BLE and updates over BLE come in later releases.
Until then, authorization mode starts and ends, but no management app
can be authorized over BLE.

Firmware 1.0.0-rc2

Changed

• An error blinks red three times, then pauses, so it doesn't look like
  pairing's fast blink.
• Identify shows magenta, blue and white three times instead of twice.
• Identify and power-on use the same 1 s dark gap as the other events.
• The led_normal setting's solid is now bright, so the choices are
  bright, dim, breathe and dark. A device set to solid shows
  bright.
• The project's vocabulary: the setup code is now the authorization code,
  the management window is authorization mode, and clients that manage
  the device are management apps. In the control API, auth.window is
  now auth.mode and auth.clients is auth.apps, and auth.info
  reports mode and apps instead of window and clients.
  auth.code and auth.rotate_code are unchanged, and so is a device's
  code.

Firmware 1.0.0-rc.1

The first release, for the M5Stack ATOM Lite.

Added

• A bridge from a Kenwood TH-D74 or TH-D75 over Bluetooth Classic to up to
  two phones running KISS apps over the BLE KISS API, as B.B. Link does.
  The radio's TNC is put into KISS mode at every connect, and the link
  reconnects every 15 s while the radio is off or out of range.
• Pairing a radio with a double press, or over USB.
• The LED shows the radio link, phones, pairing, the management window and
  errors, in solid, dim, breathe or dark mode.
• Reset: hold the button while plugging in.
• The control API over USB serial: status, events, settings, Bluetooth
  scan and pairing, the radio's TNC model, holding the radio link, and the
  setup code.
• The device's key and setup code, made on first start.
• Signed images in two app partitions with rollback, ready for updates
  over BLE.

v1.1.0

Bluetooth LE TNCs: the bridge can now connect to a radio's BLE KISS TNC
the way a phone app does, and share it with apps over BLE and TCP.

Added

• ble-client ports: TNCs on Bluetooth LE that follow the
  BLE KISS API,
  such as the Ailunce HA2, defined with a [tnc.ble] section. They aren't
  paired; the bridge connects as a phone app would, and drops the link
  when it lets go so the radio advertises again.
• ktbctl scan --le lists BLE KISS TNCs in range, and bluetooth.scan
  takes transport = "le". ktbctl setup and the TUI's add forms offer
  Bluetooth LE.
• status shows a TNC's ble section, and tnc.models lists radios with
  BLE TNCs.
• The td-h9 model, for the TIDRADIO TD-H9: KISS over BLE on TIDRADIO's
  own GATT service rather than the BLE KISS API's. ktbctl scan --le lists
  every named LE device, BLE KISS TNCs and known radios first, since the
  TD-H9 doesn't advertise a KISS service and its name may vary.

v1.0.0

A rewrite around bridges and ports, with a new TOML configuration and
ktbctl to manage the running daemon. The 0.5 config is not read or
migrated; "Coming from 0.5" in the README shows the equivalent TOML.

Changed

• New configuration: TOML in /etc/kiss-tnc-bridge/ (kiss-tnc-bridge.toml
  plus conf.d/*.toml) describing bridges with inline ports, replacing the
  INI file. /etc/kiss-tnc-bridge.conf is ignored with a warning.
• The daemon is a KISS switchboard: each bridge connects one TNC port
  (spp-client, serial or tcp-client) to any number of app ports
  (ble-server, tcp-server). Frames from apps go to the TNC through one serialized
  writer; frames from the TNC are broadcast to every app; apps never hear
  each other.
• The TNC connection no longer blocks BLE handling: connecting runs in its
  own task with exponential backoff, retrying when the first connect fails
  (#2), uplink frames
  are queued while it comes up, and a flood from one app backs up to that
  app instead of being dropped.
• The KISS "return" command (C0 FF C0) from an app is dropped;
  app_params = "drop" also drops KISS parameter commands.
• Each ble-server port registers its own GATT application and
  advertisement, named after the bridge's public_name.
• systemd: ConfigurationDirectory=, StateDirectory=, RuntimeDirectory=
  and ProtectSystem=strict; the lock file moved to /run/kiss-tnc-bridge/.
• The daemon handles SIGTERM as well as SIGINT.

Added

• tcp-server ports: KISS over TCP for apps, bound to loopback by default,
  an address, or an interface (wlan0:8001), with an allow list and
  max_clients.
• [[adapter]] objects give adapter MACs readable ids; adapter values can
  be an id, a MAC or hciN.
• kiss-tnc-bridge -t prints the effective bridges with their source files
  and warnings, and checks references and conflicts among enabled bridges.
• Bridges can be disabled and kept for another setup.
• A PR CI workflow (fmt, clippy, tests on Linux and macOS) and an
  end-to-end TCP test with no Bluetooth.
• [[tnc]] objects for hardware TNCs, with an spp section (Bluetooth
  address and the adapter it's paired on) and/or a serial section (device
  path, baud). A TNC can be in only one enabled bridge, over whichever
  transport.
• spp-client ports: a TNC over Bluetooth Classic, such as the TH-D74/D75's
  built-in TNC, connected through a BlueZ SPP profile (no channel numbers).
  A TNC that isn't paired is reported as unpaired and checked again every
  few seconds; pair it with bluetoothctl (see the README).
• serial ports: a TNC on a USB or UART serial device, opened exclusively,
  waiting for the device when it's unplugged and reconnecting when it's back.
• model = "th-d74" | "th-d75" puts the radio's TNC in KISS mode on every
  connect, over Bluetooth or USB. Other TNCs use the default,
  model = "generic"; an unknown model is an error that lists the models. exit_kiss_on_disconnect takes it back out
  when the bridge lets go, restoring APRS mode if that's how it was found.
• connect and idle_timeout on every TNC port type.
• tcp-server ports are announced with DNS-SD (_kiss-tnc._tcp) through
  Avahi, scoped to the interface they're bound to (announce = false turns
  it off). A name collision on the LAN moves the bridge to "Name (2)" for
  DNS-SD and BLE alike, kept across restarts in
  /var/lib/kiss-tnc-bridge/state.toml.
• kiss-tnc-bridge -t lists TNCs and warns about TNCs not paired on their
  adapter (when BlueZ is reachable), unstable serial paths such as
  /dev/ttyACM0, and serial devices that aren't present.
• A udev rule that keeps ModemManager away from the TH-D75's USB port.
• Dynamic config in /var/lib/kiss-tnc-bridge/dynamic.toml, which the
  control API will write (ktbctl), alongside the static config in /etc.
  Static config can't refer to dynamic objects, and static objects win
  collisions. Enable overrides for static bridges live in state.toml.
• Reloading: SIGHUP (and systemctl reload) re-reads the config and
  changes only what changed. Settings like allow, max_clients,
  connect, idle_timeout, public_name and log_level apply live;
  a changed TNC address or device restarts just that port, with app
  sessions staying connected; sessions a tighter allow or lower
  max_clients no longer admit are disconnected. An invalid config is
  rejected and the running bridges carry on.
• The control API: a Unix socket (/run/kiss-tnc-bridge/control.sock,
  group kiss-tnc-bridge, which the deb and rpm packages create) speaking
  newline-delimited JSON, documented in
  docs/control-api.md with a published JSON Schema. status; events for
  state changes, activity and frames (with AX.25 headers decoded for
  display); reload and config.check with the plan they'd apply and
  whether it's disruptive; and commands that create and change dynamic
  bridges, ports, TNCs and adapters, enable, disable and switch bridges
  (static ones through overrides), hold TNC links up or down, kick
  sessions, and list serial devices. Every change can be refused rather
  than disrupt anyone (non_disruptive). ktbctl comes next.
• A disabled bridge may be incomplete (no TNC port, or no app port yet),
  so a bridge can be built up a port at a time and enabled when it's
  complete. Bridges created through the control API start disabled, and
  status and -t show what an incomplete bridge still needs.
• ktbctl, the command-line client for the control socket: status;
  listing adapters, TNCs, serial devices and TNC models; adding and
  removing adapters, TNCs, bridges and ports; enable, disable,
  switch, connect, disconnect and kick; edit in $EDITOR;
  check, reload and monitor (live decoded frames). Changes that would
  disconnect someone are confirmed in a terminal and refused without one
  unless given --yes. Every command takes --json. Packaged alongside
  the daemon.
• Radios can be paired through the daemon: ktbctl scan finds them,
  listing each as it turns up (known radios first, with their model),
  ktbctl pair pairs and trusts one by TNC or address, relaying the
  passkey to confirm, and ktbctl unpair forgets it. A port waiting for
  its radio connects a few seconds after it's paired. In the control API:
  bluetooth.scan with found events and bluetooth.scan_stop,
  bluetooth.pair with pairing events and bluetooth.pair_reply, and
  bluetooth.unpair; a connection can now have several requests in
  flight.
• ktbctl setup: a step-by-step wizard for a TNC (over Bluetooth, with
  scanning, where the radio can be picked as soon as it shows up, and
  pairing, USB/serial, or a KISS TCP server on the network)
  and a bridge sharing it over BLE, TCP or both, ending with a check that
  the TNC connects and is heard. Radio-specific instructions come from the
  daemon's model table, which now lists the radios it knows (served by
  tnc.models). setup --address MAC [--adapter X] starts from a device
  a scan already found, skipping the scan.
• port.release (ktbctl release BRIDGE/PORT) hands a TNC link held by
  connect or disconnect back to its connect policy; status shows a
  held link.
• ktbctl tui (also ktbctl with no arguments, in a terminal): a
  full-screen view at 80×24 over SSH. Bridges with their ports and app
  sessions, activity lights, and the selected bridge's frames; TNCs and
  adapters, with pairing, unpairing and scanning; and every frame with a
  decode. Enabling, disabling, switching, connecting and kicking from a
  key, asking first before anyone is disconnected. a adds a port, an
  empty bridge, a TNC or a name for an adapter in a small form, or hands
  off to ktbctl setup (from the scan box, with the device picked
  there); E hands off to ktbctl edit for the selected
  bridge, TNC or adapter, and C for all of dynamic.toml. It reconnects
  when the daemon restarts.

Fixed

• Phones no longer pair with the bridge. BlueZ asks every phone that
  connects to pair (it reads the phone's battery level), and the
  pairing failed, so phones prompted, stalled and reconnected over and
  over. The bridge never needed pairing; one BlueZ setting stops BlueZ
  asking (ReverseServiceDiscovery = false, see "Phones and pairing" in
  the README), and -t and the daemon warn when it isn't set.
• When the daemon stops, phones connected over BLE are disconnected, so
  apps like aprs.fi notice instead of staying "connected" to nothing.
  After a crash, the restarted daemon disconnects the phones the old one
  left connected, so they reconnect to it.
• A phone whose app has disconnected no longer hides the bridge from other
  phones. iOS keeps the link open, and most controllers can't advertise
  while anything is connected, so the daemon now drops the link of a
  phone it has served that stays connected without a session (checked
  every 10 s).
• A second phone can find the bridge while one is connected, on
  controllers that can advertise while connected (such as the Raspberry
  Pi 4's built-in chip and the RTL8761B):
  the daemon registers a new advertisement each time a phone connects,
  since the kernel brings the old one back only when that phone leaves.
• When a phone leaves, other phones can still connect. On controllers with
  legacy advertising, such as the Raspberry Pi 4's built-in chip, the kernel
  replaced the bridge's advertisement with a nameless one phones couldn't
  connect to; the daemon now advertises afresh a few seconds after a phone's
  link drops.

v0.5.1

Fixed

• logic bug in the just works pairing code

v0.5.0

Fixed

• Add a NoInputNoOutput pairing agent so BLE pairing uses the "Just
  Works" model. Previously, when BlueZ probed a connected client's protected
  characteristics it would trigger a numeric-comparison pairing, prompting for
  a pairing code that the headless daemon could not confirm — causing some
  clients to fail to connect.

v0.4.5

Changed

• only allow a single instance of kiss-tnc-bridge to run, running multiple
  instances concurrently, especially fron the same config file can cause
  race conditions and malformed data sent to the TCP TNC.
• the default max_clients is now 1, since not all bluetooth chips support
  multiple simultaneous connects on the same BLE GATT advertisement

v0.4.4

Improved

• more improvements for disappearing bluetooth adapters

v0.4.2

Fixed

• connection counting bug