In this tutorial, we will see how to make an image clustering based AI with the Seeed Wio Terminal and the Grove AI camera. There are different tutorial on this, the main source of this tutorial is located here. The purpose of this is to have a step by-step approach for my student to realize this in a limited time they have.
This is based on SeeedStudio K1100 development kit.
Continue reading
The Dragino LPS8, LoRaWAN gateway is a helium ready device you can add to Helium as a Data-Only. It means it does not participate to PoC but earn HNT for transferring traffic.
It’s not a ready-to-go data-only, so you need to register the hotspot in the helium block-chain on your own but it run the gateway-rs software internally.
This device as been designed for Helium, but not only, it can be connected to TTN or another different network, like a private network. The installation with Helium network is not really complicated but you will need to process some command on a terminal and manipulate wallet-cli.
Continue reading
ChirpStack is an open-source LoRaWAN network server that is being use in a coming future with Helium as a replacement of the console. This blog post explains how to install it with the companion solution I’ve built to interact with Helium router.
The Helium Chirpstack environment is still in Beta. This blog post will not be fully complete until the prod phase and you still see this orange banner. You can take a look at this post if you are curious, you will use it if you are part of the beta test. For the rest, it’s batter to come later (some part a voluntary missing).
Continue reading
The first versions of Nebra indoor miner came with CM3 (Raspberry Pi Compute Module) embedding eMMC memory. As you may know, Helium has been really I/O intensive, particularly this summer when the blockchain was filling really fast the small amount of storage the CM3 has. As a consequence, all my Nebra indoor miner dead around the same week. Diagnostic seemed to be a storage failure.
Here is the story about making them live again
Continue reading
Some time ago, a twitter thread made the community react about the amount of $6600 of communications consumption on the Helium network. This thread was full of approximations in order to present negatively the growth of the Helium network. But it is also an opportunity to take stock of the development of the use of the network. We will see in this article who operates the Helium decentralized network, what are the current data volumes and what are the associated financial metrics.
In short, we cannot talk about Nova Labs’ revenue with respect to direct communication costs because these costs are associated with different third parties offering the packet routing service. We cannot rely on this cost to estimate an associated business volume because there are many indirect costs as I have already specified in my blog post analyzing the running costs of a Helium router/console. Finally, regarding a long period where gamers found a way to earn a few dollars on the back of Nova Labs, involving many ancillary costs, distorted the data for June. You will understand all this in the rest of the article.
Disclaimer: I’m the owner of the public helium console helium-iot.eu (oui 6) – no need to makes comment like “he have written this because he own … blablabla”
Continue reading
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
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
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