Bluetooth presence monitoring, and HTTP inbound endpoints now require a token

v0.1.61
Platform

Features

  • Device Manager: paired Bluetooth devices can be added to monitoring straight from Discovery. A monitored device is probed on an interval, and a Device Offline alarm activates automatically when it goes out of range or disconnects, clearing again once it is back.

Bug Fixes

  • Device Manager: Test Connection now works for an integration whose address already combines a host and a port, instead of treating the combined value as the host alone.
  • Device Manager: unpairing a device that is only known through an existing pairing (not currently visible in a scan) now goes through the right adapter instead of failing.
  • Device Manager: the Add Integration wizard can finish even when discovery finds zero devices, instead of getting stuck on that step.
  • Device Manager: Discovery no longer offers a Bluetooth GATT connection for a classic-only Bluetooth device.
  • Device Manager: a paired Bluetooth device's connected and trusted status now stays live instead of going stale until the next pairing event or a restart.
  • ControlBird AI: entering a provider API key now actually saves it, and a save that is rejected is reported instead of silently clearing the field.
  • Extensions: installing a missing dependency now picks the newest version compatible with your platform, instead of always installing the catalog's latest.
  • Extensions: a node upgraded from the full image to the slim image now correctly reports an extension that is missing its binaries instead of counting it as healthy.
  • Shell: opening a terminal session with certain characters in its session id no longer crashes the session.
  • Automations: adding to or subtracting from a Decimal-typed field now works on every node, matching the behavior already in place for other value types.

⚠️ Breaking Changes

  • **HTTP Service**: inbound HTTP endpoints (the ones that receive webhook or API calls into ControlBird) now require a bearer token once you update to the HTTP Service extension released alongside this platform version. Set a token on the endpoint and send it as an Authorization header on every request; requests without it will be rejected.