Hello,
I registered a device in TTN that was already sending data. Since it was assigned to the wrong group, I deleted it and re-registered it. Reactivating the device doesn’t work. (No activity yet) What can I do? Thank you
Details matter - please expand on what device, where registered, where moved to, details, are you attempting to re-register… are you device owner? collaborator? using Web/Console/GUI or CLI?
Yes, I own the device (Adeunis ARF8190BA). I registered it in the TTN via the web browser, deleted it, and then re-registered it. During the re-registration, I changed the End Device ID. I deleted it because I was told it’s better to select and register the device from the LoRaWAN Device Repository. Then I also got the correct payload formatter.
Did the person advising you mention how often the device does a link check?
Its current session is now invalid and you’ll have to wait to see how long it takes to figure this out & rejoin. Because there is no connection unless the device connects - changing on a computer doesn’t tell the device anything unless it uplinks - but because the session is now invalid, it won’t reach the application …
Don’t worry, this is only a moderate foot-gun problem. Confirmed downlinks are the best way to remove feet.
Confirmed downloads… what do you mean by that?
Message at Schedule Downlink:
Downlinks can only be scheduled for end devices with a valid session. Please make sure your end device is properly connected to the network.
Basically saying dont use them! If you are in trouble now, that is nothing c/w the trouble that can ensue from trying to use them…and it then goes wrong. That is not directly relevant to problem you are trying to fix.
What do you know of
What is the behaviour of the ARF unit?
The ARF sensor is here… it’s not being used. I don’t see any activity.
WRT Link Check?!
We are all volunteers here and few will bother to go research detailed device behaviour or research specific devices…unless you provide links to actual device used, manuals/user guides etc. Provide info on how configured, what firmware builds etc. That will start the process of people helping you. Nick has already flagged one avenue for investigation…
Unfortunately, uploading the manual is not possible because the file is too large. The sensor was registered manually.
End device ID: XXXX
Frequency plan= Europe 863-870 MHz (SF12 for RX2)
LoRaWAN version: 1.0.3 rev A
The AppEUI and DevEUI are correct, as is the AppKey.
And a good thing too because the internet doesn’t need another copy and would just take some more disk space. This was what you were asked for:
As to this:
This was a light hearted way of saying you’d royally screwed yourself - as in you’d shot yourself in the foot but it wasn’t as bad as using confirmed downlinks to really shoot yourself in the foot properly.
The bottom line is that you’ve changed the “login” for the device on the server but it doesn’t know that so it using it’s previous “login”. By login I mean the OTAA session which is a LW fundamental so saying much more if you aren’t clear on it is pointless. You can read about it here. The whole of the Learn section may be worth a review.
If you are on TTN, why are you not using the recommended frequency plan?
In the meanwhile, if the device isn’t being used, what’s the actual problem?
And if it’s “here”, where ever that is, maybe on your desk, can you not just reset it or take the battery out & back in?
PS, it is entirely possible to remove a device and re-register it AND transfer the active session over using the CLI, but that’s some serious typing!
I solved the problem myself. The sensor is registered and transmitting. Thanks to all the volunteers.
How?
We ask that people share solutions so that others can benefit - this is the reason we spend time helping - to improve the pool of collective knowledge.
And if it’s “here”, where ever that is, maybe on your desk, can you not just reset it or take the battery out & back in?
So not so much solving it yourself as doing a reset / battery disconnect 
I’ve removed the battery many times, to no avail.
Install the software, connect the sensor to the PC, enter the data, and send it to the sensor. I’ve never had this process with any other sensor before… and I’ve re-registered sensors many times, without any Problems.
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.