Configuring LoRaWAN demo for use with TTN

[woobagooba]

Questions ...

I have a simulator reporting GW ID of 00:00:00. This is odd in that it is all zeros, is only 3 octets long (your video demos display an 8 octet GW ID), and appears not to be based on any of the platform MAC addresses.

A GW must be registered with TTN and that GW's EUI must be set to the LoRaWAN simulator reported Gateway ID, correct? If yes, TTN will not accept a GW EUI of all zeroes.

The LoRaWAN demo appears to be hardcoded for EU 868, must the TTN gateway also be configured for EU 868?

[janjongboom]

@woobagooba It tries to read the mac address of the network card, but apparently fails. Quick workaround:

• Comment out lines 502-504 in launch-server (https://github.com/janjongboom/mbed-simulator/blob/master/server/launch-server.js#L502)
• Set gateway ID manually in https://github.com/janjongboom/mbed-simulator/blob/master/server/launch-server.js#L322

Must the TTN gateway also be configured for EU 868?

Yes, EU868. You can optionally override the channel plan here, then remove libmbed.bc and recompile. But I'd advise to keep it at EU868 for now.

[woobagooba]

OK will try the code mod to set the GW ID. It would be helpful to have an env var override similar to HOST and PORT.

[janjongboom]

@woobagooba I agree. PR is welcome ;-)

[woobagooba]

Unlikely we will be able to dig that far into the code base. We are identifying the Windows specific bugs, working to provide you accurate install instructions, and also working on Docker-izing this. Appreciated if you could address this GW ID bug or provide the env var override.

[woobagooba]

LoRaWAN demo which will work using the online MBed OS Sim instance and TTN will not work with our local instance of the Sim. GW ID of launch-server.js was modified per your instruction, and we further hardcoded LORA_PORT and LORA_HOST.

What are we doing wrong? Please see attached...