{% extends "base.html.twig" %}

{% block title %}Devices Overiew{% endblock %}

{% block body %}

    <div class="container-fluid">
        <div class="row">
            <div class="col-md-12">
                <div class="bgc-white bd bdrs-3 p-20 mB-20">
                    <h4 class="c-grey-900"><i class="c-yellow-500 fas fa-question-circle"></i> Devices Overiew</h4>
                    <hr>
<p class = "text-justify">
The Devices table provides flexible overview of devices connected to DWARFG_LONG. You can use the table not only to sort your devices quickly, but, more importantly, to filter the devices so that you see only the subset of devices you are interested in.
</p>
<p class = "text-justify">
You can, for example, filter only the devices based on a synchronization status or search based on DevID (or a particular name if you name your devices).
</p>
<p class = "text-justify">
Use table header for sorting, and first line with text boxes for filtering.
</p>
<p class = "text-justify">
You can also name your devices directly in the table, just click on the name in the appropriate device line. Additional actions can be accessed from the device details that are accessible after clicking on the <b>Detail</b> button or via other pages.
</p>
<p class = "text-justify">
While the default layout of the table is both compact and shows the most wanted columns, you may want to customize it by removing some of the columns or adding some additional ones. You can configure the table layout at <b> System -&gt; Settings -&gt; Device Table Columns </b>.
</p>
<h5 style="margin-top: 30px;">Device ID - DevID</h5>
                    <hr>
<p class = "text-justify">
Every device is automatically assigned a device ID on first connection to the DWARFG_LONG server. The DevID is a number between 1-65535, which is represented by 4-letter string for easier remembering. You can also name any device using a custom name, allowing for even easier identification.
</p>
<p class = "text-justify">
The Device ID is assigned based on a MachineID which is an identifier generated during agent deployment on the device. If, for any reason, the agent gets wiped from the device, another agent installation usually produces identical MachineID thus the same MachineID is generally assigned to the device after the new agent installation and all the historical data are retained and connected - unless the device has been deleted on the server using the Delete device function.
</p>
<h5 style="margin-top: 30px;">Asynchronous communication concept</h5>
                    <hr>
<p class = "text-justify">
All regular information exchange between a device and server is initiated by device. Basically, there is an interval set in the agent running on a device that controls how often does the device contact the server (NOTE: 260 second is the default interval under regular conditions but that is just the default value specified in the DEFAULT agent profile. You may both change the value and also assign a different agent profile to the device, see more on <a href="{{ path('admin_help', {page: 'agentProfiles'}) }}"> Agent profiles </a>).
</p>
<p class = "text-justify">
Because of this asynchronous communication, there is not really any way to expedite any requested action to the device from the server side (exceptions below). Once you request e.g. a configuration change, firmware flashing or any action that needs to be propagated to the device, it will be passed to the device on the next device -&gt server connection, not earlier. The only way how to speed things up is to expedite the connection from the device side by either using the UI (button <b>Sync to server Now</b>) or restarting the agent.
</p>
<p class = "text-justify">
If the device resides on the same network as a server, it may be reached directly by e.g. a SSH connection. Some of the DWARFG_LONG features may use such connection to perform the requested functionality immediately instead of waiting for next device connection. One of the examples is <a href="{{ path('admin_tool_sms_sender_index') }}">Send SMS functionality</a>. For more information about how to use the tool please refer to <a href="{{ path('admin_help', {page: 'sms-sender'}) }}">help page of Send SMS</a>.
</p>
<p class = "text-justify">
DWARFG_LONG is built with a significant accent on performance. To be able to process large amount of devices while not consuming significant amounts of resources (thus allowing to run on a low-end hardware), the asynchronous concept is applied on multiple places. One of this places is the UI so sometimes you may need to wait a few seconds for your actions to be processed by the DWARFG_LONG service. It does not mean that the service is too busy, it is simply the effect of asynchronous communication concept applied on multiple layers - a slight cost of robust design and high data-processing performance.
</p>
                </div>
            </div>
        </div>
    </div>

{% endblock body %}