What firmware have you loaded to it? I banged on the Semtech in the end (legacy) - works perfectly.
Hi,
This doesnt look like my gateway. There is nothing like config.json, my Micro Lite wants files like “custom_conf.json”
“Kona Micro Lite” is a new name of “Kona Pico”.
1 Like
They renamed Kona Pico to Kona Micro Lite and that created some mess.
Should be something like this:
{"private_key_password":"ubiq2015","network":"semtech","semtech":{"host":"router.eu.thethings.network","up_port":1700,"down_port":1700}}
If you’re not in EU, replace “router.eu.thethings.network” with proper router name.
Same here! Did you use the Windows app to set it up?
No, the KonaFT doesnt work on Micro Lite.
Thank you Hobo, I think this is correct. But i dont understand which password it is. And how can the Micro gateway connect to the gateway in my TTN-account? I guess its using the Gateway ID.
Stephan
Ha! That’ll be the problem then 
tftp is pretty good though, but really they ought to make this clearer in the docs.
The gateway is up and running. Thanks for your support.
1 Like
Hi,
I’m trying to connect a Kona Micro Lite for the first time. I uploaded the semtech.v1.7 firmware and copied customer_ttn_EU_legacy and EU868.default.channels.LoRaWAN json files (provided by Tektelic support) in, respectively, Customer.json and LoRaWAN.json using tftp.
I registered the Gateway on TTN V3, using the “+ add gateway” registration.
Since, the gateway status remains as “disconnected”.
I checked the gateway EUI, it is correct.
I also checked the current version of the firmware as well as configuration files using the tftp GET function. Everything seems ok.
Any idea where the problem could come from?
Sounds like that one will point to V2. You need a configuration on the gateway that refers to eu1.cloud.thethings.network. If it doesn’t it won’t work for V3.
Thank you! I modified the configuration file and it works.
Now I face a new problem : in the live stream of this gateway, a new message is displayed every 30 seconds named “receive gateway status”… I guess this is not normal, is it?!
Yes that is normal - GW’s - depending on config and packet forwarder used - will send a status message/keep alive on a regular basis to the NS so it knows the GW is still connected even if no traffic coming through. 30sec is a common period and many GW’s allow this to be modified - 30s is a good compromise between finding out a GW has gone quite and the amount of traffic handled by the comms link and back-end. If you feel this is too frequent check the GW config sw as there may be option to extend update period - 60 sec, 5 mins - 15 mins or what ever you are comfortable with or the system allows.
Don’t modify it, the backend needs regular (<60 seconds) keep alive packets to know a gateway is active and can be used for downlinks.
1 Like
Thanks. I also have a TTIG connected on TTNv3 and don’t see these messages in the live stream. Do you know why?
Ah yes of course knew that but wasnt thinking! Dho… caught out by fact early TTIG deployments only ‘connected’ via web sockets when they had traffic to send and often quickly timed out making me think >60s was kinda ok…but no! 
@Claireh91 TTIG uses BasicStation protocol with other handling procedures that would explain the lack of specific status messages…
I understand. Is it possible for the end-user to filter the type of messages to be displayed in the live stream (status, uplink, downlink)? If I remember correctly, we could do it in the V2 console but I can’t see the feature here.
The console currently has two modes, verbose and ‘default’. If default shows too much information you are out of luck for now, there are no filters available.
Dear,
I am having issues with my Kona Micro Lite.
I have followed the instructions from the website
Micro Lite TTN v3 setup
These instructions and associated files are a quick start to getting a Tektelic Micro Lite running on TTN. These instructions are provided by Sensational Systems/connectedthings.store
Connect the Micro Lite gateway to your network. It will use DHCP to get an IP address from the network. Obtain this IP address from your router/DHCP server.
Use TFTP to push the firmware image and config file to the Micro Lite gateway. Gateways shipped from connectedthings.store are now preloaded with the v1.7 firmware binary, so you can skip the transfer for the semtech-v1.7.bin file, unless you have an older unit and want to upgrade.
The TFTP operations look like this:
tftp> connect 192.168.1.xxx
tftp> binary
tftp> put semtech-v1.7.bin Gateway.bin
tftp> put customer_conf.json
// Fetch serial/MAC etc
tftp> get Basic.json
Now register the gateway using the TTN v3 console at The Things Network Console
Use the gateway ID from the label on the bottom of the gateway as the gateway EUI in the console.
The gateway has successfully connected to the console. I am also able to receive the uplink messages. The problem is that devices are not able to successfully join through the Kona Micro Lite. I am also not able to send downlink messages to the device through Kona Micro Lite.
If I connect The Things Indoor Gateway, the devices immediately join the server and I have also no issues sending downlink messages to the devices.
Do you think there is something wrong with the configuration or with the hardware?
Thank you in advance!
Marko
