Node and Uno cannot join

aberenyi · June 8, 2021, 9:32am

Hi there,

After some back and forth I’ve managed to register my gateway on TTS CE (V3).

However, I’m struggling with the end devices. I have 1x Node and 2x Uno, however I see the same issue with all of them.

I’ve registered and app and added end devices, but it looks like they cannot reach the network.

Logs from Node below.

09:12:27.760 -> Light: 15
09:12:27.760 -> Temperature: 27.94 C
09:12:27.760 -> Temperature alert: No
09:12:27.760 -> Moving: No
09:12:27.760 -> Button pressed: No
09:12:27.760 -> Color: Black
09:12:27.760 -> USB connected: Yes
09:12:27.760 -> Battery voltage: 4634 MV
09:12:27.760 -> -- TTN: STATUS
09:12:27.760 -> EUI: 0004A30B001C6521
09:12:27.760 -> Battery: 3294
09:12:27.798 -> AppEUI: 0000000000000000
09:12:27.798 -> DevEUI: 0004A30B001C6521
09:12:27.798 -> Data Rate: 5
09:12:27.798 -> RX Delay 1: 1000
09:12:27.798 -> RX Delay 2: 2000
09:12:27.798 -> -- TTN: JOIN
09:12:28.416 -> Model: RN2483
09:12:28.416 -> Version: 1.0.1
09:12:28.416 -> Sending: mac set deveui 0004A30B001C6521
09:12:28.416 -> Sending: mac set adr off
09:12:28.452 -> Sending: mac set deveui 0004A30B001C6521
09:12:28.452 -> Sending: mac set appeui 0000000000000000
09:12:28.489 -> Sending: mac set appkey B9.....................1B
09:12:28.489 -> Sending: mac save 
09:12:29.726 -> Sending: mac set rx2 3 869525000
09:12:29.726 -> Sending: mac set ch drrange 1 0 6
09:12:29.726 -> Sending: mac set ch dcycle 0 799
09:12:29.764 -> Sending: mac set ch dcycle 1 799
09:12:29.764 -> Sending: mac set ch dcycle 2 799
09:12:29.764 -> Sending: mac set ch dcycle 3 799
09:12:29.764 -> Sending: mac set ch freq 3 867100000
09:12:29.802 -> Sending: mac set ch drrange 3 0 5
09:12:29.802 -> Sending: mac set ch status 3 on
09:12:29.802 -> Sending: mac set ch dcycle 4 799
09:12:29.802 -> Sending: mac set ch freq 4 867300000
09:12:29.839 -> Sending: mac set ch drrange 4 0 5
09:12:29.839 -> Sending: mac set ch status 4 on
09:12:29.839 -> Sending: mac set ch dcycle 5 799
09:12:29.839 -> Sending: mac set ch freq 5 867500000
09:12:29.874 -> Sending: mac set ch drrange 5 0 5
09:12:29.874 -> Sending: mac set ch status 5 on
09:12:29.874 -> Sending: mac set ch dcycle 6 799
09:12:29.909 -> Sending: mac set ch freq 6 867700000
09:12:29.909 -> Sending: mac set ch drrange 6 0 5
09:12:29.909 -> Sending: mac set ch status 6 on
09:12:29.909 -> Sending: mac set ch dcycle 7 799
09:12:29.945 -> Sending: mac set ch freq 7 867900000
09:12:29.945 -> Sending: mac set ch drrange 7 0 5
09:12:29.945 -> Sending: mac set ch status 7 on
09:12:29.983 -> Sending: mac set pwridx 1
09:12:29.983 -> Sending: mac set retx 7
09:12:29.983 -> Sending: mac set dr 5
09:12:29.983 -> Sending: mac join otaa 
09:12:36.099 -> Join not accepted: denied
09:12:36.099 -> Check your coverage, keys and backend status.
09:12:46.116 -> Sending: mac join otaa 
09:12:52.223 -> Join not accepted: denied
09:12:52.223 -> Check your coverage, keys and backend status.
09:13:02.222 -> Sending: mac join otaa 
09:13:08.330 -> Join not accepted: denied
09:13:08.330 -> Check your coverage, keys and backend status.
09:13:18.331 -> Sending: mac join otaa 
09:13:18.369 -> Response is not OK: no_free_ch
09:13:18.369 -> Send join command failed
09:13:28.374 -> Sending: mac join otaa 
09:13:28.410 -> Response is not OK: no_free_ch
09:13:28.410 -> Send join command failed
09:13:38.392 -> Sending: mac join otaa 
09:13:38.426 -> Response is not OK: no_free_ch
09:13:38.426 -> Send join command failed
09:13:48.408 -> Sending: mac join otaa 
09:13:48.443 -> Response is not OK: no_free_ch
09:13:48.443 -> Send join command failed

Logs from Uno.

