A websocket ping?
No, just old fashioned ping -t
I believe it is pending still. I haven’t had a reply yet on that thread (only posted today).
My guess is once they manually enable it on the backend it should just work. From what I read I should NOT delete the gateway from the console as the EUI will not be usable anymore?
so this other issue is that you want to connect a gateway to the AU router but it’s not done yet?
What do I need to do next to get this thing working…
- Is it the fault of the server.
- Is the Gateway set up incorrectly.
- Other.
Thank you.
CDonohoe
Can you provide your EUI? or Ping me directly via a direct message and I can see if your gateway establishes contact with the server or not.
Please find the gateway details:
Gateway ID
eui-2cf432fffe5041c0
Description
lorawan test
Owner
Status
not connected
Frequency Plan
Europe868MHz
Router
ttn-router-eu
CDonohoe
@KrishnaIyerEaswaran2 Yes I believe so.
Nothing appeared to connect last night (I have three different devices around the property that send data at regular intervals).
The devices were working correctly last night before I powered off our Sentrius gateway.
Checking the TTN console, it showed this morning the TTIG was last seen 7 hours ago. I just power cycled it and the console showed it online but no messages have been received as of yet (I restarted one of the sensing devices to force it to reconnect/send an update).
Gateway is eui-58a0cbfffe8031b1
Hello Krish,
The gateway eui is 58-A0-CB-FF-FE-80-1D-F4 and not as posted previously.
CDonohoe
The gateway eui is 58-A0-CB-FF-FE-80-1D-F4
Did you register that in TTN Console? I’m not seeing it on either https://www.thethingsnetwork.org/gateway-data/gateway/eui-58a0cbfffe801df4 nor https://www.thethingsnetwork.org/gateway-data/user/CDonohoe but maybe that’s caused by NOC issues. (And the curl
command yields 404 Not Found, Not Provisioned, for that.)
Is registration in TTN Console required?
Yes, the registration is mandatory. For now, these gateways are identified as US915/EU868 based on their EUIs and a default frequency plan is sent out, even when not registered properly. But, with the official V3 support, you can select other supported frequency plans while you register your gateways as you would do with other gateways currently.
Hey @arjanvanb that is interesting you say that, I’ve had no luck with my gateway all.
Checking the link https://www.thethingsnetwork.org/gateway-data/user/matqua shows that it is on the US_902_928 frequency plan.
And I soldered some headers and drilled a few holes in the case and I see this in the serial debug:
[S2E:INFO] Configuring for region: US902 -- 923.0MHz..928.0MHz
So I guess that could be why it is not accepting messages from my nodes.
The FAQ on the forum could be outdated (but: same text on https://www.thethingsnetwork.org/docs/gateways/thethingsindoor/faq.html which also still says it’s only EU868 and US915). The rest is black magic to me, so you’ll need @KrishnaIyerEaswaran2 to explain more. Until then: please provide details about the frequency plan and all that you selected in TTN Console?
@CDonohoe: This gateway 58-A0-CB-FF-FE-80-1D-F4
is not in my list of gateways. Perhaps you purchased it from a seller that manages these gateways themselves.
@arjanvanb is right. At the moment, we only support the EU868
US915
frequency plans by default based on the band supported by the Gateway itself.
The 915 gateways also support AU915 but that’s manual configuration for me so I only do a small subset of gateways for test purposes.
Ok then. So is it possible for you enable AU915 on my gateway eui-58a0cbfffe8031b1?
Please add your gateway to this list; TTIG AU915 support
Once we reach a certain number, I’ll batch configure them (mostly later today).
All of this is a temporary annoyance. I’m working hard on getting a self service server setup for TTIGs. More information to follow later.
Already done. Thanks for that.