BluetoothLE Hubs Release Notes
1.5 - November 6, 2026
Section titled “1.5 - November 6, 2026”Chore
BluetoothLE Hubs now lives in the Shiny Hubs repo and releases with it: every Shiny.BluetoothLE.Hubs and Shiny.UniversalHubs package shares one version from 1.5
Fix
Connecting to a host found in an earlier scan no longer times out on Apple devices. Starting a scan drops undiscovered peripherals from Shiny’s cache and creates fresh ones, so the connection’s events went to the new instance while the client waited on the old one.
Connect now uses the manager’s current peripheral for that device (IBleManager.GetKnownPeripheral)Feature
Handler hubs: hubs added while the app runs, with no compiled hub class. An
IBleHubHandler answers methods by name, with values exactly as the caller serialized them. AddBleHubServer(server => server.AllowHandlerHubs()) lets the server start without compiled hubs, and IBleHubHandlerHost.Add / Remove manage them, each an IBleHubHandle to start, stop and push to. A hub added while the GATT service is up rebuilds it when it first starts, and the other hubs’ BLE clients are asked to reconnect then. An advanced seam that Universal Hubs’ dynamic hubs are built on. See Handler HubsFeature
BleHubArgumentWriter.WriteSerialized(bytes) and BleHubArgumentReader.ReadSerialized() write and read a value already serialized, for hubs that never see the values’ typesEnhancement
Hidden client seams for proxies dispatched by name:
BleHubClient‘s protected InvokeSerializedCore / StreamSerializedCore leave results as the host serialized them, and AddBleHubClientCore() registers what every client needs without a proxy (AddBleHubClient now uses it). Universal Hubs’ dynamic hub clients are built on themEnhancement
An error a hub relays keeps its type: throwing a
BleHubRemoteException from a hub method sends the caller its RemoteErrorType rather than the exception’s class name, on every transport. BleHubRemoteException.TypeOf(exception) gives the type a caller is toldFix
BleHubHost.Dispose no longer touches the BLE hosting manager when hosting never started. It threw on a device without usable Bluetooth1.4 - October 23, 2026
Section titled “1.4 - October 23, 2026”Feature
Media channels: an ordered, bidirectional packet pipe per hub connection on its own L2CAP PSM, for live audio and video. Host:
BleHubHostOptions.EnableMediaChannels(maxPacketSize, secure), IHubContext<THub>.MediaChannelOpened and GetMediaChannel(connectionId). Client: IBleHubConnection.CanOpenMediaChannel and OpenMediaChannel(). Both sides get an IBleHubMediaChannel (Send, Receive, MaxPacketSize, IsOpen, Completion), closed when the connection ends or the hub stopsEnhancement
The handshake reply carries the media PSM and a random per-connection token, which the client presents on the channel. The fields are additive, so 1.4 is wire compatible with older hosts and clients
Enhancement
The transport seams carry media channels:
IBleHubClientTransport.CanOpenMediaChannel / OpenMediaChannel (with defaults, so existing transports keep compiling) and IBleHubTransportEndpoint.MediaChannelOpened1.3 - October 12, 2026
Section titled “1.3 - October 12, 2026”BREAKINGChore
Built on Shiny 6:
Shiny.BluetoothLE and Shiny.BluetoothLE.Hosting 6.0.0, and Shiny.Extensions.Serialization 6.0.0. Apps referencing Shiny 5.x packages must move to 6.0.0. Wire compatible with 1.21.2 - October 10, 2026
Section titled “1.2 - October 10, 2026”Fix
Discover() no longer lists the app’s own host. An app that hosts hubs and scans at the same time saw its own advertisement. It is now matched by the service UUID and the advertised local name while the host advertises, so give hosts distinct namesEnhancement
Every new BLE connection asks for the largest ATT MTU (517, was 512), and the negotiated size is logged. Android negotiates it; Apple platforms negotiate on their own
Fix
Frames now fill the link. Shiny’s
IPeripheral.Mtu is the payload size (ATT MTU minus 3), and blehubs treated it as the ATT MTU, so every write and notification was 3 bytes smaller than the link allowed. BleHubConnectedClient.Mtu now reports the ATT MTU (3 more than before). Wire compatible1.1 - October 9, 2026
Section titled “1.1 - October 9, 2026”Feature
Clients can rename themselves without reconnecting:
IBleHubConnection.Rename(name) and ClientName. The host checks the new name with ValidateClient, then runs the new BleHub<T>.OnRenamedAsync(previousName), either of which can refuse (BleHubRemoteException.RenameRefused). IHubContext<THub>.ClientRenamed is raised, and BleHubConnectedClient.Name follows renamesFeature
IBleHubHost.Rename(localName) renames the host without stopping anything. It re-advertises under the new name and tells every connected client, whose HostName updates and HostRenamed event is raised in order with hub eventsEnhancement
The transport seams carry renames:
IBleHubTransportEndpoint.Rename, IBleHubPeerChannel.HostRenamed, IBleHubClientTransport.Rename and IBleHubClientTransportEvents.HostRenamed. New members have default implementations, so existing transports keep compilingBREAKINGEnhancement
One service UUID per host: every hub is a characteristic inside one service, and it is the only UUID advertised. Set it with
server.ServiceUuid(...) on the host and o.ServiceUuid on each client (both default to BleHubProtocolOptions.DefaultServiceUuid). Hubs no longer take a service UUID, and neither does BleHubRegistration. Hubs on separate services overflowed the 31 byte advertisement: Android hosts failed to advertise, and iOS hosts were invisible to Android scannersBREAKINGEnhancement
One registration call per side. Hosts use
AddBleHubServer(server => server.ServiceUuid(..).Host(..).Protocol(..).AddHub<THub>(characteristicUuid, ..)), called once; it refuses duplicate hubs, duplicate characteristics and malformed UUIDs at registration. Clients use AddBleHubClient<T>(characteristicUuid, o => ...) with the new BleHubClientOptions (ServiceUuid, Protocol). AddBleHub, ConfigureBleHubHost and ConfigureBleHubProtocol are removedEnhancement
The host and client packages now target Android, iOS and Mac Catalyst as well as
net10.0, and register the platform BLE stacks for you (AddBluetoothLeHosting() / AddBluetoothLE()). On Apple the client turns off iOS’s background connect, disconnect and notification alerts, because hubs are foreground only; register your own AppleBleConfiguration first to change that1.0 - October 9, 2026
Section titled “1.0 - October 9, 2026”Initial Release