11:25:14.038 -> -- STATUS
11:25:14.038 -> EUI: 0004A30B001BAC9B
11:25:14.038 -> Battery: 3233
11:25:14.038 -> AppEUI: 0000000000000000
11:25:14.075 -> DevEUI: 0004A30B001BAC9B
11:25:14.075 -> Data Rate: 0
11:25:14.075 -> RX Delay 1: 1000
11:25:14.075 -> RX Delay 2: 2000
11:25:14.075 -> -- JOIN
11:25:14.678 -> Model: RN2483
11:25:14.678 -> Version: 1.0.5
11:25:14.712 -> Sending: mac set deveui 0004A30B001BAC9B
11:25:14.712 -> Sending: mac set adr off
11:25:14.747 -> Sending: mac set deveui 0004A30B001BAC9B
11:25:14.747 -> Sending: mac set appeui 0000000000000000
11:25:14.747 -> Sending: mac set appkey A4......................BF
11:25:14.781 -> Sending: mac save 
11:25:16.149 -> Sending: mac set rx2 3 869525000
11:25:16.149 -> Sending: mac set ch drrange 1 0 6
11:25:16.149 -> Sending: mac set ch dcycle 0 799
11:25:16.149 -> Sending: mac set ch dcycle 1 799
11:25:16.183 -> Sending: mac set ch dcycle 2 799
11:25:16.183 -> Sending: mac set ch dcycle 3 799
11:25:16.183 -> Sending: mac set ch freq 3 867100000
11:25:16.216 -> Sending: mac set ch drrange 3 0 5
11:25:16.216 -> Sending: mac set ch status 3 on
11:25:16.216 -> Sending: mac set ch dcycle 4 799
11:25:16.253 -> Sending: mac set ch freq 4 867300000
11:25:16.253 -> Sending: mac set ch drrange 4 0 5
11:25:16.253 -> Sending: mac set ch status 4 on
11:25:16.253 -> Sending: mac set ch dcycle 5 799
11:25:16.286 -> Sending: mac set ch freq 5 867500000
11:25:16.286 -> Sending: mac set ch drrange 5 0 5
11:25:16.286 -> Sending: mac set ch status 5 on
11:25:16.320 -> Sending: mac set ch dcycle 6 799
11:25:16.320 -> Sending: mac set ch freq 6 867700000
11:25:16.320 -> Sending: mac set ch drrange 6 0 5
11:25:16.354 -> Sending: mac set ch status 6 on
11:25:16.354 -> Sending: mac set ch dcycle 7 799
11:25:16.354 -> Sending: mac set ch freq 7 867900000
11:25:16.387 -> Sending: mac set ch drrange 7 0 5
11:25:16.387 -> Sending: mac set ch status 7 on
11:25:16.387 -> Sending: mac set pwridx 1
11:25:16.387 -> Sending: mac set retx 7
11:25:16.387 -> Sending: mac set dr 5
11:25:16.387 -> Sending: mac join otaa 
11:25:22.556 -> Join not accepted: denied
11:25:22.556 -> Check your coverage, keys and backend status.
11:25:32.526 -> Sending: mac join otaa 
11:25:38.665 -> Join not accepted: denied
11:25:38.665 -> Check your coverage, keys and backend status.
11:25:48.697 -> Sending: mac join otaa 
11:25:54.808 -> Join not accepted: denied
11:25:54.808 -> Check your coverage, keys and backend status.
11:26:04.833 -> Sending: mac join otaa 
11:26:10.970 -> Join not accepted: denied
11:26:10.970 -> Check your coverage, keys and backend status.
11:26:20.946 -> Sending: mac join otaa 
11:26:27.108 -> Join not accepted: denied
11:26:27.108 -> Check your coverage, keys and backend status.
11:26:37.098 -> Sending: mac join otaa

A couple of questions:

Is it possible that the end devices cannot connect to my local gateway to reach the network? This would make sense as I cannot see any traffic on the console’s gateways section, however, the gateway’s status is “Connected”. If so, how can one debug this?
The same happens with the Uno, even though I’ve updated the firmware to 1.0.5 and move the node quite far away from the Gateway (as I read somewhere that it should be at least 5 metres apart).
The 0000000000000000 JoinEUI/AppEUI looks suspicious, but that’s the value reported by the node, so I just went ahead with that.

Cheers

descartes · June 8, 2021, 9:45am

Denied would imply a problem with the registration.

I haven’t investigated fully, but the assertion on the console that all 0’s for an AppEUI doesn’t seem to work with older stacks. So perhaps generating one from the v2 console and setting that in the devices and on the v3 console would be worth a try.

aberenyi · June 8, 2021, 10:47am

Thanks for the fast reply @descartes.

I’ve tried that but the logs show the exact same Check your coverage, keys and backend status and Response is not OK: no_free_ch messages.

descartes · June 8, 2021, 10:56am

I was looking at the Uno log for the denied.

No free channel means that it has run out of channels to try due to duty cycle limits.

Did you setup the devices using the repository entries?

I have a ThingsNode running with a none-zero AppEUI and the Uno board uses the same Microchip LoRaWAN module so will need the same sort of setup.

aberenyi · June 8, 2021, 11:33am

I’m not quite sure what you mean by this - could you please elaborate?

descartes · June 8, 2021, 11:47am

When you add a device in v3, by default it asks if you know the device manufacturer, from which you can make a selection - or you can opt to make a manual entry.

aberenyi · June 8, 2021, 11:49am

Oh, I see.

Yes, I’ve created both types of devices by selecting the pre-populated options from the dropdown.

Node:

Hardware
Brand	the-things-products
Model	the-things-node
Hardware version	1.0
Firmware version	1.0

Uno

Hardware
Brand	the-things-products
Model	the-things-uno
Hardware version	1.0
Firmware version	quickstart

Should I try with manual entries?