With the v2 → v3 in mind, I am trying to figure out how to retrieve that status of v3 gateways?
Currently I am using NodeRed (node-red-contrib-ttn module) to fetch v2 gateways.
Hello everybody
I could not find the https adress i have to use for the eu1 server?
With the http://noc.thethingsnetwork.org:8085… it does not work.
Thanks for your help!
If that is the url you used then not surprised it didn’t work, as incomplete. Also if/when you get the correct one you will see it is actually a V2 noc (as called out in the url) so won’t work with V3.
I am still a bit puzzled by the ‘last_status_received’ element…
My GW is online, and the uplink/downlink counts show increasing but the timestamp on last_received_status is almost the same as the connected_at timestamp:
As discussions evolve here we get more insights in to the infrastructure - to stop the database(s) melting, some data is cold - ie it’s not updated live - which makes sense.
The wording and the structures imply that the timestamp is when the gateway last sent a status message - the question being is, what is that status message!
@htdvisser, can you tell us how the last_status_received field is defined / updated please.
This depends on the type of gateway. The UDP packet forwarder, as well as the MQTT forwarder of The Things Kickstarter gateway regularly send status messages with information about the gateway. The Basic Station protocol doesn’t send regular status messages, and the only status we get is when it sends the station, firmware, package, model, protocol and features fields when it connects.
Many thanks for the clear feedback. It explains why there is a difference between de gateways. In my case I use the ‘Basic Station’.
As I am trying to monitor my gateways in a simple NodeRed flow, is there a query possible, which basically shows the same status, as is visible the new console?
In other words, where is the console Gateway status retrieved from, and can we do that via any API?
The lack of status messages was opened on Basics Station Github back in November 2019. It includes a response “We have this feature on our roadmap and it will be included in future releases.”
@htdvisser you are a bit closer to the action, Any idea when that might occur?
Reason for asking. I along with others have asked that question in the github issues and no response. Just wondered if htdvisser may have some idea. Not looking for any action on his part.
I would have a go but I’m not sufficiently versed in C to do this. I have looked a few times but could not figure out its architecture to understand how it would be added. I also came to the conclusion it’s not easy and the code may need some restructuring, otherwise it most likely would have already been done by now.
Lean Design
- No external software dependencies (except mbedTLS and libloragw/-v2)
- Portable C code, no C++, dependent only on GNU libc
- Easily portable to Linux-based gateways and embedded systems
aka:
We kept things simple by omitting any design documentation and made all the filenames somewhat cryptic.
I think we can be almost 99.999% sure TTI have their hands full so any addition would be a community effort and it would be rather gateway specific as to what attributes it could send. It would certainly be nice to know if your gateway is cooking or has enough battery life when running on solar.
Maybe @Jeff-UK could make enquiries, particularly as he’s in to solar and a bit of status info may help him too.
Exactly what I do. I have decided not to move to Basics Station until “status” is available.
Even though I bumble my way through writing C, I also send additional gateway data direct from the gateway to a database. Data elements include lorawan traffic (status) data, voltages & temperatures etc inside the gateway and environmental sensors located in close proximity and connected to the gateway.
Great feedback on Github, there is a way in Basics Station to create the “stats” message.
There is a more generic feature where a string of data can be injected from outside Basics Station into the gateway-server link.
For gateway status, all that is needed is another application to append an appropriately formatted string to a file name cmd.fifo and Basics Station will inject this.