New event on the emnify platform: 75% of your monthly limit reached

24.02.2023
guide-image

The emnify platform gives you the opportunity, through the service policies, to set up a monthly data & SMS limit. This feature is now complemented with a new event/alert warning you that 75% of said limit has been reached.

In this article, we will show you how to use this new feature to have better control of your consumption and get notified via email when 75% of your data limit has been reached.

Requirements

  • an emnify account
  • at least one connected device
  • a Zapier account linked to your emnify account

1. On the emnify portal

a. Setting up a data limit & assigning it to the device

Please refer to this article for setting up a data or SMS limit.

For this exercise, we will set up a small limit of 12MB and assign it to our test device:

b. Testing the alert & finding the event

Once you’ve correctly set up your data limit, and used some data, go to “Details” on the device with the data limit:

Then go to the “Events”:

The following event will show up once you’ve used 75% of said limit:

In this case, the limit set was 12 MB per device and per month. Therefore, the event showed up once 9 MB of data was consumed:

2. Setting up an email alert via Zapier

If you haven’t used the combination emnify + Zapier before, please refer to this article for a comprehensive introduction.

a. Create your Zap

All set? Then create a new Zap:

Choose emnify as the triggering app:

b. Select the right event

Choose “All emnify events”:

Choose your account (to associate your account, please refer to this article on how to associate your emnify account):

Choose event number 65, “Endpoint data traffic limit warning”:

Concretely, choosing this event will create a data stream between emnify and zapier which will only redirect the event “Endpoint data traffic limit warning” to your Zapier account. As such the data stream will show up in the “Integration” tab of your emnify account and we recommend naming it properly so you don’t confuse it with other data streams that you might have created, and deleted by mistake:


c. Test your trigger

After creating your Zap and selecting your event of interest, it is time to test your trigger.

In this step, Zapier will consult all emnify events in order to find a previous instance of the event “Endpoint data traffic limit warning”. If such an event happened before, then you’ll receive a recap. Click to “Continue”:

If this event has not occurred before, then Zapier will notify you and ask you if you want to proceed. You can then click Skip Test or go back to step 1.a :

d. Have this event trigger an email being sent

You can then choose the application which will issue the notification following the occurrence of the event. In this article, we will use Gmail, but as you can see, there are hundreds of other options, including Outlook, Slack, Mailchimp, SalesForce, Hubspot, etc.

Once you’ve selected, choose the type of action you want the app to perform. In this example, we want Gmail to send us an email:

Then choose your account.

Once the account has been chosen, please select the recipient of the email. You can also add addresses in CC, and BCC as well as the originator of the email and her/his/its name.

Finally, you can decide what will be the content of the email, especially the title and the body of the email. Zapier conveniently provides you with fillers obtained from the test we performed earlier. Once the Zap has been turned on, future notifications will automatically contain all information regarding to your device name, ICCIDs, tags, etc.

e. Test & Publish your Zap

Zapier will then show you a recap and ask you to confirm. If you are happy with all the email looks like, click Continue. A test will be performed straight after:

If you are happy with the result, you only have to click on “Publish Zap” and let the combo emnify + zapier monitor your consumptions and do the work for you automatically.

3. Implement on all your devices

After this testing device and testing data limit, you can obviously use this feature on a larger scale, with different devices and different data limits, for instance, 1,500MB:

Related Posts

Image for post LwM2M vs MQTT: Which one is the best for IoT Solutions?

LwM2M vs MQTT: Which one is the best for IoT Solutions?

