Orne Brocaar

> So it can’t be monkey patched? I don't see it is not possible. I do distribute ARM binaries (see the compile instructions in the docs). I'm just saying that...

> [lora-appserver] internal/migrations/migrations.go:1: running "go-bindata": exec: "go-bindata": executable file not found in $PATH This should be installed here: https://github.com/brocaar/lora-app-server/blob/master/Makefile#L68 It looks like in your ARM build something is failing. I...

Have you tried to use the arm32v7 golang and alpine containers, e.g. ``` FROM arm32v7/golang:1.12-alpine AS development ENV PROJECT_PATH=/lora-app-server ENV PATH=$PATH:$PROJECT_PATH/build ENV CGO_ENABLED=0 ENV GO_EXTRA_BUILD_ARGS="-a -installsuffix cgo" RUN apk add...

This is currently not (yet) supported, but would be possible already when using the API.

Wouldn't a correlation ID solve this issue? Usually a location or device-status message comes from an uplink. With a correlation ID you could retrieve these fields from the uplink event...

I'm aware that there might be some issues with rejoin-requests. I hope to test this asap when I have a device available / setup which can reproduce this issue.

What is the ID of your gateway?

Please see the logs: > subject name : CN=0011223344556677 `0011223344556677` != `6f114e6bfcc4e407`, which explains the error: > The certificate Common Name (CN) does not match with the expected CN

@MatteoAndreoni you have configured the ChirpStack Gateway Bridge to validate the client-certificate, but you have not configured a client-certificate on the BasicStation: > tc has no key+cert configured - running...

Thanks @hilt0n, implementing duty-cycle control and statistics will be very useful for the near future. I'll park this now until the AS-NS merge has been done as I need some...