> ## Documentation Index > Fetch the complete documentation index at: https://documentation.kodelabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Device graphics > Create and interact with equipment-level visual representations showing live point data, status indicators, and control options. Device graphics are a building-level feature. Select a building from the [sites list](/products/kode-os/sites-and-map) to access device graphics through the Devices module or Graphic Tool. Device graphics are equipment-level visual representations that display live point data, status indicators, and interactive controls for a single device. They provide a focused view of how an individual piece of equipment is operating, making them valuable for troubleshooting, commissioning, and day-to-day monitoring. ## Access a device graphic You can reach a device graphic from two locations: * **Device details page** -- select a device from the [devices list](/products/kode-os/devices/devices), open its details, and click the `Graphic` tab * **Graphics module** -- click `Graphics` in the left sidebar, select the `Devices` tab, and open an existing device graphic Graphics module showing the Devices tab with device graphic cards, and a three-dot menu expanded on VAV_310 showing Edit, Save as template, and Delete options From the Devices tab in the Graphics module, click the three-dot menu on a graphic card to access `Edit`, `Save as template`, or `Delete` options. ## Create a device graphic You can create a device graphic from two entry points: * **Device details page** -- navigate to a device, click the `Graphic` tab, and click `+ Create New` * **Graphics module** -- click `Graphics` in the left sidebar, select the `Devices` tab, and click `New Graphic` VAV_304 device details page showing the Graphic tab with Apply Template and Create New buttons on an empty canvas Click `+ Create New` to open the New Device Graphic dialog. New Device Graphic dialog with fields for Graphic Name, Device dropdown showing VAV_304, Description, and a Device File drag-and-drop upload area Enter a descriptive name for the device graphic. The device this graphic belongs to. When creating from the device details page, this is pre-filled. When creating from the Graphics module, select the device from the dropdown. Add an optional description of the graphic's purpose. Upload a background image, equipment diagram, or schematic. Drag and drop a file, click `Browse files` to upload from your computer, or click `Browse from files` to select from previously uploaded files. Click `Done` to create the graphic and open it in the [Graphic Tool](/products/kode-os/graphics/graphic-tool) editor. ## Build the device graphic The Graphic Tool editor provides three tabs for building device graphics: Devices, Elements, and Basics. ### Devices tab The `Devices` tab lists all devices and their points. The main device assigned to this graphic appears at the top of the list with a red flag icon. A green checkmark with a number indicates how many points from that device are already placed on the graphic. Graphic Tool editor showing the Devices tab with VAV_407 flagged as the main device, a 3D AHU model on the canvas with point markers showing Discharge Air Temp and other readings Expand a device to see its points with current values. Drag a point onto the canvas to place a marker at the corresponding location on the diagram. You can add points from any device, not only the main device assigned to the graphic. ### Elements tab The `Elements` tab lists all elements placed on the graphic canvas, including device markers and text labels. Select an element from the list to highlight it on the canvas and access its style options. Graphic Tool showing the Elements tab with VAV_409, VAV_407, and Text entries listed, and the device graphic on the canvas ### Basics tab The `Basics` tab contains shapes, device widgets, uploads, and built-in drawings for constructing device graphics. Graphic Tool showing the Basics tab with Shapes, Device Widgets, Uploads, and Drawings sections including AHU Elements with Sensor and Fan categories * **Shapes** -- add rectangles, circles, triangles, arrows, polygons, lines, and text labels * **Device Widgets** -- add device tables, zone tools, and pivot tables * **Uploads** -- upload custom images from your computer * **Drawings** -- use pre-built equipment components (AHU elements, sensors, fans, coils) from the built-in library For details on each section, see the [Graphic Tool Basics tab](/products/kode-os/graphics/graphic-tool#basics-tab) documentation. ## Save as template Device graphics can be saved as templates and applied to other devices of the same type. Click `Save as template` in the upper right corner of the editor. Save as template dialog with Template Name field showing VAV Template, a Description field, and Cancel, Save and Apply, and Save buttons Enter a name for the template (for example, `VAV Template`). Add an optional description for the template. * **Save** -- saves the template for future use * **Save and Apply** -- saves the template and opens the Apply Template dialog, where you can select other devices to apply the template to Apply Template dialog showing a search field with vav_310 entered, a device list with VAV_310 on Floor 3, and Close and Next buttons Search for devices by name, filter by type or area, and select the devices you want to apply the template to. Click `Next` to proceed. On the next step, choose how the template maps points to the target devices: * **Ontology field** -- matches points based on their ontology classification * **Point name** -- matches points based on their exact point names The `Compatibility` column shows how many points from the template match the target device (for example, `6/6` means all six points matched). Apply Template dialog with Ontology field selected, showing VAV_310 with 6 out of 6 compatibility Apply Template dialog with Point name selected, showing VAV_310 with 6 out of 6 compatibility Select the target devices and click `Apply`. The Activity Log tracks the template application status. Activity Log showing Graphic Template VAV_310 with Completed status Once applied, the target device's Graphic tab displays the same layout and markers as the original template. VAV_310 device Graphic tab showing the applied template with a 3D AHU model, point markers, and live data values You can also apply a saved template from a device's `Graphic` tab by clicking `Apply Template`. ## Manage device templates Click `Templates` at the bottom of the Graphics module sidebar to view all saved device templates. Graphics module showing the Templates link in the sidebar and the Device Templates page with a VAV Template card, search bar, and Import Template button Click the three-dot menu on a template card to access management options. Device Templates page with three-dot menu expanded on VAV Template showing Apply template, Export template, and Delete options ### Apply a template Select `Apply template` to open the Apply Template dialog. Search and select the devices you want to apply the template to, then click `Next`. Apply Template dialog showing a list of VAV devices with Device, Type, and Area columns, a search bar, and filter options Choose the matching method (Ontology field or Point name), review the compatibility scores, and click `Apply`. Apply Template confirmation showing VAV_304 with 6 out of 0 compatibility and VAV_101 with 6 out of 6 compatibility ### Export and import templates Select `Export template` from the three-dot menu to generate a shareable link. The link is copied to your clipboard automatically. Export Link Generated notification showing the link has been copied to clipboard with instructions to use the import button To import a template from another building or site, click `Import Template` at the top right of the Device Templates page. Paste the exported link, enter a name and canonical type, and add an optional description. Import Template dialog with fields for Import URL, Name showing FCU Template, Canonical Type showing fcu, and Description Paste the template link copied from the export step. Enter a name for the imported template (for example, `FCU Template`). The device type this template applies to (for example, `fcu`). This value is carried over from the exported template and cannot be edited. Add an optional description for the template. Click `Save` to add the template to your Device Templates library. ## Interact with writable points Writable points on a device graphic display an interactive indicator. Click a writable point marker to open the command panel. The panel displays the device's variables on the left and the action form on the right. Command panel for VAV_301 showing variables including Discharge Air Flow, setpoints, and cooling flow on the left, with action fields for Priority, Value, Duration, Reason, and Specific Reason on the right * **Priority** -- select the command priority level (for example, `Override`) * **Value** -- set the target value. Use `+` and `-` to adjust. * **Duration** -- specify how long the command remains active. Check `Permanent` for an indefinite override. * **Reason** -- select a predefined reason from the dropdown * **Specific Reason** -- enter a custom reason for the change The bottom of the panel displays the current priority level and value. Click `Save Changes` to send the command, or `Close` to cancel. Click `Activity Log` in the upper right corner to view the command history. ### Command actions and priority levels Cloud BMS uses a BACnet-inspired priority model for writable points. The same command dialog appears for BACnet and non-BACnet integrations, such as REST API thermostats. How each action maps on the device depends on the connector. BACnet points that accept commands have **16 priority levels** (1 is highest, 16 is lowest). When every level is empty (`null`), the point uses a **fallback / default** value (`Relinquish_Default` in BACnet). That fallback is **not** a 17th BACnet priority. Some interfaces label it as level 17 for display only. `Override` and `Set` turn different knobs under the hood, even when the visible value looks the same. | Action | What it writes\* | Description | | ---------- | -------------------- | ------------------------------------------------------------------------------------------- | | `Override` | Priority 8\* | Temporary exception in the priority array. Takes precedence over lower-priority automation. | | `Set` | Fallback / default\* | Changes the fallback or default value. | | `Auto` | — | Clears an `Override` | | `Release` | — | Clears a `Set` | \*Typical for most BACnet and Niagara deployments. Connectors and site standards can differ. `Override`, `Auto`, and `Set` borrow Niagara-style action names. `Release` is a Cloud BMS action that clears a `Set`. In Niagara-style control, `Set` keeps a non-null fallback so sequences and logic keep a reliable baseline. Use the priority array (including `Override`) for programmed automation and temporary exceptions. To make `Set` write to priority 16 instead of the fallback or default, enable **`Set in Slot16`** (Niagara) on the point. Configure that option from [device details](/products/kode-os/devices/devices#view-and-edit-points), [device templates](/products/kode-os/devices/device-templates), or [points batch update](/products/kode-os/points/points-batch-update). ## Tables on device graphics Add table views to a device graphic to display multiple point values in a structured format. Tables are useful when a device has many points that do not map well to specific positions on a diagram. * Select points from the device (or from related devices) * Tables support two columns: point name and current value * Customize colors, column width, and font sizes * Batch-edit table styling across the graphic ## Use device graphics for troubleshooting Device graphics support troubleshooting by providing a visual context for equipment behavior: * **Ductwork and airflow visualization** -- position supply air, return air, mixed air, and exhaust temperature readings along the airflow path to trace issues through the system * **Valve and damper positions** -- display valve and damper positions alongside their corresponding temperature or pressure readings to identify control loop problems * **Alarm and fault indicators** -- point status icons (alarm, down, fault, stale, overridden) appear next to markers, highlighting which points have active issues * **Setpoint comparison** -- use difference-from-setpoint smart markers to visually identify when a device is not achieving its target ### Common troubleshooting scenarios | Scenario | What to look for on the graphic | | -------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | | Comfort complaint in a zone | Compare zone temperature against the cooling or heating setpoint. Check if the VAV damper is fully open or the valve is at the expected position. | | AHU not maintaining supply temperature | Verify the cooling valve position and chilled water temperatures. Check the mixed air damper and outdoor air readings. | | Equipment cycling | Watch the run status and command points for rapid on/off transitions. Compare against the setpoint and deadband. | | Sensor disagreement | Overlay supply, return, and zone temperatures to identify readings that diverge from expected patterns. | ## Next steps Learn about smart markers, zones, layers, and settings for all graphic types. Create system-level schematics with live data overlays. View devices on spatial floor plan layouts.