BotWave

v1.1.6-neea Breaking

This release includes 1 breaking change for platform teams planning a safe upgrade.

Published 7h Home Automation

View tool

✓ No known CVEs patched

Read the diff → Tool health → What is this tool? →

✓ No known CVEs patched in this version

Topics

botwave fm good-first-contribution network piwave python

+3 more

radio raspberry-pi rds

Affected surfaces

breaking_upgrade

ReleasePort's take

Moderate signal

editorial:auto 5h

BotWave v1.1.6‑neea adds `transaction_id` support to remote shell commands and exposes the ID via BW_TRANSACTION_ID, but changes log streaming so output is now isolated per client by default.

Why it matters: The release introduces a new transaction_id feature (severity 40) while delivering a breaking change (severity 70) that isolates remote log streams per client, affecting all handler scripts and logging integrations.

Summary

AI summary

Updates What Changed, https://github.com/dpipstudio/botwave/wiki/Integrating-botwave-in-your-apps, and https://github.com/dpipstudio/botwave/wiki/Integrating-custom-backends across a mixed release.

Changes in this release

Type	Severity	Summary	CVE
Breaking	High	Breaks shared log stream behavior; remote output now isolated per client by default. Breaks shared log stream behavior; remote output now isolated per client by default. Source: llm_adapter@2026-06-03 Confidence: high	—
Feature	Medium	Adds `transaction_id` support to remote shell commands. Adds `transaction_id` support to remote shell commands. Source: llm_adapter@2026-06-03 Confidence: high	—
Feature	Medium	Exposes current transaction ID as `BW_TRANSACTION_ID` environment variable in handler scripts. Exposes current transaction ID as `BW_TRANSACTION_ID` environment variable in handler scripts. Source: llm_adapter@2026-06-03 Confidence: high	—

Full changelog

What Changed

transaction_id support: Commands sent over the remote shell can now carry a transaction_id=<value> tag. BotWave echoes it back on every log line produced by that command, making it easy to correlate responses and filter out ambient log noise. See the wiki for usage examples and integration patterns.
BW_TRANSACTION_ID handler variable: The current transaction ID is now exposed to handler scripts as a BW_TRANSACTION_ID environment variable (empty string if not set).
Remote output isolation: Log output from a remote shell command is now sent back only to the client that ran it, instead of being blasted to every connected client. This behavior is on by default and can be disabled with ISOLATE_REMOTE=false. This does NOT affect STDOUT and eventual file logs.
Docs: New Integrating custom backends wiki page covering how to build and register your own backend binary.

[!WARNING]
This update may break scripts relying on the full shared log stream. Either update your scripts, or set ISOLATE_REMOTE=false.

Updating to this version

To update to this version, run the following command:

bw-update --to v1.1.6-neea

Commit history

=--- v1.1.6-neea ---= (7ed07f2)
Merge pull request #68 from dpipstudio/wsshutup (4d917da)
shared,ws_cmd.py: integrated remote cmd output isolation (ffb8bbd)
shared,logger.py: integrated ws isolation (c72022e)
Merge pull request #67 from dpipstudio/transac-log (bee787d)
docs: updated handlers doc to mention BW_TRANSACTION_ID (ace0c2b)
server,local: added BW_TRANSACTION_ID var to handlers context (50bed1e)
server: added support for transaction_id elements in commands and logs (02c0721)
local: added support for transaction_id elements in commands and logs (0db2ed0)
shared,logger.py: added support for transaction ids (dfbb3a3)
Update installation.json for release v1.1.5-erycibe-rev-1 (d27d4ed)

Breaking Changes

Remote shell command output is isolated per‑client by default; existing scripts expecting a shared log stream must be updated or set `ISOLATE_REMOTE=false`.

View diff on GitHub

Weekly OSS security release digest.

The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.

No spam, unsubscribe anytime.

Share this release

Share on X Share on Bluesky

Track BotWave

Get notified when new releases ship.

About BotWave

FM broadcasting system with server-client architecture for managing multiple Raspberry Pi transmitters remotely.

All releases →