# Device

## Create the file structure <a href="#create-the-file-structure" id="create-the-file-structure"></a>

Set up a directory structure with the following files

```
├── src           
│   ├── view.xml           
├── LICENSE
├── README.md
├── manifest.toml
```

## manifest.toml

Fill this file with proper configuration according to the *Device* section within the Private Plugins page. Based on that, the manifest should look like:

```
manifest_version = 2.0

[settings]
version = "0.0.1"
plugin_type = "device"
license_name = "MIT license"
categories = ["End Device"]
filters = {brand = ["Advantech"], connectivity = ["Ethernet"]}
```

## view\.xml&#x20;

For the moment given, this file is not fully implemented for Device plugin, so it is not relevant at all for this plugin type, however it should contain dummy, albeit valid data so the plugin can be deployed. For this reason, you can use the following `view.xml` file on your Device plugin development as dummy file:

```xml
<form name="formName">
    <group name="ubidotsInformation">
        <group name="fieldToken">
            <label name="labelToken">Ubidots Token</label>
            <token name="token" placeholder="Select Token"/>
        </group>
    </group>
</form>
```

## LICENSE and README.md&#x20;

Write the contents of the README.md and LICENSE files.

## Compressing the files

Compress the files in zip format from the root of the file structure, not the parent folder.