My new Things node seems not able to send data (uplink) to its application; butit is constantly sending activation data.
I did the following actions :
I was able to retrieve the device EUI (by downloading the DeviceInfo sketch) and registering it in my console; by creating an application I received an application EUI and an Appkey, which was copied in the Basic sketch (and uploaded to the device). I’ve checked these codes twice.
In the application data console, the device seemed to be sending constantly activation codes and receives always new devices addresses. But it does not answer with sending temperature, battery level,…etc.
I made a new application and restarted the complete work process.
I have installed new batteries (rechargeables).
The RSSI seems very low (fluctuates between -117 and -121), but as it is receiving its activation request, i am not sure that this is a problem.
Could anyone give a suggestions what other actions to take to overcome this? Is the device broken? Why does the application receive different device addresses?
Just to be sure: the RSSI you see is that for the OTAA Join Request (orange icon), as sent by the node and received by one or more gateways. (Probably one gateway as you’re only mentioning one RSSI.) If you have access to gateways logs (like in TTN Console) then you’d also see the OTAA Join Accept being sent (green icon). You cannot see the RSSI for the Join Accept, but most likely the node has not received that, and keeps retrying.
So, you need a better reception (take the node outside; increase its height?), or need to try at a lower data rate (higher SF):
As an aside: as TTN assigns a DevAddr, it has accepted the Join Request, so the settings in the device match the settings in TTN Console (DevEUI, AppEUI, AppKey).
Thank you for the quick reply.
I changed SF to 10 and this resulted in regular uplinks (the node was already installed outside to measure the outside temperature).
And the application reports a better rssi (-113 ->-115) and multiple gateways.
You suggest to access the TTN gateway, but can you confirm that, as these are not my property, I cannot configure them in my console?
If you know the gateway owner, you could ask them to add you as a collaborator in TTN Console. But unfortunately, there is no “read-only” collaboration, so they might kindly decline such request…
So indeed: you cannot see the traffic of gateways that you do not own, and are not a collaborator of.
