You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 14, 2021. It is now read-only.
Do an OTAA join. Configure the FSK channel manually as the network does not configure it. Force the device to DR7 (FSK).
What went wrong or what is missing?
The uplinks are transmitted. I can see them on the air using an rtl-sdr dongle. I can also see my gateway receives the packets. When telling the gateway to forward packets to my own computer I can see them being received. The packets do not appear on the gateway traffic tab on the TTN Console. The packets also do not appear under the data tab of the device on the Console.
Do you have Screenshots?
No
What kind of OS/Browser/Gateway are you using? Which version?
I tried both the Semtech UDP packet forwarder as well as the MQTT gateway connector (mp_pkt_fwd).
What are the IDs and EUIs of your Device/Gateway? (if applicable)
--
What do your configuration files look like?
--
What do your log files look like?
When sending the packets to my own computer I can see the FSK packets are received.
This is a bug report for the backend.
Uplinks on the FSK channel.
Do an OTAA join. Configure the FSK channel manually as the network does not configure it. Force the device to DR7 (FSK).
The uplinks are transmitted. I can see them on the air using an rtl-sdr dongle. I can also see my gateway receives the packets. When telling the gateway to forward packets to my own computer I can see them being received. The packets do not appear on the gateway traffic tab on the TTN Console. The packets also do not appear under the data tab of the device on the Console.
No
I tried both the Semtech UDP packet forwarder as well as the MQTT gateway connector (mp_pkt_fwd).
--
--
When sending the packets to my own computer I can see the FSK packets are received.
No
The text was updated successfully, but these errors were encountered: