Error when Upgrading TTN Lorawan Devices

rgarmyn · March 7, 2024, 3:44pm

Hi,
I’m attempting to upgrade the TTN library of devices to the latest version. I’m running ChirpStack v4.5 on Docker. I pulled the latest version and executed make import-lorawan-devices, but encountered the following error;

Reading codec function code path="/opt/lorawan-devices/vendor/n-fuse/sta.js"
thread 'main' panicked at chirpstack/src/main.rs:120:18:
called `Result::unwrap()` on an `Err` value: Unexpected region: AS923-2
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
make: *** [Makefile:4: import-lorawan-devices] Error 101

Has anyone encountered a similar issue, I am not familiar with Rust so I didn’t try yet to trace back the error, Is there another way to upgrade the TTN library in Docker?

rgarmyn · March 8, 2024, 7:30am

To clarify; the import works when using the version from GitHub - brocaar/lorawan-devices: Device Repository for LoRaWAN devices, which is from 2y ago.
The upgrade doesn’t work when using the latest version of the repository from: GitHub - TheThingsNetwork/lorawan-devices: Device Repository for LoRaWAN devices.

Liam_Philipp · March 8, 2024, 3:35pm

Probably because it’s illegal now:

github.com/chirpstack/chirpstack

Remove importing The Things Network's Device Repository

chirpstack:master ← TheThingsNetwork:feature/remove-device-repo-import

opened 01:52PM - 15 Nov 22 UTC

johanstokking

+0 -292

This removes importing The Things Network's Device Repository via `import-ttn-lo…rawan-devices`. First, the import is full reuse and/or extraction of a database that is obtained, verified (reviewed, tested) and structured by The Things Industries, and therefore violates database protection rights. This right is implicitly granted under EU law, but we clarified this today in https://github.com/TheThingsNetwork/lorawan-devices#database-protection-right. Second, this code depends on a very specific structure of the Device Repository. We do not provide guarantees that we follow this structure going forward. In fact, we are planning changes to the database structure that will break this import tooling. I guess it is interest of the ChirpStack user community that import functionality is unavailable rather than it is broken. We do not accept that our branding is associated with functionality that we know will break in the future.

rgarmyn · March 8, 2024, 6:08pm

That’s a shame, I contributed my decoders to TTN as they were not available yet in the library…
So it’s not legal anymore to import the library after the version from 2022?

Liam_Philipp · March 8, 2024, 6:13pm

To my knowledge: no. You are no longer allowed to import the entire repository. But if you’re looking for a single device codec, a little copy paste never hurt anyone

jjanderson · March 14, 2024, 11:03am

Yea, TTN basically sucks all the hard work out of their community and then claims the work as their own making legal threats to anyone who tries to use community code… what a nice company /sic

ccall48 · March 14, 2024, 11:14am

yeh i think they missed many contributed to it because it was more so for lorawan community in general rather then just them…

in saying that it was still working on my test lab until the last pull i did which shows the same error. so maybe there is just an error in their repo as its supposed to be to a standard.