Skip to content

Release 2026.11.0

Latest

Choose a tag to compare

@abeggled abeggled released this 03 Nov 20:44
· 164 commits to main since this release
03c85ce

Breaking changes 🚨

  • none

New features ✨

  • Adapters/Admin GUI: The Home Assistant adapter becomes an integration layer instead of a manual entity-ID bridge, so integrations Home Assistant already provides β€” e.g. Sonos or Velux β€” can be used from OBS without hand-building every binding. Connection: one WebSocket per instance subscribes only to the bound entities (with a fallback for older Home Assistant versions), checks the connection with a ping every 30 s, reconnects with a growing delay (1–60 s), and after every reconnect or binding change takes a full snapshot, so a new binding gets its value at once and nothing is missed during an outage. The instance only shows Connected after a successful login. Quality: unknown and transitional states (e.g. locking, opening) keep the last good value with quality uncertain; unavailable, fault states (e.g. jammed), removed entities and a lost connection keep it with quality bad β€” after an OBS restart the stored value counts as the last good one. An unchanged value reported again after a reconnect, a restart or a binding change is not sent on to other adapters or logic again. Import: the new Import button on a Home Assistant instance opens an entity browser with live search and filters for domain, area, integration, device and availability; per entity you pick the proposed profile, other profiles, the plain state or individual attributes. The preview changes nothing and shows name, type, unit, direction, tags, read mapping, actions and the Boolean convention (e.g. true = locked), and the name of every new object can be edited there; the import creates only new entries, is repeatable, reports entities renamed in Home Assistant or already bound by hand as conflicts and never overwrites existing objects. Attributes are imported read only. Profiles for sensor, binary_sensor, switch/input_boolean/fan, light (on/off, brightness), lock (locked, open), cover and valve (open/closed, position, stop, tilt), media_player (state, play/pause, power, stop, next/previous, volume, mute, source, title, artist), number, select, text, button and scene map states and actions declaratively β€” e.g. true β†’ lock.lock, false β†’ lock.unlock β€” and are only offered when the entity supports them; command profiles never act on false, and ambiguous domains (alarm panel, climate, vacuum, lawn mower, media playback versus power) never get a silent write mapping. Bindings: the binding form searches entities, attributes, domains, actions and data fields of the live instance (free input stays possible), offers the profile and a Read as type, shows the resolved mapping and accepts an advanced, validated JSON mapping (action, write_actions, state_map, transitional_states, fault_states) without templates or expressions. Existing bindings with Service Domain, Service Name and Service Data Key keep working exactly as before and take precedence over a profile, so no migration is needed. A failed Home Assistant action now counts as a failed write and shows a warning on the instance, instead of being logged and treated as success. The Home Assistant token is no longer shown to users without administrator rights. The ioBroker import now removes an object again when its binding cannot be created, instead of leaving it behind. #1392
  • Admin GUI/API: OBS now tells you when a newer version is available. A new Settings β†’ Updates tab holds the update channel β€” Stable (regular releases only), Pre-release (regular releases and release candidates, never nightlies) or Nightly (nightly builds only) β€” which existing installations derive from the installed version (2026.10.0 β†’ Stable, 2026.11.0-RC1 β†’ Pre-release, nightly-YYYYMMDD β†’ Nightly). The server classifies the GitHub releases itself instead of relying on GitHub's "latest release", ignores drafts and unknown tags, never compares a nightly's date like a CalVer patch number, and never offers a nightly as a stable or pre-release update. It checks a random 0–719 minutes after start-up and then every twelve hours, with conditional requests (ETag) and a server-side cache so open browsers do not query GitHub; administrators can also check right away. When an update is available, every Admin GUI page shows a notice with channel, installed and latest version, the time of the last successful check and a release notes popup that lists only the channel's versions between the installed and the latest one; the Markdown from GitHub is rendered without any embedded HTML. A failed check keeps the last successful result, marks it as possibly out of date and does not retry early; hosts without internet access can turn the check off with update_check.enabled: false. Five read-only system DataPoints with the same IDs on every installation β€” OBS Update Channel, OBS Current Version, OBS Latest Version, OBS Last Check and OBS Update Available β€” make the status usable in the Visu and in Logic; they cannot be renamed, duplicated, deleted or written through the Admin GUI, the API, MQTT, adapter bindings or Logic, and OBS Latest Version/OBS Update Available stay uncertain until the first successful check. #1370
  • Admin GUI/Visu: New settings tab Visu devices for per-device start pages. Each device profile (e.g. "Phone", "Hallway wall panel") has a name, a link identifier, a start page and an optional return to the start page after a configurable number of seconds without touch, mouse or keyboard input β€” handy for wall panels that should always fall back to their home page. A device picks its profile once, via its link (/visu/?device=<identifier>, also usable as a bookmark or kiosk start URL) or via the new Device selector on the Visu overview, and remembers it in its browser; /visu/ then opens the profile's start page instead of the overview. The Visu never returns from the editor, the page management or a login/PIN prompt, and a protected start page still asks for its PIN or login. Profiles are stored centrally with the app settings, so configuration export, backups and factory reset include them. Without a profile everything behaves as before. #1379
  • Admin GUI/Visu: New Visu alarms (Settings β†’ Visu alarms) bring a message or a Visu page to the foreground of the Visu when something happens β€” e.g. "Mail has arrived" when the mailbox contact triggers, or a notice while the phone rings. Each alarm watches a datapoint with a condition (like the MESSAGE bindings) and starts when the condition becomes true; it shows either a message window (title, text, icon, urgency colour) or a Visu page designed in the editor as a popup, ends with an acknowledge button (on all devices at once) and/or automatically when the condition goes away, can play a signal tone and can be limited to selected Visu devices. Alarms appear on top of every page and the overview, also without login; the dedicated alarm channel only carries what the alarm defines for display, never datapoint values. Nothing is raised for a state that was already present when saving or starting the server. #1383
  • API/Logic Engine: POST /api/v1/logic/graphs/validate now also reports two mistakes that so far passed without a warning and only showed at run time. A block setting whose name the block does not know β€” typically a typo such as operater instead of operator on a Compare block β€” is reported as unknown_config_field, with a "did you mean" hint when a known setting is close; until now the block silently ignored it and ran with its default. The block name (label), per-port negation (negate_…) and the few settings the editor stores outside a block's schema (e.g. the static texts of String Concat, the value map of Read/Write Object) are not reported. A placeholder for a block type this server does not know (e.g. after an import) is reported as missing_node_type with the original type name, instead of validating without any warning although the block does nothing. Legacy thresholds of a Heating Circuit block that the block no longer reads are reported as ignored_config_field. This mainly helps AI agents and scripts that build logic sheets through the API. #1208
  • KNX/Admin GUI: KNX bindings with direction SOURCE or BOTH can now poll their device periodically. The new Read periodically (seconds) field in the KNX binding form (read_interval_s) makes OBS send a GroupValueRead to the state group address β€” or the group address if none is set β€” at that interval, so DataPoints stay current for devices that do not send their state on their own; the response updates the DataPoint through the normal SOURCE path. Empty or 0 turns polling off and is the default, so existing installations keep their bus traffic; the interval must be between 10 seconds and 86400 seconds (one day). Bindings that read the same group address share one poll at their shortest interval. Polling only runs while the KNX instance and its tunnel are connected β€” reads pause during a tunnel drop instead of piling up β€” repeats a read missed during a tunnel drop right after the reconnect (pollers that missed nothing keep their rhythm, so a flapping tunnel causes no burst of reads), follows binding changes without duplicate reads, spreads the first reads over up to 30 seconds to avoid telegram bursts, and keeps going when a single read fails. DEST and disabled bindings never poll; the API rejects an interval on a DEST binding. Every poll adds load to the KNX bus. #1402
  • Logic Engine/Admin GUI: A Trigger (cron) block can now be fired by hand while debugging a logic sheet. Until now you had to wait for the next scheduled time to see what the sheet does: a Trigger has no input whose value could be overridden in the debug view, and Run does not fire it. In debug mode, the block's Debug values tab now has a Fire now button that runs the sheet once as the schedule would β€” including its writes and notifications, with any debug overrides set on other blocks applied β€” after the usual save and permission check, and shows the resulting values right away. The button is locked while it runs and on a disabled sheet, and Run still never fires a Trigger. POST /api/v1/logic/graphs/{id}/run accepts the Trigger block IDs to fire in the new fire_triggers field, which the audit log records; a block ID that is no Trigger, or a Trigger whose level the same request overrides, is rejected with 422. #1276
  • Logic Engine/Admin GUI: Added a Binary Statistics function block (binary_stats, "BinΓ€rstatistik") that counts how many of 2–30 binary inputs are TRUE and FALSE, so questions such as "how many windows are open?" or "at least 2 of 3 smoke detectors" no longer need a chain of compare/formula blocks or a Python script. Inputs and per-input negation work exactly like AND/OR/XOR (negation is applied before counting). The block outputs the number of TRUE and FALSE inputs, the number of evaluated inputs, the TRUE share in percent (one decimal, rounded half up), a strict majority flag, a separate tie flag for an even split and a "k of n" threshold flag (threshold_count, 0 = off). Unwired inputs are ignored by default so that three wired inputs out of ten are not reported as seven permanent FALSE values; the unwired_inputs setting can instead count them as FALSE like AND/OR. A wired input that delivers no value in a run always counts as FALSE. With no wired input every count and the percentage is 0 and every boolean output false. The block is purely combinational and keeps no state. #1164
  • Logic Engine/Admin GUI: Adds a new Logic category Energy Management and its first block, Surplus control ("HEMS Lite"). The block distributes the energy surplus measured at the grid connection point across any number of consumers by priority β€” wallboxes, water heaters, heating elements, heat pumps, pool pumps or any other deferrable load β€” where a hand-built replacement used to take many separate blocks. Consumers are continuously controllable (a 0–100 % setpoint with minimum/maximum, step size and minimum power), simple on/off loads with separate switch-on and switch-off thresholds, or one-shot triggers (e.g. start a washing machine through an API) that fire once per release, with lockout time and a choice of how they are re-armed. The consumer list is sorted by drag and drop and its order is the priority β€” there are no priority numbers, so duplicates are impossible; new consumers are appended at the bottom, and the budget is cut from the bottom up when it shrinks. Every consumer keeps a stable internal ID, so reordering never re-wires an existing connection. The grid connection can be measured as one bidirectional value (positive = import), as two separate positive import/export inputs (netted internally as import βˆ’ export), or as a feed-in value only (documented limitation: at 0 W the block cannot tell a balance from import, so it holds and then sheds step by step). The power budget keeps already allocated power in the calculation (used power βˆ’ grid power βˆ’ reserve), minimum run time, minimum off time, switch-on/off delays and hysteresis prevent needless switching, and "output only on change" avoids unnecessary writes. Missing, non-numeric, NaN or stale meter values β€” and a cleared Enable or Plant-OK input β€” put all outputs into the safe state (0 %, off, no trigger) and are written to the log; after a restart the block always starts safe and never fires a trigger because of a restored state. Per-consumer status and diagnostic outputs (grid power, surplus, budget, allocated, remaining, block status, warning) make every decision traceable. The block runs its own control interval (default 30 s, 5 s to 60 min). Help page: Blocks: Energy (HEMS). #1327
  • Logic Engine/Admin GUI: Every consumer of the Surplus control block (HEMS Lite) now has its own boolean Release input, so higher-level logic can lock a single consumer temporarily β€” a wallbox only while a car is plugged in, hot water only within operating hours, a heat pump reporting a fault or interlock β€” instead of removing it from the configuration or faking its power. A locked consumer is skipped in the distribution as if it were not listed: its allocated or reserved power goes to the released consumers below it, a percent output goes to 0 %, an on/off output to false, a trigger does not fire and a running pulse ends, and its status is the new blocked, which is distinct from a missing surplus, a waiting time or a fault. The lock acts at once, also between control cycles, and takes precedence over minimum run time, switch-on/off delays, priority and "hold the last outputs". The consumer keeps its position; once released, it takes part again from the next control cycle β€” never with its earlier setpoint, its minimum off time and switch-on delay apply as usual. An unconnected Release input uses a configurable default (released unless changed), so existing configurations behave unchanged; for a connected input whose value is missing, stale (beyond the hold time) or not a yes/no value, the consumer is locked by default, or optionally falls back to the default, and the fault is logged once. In debug mode, the consumer list in the block's properties shows each consumer's Released/Blocked state live. #1359
  • Visu: New Event list ("Terminliste") widget shows the coming days' appointments as a list β€” Today, Tomorrow, then the date (e.g. Wed 15.07.26, format configurable), each followed by that day's events with their start time; all-day events come first. Up to eight calendar sources are merged into one list, each in its own colour (e.g. waste collection in orange, private appointments in green). Further options: number of days (default 7), separator (semicolon, asterisk or one line per event), show location, and show days without events. A source is an object holding the array output of an iCalendar Logic block filter, so the calendar β€” including a secret Google Calendar iCal address β€” is fetched on the server and its URL never reaches the Visu; the list moves on by itself at midnight in the server timezone. A Write Object block now stores a list or object value written to a STRING object as JSON text; previously the raw array was refused as a type mismatch and never reached the object's bindings. Help page: Visu β†’ Widgets. #999
  • Visu: The Chart ("Verlauf") widget is easier to read with many series. The legend no longer draws a colour box per series; each entry is underlined in its series colour instead, which takes less room, and clicking an entry still hides or shows the series β€” now also across the automatic reloads, which used to bring hidden series back. The colour swatches in the hover tooltip are now filled completely in the series colour; previously a line series showed only its almost transparent area colour, so the series were hard to tell apart. The default palette for new series grows from 8 to 12 colours, so colours repeat only from the 13th series on; existing series keep their stored colours. The grid lines now follow the Visu theme: light grey in light mode, where the dark-mode grey showed as almost black lines, and a lighter grey in dark mode, where they were barely visible against the card; they switch along when the theme is toggled. In the configuration, the title field is now labelled "Chart title", and the primary series explains that without its own label it takes the chart title β€” so the name of the first series no longer ends up as the title by accident. #1361
  • Visu: The Link widget has a new Icon size (px) setting. Until now its icon was always rendered at the fixed text-4xl size, and an SVG icon was squeezed into a 1em square, so a wide picture (a car, a house front) shrank to a sliver in the middle of the tile. With a size set, the icon is drawn at that font size and SVG icons keep their aspect ratio β€” 1em high, as wide as their proportions require, but never wider than the tile; emoji simply scale. 0 (the default, also for existing widgets) keeps the previous rendering unchanged.
  • Visu: The Link widget has a new option Back to the previously visited page. When it is set, the link returns to whichever page was open before β€” useful for a single "back" button that is placed on many pages and can be reached from different places. If there is no previous page (e.g. the page was opened directly or the browser was just started), the link falls back to its target page as before. Existing links are unchanged.
  • Visu: The word clock of the Clock ("Uhr") widget can now show the exact minute. The new option Minute dots in the corners adds four dots around the letter grid that light up clockwise from the top-left corner for the 1–4 minutes between the 5-minute steps, so "quarter to six" ("dreiviertel sechs") with two dots reads 17:47 and with three dots 17:48. With the dots switched on, the words round down to the last 5-minute step instead of to the nearest one; widgets without the option keep their current display.

