And the latest…
Looks good but no cigar yet!
I tried pushing the repo from a raspberry pi at home with the modified
start.sh and it builds! It may be something to do with CR/LF line-endings using the two different Windows10 machines I had tried before, both failed!
Unfortunately however, while runnng the modified
start.sh code now generates the same EUI from the device MAC address, the device seems to try and connect each restart with a completely randomly generated EUI each reboot?
This first console outuput here is the very first few lines as the main service starts
main Gateway EUI: e45f01fffe3c42dc
main Using MODEL: SX1301
main Server: wss://eu1.cloud.thethings.network:8887
main Resetting gateway concentrator on GPIO 25
In this instance the EUI here is generated by the
If however I look further down the log I can see that the connection is refused by TTS as the gateway EUI submitted by this device is a completely random number and has no relation to the EUI above. Look at this from circa 30 lines below the last console output in the same reboot:
main key usage : Key Cert Sign, CRL Sign
main 2022-01-16 21:26:02.638 [AIO:INFO] tc has no cert configured - running server auth and client auth with token
main 2022-01-16 21:26:02.732 [TCE:INFO] Connecting to INFOS: wss://eu1.cloud.thethings.network:8887
main 2022-01-16 21:26:03.032 [TCE:ERRO] Infos error: ::0 Failed to fetch gateway: error:pkg/gatewayserver:gateway_eui_not_registered (gateway EUI `02426FFFFE0F12EA` is not registered)
I am not sure how this spurious number is being sent to TTS as the EUI? Is there somewhere else where this number can be generated?
If however I copy/paste the random EUI: 02426FFFFE0F12EA to the TTS gateway “general settings > EUI” it connects but I am back where I started with a gateway that can not re-connect after a restart?