pierrot10
(Pierrot10)
June 28, 2021, 12:09pm
3
Thanks for your reply.
However my gateway is saw from V2 but not from V3.
I wonder if I registered it correctly to V3.
Because when I look at my Gateway from V2, the gateway ID is eui-1234567812345678
in V3 I enter ttog1 as gateway ID and in the EUI field, I saved 1234567812345678
Should I create a new gateway in V3, with the Gateway ID eui-12234567812345678?
Then what should I save in the EUI field?
I am a bit confused because here it show what I did
descartes
(Nick McCloud)
June 28, 2021, 12:24pm
4
You can put anything you like in the ID field.
You put the EUI in the EUI field.
You also change your gateway to point to the v3 server for your region!!
pierrot10
(Pierrot10)
June 28, 2021, 12:34pm
5
OK, then why my gateway is not seen in V3? I may have did some things wrong.
In fact, in the V3 console, the gateway is not connected.
Or should I wait for first message? But usually, the gateway is seen as soon as I power it
descartes
(Nick McCloud)
June 28, 2021, 12:38pm
6
Have you changed the configuration on the gateway so it is sending to the v3 server like I asked above?
pierrot10
(Pierrot10)
June 28, 2021, 12:46pm
7
You mean, I have to connect the ethernet cable to the TTOG and look for that change?
And hwo can I knoiw the V3 server for my region
I am a bit panic, but I just created an new application and , in V2, I was used to use HTML integration. I did not find HTML integration in V3. Has it been suppressed?
Because in that case, I no workaround to make my station working with TTOG in V3, for now…
NB: In V2, I have not check “Automatically Update Gateway”
descartes
(Nick McCloud)
June 28, 2021, 12:52pm
8
Surely the TTOG already has an Ethernet cable plugged in?
You need to go on to the TTOG console and change the router address - you may benefit from reading the instructions.
Reading the documentation for gateways at:
pierrot10:
Has it been suppressed?
No, it’s now called Webhooks
I’m not aware that v2 will know the gateway should be on v3 so it won’t update automatically anyway.
Rather than panic, read the documentation for the TTOG and look at the online documentation for migration.
pierrot10
(Pierrot10)
June 28, 2021, 1:12pm
9
Yes
But as I am in Switzerland, I guess my server is correct
But at some point, I have to delete my gateway from V2. I have not delete it yet.
No, it’s now called Webhooks
In the same time, I found the webhook and I tried creating a custom but it look so different. But let solve first the gateway, because it sill disconnected
pierrot10
(Pierrot10)
June 28, 2021, 2:37pm
10
Someone, in Switzerland, had succesfully registered a TTOG gateway in stack V3?
In my Gateway console the TTN server is: eu1.cloud.thethings.network
But I have been loged into the gateway, and I controlled the configuration following that page
The page provide you a link to the router address for the region
Into my TTOG gateway, I have not saved: router.eu.thethings.network
but ttn.opennetworkinfrastructure.org
but I guess, it does not matter, isn’t?
descartes
(Nick McCloud)
June 28, 2021, 2:53pm
11
No, no you don’t, because you can NEVER go back - look at the forum discussion where we countless say this.
pierrot10:
Into my TTOG gateway, I have not saved: router.eu.thethings.network
but ttn.opennetworkinfrastructure.org
but I guess, it does not matter, isn’t?
How will it know where to send the uplinks to the new version of the TTN??
You HAVE to change the gateway server address ON THE GATEWAY to the one shown on the console.
kersing
(Jac Kersing)
June 28, 2021, 3:04pm
12
pierrot10:
Into my TTOG gateway, I have not saved: router.eu.thethings.network
but ttn.opennetworkinfrastructure.org
but I guess, it does not matter, isn’t?
On the V3 gateway page there is a button to download global_conf.json. In that file search for “server_address” and use that value on your gateway. If you don’t it will not work.
pierrot10
(Pierrot10)
June 28, 2021, 3:09pm
13
Aïe, I did it
You HAVE to change the gateway server address ON THE GATEWAY to the one shown on the console.
Ok, then my mistake is here. Initially I have ttn.opennetworkinfrastructure.org
I am sorry but I am confused because here It show
router.eu.thethings.network
EU 433 and EU 863-870’ for Europe or
ttn.opennetworkinfrastructure.org
for Switzerland.
to the one shown on the console
Then I have to saved ‘eu1.cloud.thethings.network’ ???
Thanks for your patience
pierrot10
(Pierrot10)
June 28, 2021, 3:12pm
14
kersing:
server_address
OK, thanks kersing and descartes.
I am going to make the change on the gateway
descartes
(Nick McCloud)
June 28, 2021, 3:13pm
15
pierrot10:
Aïe, I did it
I never understand why people take unilateral action after asking for advice.
pierrot10:
Ok, then my mistake is here. Initially I have ttn.opennetworkinfrastructure.org
I am sorry but I am confused because here It show
router.eu.thethings.network
EU 433 and EU 863-870’ for Europe or
ttn.opennetworkinfrastructure.org
for Switzerland.
Those are the instruction to v2.
I gave you the link to v3 documentation which yielded the correct address of ‘eu1.cloud.thethings.network’.
pierrot10:
Thanks for your patience
Can you not hear me screaming at the screen from here??
pierrot10
(Pierrot10)
June 28, 2021, 3:26pm
16
Hello
OK that work now. My gateway is now connect.
@descartes sorry to not have understood immediately. What you wrote, it was what I should have done earlier :).
I never understand why people take unilateral action after asking for advice.
But what the matter now as my TTOG gateway has been migrated to V3 and V2 will closed in december 2021?
My second Gateway is a TTIG and I will migrate it later. I read the V3 is not ready yet for TTIG. I do not if it’s still available.
descartes
(Nick McCloud)
June 28, 2021, 3:29pm
17
C’est la vie!
It is not ready yet but will be soon, it is being tested by the TTI team now.
pierrot10
(Pierrot10)
June 28, 2021, 3:58pm
18
Thanks a lot.
Now next challange is the HTTP integration (webhook) in V3
descartes
(Nick McCloud)
June 28, 2021, 5:34pm
19
Same principals as v2 but the JSON format has changed
pierrot10
(Pierrot10)
June 28, 2021, 10:01pm
20
descartes:
JSON format has changed
OK; it look a big change
The format start as the following
{
"end_device_ids": {
"device_id": "st-27",
"application_ids": {
"application_id": "per"
},
"dev_eui": "0000000000000020",
"dev_addr": "2XXXXXX"
},
and the data I need to collect are now in ‘uplink_message’ instead of ‘payload_field’
Isn’t?
I upgraded our TTOG to the Basics Station firmware for V3. But you must ensure the internal clock is set.
pierrot10
(Pierrot10)
June 29, 2021, 7:00pm
22
hello @mid-walesha ,
Thanks but what do you mean by internal clock. I lookedt at the gateay and at console under the gateway section, I did not see any internal clock option