While building IoT solutions, keeping the footprint small is of utmost importance. This requirement influences all design aspects of IoT solutions, including communication. Transferring data from your IoT devices to your application servers efficiently is important, but at the same time, you also need to have a lightweight way of doing so. In this post, I will compare MQTT and LwM2M communication protocols for IoT solutions. What are Communication Protocols? Simply put, communication protocols are rules that define how two connected systems communicate with each other. These protocols cover everything from authentication, signalling, security, data transfer, flow control to error detection and handling. The Internet of Things drives innovation in these protocols to make them more efficient and secure among other things. What is MQTT? MQTT stands for MQ Telemetry Transport where the MQ part comes from an IBM product called the MQ Series. MQTT is a protocol that was specifically built for M2M and IoT message transfer by Andy Stanford-Clark (IBM) and Arlen Nipper (Arcom). The protocol helps transfer messages using the publish and subscribe model which enables it to send messages to one or multiple subscribers. What is LwM2M? LwM2M stands for Light Weight M2M. It is a protocol designed by OMA SpecWork’s for device management but is also suitable for data transfer with the objective of attaining reduced power and data consumption. It is built on top of CoAP (Constrained Application Protocol) which increases its bandwidth efficiency. LwM2M has a transport agnostic design which by default uses UDP, but also supports TCP and SMS. Architecture MQTT As mentioned, MQTT has a publisher and subscriber model. There is no direct connection between the sender of the message and the receiver. There are 2 basic components in this architecture. Client Broker Clients can publish messages on topics to the broker. The broker then dispatches these messages to any clients that subscribe to that topic. Thus the broker decouples the publisher and the subscriber. MQTT brokers do not normally store messages, but do offer buffering of messages in some cases. MQTT uses TCP/IP to connect to the broker. The broker authenticates and authorizes the clients and maintains the session data of all active clients. The broker is responsible for receiving all messages, filtering the messages, determining who is subscribed to each message, and sending the message to these subscribed clients. LwM2M In an attempt to standardize device management and telemetry, LwM2M supports device management functions, in addition to data reporting (as MQTT does). Bootstrapping Device Configuration Firmware Update Fault Management Configuration & Control Reporting For all the above functions there are procedures defined, e.g. how the device registers at the server, or how the server initiates a client diagnosis. The common structure under all the above functions is a client - server model. The client initiates the connection with the server. The server then uses REST APIs to perform either of the above functions. Implementation MQTT An MQTT client can be any device that runs the MQTT library and connects to the MQTT broker and can have a very small footprint depending on the library used. An MQTT client usually sends data to the server, such as telemetry data. It contains scripts to publish messages to a topic. There are several MQTT client libraries available depending on your preferred programming language. An MQTT broker is the heart of this protocol and can handle millions of MQTT clients depending on the implementation. An MQTT broker needs to be highly scalable, integrated into your backend systems, and failure-resistant. The broker needs to receive, filter and forward all messages to the clients that subscribe to them. As mentioned earlier, it needs to maintain the data-sessions of all the clients connected to it. There are several implementations of the MQTT broker available as open-source or paid. LwM2M Depending on the function that you are using it for, there can be several implementations of the LwM2M client and server. The LwM2M client initiates a connection with the server. LwM2M uses a simple resource model with the core set of objects and resources defined in the specification. As an example, the device here is an object, with id 3 and the device has resources like firmware version, serial number, etc. which have a fix resource id. So to get information about a particular resource of the object device, the server can send a call like READ 3/3/0. The LwM2M client implementation contains code to initiate the connection with the server with credentials, sending the necessary data requested by the server, callback functions for LwM2M resource executions and send error events. It can also contain other functions depending on the use-case. The LwM2M server on the other hand needs to authenticate LwM2M clients, send correct requests using the REST API and process the requested information. There are several open-source as well as paid implementations available for the LwM2M client as well as server. LwM2M also has a Developer Toolkit which can be used to implement your own versions. Security MQTT MQTT supports various authentications and data security mechanisms. These mechanisms are configured on the broker and the client needs to comply with these mechanisms. MQTT uses TCP/IP and you can also leverage Transport Layer Security (TLS) to use secure the connection. LwM2M LwM2M also supports authentication and data transport security mechanisms. LwM2M uses CoAP which usually uses UDP as the transport protocol. When using UDP, LwM2M supports DTLS. CoAP also supports TCP and TLS accordingly. Use Cases MQTT MQTT is used for sending payload for low-power and constrained applications, thus making it a favorite choice for many IoT applications. MQTT brokers are a big component of Cloud based IoT solutions. Logistics - for connectivity and real-time monitoring of vehicles Manufacturing - For monitoring of manufacturing plants Smart Home - For energy monitoring, home security, home patient monitoring Oil and Gas - The use-case it was first built for, to monitor the oil pipelines Consumer products - Like smart appliances Urban Mobility - For city transportation systems, car sharing etc. LwM2M While LwM2M also supports sending telemetry data, it was built to standardize device management and provisioning, thus making it ideal for the 6 functions that it defines in its implementation. Bootstrapping - Enables headless device management, thus enabling shipping the devices without configuring them in the factory. Device Configuration - Enables device life cycle functionalities like enable, disable and update. Firmware Update - Enables FOTA/ SOTA for devices. Fault Management - Enables monitoring of statuses like battery level, memory, sw/hw version etc. Configuration & Control - Enables setting of APN and other functionalities for cellular connectivity, as well as activating, rebooting and disabling the device. Reporting - Enables error reporting from the devices Conclusion While deciding the right protocol for sending essential data from your connected devices to your application, the question is not whether you use MQTT or LwM2M. From the above description, you can see that both protocols were designed for different and specific purposes. So if your application needs a higher payload of data to be sent, you might choose MQTT and will have to implement functionalities like device provisioning, OTA on top of it. On the other hand, if the application needs to monitor critical statuses on the device, as well as needs the convenience of lightweight device management, you might want to choose LwM2M. Platforms like AWS IoT, Azure IoT Hub have an inbuilt version of the MQTT broker which you can use to send payload through your device. You then only have to configure the MQTT client on the device. The device management in AWS IoT and Azure IoT hub is then done through device shadow and device twins respectively. If you are hosting and managing your own cloud applications, you can use LwM2M for device management and build your own MQTT broker for messaging. There can also be use-cases where you might need to use a combination of both. In any case, it is important to understand that MQTT and LwM2M protocols are not replacements of one another but built for distinct use-cases. Stay glued to this space to see a comparison between MQTT and CoAP next. And if you wish to know more about protocols and IoT check out our Comprehensive Guide to IoT Protocols. Until then, Stay Connected!