As said, the GW connected immediately when I tried to register to Balena some weeks ago. So I will test Jac´s Balena route tomorrow. I´ll let you know the outcome.
The older code relies on V2 to get part of the configuration and requires valid V2 credentials for that. My updated version (the second GitHub link in that topic) has been modified to get rid of the V2 dependencies.
I hope my problem fits into this topis. It is regarding migration from v2 to v3 and from packet forwarder to basic station. I’m using RPi (3 and 0), iC880A and RAK 831, all in Balena. (I’ve migrated Lorix before without any problem). First migration of RPi&iC880A was easy. Even more: problematic iC880a, which I had to start packet forwarder on it even more than 4-5 times, now starts without any problems.
Next was RPi&RAK831, as it is described here: GitHub - balenalabs-incubator/basicstation: LoRa Basics™ Station - The LoRaWAN Gateway Software. Again, succesful. But that’s it.
Another two RPi&RAK831 couldn’t connect despite the equal settings, with the same error. No way …
Does someone have any idea where to start “witch hunt”?
Balena’s log says:
main 2021-07-20 15:18:51.856 [RAL:VERB] SX1301 ifchain 9: enable=1 rf_chain=1 freq=300000 bandwidth=3 datarate=50000 sync_word=0/0
main 2021-07-20 15:18:51.856 [RAL:VERB] SX130x LBT not enabled
main 2021-07-20 15:18:51.856 [RAL:VERB] Station device: /dev/spidev0.0 (PPS capture disabled)
main 2021-07-20 15:18:51.857 [RAL:ERRO] Concentrator start failed: lgw_start
main 2021-07-20 15:18:51.857 [RAL:ERRO] ral_config failed with status 0x08
main 2021-07-20 15:18:51.857 [any:ERRO] Closing connection to muxs - error in s2e_onMsg
main 2021-07-20 15:18:51.857 [AIO:DEBU] [3] ws_close reason=1000
main 2021-07-20 15:18:51.857 [AIO:DEBU] Echoing close - reason=1000
main 2021-07-20 15:18:51.904 [AIO:DEBU] [3|WS] Server sent close: reason=1000
main 2021-07-20 15:18:51.904 [AIO:DEBU] [3] WS connection shutdown…
main 2021-07-20 15:18:51.905 [TCE:VERB] Connection to MUXS closed in state -1
main 2021-07-20 15:18:51.905 [TCE:INFO] INFOS reconnect backoff 10s (retry 1)
Hi, followed by the “Basicstation” repository guide with a board “IC880A” and a RAPSBERRY PI3 and in the TTN V3 console comes out as disconnected. Apart from what appears in the guide would have to do something else?
flash_off
08:11:32
Disconnect gateway
network_check
08:11:32
Receive gateway status
This is what live data responds to and the following one is the balena logs.
2021-07-26 06:26:45.533 [RAL:VERB] SX130x LBT not enabled
main 2021-07-26 06:26:45.533 [RAL:VERB] Station device: /dev/spidev0.0 (PPS capture disabled)
main 2021-07-26 06:26:45.534 [RAL:ERRO] Concentrator start failed: lgw_start
main 2021-07-26 06:26:45.534 [RAL:ERRO] ral_config failed with status 0x08
main 2021-07-26 06:26:45.534 [any:ERRO] Closing connection to muxs - error in s2e_onMsg
main 2021-07-26 06:26:45.534 [AIO:DEBU] [3] ws_close reason=1000
main 2021-07-26 06:26:45.534 [AIO:DEBU] Echoing close - reason=1000
main 2021-07-26 06:26:45.570 [AIO:DEBU] [3|WS] Server sent close: reason=1000
main 2021-07-26 06:26:45.570 [AIO:DEBU] [3] WS connection shutdown...
main 2021-07-26 06:26:45.570 [TCE:VERB] Connection to MUXS closed in state -1
main 2021-07-26 06:26:45.570 [TCE:INFO] INFOS reconnect backoff 10s (retry 1)
main 2021-07-26 06:26:55.572 [any:INFO] ./tc.trust:
Hi, for Pi there is a some software created by @kersing that should do the job - he created gateway software way back in time - the forum search should track it down, it was in the last week or so if I recall.
OK, thank you very much, the question is that i dont know where to start looking. For the moment i will search @kersing to see if there’s luck. If I manage to fix it or find the software, I’ll leave the link attached to this mensage.
Hi, I follow Kersing’s tutorial as you told me but now it gives me another mistake, apparently I have the gw_key and gw_id badly but I put them according to the documentation. What could the problem be?
Anyway, on the gw_key I put “API KEY secret key” and on the gw_id “gateway ID.”
BalenaCloud log error
HTTP Error 404: Not Found
main Unable to fetch configuration from TTN. Is the TTN API reachable from gateway? Are your GW_ID and GW_KEY correct? Retry in 30s
i did try to ping the gateway server address but it does not comunicate with any on of the devices in my network.
Hi guys, just a hint - I had the same problem a couple of days ago, with the log message “*Unable to fetch configuration from TTN. Is the TTN API reachable from gateway? Are your GW_ID and GW_KEY correct? Retry in 30s”.
