@engelking Since my gateway has both received and transmitted messages, I assumed it was functional for downlinks, at least with some nodes.
FWIW this morning it started retrying at 10:07 local time and stopped after slightly over 100 messages.
I have subscribed to the Braunschweig group in August, but not been in contact with anyone else (not a good year for getting together). There is a Technical University (or something similar) in Wolfenbuettel to the south of me. I know they have one or two gateways., From there you have better LOS to my location, than from most of Braunschweig.
Given that the broadcast restarted past 10am this morning, I immediately started suspecting a project of a late sleeping student 
Not my son atleast… he is in Hamburg! 
(to far to reach your GW unless something miraculous wrt atmospheric ducting). Thinking about it that is also too early…
It might not be, but >95% of the time it is.
Would be good to figure out the identity of that malfunctioning box and report it. Could be a software issue, could be sitting on a too slow backhaul network such that the transmit commands have expired before they actually hit the hardware (even for join accepts, they’re held in the server until less than a second before the transmit deadline, so that they can be shipped to potentially primitive gateways in strict order)
Noticed the other day that the ST micro eval kit’s gateway would basically cause this sort of problem, too, as it lacks the usual transmit amplifier and thus transmits substantially more weakly than a node would - so it would work close in for the owners own lab experiments but cause precisely this kind of problem further out.
@AvdN I do also see the node (from the north of Braunschweig) and two other ones with almost the same DevEUI (4C and 4D at the end). I just installed a Gateway using a self-hosted ChirpStack. My guess is the local energy supplier, who also started to install some gateways and nodes. Also this Thread hints to some energy meters, that use this AppEUI.
I just registered, so cannot send PMs. Maybe you can, so we can solve this privately. Since it’s a regional issue, it’s maybe not of interest for the others.
@JonasS @AvdN I am seeing also OTAA requests every second in Hannover from multiple nodes (cca0e5fffe06XXXX / 2211FFEEDDCCBBAA) with Spreading Factor 12. As the node ID is increasing permanently, I don’t think it is by accident.
Have you already found something? I would like to locate that as well.
BR
Hello there!
Is there anybody out there? ;)) In the last month i play to register OTAA a raspberry with dragon - (yes i’ll find out, now slightly incompatible) and actual a arduino MKR WAN 1300 without succsess here in north BS - sometimes it is easyer with basic informations,
Should the b827ebfffeae093f reachable or is this a stupid idea or something privat? I found a lot probaby points (wrong freq. , wrong antenna, wrong version (dragon), fake antenna) every info is welcome ;))
nice day!
No body here but us mice! 
Out where? Where are you? North BS = ? Country code BS = Bahamas, or Bishop Stortford a town, or…
According to this (Old V2 data?):
https://account.thethingsnetwork.org/api/v2/gateways/eui-b827ebfffeae093f
Lat and Longitude indicates GW in the middle of the Arabian sea (looks handy for monitoring Somali Pirates!) - so unless moved under V3?
Mice? scratch that… nobody here but us fish!
WRT your kit and set up - we need details and specifics, otherwise just guess work. What have you tried, what results or outcomes have you seen? What firmwre or toolchains used? Which libraries etc.
I think it may have moved as it is now showing as slightly north of Mr Cryptic’s postal code. That gateway was last seen by TTN at 20:38 today but it doesn’t mean Mr C is in range of it because the Dragon he has on top of his Pi may not have sufficient fuel to reach it.
Almost always being successful with getting started with LoRaWAN requires you have your own gateway so you can see what’s going on. But in theory, if you setup the MKR WAN and get within a few hundred meters of the gateways location you may get a result.
Apart from that, less SteamPunk and more detail would help us to help you.
by about 25m, was checking if anyone paying attention whilst getting the message across that we have no detailed info to even start to help… quick switch of Lat/Lon allowed for better illustration of we dont know where you are or what using - Arabian Sea more effective/dramatic than 'how close are you to IKEA Braunschweig"
Guess it will depend on ground clutter and topology between just where around the BerlinerStr Gleismarode or Voksmarode areas OP is based and its associated higher ground relative to the GW position close to the lower ground near Kreiz Braunschweig Nord. Suspect the intervening slightly elevated ground near Kralenriede ‘may’ be an issue esp if the MKR WAN 1300 being used close to local ground level…given it looks like we are talking 4-5.5km distance…
Have you considered a job as a bounty hunter?
Oh, Ok ;)) a lot people out there - Thanks for jokes and instant reply! ;))
Yes, BS could be Bahamas but maybe not in a request connected with Braunschweig, Germany ;))
and sorry here some informations:
the correct notation was N52…E10… not N10 E52
ground altitude of my testbed: 80,5m (+5) altitude gateway 72m (…+?)
LoS: est. 2,05 km
my Ant.: BINGFU Lora Gateway Antenne 868MHz 2dBi (hopefully! 868MHz…)
And i’ll do not want claim your time - so i focus on (maybe) simple questions:
How can i check if the gateway Gateway ID:* b827ebfffeae093f? is working, online, current valid version, connectable and my OTAA will work?
healthy greetings from Germany (not under the sea)
Is it on v2 or v3?
good question
TTN Mapper shows
b827ebfffeae093f
EUI: B827EBFFFEAE093F
Network: NS_TTS_V3://ttn@000013
Last heard at 2022-07-23T09:18:22.062285Z
Lat, Lon: 52.31001187973531, 10.518301427364351
Altitude: 8m
this means V3? an online ? but connectable?
can i be shure OTAA ‘must’ work?
I can see it on V3 - Online
{"netID":"000013","tenantID":"ttnv2","id":"eui-b827ebfffeae093f","eui":"B827EBFFFEAE093F","clusterID":"ttn-v2-eu-4","updatedAt":"2022-01-05T14:09:05.458106Z","location":{"latitude":52.31004776,"longitude":10.51830208,"altitude":0,"accuracy":0},"antennaCount":1,"online":false}
{"netID":"000013","tenantID":"ttn","id":"b827ebfffeae093f","eui":"B827EBFFFEAE093F","clusterID":"eu1.cloud.thethings.network","updatedAt":"2022-07-23T09:38:29.841989Z","location":{"latitude":52.31001187973531,"longitude":10.518301427364351,"altitude":8,"accuracy":0},"antennaPlacement":"INDOOR","antennaCount":1,"online":true,"frequencyPlan":{"region":"EU_863_870","loraMultiSFChannels":[868100000,868300000,868500000,867100000,867300000,867500000,867700000,867900000]},"rxRate":3685.3882,"txRate":0}
And how would anyone be able to discern that - we are all volunteers, there is no reason for us to scroll up or indeed answer, make it easy for us to help you.
As it happens both me & Jeff have serious stalker skills and actually know Germany, so you happened to be lucky, this time.
Altitude and antenna type are not so relevant - you can’t make radio waves do as you wish but if you are on the door step of the gateway, there is no reason for it not to hear your device.
First, read the replies you’ve already got - I’ve already answered the first two.
Current valid version? What’s that? And irrelevant due to the above.
Connectable? You don’t connect to a gateway - search the forum for the normal responses to this mis-idea - devices transmit, gateways hear and if the signal is properly formatted, send it to the Network Server.
The way to debug a device is to look at the serial output - does it seem it’s trying? Then check the gateway web console to see if it is hearing the device - which you can’t do as it’s not your gateway which is why we say get a gateway of your own. Then if the join request is being heard, look at the device web console to see if the EUI’s & AppKey are being accepted and a join accept is being sent.
I had a Dragon 32 about 40 years ago as a first computer but I’d not think of hooking it up to a small berry fruit. Which is the third and possibly last time anyone will prompt you for details (correct spellings, hardware & software version numbers, etc) of your kit to help you debug it.
Either will work.
This issue is all about range to gateway. Once in range, then it will be about the correct credentials and using an actual device, not a mythical flying lizard sitting on fruit.
Reason for the question is to make sure the gateway is on V3 ( if not migrate it, as you know lots of gateways still on v2), but it is on v3
5 KM radius
And your gateway is fairly active, with “rxRate”:3685.3882
