<html><head></head><body><p dir="ltr" id="isPasted">Cellular IoT is hard. Building an end to end application requires in-depth understanding of hardware, firmware, cloud, wireless communication, power management and security to name a few. It’s hard to imagine people having expertise in all of these fields. Unfortunately, <strong>the strength of an IoT solution is as good as its weakest link</strong>. In order to bring a successful IoT project to life, the whole IoT chain needs to be understood.</p><p dir="ltr">In this article, 5 valuable lessons are shared which are gained through painful mistakes.&nbsp;</p><h2 dir="ltr" id="isPasted">LESSON #1</h2><h3 dir="ltr"><strong>Inactive devices can get “purged” by Mobile Network Operators</strong></h3><p dir="ltr" id="isPasted">Novel developments enable IoT devices to enter a deep sleep state while keeping the session with the network operator alive. In order to transmit data, the device simply needs to wake up to initiate the communication instead of going through a complicated process to reconnect to a cell tower. These low power modes are known as Power Save Mode (PSM) and extended Discontinued Reception (eDRX).&nbsp;</p><p dir="ltr">Unfortunately, this doesn’t always work as expected. When mobile operators detect little to no activity they may close the connection with the device to free up resources in their cell towers. This is referred to as “purging” and can happen after several weeks of inactivity, but it may already occur within 1 day.</p><p dir="ltr">Keep in mind when developing your IoT firmware that devices can get purged by mobile operators. When this occurs, a reconnection process is required to establish a new session with a mobile operator.</p><h2 dir="ltr" id="isPasted">LESSON #2</h2><h3 dir="ltr"><strong>Operators don’t allow devices to connect and disconnect too frequently</strong></h3><p dir="ltr">Cellular IoT devices may reconnect to a network operator around six times per hour (source: AT&amp;T). When reconnecting more often, your mobile operator may not allow you to access their network.</p><p dir="ltr">When conducting tests which require the device to reconnect frequently, you may need to switch network providers to enable more reconnections, or simply be patient. When applications require frequent transmissions, the connection with the cell towers needs to stay open. To reduce power, devices can be put in low power modes like eDRX or PSM to reduce battery drain.</p><p dir="ltr"><img src="https://images.wevolver.com/eyJidWNrZXQiOiJ3ZXZvbHZlci1wcm9qZWN0LWltYWdlcyIsImtleSI6ImZyb2FsYS8xNjYzNjg2NTI4MDkyLU1vbm9nb3RvLUlvVC5qcGVnIiwiZWRpdHMiOnsicmVzaXplIjp7IndpZHRoIjo5NTAsImZpdCI6ImNvdmVyIn19fQ==" style="width: 766px;" class="fr-fic fr-dib"></p><h2 dir="ltr" id="isPasted">LESSON #3</h2><h3 dir="ltr"><strong>Data transmissions drain your battery, no matter the technology used</strong></h3><p dir="ltr">To better address the needs for battery-powered IoT devices, the novel cellular technologies NB-IoT and LTE-M hit the market. These new technologies support lower power modes to extend the battery life. However, using a low power wireless technology doesn't change the fact that sending or receiving data consumes lots of energy. Don’t expect a device to run on its batteries for months when sending data every few minutes.&nbsp;</p><p dir="ltr">Transmitting or receiving data using LTE-M technology consumes roughly 100 to 360mA (sources: Quectel, Nordic and u-blox). The key lesson to reduce battery consumption is to reduce the frequency of transmissions and receptions and put your devices to deep sleep for as long as possible. To realize a battery lifetime of multiple years, reduce the daily transmission to a few times per day. Between transmission, put your device to deep sleep mode or turn the radio off completely.</p><h2 dir="ltr" id="isPasted">LESSON #4</h2><h3 dir="ltr"><strong>Use developer-friendly cloud platforms to close the loop</strong></h3><p dir="ltr"><strong>IoT is not about monitoring data, it’s about triggering actions based on data.</strong> When building your application, make sure to directly close the loop by realizing an actuation based on the data you send. Examples are triggering webhooks, sending notifications by email or SMS, or transmitting a message to the cellular device with instructions to activate or deactivate certain processes.</p><p dir="ltr">There are many IoT platforms which enable triggers to be initiated based on incoming data. Unless you are an Azure or AWS expert, don’t start with these advanced platforms. Instead, use a platform which is easy to set up, allows for quick visualizations and rules to initiate triggers using little to no code. Some of my personal favorites include <a href="https://akenza.io/" rel="noopener noreferrer" target="_blank">Akenza</a>, <a href="https://datacake.co/" rel="noopener noreferrer" target="_blank">Datacake</a>, <a href="https://qubitro.com/" rel="noopener noreferrer" target="_blank">Qubitro</a>, <a href="https://ubidots.com/" rel="noopener noreferrer" target="_blank">Ubidots</a> and <a href="https://www.avsystem.com/" rel="noopener noreferrer" target="_blank">AV Systems</a>.</p><h2 dir="ltr" id="isPasted">LESSON #5</h2><h3 dir="ltr"><strong>Benefit from knowledge within IoT communities</strong></h3><p dir="ltr">There are many IoT communities and discussion forums out there aimed at connecting people and sharing experiences and expertise. At Monogoto, we recently launched a Community Forum to support cellular IoT developers in their daily work. The Forum is used to bring knowledge and experience together.</p><p dir="ltr"><strong>We invite you to join the&nbsp;</strong><a href="https://forum.monogoto.io/t/5-cellular-iot-lessons-learned/204" rel="noopener noreferrer" target="_blank"><strong>Monogoto Forum</strong></a><strong>&nbsp;and share your key lesson to support others in their cellular journey.</strong></p><p dir="ltr"><a href="https://forum.monogoto.io/t/5-cellular-iot-lessons-learned/204" rel="noopener noreferrer" target="_blank"><strong>→ Share your key lessons learned</strong></a></p><p dir="ltr"><img src="https://images.wevolver.com/eyJidWNrZXQiOiJ3ZXZvbHZlci1wcm9qZWN0LWltYWdlcyIsImtleSI6ImZyb2FsYS8xNjYzNjYxOTQ2MDE2LU1vbm9nb3RvLUZvcnVtLmpwZWciLCJlZGl0cyI6eyJyZXNpemUiOnsid2lkdGgiOjk1MCwiZml0IjoiY292ZXIifX19" style="width: 766px;" class="fr-fic fr-dib" alt="https://forum.monogoto.io/"></p></body></html>

Valuable IoT lessons, gained through painful mistakes

5 Cellular IoT Lessons Learned

Lightweight Machine to Machine, a simplified communication and device management standard for the Internet of Things.

What's this LwM2M standard, and why should you care?

Announcing the December Build Month. A program to support developers in building their next IoT project with cellular technology.

Monogoto's Cellular IoT Build Month

Optimizing energy efficiency is an art, as well as a crucial skill for any developer building battery-powered IoT devices.

The Subtle Art of Low Power Cellular IoT

Adding cellular connectivity to your Raspberry Pi can be done in a few simple steps.

Add cellular connectivity to your Raspberry Pi

More by Monogoto

What's this LwM2M standard, and why should you care?

Monogoto's Cellular IoT Build Month

The Subtle Art of Low Power Cellular IoT