….that reminds me TTKGW new users or people revisiting old setup for a TKGW following ttn.fyi/activate link end up directed to that page…. = GOOD! Problem is users of Things Nodes are told to follow same link and up in same place = BAD! (ESP as no onward link to correct Node set up per note 4. In the shipped quick start leaflet . 4. Continue with the steps as described in the illustrated guide quick start guide for The Things Node found on https://ttn.fyi/activate.
Can you update page to at least show a Node docs link?
Is there a reason why the suggested changes in the firmware (pull requests on github) are not taken into account?
Reason I am asking is that since a certain update of TTN V3 I had connection problems with my gateway, which I did not have before. If the gateway lost its connection it would not reconnect (3 flashing blue LEDs). This could only be solved by removing power. This happened at least once a week. I thought of stopping with this gateway.
But I contacted the programmer of the pull requests (Daniel Kucera) and he gave me his version. This worked flawless for one year, until today (again blue LEDs flashing). And I discoverded the gateway updated itself to V1.0.9. I thought I had disabled automatic update. It seems I am back to the old situation now.
Would be nice if this could be solved by using the suggested improvements.
I am wondering whether I am the only one with this kind of problem?
The main reason is that The Things Kickstarter Gateway doesn’t have an official maintainer (or in TTI terminology: “code owner”).
Over the last couple of years, I’ve only submitted some small and easy patches to prevent the thing from breaking down (mostly just updating Root CAs) but if my own TTKG doesn’t have a problem, I’m not touching that code.
However, I believe my colleague @adrianmares recently started experimenting a bit with TTKG firmware, so I’ll ask him if he can perhaps review and test those patches.
I have been running these fixes for a couple of months now, so I have incorporated them into the current develop channel - it should be available to your gateway once you change the channel from stable to develop and restart the gateway.