# Best practices: Getting started ## 1. **Device Addition** ### **Product definition** Initiating your journey with the 'Product' definition is fundamental. This approach is the cornerstone of easy fleet management. By using Products, you ensure that all devices on one kind inherit essential characteristics, creating a uniform yet flexible operating environment. {% hint style="info" %} All Devices belonging to one same Product have the same Payload Decoder, Fields and Dashboard. If you modify one device, all of them will reflect those changes. This enables you to manage fleets of hundreds of devices, maintaining the integrity ensuring that your whole IoT fleet stays up to date. {% endhint %} In the following video you will learn how to add a device to an existing product. {% embed url="" %} [Learn more about Products.](https://docs.datacake.de/device/product) ### **Configuration Fields** Configuration fields introduce a layer of customisation for the individuality of each device and offer flexibility when using the Product definition. This is important when devices require unique operational parameters, ensuring they perform their roles effectively. If, for example, your gas tank filling measuring devices are all of the same type, however, they are installed in tanks of different heights. In this case the configuration fields allow you to define a different height value for each tank. These can be used in the payload decoder to make calculations, or they can be called within the new rule engine to trigger notifications. [Learn more about Configuration Fields.](https://docs.datacake.de/device/database/configuration-fields) ### **Batch addition of devices** Utilising the CSV drag-and-drop feature for adding devices is more than an operational shortcut; it's a growth strategy. By integrating multiple devices simultaneously, you maintain a rhythm and coherence to your expanding network. This strategic addition ensures your system scales with purpose, keeping complexity at bay. {% hint style="info" %} There is not known limit to the amount of devices you can add at once to Datacake. Make sure all DevEUIs are unique, otherwise you will get an error **No valid DevEUIs were found in the CSV file**. {% endhint %} Make sure that the order of the columns on the CSV file is correct and that there are no empty rows or columns. The order must be **DevEUI, Name, Location description, Tags**. Location description and Tags are optional columns. The tags must be separated by commas in the same column of the document. Here an example of a CSV file containing all columns mentioned: | 49 54 95 75 56 55 65 66 | Device 1 | First Floor | Office01, Temperature | | ----------------------- | -------- | ------------ | --------------------- | | 49 23 47 30 94 74 38 24 | Device 2 | Second Floor | Office02, CO2 | For batch adding devices to the **Datacake LNS** you need to prepare the CSV file with the following information: DevEUI, Name, AppEUI (or JoinEUI), AppKey, Frequency, Class, Location description, Tags.
49 54 95 75 56 55 65 66Device 1cd1a75ae5818dcbec39ebd8578c3d7ac6dfef73afb60dfbaEU_863_870_TTNAFirst FloorOffice01, Temperature
49 23 47 30 94 74 38 24Device 2cd1a75ae5818dcbef171b14be6e3494ce6da3dd8e67cbb8cEU_863_870_TTNASecond FloorOffice02, CO2
Remember that DevEUI and AppEUI are strings 8 bytes long. AppKey is a 12 byte string. All of them should be provided by your device manufacturer. We currently support the frequencies: * `EU_863_870_TTN` * `US_902_928_FSB_2` And the devices classes: * `A` * `C` {% hint style="warning" %} Please make sure the frequency and class are written correctly, exactly as shown above. {% endhint %} Again, Location description and Tags are optional columns. {% hint style="info" %} Make sure that your CSV file doesn't have a header with the titles (it should simply start with the first device). Otherwise the platform will return an Error message. {% endhint %} ## 2. Data Ingestion Rate Guidelines for Datacake To ensure optimal performance and reliability, all IoT devices connected to Datacake must adhere to the following data ingestion guidelines: * **Minimum Ingestion Interval**: Devices should **not** send payloads at intervals of less than **1 minute**. The Datacake platform is not designed to handle high-frequency data transmission, and payloads sent at rates faster than this may result in data loss or system instability. * **Intended Use**: Datacake is optimised for IoT devices that typically transmit data **a few times per day**. Our infrastructure and functions are built around this usage pattern, and adhering to these guidelines will help maintain system efficiency and reliability. Please configure your devices accordingly to prevent any potential issues with the platform features. ## **3. Workspace management** Implementing separate workspaces for different tenants is a practice of meaningful delegation. You can manage who gets access to what in an easy way. If you have multiple customers/locations/departments, the easiest way to grant access to specific devices is to have different workspaces for each one of them. When having control over the devices is important, Datacake recommends you to create a **master workspace**, to which you will add all of your devices, while having sub-workspaces for each one of your customers. You can use the [Pincode claiming](https://docs.datacake.de/device/claiming) functionality to claim specific devices to those sub-workspaces. This structure safeguards your devices, ensuring it remains a hub for all devices, while subsidiary workspaces function as dedicated environments tailored to specific tasks or teams. This clear delineation promotes responsible access and efficient management. An additional advantage of employing this structure is that it ensures the receipt of a unified invoice including all devices in the master workspace, due to the fact that the billing procedure is conducted on a per-workspace basis. ## **4. Application of Tags** By applying tags, you facilitate targeted reporting, efficient rule-setting, and effective device visualisation. You can set/create tags when adding the devices to the platform. You can also add them once the devices are on the platform using the Actions/Add Tags button or by navigating to each device's configuration section. You can manage devices and sort them by type/location/owner, among others. Tags can be used to generate reports in device batches, create custom notifications in the new rules system or add them to the map widget. The following video shows you how to use the multi-selector in the List view to add tags to your devices: {% embed url="" %} ## **5. Overview, List, Grid and Map Views** Choosing between your Overview, List, Grid and Map views is a decision rooted in your information needs. This choice influences how you interact with your fleet data, prioritising the most critical metrics front and center. By customising these views, you are making a conscious decision about what metrics drive your decisions daily. At the top of the page, next to "Add Device" you will see the Settings configuration. That will allow you to configure the Temperature unit (°C or °F) and select the Sensor Metrics style (Cards or Table). ### Devices View – Overview The **Overview** tab provides a high-level summary of all devices within your workspace. It is designed to give you an immediate understanding of device status and key sensor metrics across your entire fleet. This view displays aggregated KPIs in the form of visual cards, allowing you to quickly identify issues, trends, and overall performance. At the top of the Overview page, you will find the **Device Status** summary. These cards provide a quick snapshot of your fleet’s operational state: * **Total Devices** – The total number of devices in the workspace. * **Online Devices** – Devices currently connected and actively sending data. * **Offline Devices** – Devices that are currently not connected. * **Active in Last 24h** – Devices that have transmitted data within the last 24 hours. This section helps you quickly assess system health and connectivity across all devices. Below the Device Status section, you will find the **Sensor Metrics** area. This section contains metric cards automatically generated based on the **device** [**semantics**](https://docs.datacake.de/field-semantics) configured in your devices. Semantics define the meaning of device fields (e.g., Temperature, Humidity, CO₂, Battery, Signal Strength, etc.), allowing Datacake to aggregate and display them consistently across devices. Each KPI card in the Overview is interactive. When you click on a card you are redirected to a detailed view. The system filters devices that contain the selected semantic. * You can see: * Average value * Minimum value * Maximum value * The list of relevant devices * Individual device values This allows you to move from a fleet-wide summary to a more detailed device-level analysis in just one click. The Overview view is ideal when you want to quickly check overall fleet health, identify abnormal environmental conditions, detect connectivity issues, compare aggregated values across devices and/or monitor key KPIs at a glance. It serves as a dashboard-style summary before switching to List, Grid, or Map view for more specific device management tasks. ### Devices View – List The **List** view provides a structured, table-based overview of all devices in your workspace. It is designed for detailed device management, quick comparisons, and bulk operations. This view is especially useful when you need to configure multiple devices at once or customise the displayed device information. Each row in the List view represents a single device. By default, the table displays Online status, device name, primary, secondary, device signal and device battery. You can select which columns to display. The options available are: * Online Status * Device Name * Primary Value * Secondary Value * Device Signal * Device Battery * Serial Number * Location (Location description) * Tags * Last Seen * Product * Product Type (LoRaWAN, API, etc) * Device Location (geolocation coordinates) The visible columns depend on your configuration (see below). You can drag each of them up or down the list, depending on the position you want to put them in. {% hint style="warning" %} Keep in mind that the selected columns are stored in the caché memory of your browser, so your customers or users within the platform will have the possibility to select the columns that are important to them. This facilitates customisation, therefore if you want your customers to see certain parameters then you will have to create custom views using global dashboards. If you clear your browser cache or switch browsers/devices, your column configuration may reset. {% endhint %} At the top of the List view, you can also use the **Search bar** to quickly find devices. #### Multi-Select and Bulk Actions The List view supports multi-device selection for bulk management. At the right side of the table you will see the option to select devices. Click on the first checkbox to select all of the devices (in the current page), or feel free to multi-select the devices you'd like to configure. A selection bar will appear at the top showing the number of selected devices. Once devices are selected, you can perform bulk operations: 1. Click **Edit** to open a configuration modal that applies changes to all selected devices. Within the Edit modal, you can: * Change the **Device Name** * Use a name template (e.g., `{name}`, `{serial}`, `{location}`) * Use index counters for batch renaming * Set or update the **Location description** * **Add tags** to all selected devices * **Remove tags** from all selected devices Changes are applied to all selected devices simultaneously. If a field is left empty in the modal, the current value will remain unchanged. 2. Click **Delete** to remove all selected devices at once. {% hint style="danger" %} Deleting devices is permanent and cannot be undone. {% endhint %} ### Devices View – Grid The **Grid** view displays your devices as visual cards, providing a compact and intuitive overview of each device and its key metrics. This view is ideal when you want a quick, device-by-device snapshot while still maintaining a visually structured layout. Each card typically displays: * **Device Name** * **Meta information** (e.g., Serial Number, Location, or Last Updated) * **Primary value** * **Secondary value** * **Battery level** * **Signal strength** * **Online status indicator** * Quick action icons (View and More options) The layout makes it easy to visually scan multiple devices at once. You can customize how device cards are displayed using the **Settings** button in the top-right corner. The options allow you to choose which metadata appears under the device name: * **Serial Number** * **Last Updated** * **Location (Location Description)** Only one meta information field can be displayed at a time. You can also adjust the size of the device cards: * **Small** – Compact layout, ideal for viewing many devices at once. * **Medium** – Balanced view with more readable spacing. * **Large** – Expanded layout with greater emphasis on device values. This allows you to optimize visibility depending on screen size and monitoring needs. At the top of the Grid view, you can use the **Search bar** to search and filter devices. ### Devices View – Map The **Map** view allows you to visualize your devices geographically on an interactive world map. This view is ideal for location-based monitoring, regional analysis, and large-scale deployments where physical device distribution matters. To appear in the Map view, devices must have: * A defined **Device Location** field * Valid **geolocation coordinates** (with latitude and longitude) If a device does not have proper coordinates configured as Device Location ([Roles](https://docs.datacake.de/device/database/fields/field-roles)), it will not be displayed on the map. Each device is represented by a marker on the map. Depending on the configuration established in **Settings**, markers can display: * Primary value * Secondary value * Device battery * Device signal * No value (Marker only. The marker taken will be the Device's Icon set in your device's "Configuration" section) When clicking on a marker, a detail popup appears showing: * Device name * Meta information * Primary and/or secondary values * Battery status * Signal strength * Status indicators (if applicable) * Quick access icons (View / More options) This allows you to analyze device performance directly within its geographic context. When multiple devices are located close to each other, the Map view can group them into **clusters**. * A cluster displays the number of devices inside it. * Zooming in separates clustered devices into individual markers. You can enable or disable clustering via the **Settings** menu. You can also adjust the visual style of the map: * Light * Dark * Outdoors * Satellite * Streets This helps optimize visibility depending on lighting conditions, presentation needs, or specific geographic use cases. ### Navigation Controls The Map view includes: * Zoom controls (+ / −) * Pan functionality * Search functionality (via the top search bar)