Things Uno not joining anymore

Hi all,

after The Things Conference I did set up The Things Uno and it was able to join TTN via my picoGateway (8 chan) at home and also with the gateways in the city of Aachen.
Then 2 days ago the Uno stopped working and now rejects to join the network. I did check coverage and my gateway at home. I also checked the status page of TTN. All systems are working just fine.
After digging around a bit, I updated the RN2483 from 1.0.1 to 1.0.3 to check if it was a chip related issue. Sadly this didn’t work out, too.

Microchip LoRa dev util shows:
21:33:56.652 > mac join otaa
ok
denied

The TTN console for the gateway just keeps blank all the time. No join request is registered.

The TTN console now shows the join request, but the join is not successful as before…2018-02-20 21_50_21-The Things Network Console
2018-02-20 21_51_24-The Things Network Console

Is there anything else I could check?
Could this be a hardware related issue, like the antenna is broken or smth. like that?

All the best
/Robert

I had the same this afternoon… did you see the status report ?
I suggest try again tomorrow … looks a lot like a kind of DDos

1 Like

Could be related to the outage of the EU bridge, but the node went offline at about
2/19/2018 07:10:14
Perhaps the UDP flood began on Monday and the collapse of the TTN backend was just today.
I will give it a try tomorrow, when TTN is back to normal…

1 Like

#metoo :sunglasses:

…but it should also show a Join Accept response if the keys were accepted and the same gateway was selected to transmit that (or some error if all gateway(s) are busy). And the device’s Data page should show the activation too, if the keys were accepted.

I doubt that would be affected by the earlier network problems. But maybe it is.

Orange/yellow uplink for a Join Request, and a green downlink for its Join Response:

(August 2017 screenshots.)

the thing I see from his screenshot is no join response and a very short interval

Nice catch, that’s a short interval indeed: it’s not even waiting for the 5 seconds RX1 in some cases.

which is strange for a TTN uno with RN2483 … it would never allow that (I think :smirk: )

Also, when joining too often, the chances of repeated (invalid) nonces increase too. (Though that would also show an error: OTAA shows "Activation DevNonce not valid: already used")

Is the node somehow resetting all the time? Is its power okay?

Is there anything in the “trace” part of the Join Requests in TTN Console?

1 Like

Hi BoRRoZ and Arjan,

the TTN Uno is just configured normal. I also did a full reset and reconfigured it, but the result is just the same. The Uno is powered by a 5-Port USB-Power-supply rated 40W total with 2.4A max per Port. And only 3 devices connected one mobile phone, a twine temp sensor and the TTN Uno…

The current setting from Arduino console is:
    -- STATUS
EUI: 0004A30B001BAE04
Battery: 3233
AppEUI: 70B3D57ED0009DC8
DevEUI: 0004A30B001BAE04
Data Rate: 5
RX Delay 1: 1000
RX Delay 2: 2000
-- JOIN
Model: RN2483
Version: 1.0.3
Sending: mac set deveui 0004A30B001BAE04
Sending: mac set adr off
Sending: mac set deveui 0004A30B001BAE04
Sending: mac set appeui 70B3D57ED0009DC8
Sending: mac set appkey 7A79DE6E55FDED572B6E13AA709115C8
Sending: mac save 
Sending: mac set rx2 3 869525000
Sending: mac set ch drrange 1 0 6
Sending: mac set ch dcycle 0 799
Sending: mac set ch dcycle 1 799
Sending: mac set ch dcycle 2 799
Sending: mac set ch dcycle 3 799
Sending: mac set ch freq 3 867100000
Sending: mac set ch drrange 3 0 5
Sending: mac set ch status 3 on
Sending: mac set ch dcycle 4 799
Sending: mac set ch freq 4 867300000
Sending: mac set ch drrange 4 0 5
Sending: mac set ch status 4 on
Sending: mac set ch dcycle 5 799
Sending: mac set ch freq 5 867500000
Sending: mac set ch drrange 5 0 5
Sending: mac set ch status 5 on
Sending: mac set ch dcycle 6 799
Sending: mac set ch freq 6 867700000
Sending: mac set ch drrange 6 0 5
Sending: mac set ch status 6 on
Sending: mac set ch dcycle 7 799
Sending: mac set ch freq 7 867900000
Sending: mac set ch drrange 7 0 5
Sending: mac set ch status 7 on
Sending: mac set pwridx 1
Sending: mac set retx 7
Sending: mac set dr 5
Sending: mac join otaa 
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa 
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa 
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa 
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa 
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Response is not OK: no_free_ch
Send join command failed
Sending: mac join otaa 
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa 
Join not accepted: denied
Check your coverage, keys and backend status.
Sending: mac join otaa 
Join not accepted: denied
Check your coverage, keys and backend status.

Ok, after removing the device from my app, and re-adding it, with the new AppKey, everything works fine. Don’t really know, what made the UNO run mad, but now it looks quite normal.
2018-02-21 13_39_39-The Things Network Console

1 Like

not to me… 2x same packets @ the same time and skipping one frame

  • ok skipping can be collusion… better to look at application/device console

You are right BoRRoZ, I had to restart the Gateway. Now the Msg is received just once :slight_smile:

2018-02-21 15_37_32-The Things Network Console

compared to the gateway.log

Screenshot_20180221-153719

But SerialConsole showed only one transmission:
Sending: mac join otaa
Join accepted. Status: 00000401
DevAddr: 26012CF9
– LOOP 15MIN SendSensorData
Sending: mac tx uncnf 1 08011D00C000452500E0D7452D00D01846
Successful transmission

----- FIXED by reboot ----
2018-02-21 16_18_32-The Things Network Console

2 Likes