ThingsBoard is an open-source IoT platform designed for device management, data collection, processing, and visualization. It supports a variety of communication protocols, including MQTT, CoAP, and HTTP, allowing seamless integration with diverse devices and sensors. The platform offers powerful tools for monitoring and controlling devices, as well as visualizing sensor data through customizable dashboards.
ThingsBoard provides essential features such as device provisioning, real-time data processing, and rule engine capabilities for automated actions based on data inputs. It also supports user role management, enabling secure access control. With its scalable architecture, ThingsBoard can be deployed on-premises or in the cloud, making it suitable for a wide range of IoT applications, from smart cities to industrial IoT use cases. The platform is highly extensible, supporting integration with third-party systems and services, ensuring flexibility for developers and businesses alike.
In my previous article, I shared my first steps as a Mioty user. Today, I want to dive into the creation of devices using this technology. It took me some time to publish this follow-up, as I encountered a few challenges—primarily related to an ecosystem that, unfortunately, remains stubbornly inaccessible.
In this initial post, I’ll share my experience with a ready-to-use module from Radiocraft. Future articles will explore other solutions… depending on my available time, of course. As you can probably tell, I haven’t been posting much lately, as I’ve been busy with other projects. Stay tuned!
The choice of an STM32WL microcontroller precludes the use of internal EEPROM, requiring the use of either an external EEPROM or the internal Flash memory for storing persistent data. The latter option is often favored in many designs (and modems) for cost reasons, though it comes with certain implications.
Using networks like LoRaWAN and Sigfox involves regular persistent writes. In the case of LoRaWAN, using OTAA (Over-The-Air Activation) mode, the devNonce must be recorded during each join procedure to ensure its uniqueness over network connections. Here, the number of persistent memory writes will theoretically be low (except for the battery end-of-life scenario discussed later). For an ABP (Activation By Personalization) connection, the situation differs significantly; the frame counter (FCnt) must be recorded so that it does not reset to zero in the event of a reboot. The same applies to Sigfox and its SeqId, which must increment with each communication. Without specific logic, LoRaWAN ABP and Sigfox will write to persistent memory with each data transmission.
While an EEPROM memory area has a lifespan of about 100,000 to 1,000,000 cycles (still potentially lower than the number of messages sent during the object’s lifecycle), a Flash memory area lasts only 10,000 writes, a number quickly reached in IoT communications. Therefore, using Flash as persistent storage requires a different approach compared to EEPROM in this context.
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.
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.
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.
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:
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish.AcceptReject
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
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.
