Thx for the links. This is getting off topic, but after reading a lot more my conclusion is that basics station has two major advantages (but correct me when Im wrong or missing something):
more secure communication between gateway and the network server (the things stack)
central provisioning when managing a lot of gateways
The second advantage is not interesting for me since I only have 1 gateway.
These are indeed two of the key, if not the two key benefits. There are others, including the move away from UDP based comms - not only more secure but also more resilient than UDP, as used for the original Semtech (oft Aka ‘Legacy’) Packet Forwarder as UDP packets often go astray or get dropped as they transit ‘the net’. - So secure comms not only in the sense of being authenticated and hence from a known reliable source vs rogue/unauthorised hijacking GW but also secure in terms of greater probablility of packet delivery.
I’d respectfully suggest you do an install with what you have so you have a good chance of having a working gateway and learn the basics of devices, the console, integrations etc etc before going for the juggling of fire brands on a unicycle.
This morning I tried to connect my LIG16 to TTS Basic Station using the beta firmware. I could connect without problems, data-packages were transferred from my gateway to TTS. I could see all my nodes in their applications.
But then I observed that the system-log of my gateway filled up with “Time sync rejected”-messages.
Hi @wolfp have you refered this back to Dragino team - would be interested to get their take on this… Please report back here if you hear anything. Also is there an option to reduce the amount of logging within the setup? This feels like debugging level logs.
I tried just as you this morning. Connection works well. I also get time sync rejected errors after some time. But I think it is also able to correctly do time sync. At least I still have incoming messages…
That is just a GUI thing of the webinterface. When I refresh the page I get to see new logs. Edit: gateway traffic graph stays empty indeed. But in theThingsStack I see normal traffic coming in.
I have tested Basics Station for about an hour now, and I seem to get all uplink messages and am also able to do downlink messages. I will keep the LIG16 configured as it is for now and see how it behaves on the long term.
I am testing a LIG16. I flashed the newest firmware
OpenWRT 18.06, Version: Dragino-v2 lgw-5.4.1636008262, Build Thu Nov 4 14:44:22 CST 2021
I can join TTS-CE for both modes: UDP forwarder 1700 and basic station 443.
Now, i want to join a private TTS server but i can’t do it the… easy way.
This server has some Lorix one GW’s running fine and they join by basic station port 8887.
So, any use cases for LIG16 and private TTS servers ?
There is a new firmware available from Dragino for LIG16. This one allows the user to provide his own server certificate so it’s usable for any TTS scenario.
ChangeLog
===========
lgw–build-v5.4.1640315898-20211224-1120
*Add Iot_keep_alive Script interval setting
*Update the display of the helium page on GUI
*Reduce the gateway data traffic
*Fixed the loss of the gateway downlink queue
*Update the display of the Basic-Station page for TTN on GUI
New fw seems stable. But also with this new firmware the gateway does not show traffic statistics when you use it in Basic Station mode. If I remember correctly someone already contacted Dragino about this months ago (@wolfp was that you?)
I think you’re going to find that’s pretty common with Basic Station on most platforms. Whatever log scanning was used to capture it is expecting log messages from the UDP forwarder, while Basic Station would produce that information in a different format if at all.
New firmware, tested ok for LIG16.
GUI for gateway traffic does not show anything, don’t bother for that.
lgw–build-v5.4.1644990565-20220216-1352
*Add LPS8-N support
*Add AT&T disconnection detection
*Add Secondary LoRaWAN Server for Semtech UDP
*LPS8/LG308/DLOS8’s software of pkt_fwd iterates to fwd
*LPS8/LG308/DLOS8 supports the GUI of Gateway traffic
*Fixd fallback address lost after save WiFi setting
For me the new firmware version is not ok. There is still nothing shown in “Gateway Traffic” when you use BasicStation. I need to know what’s going on with my gateway without using the console.
Therefore I installed the new firmware using Semtech UDP.
Due to the differences between the UDP based packet forwarder and BasicStation that is unlikely to change anytime soon. So no need to report this every update.
I see a lot of reboots on my LPS8, on average every 15 hours, and Basic Station freezes after a few days/weeks.
I updated it 2 weeks ago with the new firmware (16 Feb 2022 lgw-5.4.1644990565) and configured it for Basic Station, connected over WiFi. It ran fine for 2 weeks (lots of reboots) but froze yesterday. Completely unresponsive, no ping.
I had noticed the same issue on the previous firmware (24 Dec 2021), Basic Station freezing, so I switched back to UDP and that ran without freezing; lots of reboots but always coming back online. I wanted to give Basic Station a chance with the new firmware but it seems to reboot more often, and now it froze.
The only modification i made to the firmware is installing nano and a cron job that sends the uptime over MQTT SSL every 5 minutes. Earlier i had tried to avoid the freezes with watchcat (did not work), and directing the syslog to permanent storage to investigate post freeze but i did not find any errors.
Does anyone have similar reboot/freeze issues with Dragino gateways over WiFi?
imho the LIG16 and the LPS8 have different hardware but seem to use the (nearly) same firmware. I own both gateways, the LPS8 is still on the “old” firmware running Semtech UDP without any problems since a few months.
The LIG16 is running the newest firmware with Semtech UDP without any reboots or freezes since a few days.
Your WLAN signal seems to be strong enough, it’s nearly the same signal/noise as I have.
Maybe this is more a LPS8 - related problem when using BasicStation.