Gateway appears Disconnected and unable to connect a sensor

1

Hello, I have a problem, well actually two. I have a Browan/MerryIOT Hotspot Miner V1 that i use as a gateway. This has worked quite well. Now I have purchased a SenseCap Temperatur sensor that I want to connect to my gateway. This has though caused problems. The Sensor should connect to the network automatically when I turn it on, but it does not. So i thought maybe the problem is the GW. Well… even though the webpage of the GW shows all green and connected, the TTN Console shows Disconnected. Could this be the reason for my Sensor issues, and does anybody have any tips to guide me?

Regards
Espen

2

Sounds like a helium gateway. Is it connected to TTN?

You don’t connect sensors to a gateway. You connect them to a LoRaWAN network like TTN. LoRaWAN is not WiFi.

A node/sensor in TTN need to be registered in the TTN console before it can join the network. Have you registered it?

3

Welcome @helliesene

We need details, I cant guess what you have tried.

Can you ping your gateway from your PC on the same network?
Are your gateway connected vie GSM?
Can you ping from the network the AWS servers? What is the latency?
Did you double check the configuration on the gateway?
Are your gateway Gateway EUI correct?
What do you see in the console?

Did you create a application for your sensor?
Did you register you sensor in the application?
What do you see in the console?

Go thru the basic and read the documentation

4

Hi, thanks for your answer.

Yes its a Helium GW, and yes it´s connected to TTN with the ID: sagenegw1. I am aware that the sensor does not connect directly to the GW, but the sensor needs coverage for it to connect, thats what i tried to say (sorry for me not being clear) And yes, I have registered the node to the TTN network as well as an application with the ID: tempsagene.

Here is a screenshot of the GW
Screenshot 2022-08-06 at 12.47.24

I

5

Nee more details than a pic of you gateway.

What do you see in the live consoles?

6

Hi Johan, thanks for your reply.

Yes, i can ping the GW, and its online as far as I can see. I´ve booted it a hundred times, checked the configuration, changed from wifi to cable, and everything is green from the GW.

I think I should first try to fix my sensor, because the solution may be closer :slight_smile:

I have created an application for the Sensor, and it is registered according to the manual from the vendor. Here is a screenshot of the console, there is a lot of information, and I am unfortunately not sure as to what information is critical and what is nice to know.

Screenshot 2022-08-06 at 13.13.41

7

LoRa stands for Long Range Radio access.

So how close are you as I can see the sensor is trying to join.

Generally you want to be 10m or more from the gateway with a wall in between the sensor and gateway. You want you RSSI down below the -50 to -60, -100 is even better.

If you select the join request, what to you see?

8

hmmm… 10 meter? You mean miles right? :slight_smile:

What I get is this if I click on the “Accept Join Request”
{
“name”: “js.join.accept”,
“time”: “2022-08-06T11:11:14.132049114Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “temperatur-sagene”,
“application_ids”: {
“application_id”: “tempsagene”
},
“dev_eui”: “2CF7F12032400078”,
“join_eui”: “8000000000000009”,
“dev_addr”: “260BA6B8”
}
}
],
“correlation_ids”: [
“rpc:/ttn.lorawan.v3.NsJs/HandleJoin:01G9SDM865V2Y9N9H7F1M6HKAZ”
],
“origin”: “ip-10-100-15-117.eu-west-1.compute.internal”,
“context”: {
“tenant-id”: “CgN0dG4=”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“unique_id”: “01G9SDM86M7RWEFS237943X1YZ”
}

9

Yes, 10 meters or more with a wall in between.

The RF bleeds over the channels if your RSSI is to high and it never joins. So increase your distance.

10

I am sorry… What happened to Long Range?? It says 10 km… Does it have to be a gateway every 10 meter? That cant be right. Does this apply only when joining? There are a few GW in the neighborhood, so I can take my sensor out for a ride, make it join and then take it home. Would that work?

11

Yes, just try it. Beeing to close to the gateway might cause problems.

12

For testing. Working up to lots of KM

13

Right, I´m out for a walk then
:slight_smile:

14

In the join REQUEST details you’ll be able to find which gateway(s) received the message. If you know where those are located you can check if the sensor is likely to receive the reply message. (Most sensors do not have very good and well placed antennas limiting the receiving capabilities)
In an urban environment LoRaWAN can be limited to well under a mile. In flat country side with line of sight between the gateway and the sensor 10 miles or more is not a problem.

