Adrian-Stefan Mares

For the record https://github.com/TheThingsNetwork/lorawan-stack/pull/5536 probably handles most of this. It still requires a list of gateway identifiers, but it does allow batch retrieval in order to lower the number of...

I've just checked the contents of the issue and I don't think that there are missing details here.There are only two clarifications I would add: - For ABP/Multicast devices, it's...

The NetID is not a better separator than the cluster ID in the context of the comment above - keep in mind that both The Things Stack Cloud and The...

The issue exists but I would drop the priority for now. Removing the milestone.

> Add a flow next to `DecodeUplink` in `PayloadEncoderDecoder` (`PayloadEncoderDecoderNormalizer`?), related services, API (`AppAs`), implementations of `PayloadEnocderDecoder` (whether or not they support it) and Console Another question that we should...

> You mean, it wouldn't make much sense to have an application-layer normalizer if there are various device-level decoders that produce different results? That wouldn't work indeed; they come in...

> Okay so how do we do this? Unmarshal JSON to a proto generated struct, then validate fields, and that generated proto struct would marshal back to the same JSON?...

> * nullable types (omitted field in DR vs nullable proto type with `value` subfield in proto JSON) That happens only if you use `encoding/json`. Using `jsonpb` will render normally...

> I'll benchmark this. Good. It may indeed be the case that I'm exaggerating. > But who will see that message? I meant to add it to the GitHub action...

> It is the case, see https://github.com/TheThingsNetwork/lorawan-devices/blob/master/bin/validate.js#L99. Or do you mean something else? We use the Go script so we have the same runtime as TTS. I didn't see that...