That is not a TTN compatible LoRaWAN gateway. It is a Lora (only) gateway.
If you are willing and capable of modifying the software on the LPS8N you might be able to do something. You will need to create a modified packet forwarder and create scripting to get the encryption keys from TTN. However I still think you are looking at the wrong way to solve the issue. In stead of creating some point solution to mitigate possible connectivity issues you should solve the reliability of the connectivity.
No. There is NO facility to extract the transmissions from the LPS8N over serial. If you look at your gateway you’ll see that this is NO serial port.
And even if there was, you’d have to write code to decrypt the information and extract the payload.
This is LoRa to LoRa aka Point 2 Point - which is fine, there is no encryption, it’s all simple scripts, you CAN NOT do this with an LPS8N as it’s firmware is based on 8 receivers, not one. And P2P is off-topic for this forum.
The LG01 is a single channel packet forwarder (SCPF - search for this or SCPF or DCPF on forum) NOT a LoRaWAN Gateway as above…this forum is for TTN Community and users of LoRaWAN, we do not support such LoRa only products. Short answer is No…long answer is if prepared for imperfect implementation and prepared/able to hack code - and not attempt to use connected to TTN - then some level of imperfect and incomplete functionality, with significant packet loss, is/maybe possible, but not discussed or supported here.
Get yourself (or tell your friend to get!) a TTIG or another low cost (Dragino?) LoRaWAN Gateway
I understand. My problem is LPS8N is getting turned off in between a lot causing loss of data for as much as a day (wifi problem maybe). That’s why the solution I was thinking of is locally storing data before sending it to TTN.
That does not sound like a practical solution. If you have problems with the LPS8N, then best to direct attention at solving that.
Storing sensor data locally and sending it when and if a Gateway is available, runs the very significant risk of breaking the legal duty cycle restrictions and the fair useage policy. How for instance would the nodes be configured\programmed to somehow know that the gateway was having problems ?
Are the gateway turned off or are your internet connection getting turned off?
If this is the problem I will suggest you address those issues, then you will not create new ones as how to store data locally and how to send this stored data to the back end.
In any case if you have managed to store this data locally, you should not need to send it via TTN to your back end, you can just send it straight to your backend.
As mentioned before with LoRaWAN you need to allow for data loss anyway. Up to 25% loss. If your application can’t tolerate that you’re using the wrong technology.
It’s not totally clear if the gateway power or the WiFi is turned off, or both
It doesn’t matter which, that’s not a technical problem we can solve
This is a student project - the OP could potentially relocate the kit to somewhere more reliable
As we are now on post #53 and about 1 month on, I think the ball is in @morse’s court to do something tangible that moves things forward.
@morse, if you were @kersing you could change the gateway to save ABP based uplinks and decode them offline. That’s because Jac wrote one of the most widely used gateway code. Most of the rest of us would struggle and we’ve been using LoRaWAN a fair bit. Please consider that it is not feasible for us to help you save anything on an LPS8 gateway as first, it doesn’t have the facilities to easily change the code and second, simple questions come back with unclear answers. Find a more reliable power/WiFi place for your gateway, job done.
I have one LSE01 sensor and LPS8N gateway. They are not very close to each other, they are more than 100 meters away from each other.
I am using storage integration to fetch data from TTN.
My wifi connection is not strong enough and it is getting turned off in between, this is one of the reason of me losing data.
Another reason I do not understand is, see I am supposed to get packet per 20 minutes right. As storage integration stores packet for 24 hours, so for a curl request I should get around 72 packets. Currently I received only 6 for last 24 hours. This is how I said I am losing more than 20 packets.
I feel like problem is distance as I am getting uplinks from gateway but I am not getting data packets for those timestamps.
What I am going to try:
Moving gateway closer to the sensor.
You are conflating problems….ignore storage integration at this point….it can only store messages that are valid and have been received in the back end….if you only see say 6 in 24 on main system, you can only ever see 6 in SI! It can’t magic up missed data….
That is your problem…… solve that so you have a solid stream of data going through to the LNS (& thence to SI as a back up if needed)
It’s clear that the issue is not about range but is:
About the WiFi not being “strong enough” and being turned off.
Your ability to ignore this and try and fix the problem by some other means - which is never going to work.
The simple solution is to buy a MiFi - a small WiFi router with a SIM card. Or move the gateway closer to the WiFi.
The rest of us know that if a device is transmitting and gateways are hearing those transmissions and are on the internet, the reality is that we often get >95% of uplinks.