Fixes 🐞

  • Admin GUI: After editing or cancelling the edit of a binding on a DataPoint's detail page, "Add binding" opened the form pre-filled with that binding and saving overwrote it instead of creating a new one. The form now always opens empty for a new binding (#1312).
  • Admin GUI: The confirmation dialog of the factory reset in Settings β†’ Danger Zone showed raw translation keys (settings.dangerzone.all.confirmTitle …) instead of its title, message and button label. It now shows the factory reset texts (#1315).
  • Admin GUI/KNX: In the adapter bindings on a DataPoint's detail page, the individual address (PA) of a KNX device linked to a group address ran straight into the device name β€” e.g. 1.1.102SCN-GLED1x.01 Glass LED Indicator. PA, device name and communication objects are now shown with a clear gap between them. #1199
  • Admin GUI/KNX: KNX individual addresses (PA) and group addresses (GA) were sorted as text instead of numerically per address part, so e.g. 1.0.10 and 1.0.100 were listed between 1.0.1 and 1.0.2, and 1/2/10 between 1/2/1 and 1/2/2. The device list, the device list of a group address, the group-address list and search, the group addresses of a communication object and the datapoint-traceability panels now compare every address part as a number. #1368
  • API: Exporting a logic sheet (GET /api/v1/logic/graphs/{id}/export) or a Visu page (GET /api/v1/visu/nodes/{id}/export) failed with HTTP 500 when its name contained a character outside Latin-1, such as an em dash ("Room β€” Action"), because the name went unencoded into the download's Content-Disposition header. Such names now get an ASCII fallback filename plus the exact name as filename* (RFC 5987); plain ASCII names keep the previous header (#1284).
  • API: Writing NaN, Infinity or -Infinity to a DataPoint (POST /api/v1/datapoints/{id}/value, or PATCH /api/v1/datapoints/{id} with a value) returned HTTP 500 for INTEGER DataPoints and was accepted for FLOAT DataPoints, which then put invalid JSON ({"v": NaN, …}) on the MQTT value topic. Such values are now rejected with 422 on both routes. In addition, the MQTT value payload now always sends a non-finite number from any source as null, so subscribers always receive valid JSON (#1153).
  • History: The Test Connection button in Settings β†’ History DB always reported InfluxDB v2 not reachable for InfluxDB 2.x, even with a correct URL, token, organization and bucket, because it probed /api/v2/ping β€” a path InfluxDB 2.x does not have (it answers 401 without and 404 with a token). Saving and writing were not affected. The test now checks reachability via /ping and then looks up the bucket via /api/v2/buckets with the token, so it also validates the credentials, and it names the step that failed: /ping not answering, token rejected, organization not found, or bucket not found. #1356
  • Logic Engine: A Delay (timer_delay) saved through the API with its duration under duration_s β€” the key of the Pulse block β€” fired after the 1 s default regardless of the value, because the Delay reads delay_s. A Delay that carries only duration_s (and a Pulse that carries only delay_s) now takes that value as its duration when it is a valid one, including sheets already stored, imported or restored that way; the next save from the Admin GUI stores it under the block's own key. Sheets edited in the Admin GUI were not affected. #1377
  • Logic Engine: The API client block's 1 MB response limit only cut the text after the whole response had been downloaded, and a JSON response was parsed in full before that. The block now reads at most 1 MB (rejecting larger responses up front when their declared size already exceeds it) and never parses beyond that. A response over the limit β€” text or JSON β€” now sets success to false with an error message instead of being truncated, while status still carries the HTTP status (#530).
  • Logic Engine: The Delay (timer_delay) and Pulse (timer_pulse) blocks could be placed, configured and saved, but never fired at runtime β€” a sheet routed through one of them stayed silent, without an error or a hint in the editor. Both now work. When a Delay has elapsed, the sheet runs again and its output triggers the downstream blocks once. A new trigger while the delay is pending starts it over, and the delay counts from the run that saw the trigger, so a slow block elsewhere on the sheet does not lengthen it. A Pulse sets its output true at once and false again after the configured duration, re-running the sheet on both changes. A new trigger extends it (retriggerable, e.g. staircase lighting), and the duration counts from the run that writes the pulse's start, so a slow block in that run does not use it up. Both blocks start on a rising edge, on a single pulse (e.g. from a Change Filter or the Trigger block) and on every repeated true telegram of a directly connected Read Object. A pending delay or running pulse survives a save and a server restart and still fires or ends at its planned time (at once if that has passed). Disabling a sheet discards its pending delays, and a pulse that ran out meanwhile ends on reactivation. The trigger level is kept as well, so an input that is still true is no new edge; when a save changes what feeds the trigger, its level is evaluated again β€” false now means the next rise counts, still true means no new firing (a changed threshold behind an input that is still met restarts nothing) β€” and after a restart a level whose input has fallen meanwhile is taken back. A timer's output may lead back to its own input without a Memory. A delay of at least one second begins a new logic cascade when it fires, as does a pulse of that length when it ends, so a blinker or keep-alive through data points keeps running, while a shorter one counts towards the cascade limit of the value that triggered it (#1166).
  • Logic Engine/Admin GUI: Changes to a logic sheet's connections were only kept in the editor and never saved on their own β€” drawing, deleting or re-wiring a connection and then switching sheets or reloading lost it, unless a block setting was changed or Save clicked afterwards. Every change to a sheet's content is now saved automatically after 500 ms without further edits, bundling a burst of changes into one save: connections created, deleted or re-wired (dragging a connection's end to another port now actually re-wires it instead of snapping back), blocks dropped, pasted, deleted or moved, block settings, and edits made directly on a block card such as renaming, negating an input or resizing a comment. A connection the graph validation rejects is no longer kept in the editor, where it used to block every later save. A failed save is always reported and never looks saved: the editor saves a sheet before leaving it for another sheet, a new, imported or duplicated one, and stays on it if that save fails; Run, Export and Duplicate act on the last edit, not on the older server state; and the browser asks before a reload or tab close while an edit is not yet sent. While a sheet loads or is being swapped, the canvas is read-only, so no edit lands on the sheet being left. All writes to a sheet β€” saves, enable/disable, rename and delete, from the editor and the sheet picker β€” now run one after another, so an older save can no longer overwrite a newer change. Only users with write permission trigger a save. #1333
  • Logic Engine/Admin GUI: Deleting the block that was open in the properties panel left the panel showing it. Edits there then appeared to be applied, changed nothing on the canvas and still triggered a save. The panel now closes when its block is deleted, and debug input overrides of deleted blocks are discarded as well (#1159).
  • Logic Engine/Admin GUI: The help button at the top right of a block's properties panel always opened the general "Block configuration" help page, whichever block was selected. It now opens the block's own help, the same as the help icon next to the block in the palette (e.g. the iCalendar section for an iCalendar block). Only a block without its own help page still shows the general page. #1411
  • LXC: obs-update --nightly listed a new release below every nightly of the same month β€” 2026.10.0 showed up ninth, after nightly-20261001 through nightly-20261008 β€” because a release's patch number was compared with a nightly's day of month. The version menu is now ordered by publication time, newest first; which releases are offered (the two most recent stable releases plus newer release candidates) is unchanged. The fix takes effect after the first update that installs it, since obs-update replaces itself from the installed bundle. #1323
  • LXC: obs-update now follows HTTP redirects when it fetches the release list and a channel manifest (curl -sfL). A renamed or transferred repository answers the GitHub API with 301 Moved Permanently and a JSON body, which curl -f does not treat as an error, so the release parser crashed with TypeError: string indices must be integers β€” the planned move to the open-bridge-project organisation would have cut every LXC installation off from updates. obs-update also restores the real installed version from the build stamp obs/version when the version file carries the tag of the migration patch release, and the new tools/build-migration-patch-bundle.sh builds that patch release for the placeholder repository that keeps installations with an older obs-update updatable, including those from 2026.4.5–2026.6.1 that replace themselves in place while running. #1322
  • Security: An API key holding operator grants on a DataPoint and an adapter instance could create, change and delete that DataPoint's bindings for every adapter that delegates binding changes (MQTT, ioBroker, Anwesenheitssimulation), although adapter delegation is documented as reserved for user logins. The binding routes now refuse every non-user principal, exactly like the other adapter-owned operations; admins and users with operator grants keep their access. Both checks share one decision that depends only on the principal type and the capabilities an adapter declares in code, so the WEBHOOK adapter now declares binding delegation like the other adapters instead of relying on a special case, and the AuthZ contract check rejects new adapter-type exceptions in authorization helpers. #1303
  • Visu: A page below a PIN-protected location (or another node) that has no access setting of its own could not be opened β€” after entering the correct PIN it showed Unauthorized, because the page was requested with the session of the page instead of the node that defines the PIN. Such a page now opens with the PIN session of that node. #1413
  • Visu: A private start page of a Visu device profile (access user) stayed empty after the login it asks for β€” it showed only the empty overview ("no sub-pages") instead of its widgets until the browser was reloaded, because the page tree was still the one loaded without login. The login now reloads the page tree, so private pages open right away. #1404
  • Visu: Closing a Chart ("Verlauf") widget while it was still loading its history β€” for example by switching pages quickly β€” raised an error in the browser console once the response arrived, because the widget then tried to draw into the chart it had already removed. A response that arrives after the widget was closed is now discarded (#1361).
  • Visu: Custom icons (imported SVG, KNX UF, FontAwesome) were only shown while signed in β€” anonymous and PIN visitors got an empty icon list, because the icon routes required a login. Without login the Visu now gets the icons of the pages the visitor may view: icons used on public and read-only pages and the page icons of the overview, and icons on PIN-protected pages once the PIN was entered. Icons used only on pages that require a login, or not used at all, stay hidden; signed-in users still get every icon.
  • Visu: When all series of a Chart ("Verlauf") widget were assigned to the right axis, an empty left axis with a 0–1 scale was still drawn. The left axis is now only shown when at least one series uses it, like the right one already was (#1111).

Known Issues πŸ””

  • none

Contributors 🀝

Thank you to everyone who contributed to this release:

Docker Image

docker pull ghcr.io/abeggled/openbridgeserver:latest

View on GitHub Container Registry

Checksums (SHA-256)

App Bundle

openbridgeserver-app-bundle_2026.11.0.tar.gz:

086b15ff0bc73e5d3dbaf3fa5b375d42f947570f19d3f04a36ab89b15853fd2e

openbridgeserver-lxc_2026.11.0_amd64.tar.zst:

62a3e832c74084307147ae69bf86c898f8ba8c4926335d7f29a8fe9ae81f5454

openbridgeserver-lxc_2026.11.0_arm64.tar.zst:

5f83a5c9602cb6807977ff7c9b0e577a78b1d9a68e8e4fda4c14ef96a97f21c1

Thank you!

Thank you for using the open bridge server!

Any support is highly appreciated - be it a star on Github or the recommendation of the project anywhere else.