Recently, on Linkedin, I reacted on a publication that is looking like this one. I’m used to react on LPWAN publication when they are comparing technologies as this one. Comparing apples with eggs and usually meaningless. This one was particularly interesting me because, most of the content is non-sense and scientifically subject to discussion. I’ll detail it in this blog post.
It’s really interesting the way it has been made and also the way the author publish it, react on it on Linkedin and what objectif is serves : capture people in a world where the truth is adapted to make you think only one of the technologies serves all the possible use-cases and all the others are the worst existing. The purpose is to sell you some books and services. This is really looking like the way flat hearth believers, radio waves danger believers and other groups do to find adepts and to sell goods to them. It’s really funny to see and discuss.
As the Author of the original document above considers his slide as “art” you can’t use, copy, cut (even if he published it online on social network) I have made my own one and simplify it to not entering in the expecting promotion this guy is looking for and to troll on the social networks. The curve you see are the exact copy of the original one. These data seems to come from a university work and are needed to be debunked. I just not mention the highlighted technologies other than Sigfox and LoRaWan because they are the one the slide tries to discredit and we will see how that’s wrong.
I do not identify the original author of that “artistic work” because I consider the scientific aspect of that “work” so bad that it discredit too much this person, its student and the associated university, that I don’t want to discredit these people directly. As I did on Linked-in but the author has immediately identify itself to start its promotion.
As I did not had access to the full study, sources of these graph, I can’t tell if the initial work quality that as been done is bad or if the context of the experience is explained. May be the original document explains different conclusions, so I’ll try to not judge too much the original work that has been done. I’ll judge what the author of the slide gave to us, as a single slide with pseudo-scientific information and a fake conclusion. Apparently, if you are ready to pay for the book / register… , you can get more details, thing I do not want to do to feed the troll.
Until now, all the Helium data-only hotspot I have been tested where DiY devices. They are not really complicated to manage but they are not ready-to-go, so you need to manually on-role them with a wallet and some complex CLI operation for the non-experts. This SenseCAP M2 is the first one I’m testing, ready-to-go or close to be ready-to-go (that does not means it is the only one existing).
As it is a Data-Only hotspot, it means it does not participate to the Proof of Coverage, as a consequence, there is no related rewards for this device. This device only earn the DC (Data Credit) for transferring the communications, so $1 for 100.000 packets. Before getting question, this have no return on invest in a crypto point of view. This has been made to help supporting professional applications on the Helium network.
In a previous blog post about 18 month ago, I designed my first Low Cost LoRaWAN Solar Gateway. This year, I did some updates to create a new version to support Helium Data-Only Hotspot (basically it works for any LoRaWAN networks like TheThingsNetwork).
In this version, I’m using a RAK wisegate Lite gateway, it is a bit more power consuming than the TTIG but can work on any LoRaWAN network. I’ve also changed the outdoor enclosure to get a larger and single battery.
You will also see that I’ve been updated the monitoring dashboard to get something better and free of charge. Two of them are in production. One is already deployed as an upgrade of the 1st one and the second one is in the testing phase. The First version has been on the field for more than a year. It has been offline about 10 days during that year, due to the weather conditions. This is a service level of 98,29% from its start until now. With the larger battery I’m expecting to resolve some of the small service interruption I’ve issued during last winter.
Kerlink is a LoRaWan hardware player since the first ages of this technology. This French company has equipped most of the operator’s network and is used to propose high quality industrial products.
The iFemToCell is not a new product. It exists since a couple of years and I already tested the IFemToCell 4 years ago. Recently the company has created a Helium edition we are going to review in this blog post.
This is an interesting device as it is a kind of hybrid between a light miner and a full miner. Even if the Kerlink platform is powerful, it is far away the power of a raspberry Pi and certain operations like consensus group can’t be performed. As this is now delegated to Validator, this difference have no impact on rewards. In another hand, this device is consuming less power and it is possible to power it with sun more easily. This is quite interesting.
Let see what is this device and what is specific during its deployment.
Migrating existing LoRaWAN network to Helium or joining Helium for new deployment is accessing to the world largest LoRaWAN network and enable your devices to be deployed in the large covered zone. By doing this you extends the community network and as a counter part getting benefit on future data transfer and immediately get an access to the low cost ecosystem (data transfer, network server, high redundancy network…)
In a previous post I explained how to configure a RAK Wisgate as a Helium Data-Only hotspot. In a such situation your LoRaWAN gateway becomes a hotspot relaying the Helium traffic and getting some little rewards for the data transfer. The more important is to extend the coverage. This way of doing is good but I’ve got some issues on the field: The data transfer from the hotspot to the blockchain (even if just the state channels) is high and the software, currently in alpha, is not totally stable. When deploying a gateway is isolated area to provide new coverage, honestly, these two issues are blocking points.
The second important consideration is the existing gateways, already deployed on the field: they are currently used for private networks. They have been deployed some years ago and are not in the compatibility list of Helium hardware. Even if they are, deploying a new software on them, remotely can be a problem.
For these different reasons, I’ve been investigating a different approach by creating centrally hosted hotspots connected to different LoRaWAN gateways through the legacy Semtech protocol. This is what we are going to detail on this blog-post.
It’s time to extend the Helium network out of the city centers ! Now as most of the Helium Pioneers have stacked a lot of HNT, it is time to reinvest a part of it to grow the attractivity of the network and improve the future value of the token as a consequence. At least it is my point of view on what every Helium participant should start doing. Each hostpot revenue is currently sufficiently high to participate to network extension with Data-Only equipment.
Data Only Hotspot are LongFi (LoRaWan) gateways not doing mining, they are just relaying data and, as a consequence, only earn token for packet transfer. If the network use becomes high, this could be an interesting revenue.
Data Only Hotspot target 2 different use-cases:
Low density area, they are the zone where you don’t have a big chance to have many other hotspot around and full hotspot price won’t make it interesting regarding the low chance to get PoC reward. Basically, they are good to deploy in the countryside, mountains … to extend coverage but not expecting high revenue. This is important to do to enable used-cases based on a large coverage for the network.
Professional networks. This is the main, short term, interest of Helium Data Only Hotspot. Service providers using LoRaWan are mostly relying on private networks with owned equipment’s. These equipment can be migrated or deployed on the Helium network with Data-Only Hotspot without risk of market shortage, larger reliability and lower cost and lower bandwidth and power consumption than full miners. Service providers get different advantages for doing this: get benefit of the existing Helium coverage worldwide (as primary solution or as a redundancy) and get some income for transferring other LoRaWan communication.
For my first experimentation with Helium Data Only Hotspot, I made the choice of RAK Wisgate Edge Prime because this device is reasonable price for high end experience. It is outdoor, with LTE, supporting PoE under $400. This is really fitting well with the second use-case : professional deployment I noticed above. I will later review the Dragino lower cost gateway for addressing the first use-case.
Sensecap is one of the Helium miner official hardware. This one has been made in collaboration with Seeed a big hardware maker and provider.
The production and distribution has started on July 2021 and that solution is really promising to help solving the shortage issues currently seen in the Helium market. As a reminder, Helium growth has been from 15.000 hotspots to 100,000 hotspot in less than 8 months. In a period of global shortage in semi-conductor market it is quite challenging for the hardware provider and the current estimates are about 200,000 – 400,000 back orders.
Sensecap coming batch of 10,000 and more units are really welcome, with the promise of selling produced only devices instead of pre-orders. It sounds like a good choice now days.
So let’s review the technical part of the Sensecap miner.
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.