After activating a parking sensor it sends three times data and remains silent after that. It doesnt sent any join request to which I could reply. Following an example of the payload: “80 52 00 03 70 80 02 00 01 78 9D C8 A9 F2 99 BC 7C A8”.
I want to forward the payload to an application which will forward the data again to a HTTP-Server. Is this possible without a successful join?
Has anyone experience in working with parking sensors and lora or any idea I could get further?
Many thanks for your responses.
I tried to setup a private routing environment and change the gateway sending his data to this backend. But I couldn’t find any chance to change the server address except of the router. But I think its not the right way. I used
Hi, yes I contacted the manufacturer and they said that it is NOT possible to change the devAddr of the sensors.
Yes I read the tutorial carefully and get the environment running.
The last problem which was left is changing the gateway sending to my private environment. If this is not possible I have to use another gateway… Therefore I need a confirmation that I this is not possible.
So is it right that I can not use the parking sensors with a devAddr beginning with 70 and is it too right that I can not change the official TTN Gateway to use a private backend, which will not drop data from the parking sensors?
If both is right I will send the parkings sensors or the gateway back. I just need a confirmation from someone with experiences.
Correct. Those have not been assigned by the LoRa Alliance, so you could say they’re “illegal”. Of course, anyone can do whatever they want, but as soon as they are using the LoRaWAN logo they need to adhere to the rules of the LoRa Alliance.
Note that according to some messages at Slack, apparently Actility/ThingPark Wireless does support whatever DevAddr it gets. But: I would not rely on that unless they explicitly tell you they will keep doing that in the future:
Hey guys, just want to ask some help if someone can point me to a direction where to find the solution.
My problem is this TBS-220 Parking sensor running AS923.
I have a RAK831 gateway running in Raspberry Pi host, and it can’t seem to get the data coming from the parking sensor.
I know the sensor is working because it is working in our “thingpark wireless” platform, but can’t seem to make it work in TTN.
@cruzer I guess you considered this, but in case you did not: if you continue to use Actility then I’d ask them about support of 0x70 addresses in the long turn, before getting more sensors. Just like TTN, they should only handle their own NetID…
I don’t know:
Your attempts to use @brocaar’s lora gateway bridge with the TTN Gateway are wrong, as the TTN Gateway is simply not using the Semtech protocol, which is what that bridge expects.
I don’t expect someone to write firmware for the TTN Gateway to support the Semtech protocol. (Also, right now, I would not know how to load such firmware into the gateway.)
I’d expect the TTN Gateway to some day support private backends (if those support the protocol that the TTN Gateway uses). But I don’t know if it’s already possible today. Maybe it is already possible.
@Dolsch, just for clarification, I would contact the manufacturer asking what is not possible: a) change the DevAddr by yourself, or b) upgrade the firmware of the sensor by yourself. I am just asking because if option b) is possible, then perhaps you could “create” some DevAddr in the TTN console and ask the manufacturer to compile the firmware with those specific DevAddr-s and send them to you, so you could upgrade the sensors firmware by yourself. Of course there is still an option c): you create DevAddr-s in the TTN console and ask the manufacturer to send you sensors with these DevAddr-s programmed in the new sensors. I am almost sure that the manufacturer will happily do this exchange because negative comments in this forum are not really advantageous for businesses that would like to stay long enough in the LoRaWAN based IoT arena… But this is just my personal opinion.