Parking Sensor with TTN Gateway

[bryansmith]

@Dolsch what are the first 2 digits(prefix) of the dev-addr of your sensor? The ttn broker is probably dropping the packets.

Check your gateway console traffic for the devaddr you should see the data being received and dropped instead of forwarded.

You should read this whole post and it’ll give you a better understanding of what’s happening and the fate of your sensor.:
https://www.thethingsnetwork.org/forum/t/pycom-lopy-gateway-drops-packet-with-no-brokers/10043/6

Here are some highlights from the post:

@arjanvanb

@bryansmith

it’s a 17 prefix so from according to the link below I can’t use it

Indeed; 0x17 has been assigned to EveryNet in Russia, so even when roaming is in place one day in the far future, TTN might forward it but even then you won’t be able to enjoy TTN Console.

@arjanvanb

@bryansmith

The devaddr, appskey and nwksey is hard coded so I had to override it.

What did you override? You cannot make TTN just handle any address you want:

@arjanvanb

@htdvisser wrote in Slack, about just copying some existing DevAdr into TTN Console:

[…]

We don’t issue DevAddresses for 00 / 01 but it is possible to “force-register” a device with such address (not in the console, only with ttnctl)

For such devices, we can still route data

But uplink for anything else than 00 / 01 / 26 / 27 will just be dropped before it’s even considered by the backend

So, unfortunately you’ll need to find a way to change the DevAddr in the device.