v1.0.3 Changelog

v1.0.3 Changelog

Security hardening, safer updates, and a smoother multi-device setup flow.

Firmware v1.0.3 focuses on getting BLEShark Nano devices updated, paired, and connected reliably without making customers manually reflash older units.

This release was tested across old setup firmware, old main firmware, new setup firmware, new main firmware, quick power-cycle reconnects, and a fresh 16-device setup batch.

TL;DR

v1.0.3 hardens OTA updates, improves setup and pairing, makes Shiver mesh reconnects faster, and fixes several sync, portal, storage, BLE, Wi-Fi, and IR edge cases.

For most customers, the important part is simple: existing devices can move onto this release over OTA, paired data is preserved, and multi-device setup is more reliable.

To get the full benefit, update every Nano in your mesh to v1.0.3. Mixed versions can still exist in the field, but mesh reliability and setup behavior are best when every node is current.

Safer Updates

OTA updates now use TLS/HTTPS, recover faster from transient download issues, and verify firmware more carefully before installation.

If a download is incomplete or does not match what the device expects, the update is aborted instead of being installed. Update reliability has also improved on memory-constrained devices by preparing more runtime memory before flashing.

Pairing And Setup

Pairing is more secure in v1.0.3 while still supporting devices that are already in the field.

Existing setup firmware can continue provisioning devices onto this release, so older units do not need to be manually reflashed before updating. New setup firmware also handles multi-device pairing more carefully by keeping devices in setup mode until pairing data has been shared successfully, then releasing them for OTA.

This path was tested across old setup firmware, old main firmware, new setup firmware, new main firmware, and a fresh 16-device setup run.

Mesh Reliability

Mesh peer propagation is more reliable, especially when large groups are joined together from smaller paired clusters.

Quick reconnects are also faster. If a device briefly loses power and comes back, the mesh now rebuilds that connection without waiting for the old long timeout path. In testing, reconnect time dropped from roughly 60 seconds to roughly 12 seconds, a 5x improvement.

Multi-hop commands, multi-device sync, and saved Wi-Fi network sharing remain enabled for paired devices.

Sync, Portal, And Storage

Large mesh sync transfers are more reliable and show better progress during busy mesh activity.

Settings and saved Wi-Fi data are written more safely, including names and passwords with quotes, backslashes, or special characters. The settings and captive portal paths also avoid printing Wi-Fi passwords or full provisioning payloads over serial logs.

Captive portal and AP Spam compatibility improved.

Samsung devices now support captive portal functionality with the Nano in our confirmed tests.

The transfer portal issues with captive portal uploads have been fixed, and uploaded portal/text files can now be viewed or deleted more reliably from the file manager. Large text and HTML files also open more reliably on-device without using as much memory.

BLE, Wi-Fi, And IR Fixes

BLE Spam now has broader Apple, Android/Fast Pair, Samsung, generic BT, and Windows Swift Pair payload coverage, with better identity rotation.

AP Spam random SSID generation is safer and more reliable around empty scan results.

IR fixes improve TV-B-Gone behavior, receiver cleanup, and memory use during raw timing playback.

Compatibility

Existing settings, paired Nanos, saved Wi-Fi networks, captures, portal data, IR remotes, and user files are preserved across OTA.

For best results, update every node in a mesh to v1.0.3. This release is designed so older setup and main firmware already in the field can move onto the new release without manual reflashing.

Stable release builds are available for US, EU, UK, CA, and ROW.

Back to blog