does anyone know what the USB socket next to the reset button is for ?
(I’m the author of the LoRa Gateway Bridge / LoRa Server project) I don’t think this is possible. The LoRa Gateway Bridge expects the packet-forwarder UDP protocol. The TTN gateway uses their own Protobuf over MQTT format (if I’m not mistaken).
Thanks for your response.
Do you have an idea how I could use my parking sensors with fix devAddr which be filtered by TTN? Is it possible with the TTN Gateway? Or do I have do buy or build my own gateway and configure the packet forwarder?
Sorry, I don’t know if / how this works with the TTN gateway.
In that case it is a major unacceptable vulnerability, perhaps one the TTN tech guys can comment on this further.
@arjanvanb and others… here is a log of my TTN Gateway booting up and connecting (successfully) and sending a few packages…
Click to view the full log
**************************
* The Things Network *
* G A T E W A Y *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.0, commit: 917719b9, timestamp: 1498499973
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Jun 26 2017 19:59:53
Reboot reason: 0x03
BOOT: (persisted info) 6F 72 72 65 01 03 86 D0 0E 90 F5 21 02 9D 41 60
WIFI: Entering state 0
WIFI: Entering SCAN state 0
MAIN: Initialisation complete
LORA: Changing state from 0 to 0
MAIN: Leaving state 0
MAIN: Entering state 1
FLASH: Magic bytes found: wifi config present
FLASH: Magic bytes found: activation data present
FLASH: Magic bytes found: FOTA data present
FLASH: Loading Firmware Data
CNFG: (Firmware HASH (sha256)) 69 AE B7 78 1F 49 4E 7F BC B6 C7 CD 9C 59 4F 5D FA AA 3D 81 D4 9C 56 90 A6 83 81 98 FF 18 88 6A
FLASH: Loading WiFi Data
CNFG: WiFi SSID: Things-Gateway-001EC03B4371
CNFG: WiFi key: thethings
CNFG: WiFi conn_type: 4
CNFG: WiFi sec_type: 4
FLASH: Loading Activation Data
CNFG: Gateway ID: vanesp-gw-001
CNFG: Gateway Key: ttn-account-v2.H8<redacted>V9A
CNFG: Account Server URL: https://account.thethingsnetwork.org
CNFG: Locked: true
CNFG: Locked first time: false
MAIN: Leaving state 1
MAIN: Entering state 2
INET: State change to 0
LORA: Initialisation complete
LORA: Changing state from 0 to 1
WIFI: Entering state 1
ETH: IP Address: 0.0.0.0
WIFI: Entering state 4
WIFI: Entering SCAN state 1
Scan is completed successfully
WIFI: Entering SCAN state 2
WIFI: Entering SCAN state 5
WIFI: Entering SCAN state 0
WIFI: Entering state 2
WIFI: Disabling modules
Head magic match void: trying to free an already freed block, ignore
WIFI: Entering state 3
SNTP: State change from 0 to 1
INET: Gateway has Ethernet
INET: State change to 2
INET: Connected to a network, waiting for DHCP lease, checking validity with ping
WIFI: Enabling modules for server
WIFI: Entering state 6
>WIFI: IP Address: 192.168.84.1
SNTP: State change from 1 to 2
ETH: IP Address: 192.168.2.32
CB: INET: State change to 3
INET: Ping probe
INET: Error sending probe on WiFi
INET: Ping response from PIC32INT, set as default
INET: State change to 4
LORA: Wait init complete, waiting for application.
LORA: Changing state from 1 to 2
SNTP: State change from 2 to 3
MON: SYS Stack size: 3967
MON: heap usage: 147KB (156KB), free: 192KB
SNTP: State change from 3 to 4
SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
INET: State change to 5
MAIN: Leaving state 2
MAIN: Entering state 3
CNFG: Load online user config state change to 4
HTTP: Close active socket 0
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1477 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
CONF: Parsing response token: HTTP/1.1 200 OK
CONF: ROUTER URL: mqtts://bridge.eu.thethings.network:8883
CNFG: Load online user config state change to 6
FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/EU_863_870
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1232 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
CNFG: Load online user config state change to 7
CNFG: Configuring LoRa module
LORA: Changing state from 2 to 4
LORA: Starting reconfiguration
LORA: version: 01
MON: SYS Stack size: 2855
MON: heap usage: 152KB (237KB), free: 187KB
LORA: Configuration succeeded
LORA: Starting operation
LORA: Changing state from 4 to 6
MON: SYS Stack size: 2855
MON: heap usage: 152KB (237KB), free: 187KB
LORA: Changing state from 6 to 3
LORA: GOING ASYNC
LORA: Changing state from 3 to 9
CNFG: Load online user config state change to 9
MAIN: Leaving state 3
MAIN: Entering state 4
FLASH: Loading FOTA Data
FIRM: Requesting key ...
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 568 bytes
LORA: Packet dropped! Bad CRC
HTTP: Connection Closed
HTTP: Close active socket 1
FIRM: Starting download
FIRM: available bytes: 79
FIRM: (Downloaded FOTA key) 69 AE B7 78 1F 49 4E 7F BC B6 C7 CD 9C 59 4F 5D FA AA 3D 81 D4 9C 56 90 A6 83 81 98 FF 18 88 6A
FIRM: (Stored FOTA key) 69 AE B7 78 1F 49 4E 7F BC B6 C7 CD 9C 59 4F 5D FA AA 3D 81 D4 9C 56 90 A6 83 81 98 FF 18 88 6A
FIRM: Firmware is already downloaded
MAIN: No new firmware available
MAIN: Leaving state 4
MAIN: Entering state 5
MQTT: GOT IP: 52.169.76.203
Connecting to: 52.169.76.203
MQTT: Connection Opened: Starting TLS Negotiation
MQTT: Wait for SSL Connect
MQTT: TLS ready: Connect MQTT
RQMQTT: Connected
*************************
MAIN: Gateway bridging
*************************
MQTT: Sending status packet
MQTT: Report reboot error: 0103
MQTT: Sending status succeeded: 0
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 1
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Accepted packet
MQTT: Sending UPLINK OK
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 3
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 4
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Kick LoRa module with ACK after not acked it for 60s
LORA: Accepted packet
MQTT: Sending UPLINK OK
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 6
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 7
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Kick LoRa module with ACK after not acked it for 60s
LORA: Accepted packet
MQTT: Sending UPLINK OK
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 9
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Packet dropped! Bad CRC
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 10
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Accepted packet
MQTT: Sending UPLINK OK
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 12
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 13
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Kick LoRa module with ACK after not acked it for 60s
LORA: Packet dropped! Bad CRC
LORA: Accepted packet
MQTT: Sending UPLINK OK
MON: SYS Stack size: 2843
MON: heap usage: 262KB (266KB), free: 76KB
1 Like
I’ve had my gateway on permanently for a week now, and have no high temperature components. All are touchable.
1 Like
Can someone of the tech team/ moderator confirm that this is not possible please?
So I can talk to my prof for my master thesis and look for an alternative solution…
Having problems with connecting the ttn gateway , where is the reset button ? Cannot find it or do i have to remove front cover?
Check first posts in this thread…
I’d just like to make an observation with regards The Things Network, and this forum & Kickstarter etc; We the loyal backers that have/or are wait the gateways need the communications to be better, communication from The Things Network is at best slow and inconsistent. (correct me if I’m wrong) I’ve not received or seen any acknowledgement from the team with regards any issues or what cause of action that those reporting issues need to take; yet the team and founder is re-tweeting and like all positive comments, which leads me to believe the either he/team is unaware of all these gateways that have issues or simply us backers are getting ignored as they try to push for more sales and promotion of the product as the conference!?
I was so hopeful but feel like I’ve forked out £££ for a product that has suffered delay after delay and has then been delivered with some fundament issues across the product range; as before happy to work to get this resolved; but not to be ignored by The Things Network team or see them liking good comments and hiding way from the true picture of this project.
I guess my frustration is starting to show, but I feel I like many other have given a fare chance for a response/acknowledgement
7 Likes
Grahame…
I agree. I’m lucky that mine works. But I fully understand your frustration.
In fact, as I’ve said before, TTN team should focus on getting product out, documentation out, and helping those with problems.
The upcoming conference is nice… but should be lower priority really. And the lack of an official statement or response on these forums about what they are doing to help the unlucky backers with dead on arrival gateway is not professional.
2 Likes
Yes Grahame, I fully agree. Most of the backers could settle for a bit of tweaking to make things work smoothly, is my estimate. However, there appear to be quite a number of people having very similar issues with the TTN-gateway. And lots of ideas, suggestions and test results are doing the rounds, also from users that managed to activate their gateways. But, apart from some forum moderation and participating in these technical discussions, there is nothing from The Things Network. No acknowledgment, no task force announcement, no status & outlook. This needs to improve.
1 Like
@vanesp and lets face it the conference is quite frankly a waste of time if us backers get ignored and start to voice the lack of support and communication from the team; as any reasonable investor/business wouldn’t like the bad press
just for reference for anyone that feels the need @wienke on twitter
FYI; I’m trying hard to kickstart an official response; you can follow me on twitter @GrahameHorner
I’ll hopefully get someone to reply or DM me after my tweet
@wienke please whip your team into shape and get some form of issue desk and/or acknowledgement announcement released to backers about gateway issues #weareheretohelp but cant except begin #ignored
My understanding is that TTN is relying on the folks at TWTG to try to identify and fix the problems related to the gateways; for example, in this forum, TTN core team member, Hylke Visser, wrote the following when Leondegeling was among the first to report the reboot problem…
Dec '17 - Hi @Leondegeling , I saw the debug log you sent us and notified our hardware experts at twtg.io about it. I’ll ping them again to see if they found anything. As for the source code, our colleagues are also working on getting the source code…
I can’t recall yet any instances where someone has reported having multiple gateways with one or more working and also one or more that doesn’t. Anyone know of any such circumstance?
Haven’t read that either. Your question indicates that you suspect the problem might be “the environment”: network router or ISP. Likely, because from the outside, it looks like the TTN-gateway goes through the activation process but somehow can not complete the activation process with the server(s) involved.
but no official report or communication to all backers (from what I can see) about what/or how to help resolve or communicate to the team information that could possibly help determine the root course. Microsoft, Apple, Google are big companies an get bad press for the number of bugs/issues, but all we are asking here is something that the team should already be able to do issue a communication to the fact the gateways have issues, and forum to log you have issues along with some details firmware version/logs etc. to help us help you (TTN) and (TWGT.IO)
We the backers aren’t bothered about the commercial/structure of the business or the support network (or lack of) behind the scenes, we just want to help this work and resolve issues; so again better communications please…
1 Like