we have successfully migrated our acceptance environment to the new v3 stack and so far nearly everything is working fine. Unfortunately one important part is not, which is sending messages to the devices (downlink).
We can schedule the downlink messages and we can see them being received and put onto the queue in the v3 live data view but when it comes to actually delivering them to the device, they do not arrive. Neither are the downlink messages seen on the Gateway, which we watched locally as well as on TTN.
On TTN we get the following error message in the Gateway console:
But the data json itself looks fine to me so I am asking here, is this something that has to do with the data we are sending or is this something on TTN side of things?
We tested both, scheduling the downlink message through the TTN UI as well as through the API
I have attached the json messages from the TTN UI for reference.
Maybe you can point me in the right direction to get this working…
Thanks for any help.