Orne Brocaar

I'm currently not planning to support this. There are two ways which allow you to inspect the uplink / downlink mac-commands (and PHYPayloads in general): * The live LoRaWAN frame-logs...

Actually, it might be better to close this issue. Personally I don't think it is a good idea to expose this to end-users. E.g. when you are a network operator,...

Yes, I can see the use-case of at least exposing the NetID field for now in the uplink messages. I'm a bit hesitant to add a Deployment ID at this...

I'm not exactly sure if I understand the issue. > replace the device-profile of device(s) What did you expect after this and what did not work? > msg="redis key does...

I do not plan to support freq. / channel filters but I could see an option to forward for all gateway IDs for a given backend useful. Would you be...

If it helps: ``` yocto@1f4bd9e63345:/build/tmp/raspberrypi/raspberrypi-glibc/work/x86_64-linux/rust-cross-arm/1.39.0-r0/targets$ cat arm-oe-linux-gnueabi.json { "llvm-target": "arm-unknown-linux-gnueabihf", "data-layout": "e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64", "max-atomic-width": "64", "target-pointer-width": "32", "target-c-int-width": "32", "target-endian": "little", "arch": "arm", "os": "linux", "env": "gnu", "vendor": "unknown", "target-family": "unix",...

I have made the following modification locally: ```python if 'neon' in feat: f.append("+neon") else: f.append("-neon") ``` I noticed that in some of the rust targets, this is unset rather than...

I have tried it, and the target config now looks like: ``` yocto@de7988916b62:/build/tmp/raspberrypi/raspberrypi-glibc/work/x86_64-linux/rust-cross-arm/1.39.0-r1/targets$ cat arm-oe-linux-gnueabi.json { "llvm-target": "arm-unknown-linux-gnueabihf", "data-layout": "e-m:e-p:32:32-i64:64-v128:64:128-a:0:32-n32-S64", "max-atomic-width": "64", "target-pointer-width": "32", "target-c-int-width": "32", "target-endian": "little", "arch": "arm",...

Using https://github.com/rust-embedded/meta-rust-bin instead if meta-rust solved my issue.

Hi @mullerch I removed this (also from the v4 Protobuf messages), but I don't mind adding this back if there is an use-case for this.