15

ok, is that the tenant-ID?

16

So, unfortunately it did not help. Though I have som new messages in the console. First I get this:
{
“time”: “2022-08-06T13:47:36.334Z”,
“name”: “synthetic.error.network_error”,
“isError”: true,
“isSynthetic”: true,
“unique_id”: “synthetic.1659793656334”,
“data”: {
“error”: “TypeError: network error”
}
}

And then:
{
“time”: “2022-08-06T14:03:02.376Z”,
“name”: “synthetic.status.reconnected”,
“isError”: false,
“isSynthetic”: true,
“unique_id”: “synthetic.1659794582376”
}

And then this:
{
“name”: “js.join.accept”,
“time”: “2022-08-06T14:04:16.227154785Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “temperatur-sagene”,
“application_ids”: {
“application_id”: “tempsagene”
},
“dev_eui”: “2CF7F12032400078”,
“join_eui”: “8000000000000009”,
“dev_addr”: “260B3A1F”
}
}
],
“correlation_ids”: [
“rpc:/ttn.lorawan.v3.NsJs/HandleJoin:01G9SQH2YQWJ9J538B6SFGNJQM”
],
“origin”: “ip-10-100-6-236.eu-west-1.compute.internal”,
“context”: {
“tenant-id”: “CgN0dG4=”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“unique_id”: “01G9SQH2Z3HM9YF68ZCMVBPNSZ”
}

And finally:
{
“name”: “as.up.join.forward”,
“time”: “2022-08-06T14:04:18.018561911Z”,
“identifiers”: [
{
“device_ids”: {
“device_id”: “temperatur-sagene”,
“application_ids”: {
“application_id”: “tempsagene”
},
“dev_eui”: “2CF7F12032400078”,
“join_eui”: “8000000000000009”,
“dev_addr”: “260B3A1F”
}
}
],
“data”: {
“@type”: “type.googleapis.com/ttn.lorawan.v3.ApplicationUp”,
“end_device_ids”: {
“device_id”: “temperatur-sagene”,
“application_ids”: {
“application_id”: “tempsagene”
},
“dev_eui”: “2CF7F12032400078”,
“join_eui”: “8000000000000009”,
“dev_addr”: “260B3A1F”
},
“correlation_ids”: [
“as:up:01G9SQH4PZ4A41TJGQ55C5VM0V”,
“ns:uplink:01G9SQH2YGW0XG01G11T4BJW61”,
“pba:conn:up:01G88B64003KTG4P6APMNB4FJB”,
“pba:uplink:01G9SQH2P73CFD8FSKE15WFJHA”,
“rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01G9SQH2YGHFJJXGJ38Q90QVXX”,
“rpc:/ttn.lorawan.v3.NsAs/HandleUplink:01G9SQH4PYYAJCWWVCKYANX03T”
],
“received_at”: “2022-08-06T14:04:18.015191388Z”,
“join_accept”: {
“session_key_id”: “AYJzeIvaHZ58JECbZgzPLA==”,
“received_at”: “2022-08-06T14:04:16.208386617Z”
}
},
“correlation_ids”: [
“as:up:01G9SQH4PZ4A41TJGQ55C5VM0V”,
“ns:uplink:01G9SQH2YGW0XG01G11T4BJW61”,
“pba:conn:up:01G88B64003KTG4P6APMNB4FJB”,
“pba:uplink:01G9SQH2P73CFD8FSKE15WFJHA”,
“rpc:/ttn.lorawan.v3.GsNs/HandleUplink:01G9SQH2YGHFJJXGJ38Q90QVXX”,
“rpc:/ttn.lorawan.v3.NsAs/HandleUplink:01G9SQH4PYYAJCWWVCKYANX03T”
],
“origin”: “ip-10-100-6-190.eu-west-1.compute.internal”,
“context”: {
“tenant-id”: “CgN0dG4=”
},
“visibility”: {
“rights”: [
“RIGHT_APPLICATION_TRAFFIC_READ”
]
},
“unique_id”: “01G9SQH4Q29DYSGJNBQKPX11PG”
}

17

When you connect to the SenseCap via the debug port, what version is the firmware?

Does it say what version the “LoRAWAN version” is?

Had a look at their manual, it is rather old

18

The manual say 1.0.2 but we are way beyond that now at 1.1.0 - Not that it is plausible.

19

It says software version 3.4 and hardware 2.0

20

You will need to investigate if you have the correct version.