Feature Requests

You spoke about your desire for improved connectivity events and notifications, and we listened! Development work on our upcoming major feature release, ‘Events Center’ is now well under way. What you told us you wanted: Email Notifications: You want to be notified of any critical connectivity changes on your account, including monthly and daily limits or data pool threshold changes (without the need for external Zapier integrations Improved Event Log: You wanted to better filter and troubleshoot issues with a dedicated event log, giving you immediate clarity on the root cause of disruptions—an upgrade from our current streaming-only Data Streamer feature Event Templates: You want to be able to define and group events on your own terms. For example, triggering a notification when a single device hasn't been sending data for the last 2 hours We need your help! Before we fully release our ‘Events Center’, we want to be certain that it covers your key requirements and fits your use cases. This is where you come in. Please drop a comment below about any of the following: The connectivity events that matter most to your organization Any additional notification triggers or filters you'd like to see How you're currently managing alerts and where you're facing challenges Whether multiple people are involved in responding to these alerts, and how we can help streamline your team's workflow Your insights are greatly appreciated and will help us improve our solution to better support your team's requirements when responding to important connectivity events If you’d like more of an input on the feature please feel free to drop a comment below stating so and one of our IoT experts will reach out to you.

We are interested in knowing how many devices are connected on 2G, 3G and 4G networks.

Kurz: Alias pro SIM festlegbar SIM nach Alias suchen Übersichtsseite (ggf. auch Export) mit Alias + Datenvolumen etc. Da wir unsere Simkarten unter verschiedenen Geräten tauschen, also nicht dauerhaft im gleichen Gerät verbauen, wissen wir nie genau welche SIM jetzt in welchem Gerät ist. Es wäre es für uns hilfreich, wenn wir die Karten im Portal benennen könnten. Dadurch können wir die Karten schneller im System finden. Wir haben bei uns intern beispielsweise Kategorien: E01, E02, .... C01, C02 usw. Diese IDs würden wir gerne auf die SIM schreiben und entsprechend im Portal darüber finden können. Aktuell wäre es so, dass wir die große ICC ID verwenden müssen, das bedeutet, eine sehr kleine Zahl auf den Karten lesen und abgleichen.

Would it be possible to display the last known location for devices which are offline? In Connected Devices > Device detail > Location.

Report on SMS Logs. Sent and received if any.

Hello, I think there is a need for individual data caps on SIM cards without having to edit the Policy itself. This is cumbersome when you have particularities for a small number of SIMs. Creating multiple polices for various data caps is not ideal. Thanks!

It would be helpful to select from a list the used tags.

API Endpoint: Create a new API endpoint that provides the current geo-location (latitude and longitude) of a specified device. Parameters: The API should accept device identifiers such as IMEI or device ID. Response: The response should include the device's latitude, longitude, timestamp of the location, and accuracy details. Authentication: Ensure that the API is secure and can be accessed using existing Emnify authentication methods. Use Case: This API will be used to integrate accurate device location data into our application, improving the overall functionality and user experience.

Have a notification system within Emnify that does not require the use of a third party program. We just need to be notified when SIM cards reach their alert threshold or their data limits. Its too difficult to implement a third party program for this.

Within the Emnify UI when exploring devices ( https://portal.emnify.com/connected-devices?page=1&per_page=10 ) we recently found that it was perhaps too easy to accidentally disable/enable an active device. We might suggest that at least the act of switching from enabled to disabled is followed by a confirmation to prevent this from being so easy to do accidentally from the UI.