Helium network is a crowdsourced network using a blockchain. There are multiple transactions related to the Helium devices communication. Usually, we talk about the message transmission transaction corresponding to a flat cost of 1DC ($0,00001). That said there are some questions:
what is a message definition ?
what are the other blockchain transaction impacting the communication cost ?
In the post we are going to review the answer to these questions and I’ll propose a spreadsheet to modelize these cost with some example to see the different kind of real message cost you should take into account in your business model.
Helium is a multi network server with a decentralized packet routing system. This is really clever and allows anyone to use the public infrastructure as private LoRaWAN compatible network. That way you get benefit of a worldwide coverage and, in the same time, the ability to protect your raw data from anyone looking at them. You can also create some other public network server, as we are doing with Helium-Iot.eu
The objective of a such public service is to offer a shorter route for your European devices and as a consequence a shorter response time for downlink. It also ensure your data to stay in Europe, something important for personal data like tracking, health or for industrial applications.
For a better understanding, let’s take a look at the Helium network architecture:
Thanks to the miner components incorporated in the hotspots, the traffic from the devices is directly routed to the right network server. Each of the network servers belongs to a, operator, it can be you or me or any established telecom operator. This is basically really cool !
That’s why we have decided with the company I work for to take a look at this business and launched Helium-IoT.eu. So you can connect your devices to Helium using our console https://console.helium-iot.eu
In the next page of this post I will explain how to become your own operator for making your private network. This is a bit complex operations, so if you want your own network server, as part of our services we are proposing to make it for you and host it. We also have solutions to migrate existing LoRaWan networks to Helium. Just let us know by contacting me with the contact link.
So, let’s be more technical to understand all of this.
Announced during TheThingsConference 2021 this January, TheThingsNetwork console is upgrading to v3. In fact it is really more than a simple update because this consist in merging TheThingsNetwork and TheThingsIndustrie in a common environment. This upgrade is really different than a traditional upgrade because it has an impact on any gateways and any devices ; a big impact anyone needs to manage. Here are some of the currently known impacts on the networks and the different components:
Traffic from v2 is routed to v3 but v3 is not routed to v2
Gateway are not migrated automatically
LoRa Application/Integration needs to be re-created in v3 to communicate over v3
Device LoRaWan session needs to be refreshed
Coverage map are lost
Gateways using gRPC protocol (TTN Packet forwarder won’t relay V3 traffic over V2)
… some more to be discovered
As the Network is managed by many different people, and not really planned and organized by TheThingsIndustry, we are going to have disconnections and fields operations to make all of this back to life.
It concerns the TTN Initiators (people deploying the network) but also the TTN users because they need to update Applications and restart/rejoin devices once the V2 has disappeared.
The currently know planning for Europe is (Other countries not yet planned)
April 2021 – v2 console will be read-only (you won’t be able to add devices / gateways)
September 2021 – v2 infrastructure will be switched off, no more communication on it
This blog post details my advises and experience of the migration. As I’ll do it in different waves for practical reason, this post will be updated. So please come back and refresh all along the months of February-March 2021 to get the updates, content and advice will be updated according to my progress.
Personal current advice about migration: START INVESTIGATING SINGLE DEVICE MIGRATION
I had some difficulties to migrate my first device and this has been solved by upgrading the gateway and redefining it in the TTNv2 backend. Discovering such situation earlier is important to get on time for upgrading. I recommend to start migrating 1 device to identify such situation. Migrating more than a device could still means impossible ways for some of your devices to communicate through v2 infrastructure. But it will help to prepare your infrastructure for migration.
RAK is one of the most famous LoRaWan gateway manufacturer in the hacker space as they have made HAT for raspberry Pi since a while.
I’m not a big fan of RPI based gateways as I do not want to manage RaspiOS and Rpi hardware and really prefer to have an all in one product well integrated when deploying Gateways. So the Wisgate solution is a better choice in my point of view and it has taken time before I decided to buy one of them.
I’ve bought this one for my next project of LoRaWan solar gateway as I want this one to be fully autonomous, including a 4G connectivity. I have multiple candidate gateways for this like the Kerlink iFemToCell evolution and this Wisgate Edge. The Wisgate price is lower at $249 compared to 325€ for the Kerlink. For this reason, and the fact I already tested the iFemToCell some years ago, my first choice has been on the RAK gateway.
Yes, I’ve got one of these LoRaWan light saber I was looking for, since a while! For this I really thank you Wifx who helped me to get one. I know this is really unusual for them to work with blogger, so thank you for your trust. So honestly, even if I’ve been sponsored to get the device, I’m really happy to make that gateway test. As I said this gateway is one of my favorite since a while. The reason are a really compact outdoor design. It makes the difference 😉
I did not made a test previously because this have a cost, about 500€, (549CHF) this not much expensive but a bit high regrading my non-profit activity on TheThingsNetwork local deployment.
Now, I’m done telling you my life, we can see what this gateway is proposing !
I really love Reece Innovation Solar powered pod product developed by my friend Jose Marcelino. They’ve made a agricultural / industrial autonomous solar powered LoRaWan gateway for a really competitive price. With much more money to extend TheThingsNetwork in my city I would have used a such solution. But as this is just a hobby for me, I’m looking for really low cost solution, something under 500€ per gateway.
My main issue to extend the network is not really to find roof but to find some where I can pass an Ethernet cable and provide the power from it. I have some place where I could deploy new gateway in conduction to be cable-less. The network is not the main issue as most of the time a WiFi network is accessible. Powering is a larger problem to solve. Advantages of outdoor gateway: you have sun available. So, as Reece Innovation did, I decided to make my solar gateway, the main differences are: my will have no LTE communication capability (only WiFi) and it have to cost as less as possible.
I’ve been talking about this ultra low cost LoRaWan gateway in last October and ordered one. The time to get it has been long as it has been arrived in February this year. This sounds due to an early ordering as the product is now available, even on Amazon for a price under 180€.
This price is not so low if you compare to a Laird Sentrius but we are not talking the same product ! Here we have an outdoor gateway with PoE powering. That’s really interesting. The only missing thing is a LTE communication.
This gateway exists in two different version LoRa8 for 868Mhz zones and LoRa9 for 902 MHz zone.
Let’s see it in detail and find how to configure it for joining TTN.
Privacy & Cookies Policy
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.