The First False Step
It didn’t take me long to realise that the LoPy module is only the gateway to the LoRa netowrk, and that I would need the expansion board to connect it to my computer and update its firware. Doh.
Let’s move on to my Sodaq ONE package.
The Sodaq ONE trials
Following the handy getting started guide, I installed the Arduino IDE and the additional Board Manager for the Sodaq ONE.
Unfortunately the guide stops at the end of the IDE installation, and in order to go further I had to follow the official SODAQ instructional video to be found here. At the end, a simple ‘blink’ example is suggested. Copy/pasting the code won’t be enough tho, as the IDE will complain that
This happens as the Sodaq ONE board has different defines for its leds. We can use LED_RED, LED_GREEN or LED_BLUE alternatively.
This is all cool, but towards the end the next problem came up: the board disappears shortly after connecting it with the following goodbye message:
It seems that this is quite normal (?), and if you upload your sketch before this message appears then it won’t disconnect again. I fiddled around a bit with the blink example - mostly to get my fingers to type C-style code again - and this is the results. Everything works as expected.
This sketch (and others to follow) is available on a github repo.
The next step I wanted to achieve was to connect my device to The Things Network. I live in Amsterdam, which is where the network was born, so that should be a well-covered area. I even contributed back then with the TTN Android SDK, now deprecated. I followed the instructions as per the IoT days 2017 workshop, and grabbed the Sodaq ONE Universal Tracker to get things going, but with little success. Even with all settings correct, the device disconnects and I can’t see any incoming data in the TTN console.
As a first day into IoT experiments, I had fun. I am curious about the recent Android Things initiative. But first let’s get this connection to work!