Skip to content

v2.1.1 - Bug Fix: Device Name Persistence

Latest
Latest

Choose a tag to compare

View all tags
@ril3y ril3y released this 28 Oct 12:11
· 14 commits to main since this release
v2.1.1
7805a6c

Bug Fix Release

Fixed

  • Custom device name now persists in CAPS response - The get:capabilities command now correctly returns the custom device name set via set:name instead of always reverting to the default board name.

Changes

  • CAPS response now uses get_device_name() instead of hardcoded platform_capabilities.board_name
  • Added CHANGELOG.md to track version history

Previous Issue

When you set a custom device name with set:name:MyDevice, it would work for get:name but the web UI would show the old name after querying capabilities because CAPS was still returning the default board name.

Downloads

Firmware files will be automatically built and attached by GitHub Actions in a few minutes.

  • uCAN-feather_m4_can-v2.1.1.uf2 - For Adafruit Feather M4 CAN (drag-and-drop installation)
  • uCAN-pico-v2.1.1.uf2 - For Raspberry Pi Pico (drag-and-drop installation)

Installation

  1. Connect your device while holding the BOOT button (enters bootloader mode)
  2. A drive named FTHRCANBOOT (Feather) or RPI-RP2 (Pico) will appear
  3. Drag the appropriate .uf2 file to the drive
  4. Device will automatically reset and run the new firmware

See CHANGELOG.md for full version history.

Assets 7
Loading