If it was previously registered on another network, then TTN should accept it. One cannot register an ABP device with hardcoded keys from another network (DevAddr, AppSKey and NwkSKey). But your device is using OTAA (DevEUI, AppEUI and AppKey), and that should be fine. All is not lost yet.
So: where did your friend use it earlier?
-
If your friend used it on TTN then be careful: deleting an application on TTN might orphan its devices, and then one might not be able to register such device with the same DevEUI, AppEUI and AppKey again. See How can I reuse hardcoded AppEUI and AppKey after I deleted an application?
Do NOT ask your friend to delete anything at this point.However, in that case, I’d assume you would see errors when trying to register the device with the same DevEUI, AppEUI and AppKey, which you did not mention, so that’s probably not the case.
-
If your friend used it on another network then TTN should (also) accept it. If your friend did not delete it from the other network yet, then if both networks receive the OTAA Join Request (orange icon in TTN Console), then both could transmit an OTAA Join Accept (green icon). Next, the node would receive the strongest signal (possibly the wrong network; the node would stop joining), or none at all (collisions, after which the node would try again). However, you don’t see that Join Accept in the gateway’s Traffic page at all.
As for not seeing the Join Accept:
-
The OTAA Join Request is not encrypted (the AppEUI and DevEUI are not a secret). So, in the gateway’s Trafic page you can see the AppEUI and DevEUI that the device sends. (The values you see in that Traffic page are not the ones you registered in TTN Console, but the ones sent by the device. Of course, these should match.) Check and double-check those values, again. And, again!
-
Clicking an item in TTN Console’s gateway Traffic page reveals more information, which may include some hints. What do you see there?
-
Any chance the Join Request is received by multiple TTN gateways, and another TTN gateway has a better reception, hence is selected by TTN to transmit the Join Accept? In that case, you should still see the Join Request (orange icon) in the application’s Data page as well, which then also shows a DevAddr, even if the device somehow does not actually receive the Join Accept at all. So, do you see anything in the application/device’s Data page?
Note that seeing a Join Accept only proves that the AppEUI and DevEUI are correct. If the AppKey were wrong, TTN would still send the Join Accept based on that wrong AppKey, which the device could not properly decrypt when the AppKey does not match. But for now, that’s not your problem; you first need to see TTN accept the join.
Unless it’s a really short message which allows for trial and error, in general you cannot. The EUIs are registered to to OnYield Inc Ltd, so it might be an OY1400 LoRaWAN Industrial communication and control unit. But of course, your friend used it, so must have some information too? Also, that would be a different topic.