Understand Hip-51 – Helium becoming a network of network

The HIP-51 (Helium Improvement Proposal #51) starts a new way for Helium network. When it has started about 2 years ago, Helium has been designed to propose a global LoRaWan network. But, has I explained at the beginning of this journey, it’s not just a network, its the uberization of the telecom industry. In other words, once you find a good way to transform an industry, there is no reason to just transform on of its services, better is to transform all.

Telecom are not single network, they have IoT networks with LoRaWAN, NB-IoT, LTE-M, they have some WiFi services and 4G/5G services. The HIP-51 is basically a way to go that multi-service direction to compete with telecom industry.

I’ll detail in this post the way this is working (as much as I understood it, reading the HIP-51 currently under vote), and try to explain what will be the impact on the network and tokens.

Continue reading

Monitor Helium Router / Console

The Helium router (aka console) is the LoRaWan network server. In a previous post I described how to setup a Helium router / console. In this post I will give you some details of what you can see in the grafana monitoring dashboard and this will help you to understand better how the network works to process the LoRaWan packets. We are going to detail what is an offer, a packet and the different monitoring information we can get from the router.

Continue reading

Roaming LoRaWan with Helium network

Helium is an open network, decentralized, there is a wide range of option you can do as a user, like creating your own private router to have your devices encrypted end-to-end. You can also make your LoRaWan traffic to be routed from Helium network to your own network when you are a LoRaWan network provider. Let’s take the exemple of a Telco with a LoRaWan network, let’s name it B’telco and imagine B’telco have an existing network in France. Imagine they want to extends their coverage worldwide, eventually reduce their local cost by removing some redundancy in the cities. In a such case, they can roam traffic over helium.

This means that the data of B’telco devices will be acquired by helium router, exactly as a Helium data, and then it will be routed to B’telco network server transparently. That way, the customer will have a better coverage and the B’telco cost for this worldwide extension will be really low.

In this blog post, I’ll explain how this roaming feature works and what is needed to deploy it.

Continue reading

Debunk an LPWAN / IoT comparison

The LPWAN comparison artwork

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.

Continue reading

SenseCAP M2, the Helium data-only hotspot, (close to be) ready-to-go

Sensecap M2 – data only

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.

Continue reading

Astrocast, another route to the space IoT

In some of my previous post, I did talk on Kineis IoT satellite solution. The competition is that area is large and one of the other player is Astrocast. I really thanks them for getting me in the program to explore this technology (and I apology to have been a bit long to start using it).

Astrocast is a Swiss company launching nanosatellites to currently provide Europe, Asia, Africa coverage for IoT. It uses L-Band (1-2 GHz) radio. The transmission period will be 15 minutes once the constellation will be fully deployed. The current constellation is 10 satellites for a target of 100 satellites by 2025.

Continue reading

COTX-X3 helium miner review

After reviewing different Helium miner like RAK, Sensecap, Kerlink, Nebra… now comes the Cotx-X3 miner. This miner has a long story and a bad reputation, due to something not really clean the maker did with the first units.

This is not related to the hardware quality and I’ve been happy to buy some of them for reviewing it. This miner is a full miner, based on a standard design using a Raspberry Pi 4. It has the particularity of having a front screen and an audio jack ! Don’t laughs, the reason is simple, this device has a different usage before becoming an helium miner.

Continue reading

Deploying Helium-ETL instance with API

Helium blockchain ETL is basically a copy of the Helium Blockchain into a database. That way you can query the helium blockchain history to build apps like monitoring, tax management…

The Helium blockchain API project is connected to the Helium ETL to get an easy access to these data.

I’m currently building a tool to monitor and alarm a fleet of hotspots (stay tuned) and it currently uses the Helium API (api.helium.io). But helium APIs are a bit overloaded and not made to support high rate querying from each of the application any member of the community is developing. So I’ve been decided to make my own instance of ETL and API for my own purpose. This is the experience I’ll describe in this blog post:

Continue reading