Petr Gotthard

No, there is not.

Yes, pull requests are always welcome. There is no reason for not using COPY, I guess. It's just my poor Docker expertise.

Hello Matthias,   No handler is needed for Join. That should always work.   Note that the messages like PULL_RESP or PULL_ACK are exchanged between the server and the gateway only. They...

Could you share log from the server too? The rxpk looks like a non-join frame.

``` 2020-02-01 09:28:00.796 [warning] @lorawan_backend_factory:send_to_connectors:179 Message not sent to any connector ``` Suggests the join was successful, it device sent another message, but didn't receive downlink it expected so it...

I suspect the device really expects the Downlink response. The decoder expects the application payload, i.e. what is written in your PDF. Teh LoRaWAN fields are handled by the server....

Thanks :) (b) Elixir is a layer on top of Erlang, so you should be able to translate the binary syntax more easily than with other languages. There we attempts...

Hello. Just define a JSON string and send it to the websocket. The `data` and `port` fields should be enough. Some examples are at https://github.com/gotthardp/lorawan-server/blob/master/doc/Handlers.md#downlink

Hello. I have no plans (yet) to implement class B. I am even not sure it can be implemented using the existing packet_forwarder.

Or you can perform a thorough analysis of the lorawan spec and the packet-forwarder protocol and derive the absolute minimum requirements for class B support. I may be wrong when...