Hi All,
I have a V3 Application that handels my Abeeway Micro Tracker.
The Abeeway Micro Tracker does not join the network at all and get “Host ‘cluster’ failed to handle message: No device matches uplink”
I have double checked my DevEUI, AppEUI and AppKey, I copied and pasted them now.
Any ideas as where to look?
I don’t suspect the Abeeway Micro Tracker at this moment.
Your log does not appear to show a join request, but rather in-session traffic from someone else’s node (or maybe your node, misconfigured).
Please don’t blank out the non-secret device address, if you hadn’t done so people could see if it’s even a TTN device address, traffic from TTNv2 with which V3 can do nothing, or even traffic from an entirely different network.
I don’t suspect the Abeeway Micro Tracker at this moment.
You somewhat should for now.
You need to get to the point where you’re seeing raw traffic that is an actual join request, or better yet, join requests showing in the TTN console.
So far its unclear if you have any evidence that the node has transmitted at all.
Your log does not appear to show a join request, but rather in-session traffic from someone else’s node (or maybe your node, misconfigured).
Yes the concern is that it is not joining, as I said I have actually copied and pasted the information.
Please don’t blank out the non-secret device address, if you hadn’t done so people could see if it’s even a TTN device address, traffic from TTNv2 with which V3 can do nothing, or even traffic from an entirely different network.
This is the message from the gateway every time I press the button, so I am pretty sure that it is the node
You need to get to the point where you’re seeing raw traffic that is an actual join request, or better yet, join requests showing in the TTN console.
This is my concern, the node were working a few days back, suddenly stopped working, tried about a day to get it to work, but to no avail.
Then decided to delete it and recreate it, it refuses to join.
I had a similar problem with another node, deleted it recreated it and then after about 3-4 hours stared to work.
That means the node doesn’t attemp to join and hasn’t recently (look at the counter). For an OTAA node you need to reset it and see join packets.
Where in V3 do you reset the the frame counters now?
afaik it is not possible to reset the frame counter in V3 in the moment - only by OTAA.
You do not want to reset the frame counters. You want to reset the node (the actual hardware) to force it to join again. Resetting the counters in the back-end won’t help.
You can reset counters for ABP in v3.
There is no need to reset counters for OTAA - that’s baked in.
The only way to reset the device is ether via a downlink or wait for the battery to go flat, lets wait the for the battery to go flat, should take 3-5 days 
And when does, do you replace it? If so, what is stopping you from replacing it now? Or is it a rechargeable where you really need to run out of juice?
Or, from the docs, you could ask it nicely to join with a few special squeezes:
https://docs.thingpark.com/thingpark-location/Content/C-Procedure-Topics/ReDoJoinRequestMT_T.htm
Thank you Sir, 100% working
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.