Skip to content

Update Abeeway Asset Tracker 3 (AT3) at3v3.2.29 to support 1.6.0 firmware - #1065

Open
hendAffes wants to merge 2 commits into
TheThingsNetwork:masterfrom
hendAffes:feat/abeeway-at3-v3.2.29
Open

hendAffes wants to merge 2 commits into
TheThingsNetwork:masterfrom
hendAffes:feat/abeeway-at3-v3.2.29

Conversation

@hendAffes

Copy link
Copy Markdown
Contributor

Summary

Update Abeeway Asset Tracker 3 (AT3) JavaScript codec to version 3.2.29 to support firmware v1.6.0.

Changes

  • Updated vendor/abeeway/asset-tracker-3.js to codec v3.2.29
  • Backward-compatible GADD index parsing: fw v1.5 (1-byte at offset 11) and fw v1.6+ (4-byte at offsets 11–14) both decoded correctly in shock notifications
  • New v1.6.0 parameters supported: ble_scan_presence_period, ble_scan_presence_max_time, cell_lpm_recovery_timeout, ble_scan_nb_beacons (up to 100 beacons)

Checklist for Reviewers

  • Title and description should be descriptive (Not just a serial number for example).
  • profileIDs should not be vendorID and should be a unique value for every profile.
  • All devices should be listed in the vendor's index.yaml file.
  • Firmware versions can not be changed.
  • At least 1 image per device and should be transparent.

Release Notes

  • Updated Abeeway AT3 codec to v3.2.29 with support for firmware v1.6.0 features (BLE presence detection, extended GADD index, cellular LPM recovery timeout)

hendAffes and others added 2 commits November 13, 2026 18:05
- Backward-compatible GADD index parsing: fw v1.5 (1-byte at offset 11)
  and fw v1.6+ (4-byte at offsets 11–14) both decoded correctly
- New v1.6 parameters: ble_scan_presence_period, ble_scan_presence_max_time,
  cell_lpm_recovery_timeout, ble_scan_nb_beacons (up to 100)
- Shock notification: 4-byte GADD index and numberShocks at new offsets
- 166 examples total (7 new v1.6 examples added)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
The v3.2.29 webpack bundle exported the codec under a named `driver`
library, so decodeUplink/encodeDownlink/decodeDownlink were not reachable
by the TTN scripting engine (entrypoint_not_found). Restore the UMD
header that spreads the exports onto the global scope, as in the
previously published version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@hendAffes
hendAffes force-pushed the feat/abeeway-at3-v3.2.29 branch from d2d2563 to 0d3db24 Compare November 13, 2026 17:13
@hendAffes

Copy link
Copy Markdown
Contributor Author

Hi @Jaime-Trinidad , I rebased this branch on the latest master to resolve the merge conflicts and added a small fix (0d3db24): the v3.2.29 bundle exposed the codec under a named
▎ driver export, so decodeUplink was not found by the TTN scripting engine. The codec entrypoints are now exposed as globals again, as in the previous version. The PR now only
▎ touches vendor/abeeway/asset-tracker-3.js, validation passes, and all checks are green. Could you please merge it when you have a moment? Thanks!

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants