Nicolas Juteau

Used DSN format: postgres://user:password@server/db?sslmode=require

Just in case others stumble on this issue, a workaround is to use the dsn string format `'user=chirpstack_ns dbname=chirpstack_ns sslmode=disable'`.

The following could also be configurable - number of parity fragments in each group - number of successive `FragSessionStatusReq` to send inbetween parity fragment groups

> I'm a bit hesitant to merge this. I understand that the MQTT Forwarder will not start until the Concentratord or UDP Packet Forwarder has started, however this does assure...

After a deeper look in the code, `gateway_id` is already set in config for sx1301 so it already works as described in my previous comment. The reason it does not...

I think there is a misunderstanding. I was suggesting a different way of solving the issue described here, that does not imply to override the gateway_id in the mqtt-forwarder. I...

I guess then it all comes down to the end-user use case. Some will use the `.../state/conn` - `CONNECTED` MQTT topic to monitor whether the gateway forwards concentrator messages, while...

> Or one could potentially use (the absence of) `concentratord_version` or `hal_version` metadata pushed by the mqtt-forwarder, but I have not tested this / do not know the behavior in...

Indeed, using [https://github.com/chirpstack/lorawan-device-profiles](https://github.com/chirpstack/lorawan-device-profiles) seemed like the definitive way to go for this purpose. However, we quickly found out it would not meet our needs since it only creates the device...

FYI: I have tried with other concentratord versions, down to 4.1.0 and the same issue occurs anyway (process panick + same log message with strange spidev path). I am concerned...