Device Page
In the detail page of a single Device, you can manage all the information and features of the EDGEHOG platform such as the status of the Device, the OS installed and its version, connections information, and all other useful information. It is also possible to manage the features made available on the platform such as localization, docker application management, remote connection management with the gateway, and more.
In this page it’s possible to display:
The device’s serial number;
The device’s name;
The device’s model;
Installed Gateway;
Gateway’s serial number;
Gateway’s OS;
Associated Tags
Gateway’s connection status;
Configuration status;
Battery status
All the information on the Device page and its tabs are related to the latest status reported by the Device online. When the Device status is offline, the latest information available online remains displayed in the interface.
In this section of the page, under the device image, you can check the information on the status of the device.
Online/Offline Status;
Register Status;
Provisioning Status.
The Provisioning phase is a preliminary setup that the platform acts on the Device the first time it is created. In this phase, the platform configures the Device in the way indicated by the template Model chosen. If the OS version of the gateway is not the latest available, the update is automatically sent to the Device. The Gateway may restart at this stage to install the received update. In addition, the Docker Applications set in the Model are configured on the device pending the first necessary installation/download.
Hostname
Sim Card IMSI (if present on the gateway)
Modem IMEI (if present on the gateway)
Storage
Free Memory
Power
Battery Status (if present on the gateway)
The status of all connections on the device is shown in the following table. It is possible to consult which are the active connections and their configurations.
1. Ethernet connection status 2. Wi-Fi connection status 3. Mobile connection status (if present on the gateway) 4. All the Bridged connections status
Here is the list of sensors associated with the device and their readings. There is also the possibility to export all data in a .csv file.
In this section, you can find all the Docker Applications deployed on the device. On the left, you can choose between the individual applications.
In the Services table, you can manage the entire docker service that composes the application thanks to the buttons on the right by sending Start, Stop, Install/Update commands, and refresh the interface to update the current status of the application. The devices will use the Docker Compose commands to perform the selected operations (e.g. docker-compose up, docker-compose down, docker-compose pull)
If the selected application is contained in a private registry, and an Install/Update operation is chosen, a popup for entering authentication credentials will be displayed.
The popup shows the Registry URL and Registry account data saved in the application. Besides, you will need to enter the Token or Password to enable the device to authenticate with a private registry.
We suggest to always use a Token instead of a Password to log in to a private Registry. Check the documentation provided from your Registry to know how to generate an authentication Token.
In the Application Logs section, it is also possible to make a download request of the latest logs related to that Application to check its status in detail. Press the Get new button and the Log will be available for download after a few seconds on the list.
There is a known problem in AWS ECR private registry integration. Sometimes the installation/update of container images stored in ECR registries returns "no basic auth credentials" error. If you encounter this error message, please just retry with the same user and token.
Check the Docker Application page to have more details about this feature of EDGEHOG device management.
Check the Geolocation dedicated section to see what you can do from this tab.
All gateway events (connections, disconnections, etc.) are recorded here
Here is the list of OS campaigns in which the device has been involved. Specifically are reported:
Campaign Name
OS Release
Campaign status
Device Campaign status
Here is the list of File Upload campaigns in which the device has been involved. Specifically are reported:
Campaign Name
File Name
File Version
Campaign status
Device Campaign status
The table only shows the file campaigns of which this device was part. It is not verified that the file is still present on the system in the declared folder. It is possible that a file is "consumed" by a third-party application and then moved or deleted after its use is complete.
This section enables the download of LOG files from the Device to check with higher detail the status and possible anomalies occurring to the system.
Using the Log Type options, it is possible to choose to download LOG files from the core of the OS or from a specific service. The Device Manager Agent installed in the EDGEHOG OS use thejournalctl utility to read LOG and send it online to provide a text file to the user.
It is also possible to select a time range within which the LOGs are contained and also a Max lines number.
Once a new log request starts, the user can wait and refresh the table data until the new LOG file appears in the table, ready to be downloaded.
Non-Linux systems, such as microcontroller-based devices, have access to a subset of these features, e.g. you can't choose services or the time range won't go back very far.
This is a free space where you can write notes related to the device.
