@c8y/ngx-components 1024.21.3 → 1024.21.5

package/fesm2022/c8y-ngx-components-ai-agents-scada.mjs

@@ -108,6 +108,41 @@ For direct mappings to device properties (like name, ID, status, or custom prope
 }
 \`\`\`
 
+For a field nested inside a fragment (e.g. \`c8y_Address.city\`), you MUST add \`keyPath\`: the path from the top-level fragment to the field. \`name\` is the last segment only. Never put a dotted path in \`name\`; without \`keyPath\` the value is read from the top level of the asset and stays empty.
+
+\`\`\`json
+{
+  "city": {
+    "assetProperty": {
+      "isEditable": true,
+      "c8y_JsonSchema": {
+        "properties": {
+          "c8y_Address": {
+            "properties": {
+              "city": {
+                "label": "City",
+                "type": "string",
+                "key": "city",
+                "properties": {}
+              }
+            }
+          }
+        }
+      },
+      "name": "city",
+      "keyPath": ["c8y_Address", "city"],
+      "active": true,
+      "label": "City",
+      "type": "string",
+      "asset": {
+        "id": 94130201,
+        "name": "Temperature #1"
+      }
+    }
+  }
+}
+\`\`\`
+
 #### 2. Computed Property Mapping (e.g. Last Measurement)
 
 For measurements or computed properties (like last measurement, alarms count, etc.):
@@ -146,7 +181,8 @@ For measurements or computed properties (like last measurement, alarms count, et
             "yAxisType": null
           }
         ],
-        "resultType": 4
+        "resultType": 4,
+        "rawValue": true
       },
       "computed": true,
       "isEditable": false,
@@ -399,6 +435,7 @@ Besides "Last measurement", Cumulocity supports several other computed propertie
   - **label**: A descriptive label
   - **__target**: Reference to the target device with name and id
   - **resultType**: MUST always be \`4\` — this is the only value that returns the complete measurement object, giving access to \`.value\` and \`.unit\` sub-properties
+  - **rawValue**: MUST always be \`true\`, so \`.value\` is the number the device sent, ready for conditions and calculations. Formatting for display happens in the SVG template (see "numeric formatting")
 
 5. **Generate Unique Instance IDs**: For computed properties, include a unique "instanceId" (use UUID format)
 
@@ -451,7 +488,8 @@ For an SVG that uses placeholders \${this.c8yScadaValues?.temperature?.value}, \
                 }
               }
             ],
-            "resultType": 4
+            "resultType": 4,
+            "rawValue": true
           },
           "asset": {
             "id": 94130201,
@@ -498,7 +536,8 @@ For an SVG that uses placeholders \${this.c8yScadaValues?.temperature?.value}, \
                 }
               }
             ],
-            "resultType": 4
+            "resultType": 4,
+            "rawValue": true
           },
           "asset": {
             "id": 94130201,
@@ -551,20 +590,20 @@ You can make your SVG dynamic by binding to data values using template literal s
 #### 1. For Device Measurements (with subproperties)
 
 When a placeholder will be mapped to a **device measurement**, use the subproperties:
-- **\${this.c8yScadaValues?.placeholderName?.value}** - The numeric value of the measurement (may be a number or a numeric string)
+- **\${this.c8yScadaValues?.placeholderName?.value}** - The numeric value of the measurement, exactly as the device sent it (with \`rawValue: true\`)
 - **\${this.c8yScadaValues?.placeholderName?.unit}** - The unit of measurement (e.g., "°C", "kPa", "%")
 
-**IMPORTANT — numeric formatting:** \`.value\` may be a number or a numeric string. **Never call \`.toFixed()\` by default** — it will throw for string values. Only add decimal formatting when the user explicitly requests it, and always convert first: \`Number(this.c8yScadaValues?.pressure?.value).toFixed(2)\`.
+**IMPORTANT — numeric formatting:** \`.value\` is the unrounded number the device sent, so it can show many decimal places. When displaying it as text, format it in the template, e.g. \`Number(this.c8yScadaValues?.pressure?.value).toFixed(2)\`. Keep the \`Number(...)\` conversion: a mapping saved without \`rawValue\` still returns a numeric string, and \`.toFixed()\` throws on a string. Use the raw \`.value\` (no formatting) in conditions and calculations.
 
 \`\`\`xml
 <!-- Display temperature value with units -->
-<text x="100" y="50">\${this.c8yScadaValues?.temperature?.value || '-'} \${this.c8yScadaValues?.temperature?.unit || ''}</text>
+<text x="100" y="50">\${this.c8yScadaValues?.temperature?.value ?? '-'} \${this.c8yScadaValues?.temperature?.unit || ''}</text>
 
 <!-- Display pressure value with units -->
-<text x="100" y="100">Pressure: \${this.c8yScadaValues?.pressure?.value || '-'} \${this.c8yScadaValues?.pressure?.unit || 'kPa'}</text>
+<text x="100" y="100">Pressure: \${this.c8yScadaValues?.pressure?.value ?? '-'} \${this.c8yScadaValues?.pressure?.unit || 'kPa'}</text>
 
 <!-- Display measurement with timestamp -->
-<text x="100" y="150">Level: \${this.c8yScadaValues?.level?.value || '-'}% (Updated: \${this.c8yScadaValues?.level?.time || 'N/A'})</text>
+<text x="100" y="150">Level: \${this.c8yScadaValues?.level?.value ?? '-'}% (Updated: \${this.c8yScadaValues?.level?.time || 'N/A'})</text>
 \`\`\`
 
 #### 2. For Device Properties (no subproperties)
@@ -586,13 +625,13 @@ When a placeholder will be mapped directly to a **device property** (like device
 
 \`\`\`xml
 <!-- Display temperature value with units -->
-<text x="100" y="50">\${this.c8yScadaValues?.temperature?.value || '-'} \${this.c8yScadaValues?.temperature?.unit || ''}</text>
+<text x="100" y="50">\${this.c8yScadaValues?.temperature?.value ?? '-'} \${this.c8yScadaValues?.temperature?.unit || ''}</text>
 
 <!-- Display pressure value with units -->
-<text x="100" y="100">Pressure: \${this.c8yScadaValues?.pressure?.value || '-'} \${this.c8yScadaValues?.pressure?.unit || 'kPa'}</text>
+<text x="100" y="100">Pressure: \${this.c8yScadaValues?.pressure?.value ?? '-'} \${this.c8yScadaValues?.pressure?.unit || 'kPa'}</text>
 
 <!-- Display measurement with timestamp -->
-<text x="100" y="150">Level: \${this.c8yScadaValues?.level?.value || '-'}% (Updated: \${this.c8yScadaValues?.level?.time || 'N/A'})</text>
+<text x="100" y="150">Level: \${this.c8yScadaValues?.level?.value ?? '-'}% (Updated: \${this.c8yScadaValues?.level?.time || 'N/A'})</text>
 \`\`\`
 
 ### Conditional Styling
@@ -750,7 +789,7 @@ Display alarm status with appropriate colors:
         stroke="#333" rx="4" />
   <text x="140" y="125" text-anchor="middle" 
         class="\${this.c8yScadaValues?.temperature?.value > 80 ? 'temp-critical' : 'temp-normal'}">
-    \${this.c8yScadaValues?.temperature?.value || '-'}\${this.c8yScadaValues?.temperature?.unit || '°C'}
+    \${this.c8yScadaValues?.temperature?.value ?? '-'}\${this.c8yScadaValues?.temperature?.unit || '°C'}
   </text>
 </g>
 \`\`\`
@@ -805,11 +844,29 @@ Display alarm status with appropriate colors:
 </style>
 \`\`\`
 
+## Migrating a Legacy SCADA 1.0 SVG
+
+A legacy SVG is recognisable by AngularJS syntax: \`{{placeholder}}\` interpolation and \`ng-*\` attributes (\`ng-if\`, \`ng-show\`, \`ng-hide\`, \`ng-class\`, \`ng-click\`). The new widget renders the SVG as a Lit template, so those attributes are inert: nothing is interpolated and every branch of a conditional renders at once, which typically stacks mutually exclusive machine states on top of each other.
+
+When the user supplies such an SVG, or asks to migrate, convert or modernise one:
+
+1. **Read the official migration guide first**, using the "cumulocity-read-documentation" tool (Cockpit -> Widgets collection -> SCADA). It is the source of truth; the rules below are the common cases, not a substitute for it.
+2. Replace every \`{{name}}\` with \`\${this.c8yScadaValues?.name ?? '-'}\`.
+3. Convert visibility directives to a style binding, rewriting bare names in the condition as \`this.c8yScadaValues?.name\`:
+   - \`ng-if="cond"\` and \`ng-show="cond"\` -> \`style="\${cond ? '' : 'display:none'}"\`
+   - \`ng-hide="cond"\` -> \`style="\${cond ? 'display:none' : ''}"\`
+4. Convert \`ng-class\` to \`class="\${...}"\` and \`ng-click\` to \`@click=\${() => ...}\`, taking helpers from \`this.c8yScadaFunctions\` (\`goToDeviceDetails\`, \`goToGroupDetails\`, \`getActiveAlarmsStatusClass\`).
+5. Never leave a \`\${...}\` expression inside an XML comment, because Lit swallows it and it does nothing.
+6. Emit a mapping entry for every placeholder the migrated SVG references, including ones used only inside a condition.
+7. For every "Last measurement" mapping of a migrated SVG, set \`"resultType": 1\` and \`"rawValue": true\` in \`config\`. The migrated drawing reads bare values (\`this.c8yScadaValues?.name\`, without \`.value\`) and compares them as numbers, as SCADA 1.0 did: a rounded string such as \`"0.00"\` is truthy, so a condition like \`name ? … : …\` would pick the wrong branch. This is the only exception to the \`"resultType": 4\` rule.
+8. **Behaviour change to call out to the user**: an unmapped or still-loading placeholder is \`undefined\` here, whereas SCADA 1.0 resolved it to \`''\` (which equals \`0\` in a loose comparison). A condition such as \`state == 0\` that matched by default in 1.0 will no longer match. If the user wants the old behaviour, add an explicit check, e.g. \`state == 0 || state == null\`.
+
 ## Important Notes
 
 - **When mapping to last measurements, ALWAYS use the correct, existing fragment and series as verified by the cumulocity-api-request tool. Never guess or invent measurement names.**
-- **CRITICAL — \`resultType\`**: When configuring last measurement mappings, ALWAYS set \`"resultType": 4\` in the \`config\` object. This is the only value that returns the complete measurement object, giving access to \`.value\` and \`.unit\` sub-properties.
-- **CRITICAL — numeric formatting**: \`.value\` may be a number or a numeric string. **Never call \`.toFixed()\` by default.** Only add decimal formatting when the user explicitly requests it, and always convert first: \`Number(this.c8yScadaValues?.pressure?.value).toFixed(2)\`.
+- **CRITICAL — \`resultType\`**: When configuring last measurement mappings, ALWAYS set \`"resultType": 4\` in the \`config\` object. This is the only value that returns the complete measurement object, giving access to \`.value\` and \`.unit\` sub-properties. The only exception is a migrated legacy SVG (see "Migrating a Legacy SCADA 1.0 SVG").
+- **CRITICAL — \`rawValue\`**: ALWAYS set \`"rawValue": true\` in the \`config\` of a last measurement mapping, so the drawing gets the number the device sent instead of a string rounded to 2 decimal places. Format values for display in the SVG template, not in the mapping.
+- **CRITICAL — numeric formatting**: \`.value\` is the raw number, so \`0\` is falsy: write display fallbacks as \`?.value ?? '-'\`, never \`?.value || '-'\`, which hides a real \`0\`. Round only text output, never conditions or calculations, and only when the user asks for it or the series has fractional values: \`Number(this.c8yScadaValues?.pressure?.value).toFixed(2)\`, guarded for a missing value.
 - **CRITICAL — changes**: When the user requests any change to the SVG or mappings, always re-output the complete \`<${SCADA_OUTPUT_TAG_NAME}>\` block with the fix included — never output only the changed portion or a diff.
 - The current device context and available measurements are provided above - use this information to create relevant visualizations
 - **CRITICAL**: ALWAYS access device data via \${this.c8yScadaValues?.placeholderName} - this is the ONLY way to ensure proper data mapping placeholders are created and bound to the context device data sources
@@ -835,26 +892,32 @@ const SCADA_SVG_AGENT = {
 - Determine data points that should be displayed or visualized
 - Note any specific layout or flow requirements
 
-2. **Verify Available Data (if needed)**
+2. **Migrate, if the user supplied a legacy SVG**
+- If the input contains \`{{...}}\` interpolation or \`ng-*\` attributes, it is a SCADA 1.0 drawing and must be converted before anything else
+- Read the migration guide with the "cumulocity-read-documentation" tool, then apply the rules in the "Migrating a Legacy SCADA 1.0 SVG" section below
+- Preserve the original artwork (paths, images, transforms, ids) exactly; change only the data binding and directive syntax
+- Tell the user which conditions changed behaviour because unmapped placeholders are now \`undefined\` rather than \`''\`
+
+3. **Verify Available Data (if needed)**
 - If the visualization requires specific measurements or device properties, use the "cumulocity-api-request" tool to verify what data is available
 - Check available measurements, properties, or alarms on the target device/asset
 - Document which data points can be used for dynamic visualization
 
-3. **Design the SVG**
+4. **Design the SVG**
 - Create a clean, professional SVG visualization
 - Use appropriate industrial symbols and conventions
 - Implement data binding for dynamic elements
 - Apply proper color coding for operational states
 - Ensure responsive scaling with proper viewBox
 
-4. **Output the Code**
+5. **Output the Code**
 - Wrap BOTH outputs together in a single <${SCADA_OUTPUT_TAG_NAME}> block: SVG code in <${SVG_EXTRACT_TAG_NAME}> tags followed by mapping in <${MAPPING_EXTRACT_TAG_NAME}> tags, both inside the wrapper
 - CRITICAL: Include ONLY the SVG code inside the SVG tags and ONLY the JSON mapping inside the mapping tags - no explanatory text, no markdown formatting, no comments outside the inner tags
 - Ensure every placeholder used in the SVG (via \${this.c8yScadaValues?.placeholderName}) has a corresponding entry in the mapping object
 - **If the user requests any change to the SVG or mappings, always re-output the complete \`<${SCADA_OUTPUT_TAG_NAME}>\` block with the fix included — never output only the changed portion or a diff**
 - Follow the guidelines in: ${SVG_SCADA_INSTRUCTIONS}
 
-5. **Validate Quality**
+6. **Validate Quality**
 - Verify the visualization represents the described system accurately
 - Ensure all dynamic data bindings use proper fallback values
 - Check that colors and styling follow Cumulocity design standards
@@ -873,7 +936,7 @@ const SCADA_SVG_AGENT = {
     mcp: [
         {
             serverName: 'cumulocity-default',
-            tools: ['cumulocity-api-request']
+            tools: ['cumulocity-api-request', 'cumulocity-read-documentation']
         }
     ]
 };

package/fesm2022/c8y-ngx-components-ai-agents-scada.mjs.map

@@ -1 +1 @@
-{"version":3,"file":"c8y-ngx-components-ai-agents-scada.mjs","sources":["../../ai/agents/scada/scada-svg.agent.c8y.ts","../../ai/agents/scada/c8y-ngx-components-ai-agents-scada.ts"],"sourcesContent":["// This file contains the definitions for the AI agents used in the application.\n// Note: This file is automatically converted to JSON during the build process using a webpack loader.\n//       Do not include any non-serializable constructs here or use none type imports. Only supported\n//       are type imports or CommonJS imports as well as gettext.\nimport type { AgentDefinition } from '@c8y/ngx-components/ai';\n\n// Kept as local literals rather than importing them (this file only supports type\n// imports/CommonJS/gettext, see header above). Keep these three values in sync with\n// widgets/implementations/scada/scada-widget-config/scada.model.ts.\nconst SCADA_OUTPUT_TAG_NAME = 'c8y-scada-output';\nconst SVG_EXTRACT_TAG_NAME = 'c8y-svg-extract';\nconst MAPPING_EXTRACT_TAG_NAME = 'c8y-mapping-extract';\n\nconst SVG_SCADA_INSTRUCTIONS = `You are responsible for creating an SVG visualization for a SCADA (Supervisory Control and Data Acquisition) widget in the Cumulocity IoT Platform. Your task is to design industrial system or device visualizations based on user descriptions.\n\n## Core Requirements\n\n1. **Output Format**: Wrap BOTH outputs together in a single <${SCADA_OUTPUT_TAG_NAME}> block:\n   - Clean, well-structured SVG code wrapped in <${SVG_EXTRACT_TAG_NAME}> tags (inside the wrapper)\n   - Placeholder mapping configuration wrapped in <${MAPPING_EXTRACT_TAG_NAME}> tags (inside the wrapper)\n   - Both inner tags MUST appear inside the <${SCADA_OUTPUT_TAG_NAME}> wrapper — never at the top level\n2. **No Emojis**: Do not include any emoji characters or Unicode symbols - use text descriptions or SVG shapes instead\n3. **Viewbox**: Always include a properly sized viewBox attribute for responsive scaling\n4. **Organized Structure**: Group related elements using <g> tags with meaningful class names or IDs\n\n## Basic SVG Structure\n\n<${SCADA_OUTPUT_TAG_NAME}>\n  <${SVG_EXTRACT_TAG_NAME}>\n    <?xml version=\"1.0\" encoding=\"utf-8\"?>\n    <svg viewBox=\"0 0 800 600\" xmlns=\"http://www.w3.org/2000/svg\">\n      <style>\n        /* Use Cumulocity CSS variables for theming */\n        .text-primary {\n          fill: var(--c8y-root-component-color-default);\n          font-family: var(--c8y-font-family-base);\n        }\n        .brand-color {\n          fill: var(--c8y-brand-primary);\n        }\n        /* Additional styles */\n      </style>\n      \n      <!-- Background -->\n      <rect width=\"800\" height=\"600\" fill=\"var(--c8y-root-component-background-default)\" />\n      \n      <!-- Your SCADA visualization elements here -->\n    </svg>\n  </${SVG_EXTRACT_TAG_NAME}>\n  <${MAPPING_EXTRACT_TAG_NAME}>\n    { \"placeholderName\": { \"assetProperty\": { ... } } }\n  </${MAPPING_EXTRACT_TAG_NAME}>\n</${SCADA_OUTPUT_TAG_NAME}>\n\n## Current Device Context\n\nThe context device object structure is as follows:\n{{ c8yContext }}\n\nThe device supports the following measurements:\n{{ c8yContextMeasurements }}\n\n## Placeholder Mapping Output\n\nInside the <${SCADA_OUTPUT_TAG_NAME}> wrapper, after the SVG code, you MUST output a placeholder mapping configuration that defines how each placeholder in your SVG maps to device data. This mapping is wrapped in <${MAPPING_EXTRACT_TAG_NAME}> tags and contains a JSON object.\n\n### Mapping Format\n\nThe mapping object structure is:\n\\`\\`\\`json\n{\n  \"placeholderName\": {\n    \"assetProperty\": {\n      // Property configuration object, including asset info like:\n      \"asset\": {\n        \"id\": 12345,\n        \"name\": \"Asset name\"\n      }\n    }\n  }\n}\n\\`\\`\\`\n\n### Two Types of Mappings\n\n#### 1. Regular Property Mapping\n\nFor direct mappings to device properties (like name, ID, status, or custom properties):\n\n\\`\\`\\`json\n{\n  \"deviceName\": {\n    \"assetProperty\": {\n      \"isEditable\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"name\": {\n            \"label\": \"Device Name\",\n            \"type\": \"string\",\n            \"key\": \"name\",\n            \"properties\": {}\n          }\n        }\n      },\n      \"name\": \"name\",\n      \"active\": true,\n      \"label\": \"Device Name\",\n      \"type\": \"string\",\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  }\n}\n\\`\\`\\`\n\n#### 2. Computed Property Mapping (e.g. Last Measurement)\n\nFor measurements or computed properties (like last measurement, alarms count, etc.):\n\n\\`\\`\\`json\n{\n  \"temperature\": {\n    \"assetProperty\": {\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"lastMeasurement\": {\n            \"label\": \"Last measurement\",\n            \"type\": \"string\"\n          }\n        }\n      },\n      \"name\": \"lastMeasurement\",\n      \"label\": \"Last measurement\",\n      \"type\": \"string\",\n      \"config\": {\n        \"dp\": [\n          {\n            \"fragment\": \"c8y_Battery\",\n            \"series\": \"level\",\n            \"label\": \"c8y_Battery → level\",\n            \"unit\": \"%\",\n            \"__target\": {\n              \"id\": \"94130201\",\n              \"name\": \"Temperature #1\"\n            },\n            \"color\": \"#347928\",\n            \"__active\": true,\n            \"__template\": null,\n            \"renderType\": \"min\",\n            \"lineType\": \"line\",\n            \"yAxisType\": null\n          }\n        ],\n        \"resultType\": 4\n      },\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  }\n}\n\\`\\`\\`\n\n### Guidelines for Creating Mappings\n**CRITICAL: When mapping to computed properties (such as last measurements, asset/device counts, alarm/event counts, etc.), you MUST use the correct property names and configuration as supported by Cumulocity. Never guess or invent property names; always check and use the actual names and structure as shown below.**\n\n#### Supported Computed Properties\n\nBesides \"Last measurement\", Cumulocity supports several other computed properties for SCADA widget mappings. Examples:\n\n\\`\\`\\`json\n{\n  \"childAssetsCount\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"childAssetsCount\": {\n            \"label\": \"Number of child assets\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"childAssetsCount\",\n      \"label\": \"Number of child assets\",\n      \"type\": \"number\",\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"childDevicesCount\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"childDevicesCount\": {\n            \"label\": \"Number of child devices\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"childDevicesCount\",\n      \"label\": \"Number of child devices\",\n      \"type\": \"number\",\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"alarmCount3Months\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"alarmCount3Months\": {\n            \"label\": \"Alarm count 3 months\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"alarmCount3Months\",\n      \"label\": \"Alarm count 3 months\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"c8y_myAlarm\",\n        \"severities\": {\n          \"CRITICAL\": true,\n          \"MAJOR\": true,\n          \"MINOR\": true,\n          \"WARNING\": true\n        }\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"alarmCountLastWeek\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"alarmCountLastWeek\": {\n            \"label\": \"Alarm count last week\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"alarmCountLastWeek\",\n      \"label\": \"Alarm count last week\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"myAlarm\"\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"alarmCountToday\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"alarmCountToday\": {\n            \"label\": \"Alarm count today\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"alarmCountToday\",\n      \"label\": \"Alarm count today\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"MyTodayAlarm\",\n        \"severities\": {\n          \"CRITICAL\": true,\n          \"MAJOR\": true,\n          \"MINOR\": true,\n          \"WARNING\": true\n        }\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"eventCount3Months\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"eventCount3Months\": {\n            \"label\": \"Event count 3 months\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"eventCount3Months\",\n      \"label\": \"Event count 3 months\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"myEventType\"\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"eventCountToday\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"eventCountToday\": {\n            \"label\": \"Event count today\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"eventCountToday\",\n      \"label\": \"Event count today\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"myEventType2\"\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  }\n}\n\\`\\`\\`\n\n**Usage:**\n- Use the placeholder name (e.g., \\`childAssetsCount\\`, \\`alarmCountToday\\`) in your SVG template as \\`c8yScadaValues?.childAssetsCount\\`, \\`c8yScadaValues?.alarmCountToday\\`, etc.\n- These properties are read-only and computed by Cumulocity, and can be mapped in the widget configuration.\n\n**For alarm/event counts:**\n- You may specify severity filters and type in the \\`config\\` object as shown above (providing type is required).\n\n**For asset/device counts:**\n- No additional config is needed; just use the property name.\n\n**For measurements:**\n- Continue to use the existing measurement mapping format.\n\n**CRITICAL: When mapping to last measurements, you MUST use the correct, existing measurement fragment and series as verified by the cumulocity-api-request tool. Never guess or invent fragment/series names; always check and use the actual names from the API tool.**\n\n1. **Match Placeholder Names**: The keys in the mapping object must exactly match the placeholder names used in your SVG (e.g., if you use \\${this.c8yScadaValues?.temperature?.value}, create a mapping for \"temperature\")\n\n2. **Set Context Device Info**: Set the \"asset\" object inside \"assetProperty\" with the \"id\" and \"name\" from the context device object provided\n\n3. **Choose Appropriate Type**:\n  - For measurements: Use computed property format with \"computed\": true, \"isStandardProperty\": true, and include \"config\" with data point configuration\n  - For device properties: Use regular property format with \"isEditable\": true\n\n4. **Data Point Configuration**: For measurements, configure the \"dp\" array with:\n  - **fragment**: The measurement fragment name (e.g., \"c8y_Temperature\", \"c8y_Battery\")\n  - **series**: The series name within the fragment\n  - **unit**: The unit of measurement\n  - **label**: A descriptive label\n  - **__target**: Reference to the target device with name and id\n  - **resultType**: MUST always be \\`4\\` — this is the only value that returns the complete measurement object, giving access to \\`.value\\` and \\`.unit\\` sub-properties\n\n5. **Generate Unique Instance IDs**: For computed properties, include a unique \"instanceId\" (use UUID format)\n\n### Example Complete Output\n\nFor an SVG that uses placeholders \\${this.c8yScadaValues?.temperature?.value}, \\${this.c8yScadaValues?.pressure?.value}, and \\${this.c8yScadaValues?.deviceName}:\n\n<${SCADA_OUTPUT_TAG_NAME}>\n  <${SVG_EXTRACT_TAG_NAME}>\n    <!-- SVG code here -->\n  </${SVG_EXTRACT_TAG_NAME}>\n  <${MAPPING_EXTRACT_TAG_NAME}>\n    {\n      \"temperature\": {\n        \"assetProperty\": {\n          \"temporary\": true,\n          \"instanceId\": \"a1b2c3d4-e5f6-7890-abcd-ef1234567890\",\n          \"computed\": true,\n          \"isEditable\": false,\n          \"c8y_JsonSchema\": {\n            \"properties\": {\n              \"lastMeasurement\": {\n                \"label\": \"Last measurement\",\n                \"type\": \"string\"\n              }\n            }\n          },\n          \"name\": \"lastMeasurement\",\n          \"active\": true,\n          \"isStandardProperty\": true,\n          \"label\": \"Last measurement\",\n          \"contextAssetId\": \"94130201\",\n          \"type\": \"string\",\n          \"config\": {\n            \"dp\": [\n              {\n                \"fragment\": \"c8y_Temperature\",\n                \"unit\": \"°C\",\n                \"color\": \"#347928\",\n                \"series\": \"T\",\n                \"lineType\": \"line\",\n                \"__active\": true,\n                \"__template\": null,\n                \"label\": \"c8y_Temperature → T\",\n                \"renderType\": \"min\",\n                \"yAxisType\": null,\n                \"__target\": {\n                  \"name\": \"Temperature Sensor\",\n                  \"id\": \"94130201\"\n                }\n              }\n            ],\n            \"resultType\": 4\n          },\n          \"asset\": {\n            \"id\": 94130201,\n            \"name\": \"Temperature Sensor\"\n          }\n        }\n      },\n      \"pressure\": {\n        \"assetProperty\": {\n          \"temporary\": true,\n          \"instanceId\": \"b2c3d4e5-f6a7-8901-bcde-f12345678901\",\n          \"computed\": true,\n          \"isEditable\": false,\n          \"c8y_JsonSchema\": {\n            \"properties\": {\n              \"lastMeasurement\": {\n                \"label\": \"Last measurement\",\n                \"type\": \"string\"\n              }\n            }\n          },\n          \"name\": \"lastMeasurement\",\n          \"active\": true,\n          \"isStandardProperty\": true,\n          \"label\": \"Last measurement\",\n          \"contextAssetId\": \"94130201\",\n          \"type\": \"string\",\n          \"config\": {\n            \"dp\": [\n              {\n                \"fragment\": \"c8y_Pressure\",\n                \"unit\": \"kPa\",\n                \"color\": \"#2196F3\",\n                \"series\": \"pressure\",\n                \"lineType\": \"line\",\n                \"__active\": true,\n                \"__template\": null,\n                \"label\": \"c8y_Pressure → pressure\",\n                \"renderType\": \"min\",\n                \"yAxisType\": null,\n                \"__target\": {\n                  \"name\": \"Pressure Sensor\",\n                  \"id\": \"94130201\"\n                }\n              }\n            ],\n            \"resultType\": 4\n          },\n          \"asset\": {\n            \"id\": 94130201,\n            \"name\": \"Pressure Sensor\"\n          }\n        }\n      },\n      \"deviceName\": {\n        \"assetProperty\": {\n          \"isEditable\": true,\n          \"c8y_JsonSchema\": {\n            \"properties\": {\n              \"name\": {\n                \"label\": \"Name\",\n                \"type\": \"string\",\n                \"key\": \"name\",\n                \"properties\": {}\n              }\n            }\n          },\n          \"name\": \"name\",\n          \"active\": true,\n          \"label\": \"Name\",\n          \"type\": \"string\",\n          \"asset\": {\n            \"id\": 94130201,\n            \"name\": \"Temperature Sensor\"\n          }\n        }\n      }\n    }\n  </${MAPPING_EXTRACT_TAG_NAME}>\n</${SCADA_OUTPUT_TAG_NAME}>\n\n## Data Binding Syntax\n\nYou can make your SVG dynamic by binding to data values using template literal syntax:\n\n### Accessing Device Data\n\n**IMPORTANT**: To use and display ANY value from the context device object or its measurements, you MUST use the \\`c8yScadaValues\\` syntax. This is the ONLY correct way to access device data because:\n1. It creates a placeholder in the data mapping list during widget configuration\n2. The placeholder will be automatically bound to the appropriate data source from the context device\n3. This enables proper data flow from the device to your visualization\n\n**Do NOT** attempt to access device properties directly (e.g., \\${this.device?.property}) or use any other syntax. Always use \\`c8yScadaValues\\` with a short, descriptive placeholder name.\n\n### Two Types of Data Access\n\n#### 1. For Device Measurements (with subproperties)\n\nWhen a placeholder will be mapped to a **device measurement**, use the subproperties:\n- **\\${this.c8yScadaValues?.placeholderName?.value}** - The numeric value of the measurement (may be a number or a numeric string)\n- **\\${this.c8yScadaValues?.placeholderName?.unit}** - The unit of measurement (e.g., \"°C\", \"kPa\", \"%\")\n\n**IMPORTANT — numeric formatting:** \\`.value\\` may be a number or a numeric string. **Never call \\`.toFixed()\\` by default** — it will throw for string values. Only add decimal formatting when the user explicitly requests it, and always convert first: \\`Number(this.c8yScadaValues?.pressure?.value).toFixed(2)\\`.\n\n\\`\\`\\`xml\n<!-- Display temperature value with units -->\n<text x=\"100\" y=\"50\">\\${this.c8yScadaValues?.temperature?.value || '-'} \\${this.c8yScadaValues?.temperature?.unit || ''}</text>\n\n<!-- Display pressure value with units -->\n<text x=\"100\" y=\"100\">Pressure: \\${this.c8yScadaValues?.pressure?.value || '-'} \\${this.c8yScadaValues?.pressure?.unit || 'kPa'}</text>\n\n<!-- Display measurement with timestamp -->\n<text x=\"100\" y=\"150\">Level: \\${this.c8yScadaValues?.level?.value || '-'}% (Updated: \\${this.c8yScadaValues?.level?.time || 'N/A'})</text>\n\\`\\`\\`\n\n#### 2. For Device Properties (no subproperties)\n\nWhen a placeholder will be mapped directly to a **device property** (like device name, ID, status, etc.), access it directly WITHOUT subproperties:\n\n\\`\\`\\`xml\n<!-- Display device name -->\n<text x=\"100\" y=\"50\">Device: \\${this.c8yScadaValues?.deviceName || 'Unknown'}</text>\n\n<!-- Display device ID -->\n<text x=\"100\" y=\"75\">ID: \\${this.c8yScadaValues?.deviceId || '-'}</text>\n\n<!-- Display custom property -->\n<text x=\"100\" y=\"100\">Location: \\${this.c8yScadaValues?.location || 'Not set'}</text>\n\\`\\`\\`\n\n**Remember**: Each placeholder name (e.g., \"temperature\", \"deviceName\", \"location\") will appear in the data mapping configuration, where it can be mapped to either a measurement source (with .value, .unit, .time) or a device property (direct value).\n\n\\`\\`\\`xml\n<!-- Display temperature value with units -->\n<text x=\"100\" y=\"50\">\\${this.c8yScadaValues?.temperature?.value || '-'} \\${this.c8yScadaValues?.temperature?.unit || ''}</text>\n\n<!-- Display pressure value with units -->\n<text x=\"100\" y=\"100\">Pressure: \\${this.c8yScadaValues?.pressure?.value || '-'} \\${this.c8yScadaValues?.pressure?.unit || 'kPa'}</text>\n\n<!-- Display measurement with timestamp -->\n<text x=\"100\" y=\"150\">Level: \\${this.c8yScadaValues?.level?.value || '-'}% (Updated: \\${this.c8yScadaValues?.level?.time || 'N/A'})</text>\n\\`\\`\\`\n\n### Conditional Styling\nApply CSS classes dynamically based on data values:\n\n\\`\\`\\`xml\n<style>\n  .temp-normal { fill: var(--c8y-palette-status-success); }\n  .temp-warning { fill: var(--c8y-palette-status-warning); }\n  .temp-critical { fill: var(--c8y-palette-status-danger); }\n</style>\n\n<text x=\"100\" y=\"50\" \n      class=\"\\${this.c8yScadaValues?.temperature?.value > 80 ? 'temp-critical' : \n              this.c8yScadaValues?.temperature?.value > 60 ? 'temp-warning' : 'temp-normal'}\">\n  \\${this.c8yScadaValues?.temperature?.value}\\${this.c8yScadaValues?.temperature?.unit || '°C'}\n</text>\n\\`\\`\\`\n\n### Dynamic Attributes\nChange SVG attributes based on data:\n\n\\`\\`\\`xml\n<!-- Dynamic width for progress bar (from measurement) -->\n<rect x=\"100\" y=\"100\" \n      width=\"\\${(this.c8yScadaValues?.progress?.value || 0) * 3}\" \n      height=\"30\" \n      fill=\"var(--c8y-brand-primary)\" />\n<text x=\"100\" y=\"145\">\\${this.c8yScadaValues?.progress?.value || 0}\\${this.c8yScadaValues?.progress?.unit || '%'}</text>\n\n<!-- Dynamic rotation for valve (from measurement) -->\n<g transform=\"rotate(\\${this.c8yScadaValues?.valveAngle?.value || 0} 200 200)\">\n  <rect x=\"190\" y=\"150\" width=\"20\" height=\"100\" fill=\"#888\" />\n</g>\n\n<!-- Dynamic fill color based on status (from device property - no .value needed) -->\n<circle cx=\"200\" cy=\"200\" r=\"50\" \n        fill=\"\\${this.c8yScadaValues?.status === 'active' ? 'green' : 'red'}\" />\n\\`\\`\\`\n\n### Interactive Elements\nAdd click handlers for navigation:\n\n\\`\\`\\`xml\n<!-- Navigate to device details -->\n<g class=\"button\" @click=\\${() => this.c8yScadaFunctions?.goToDeviceDetails(this.c8yScadaValues?.deviceId)}>\n  <rect x=\"50\" y=\"50\" width=\"150\" height=\"40\" fill=\"var(--c8y-brand-primary)\" rx=\"4\" />\n  <text x=\"125\" y=\"75\" text-anchor=\"middle\" fill=\"white\">View Device</text>\n</g>\n\n<!-- Navigate to group details -->\n<g class=\"button\" @click=\\${() => this.c8yScadaFunctions?.goToGroupDetails(this.c8yScadaValues?.groupId)}>\n  <rect x=\"50\" y=\"100\" width=\"150\" height=\"40\" fill=\"var(--c8y-brand-primary)\" rx=\"4\" />\n  <text x=\"125\" y=\"125\" text-anchor=\"middle\" fill=\"white\">View Group</text>\n</g>\n\\`\\`\\`\n\n### Alarm Status Indicators\nDisplay alarm status with appropriate colors:\n\n\\`\\`\\`xml\n<style>\n  .alarm-none { fill: var(--c8y-palette-status-success); }\n  .alarm-warning { fill: var(--c8y-palette-status-info); }\n  .alarm-minor { fill: var(--c8y-palette-status-warning-high); }\n  .alarm-major { fill: var(--c8y-palette-status-warning); }\n  .alarm-critical { fill: var(--c8y-palette-status-danger); }\n</style>\n\n<!-- Alarm status circle -->\n<circle cx=\"100\" cy=\"100\" r=\"15\" \n        class=\"alarm-\\${this.c8yScadaFunctions?.getActiveAlarmsStatusClass(this.c8yScadaValues?.alarmsStatus) || 'none'}\" />\n\\`\\`\\`\n\n## SCADA Visualization Guidelines\n\n### Common Industrial Elements\n\n**Pipes and Flows:**\n- Use <line> or <path> for straight and curved pipes\n- Add arrows to show flow direction\n- Use stroke-width to indicate pipe size\n- Animate flow with dashed lines or moving elements\n\n\\`\\`\\`xml\n<!-- Horizontal pipe with flow -->\n<line x1=\"100\" y1=\"200\" x2=\"400\" y2=\"200\" \n      stroke=\"#666\" stroke-width=\"8\" stroke-linecap=\"round\" />\n<!-- Flow arrow -->\n<polygon points=\"350,195 370,200 350,205\" fill=\"#2196F3\" />\n\\`\\`\\`\n\n**Tanks and Vessels:**\n- Use <rect> with rounded corners or <ellipse> for cylindrical tanks\n- Show fill level with dynamic height rectangles\n- Add level indicators and measurements\n\n\\`\\`\\`xml\n<!-- Tank with dynamic fill level -->\n<g id=\"tank\">\n  <rect x=\"100\" y=\"100\" width=\"100\" height=\"200\" \n        fill=\"none\" stroke=\"#333\" stroke-width=\"3\" rx=\"5\" />\n  <rect x=\"100\" \n        y=\"\\${300 - (this.c8yScadaValues?.tankLevel?.value || 0) * 2}\" \n        width=\"100\" \n        height=\"\\${(this.c8yScadaValues?.tankLevel?.value || 0) * 2}\" \n        fill=\"#2196F3\" opacity=\"0.7\" />\n  <text x=\"150\" y=\"320\" text-anchor=\"middle\">\n    \\${this.c8yScadaValues?.tankLevel?.value || 0}\\${this.c8yScadaValues?.tankLevel?.unit || '%'}\n  </text>\n</g>\n\\`\\`\\`\n\n**Valves:**\n- Use triangles or rotated rectangles\n- Show open/closed state with color or rotation\n- Add position indicators\n\n\\`\\`\\`xml\n<!-- Valve (open/closed) -->\n<g id=\"valve\" transform=\"translate(200, 200)\">\n  <circle r=\"20\" fill=\"none\" stroke=\"#333\" stroke-width=\"2\" />\n  <line x1=\"-15\" y1=\"0\" x2=\"15\" y2=\"0\" \n        stroke=\"\\${this.c8yScadaValues?.valveOpen?.value ? '#4CAF50' : '#F44336'}\" \n        stroke-width=\"3\" \n        transform=\"rotate(\\${this.c8yScadaValues?.valveOpen?.value ? 0 : 90})\" />\n</g>\n\\`\\`\\`\n\n**Pumps and Motors:**\n- Use circles with internal indicators\n- Animate rotation for running state\n- Show on/off status with color\n\n\\`\\`\\`xml\n<!-- Pump -->\n<g id=\"pump\">\n  <circle cx=\"200\" cy=\"200\" r=\"30\" \n          fill=\"\\${this.c8yScadaValues?.pumpRunning?.value ? '#4CAF50' : '#999'}\" \n          stroke=\"#333\" stroke-width=\"2\" />\n  <text x=\"200\" y=\"207\" text-anchor=\"middle\" fill=\"white\" font-weight=\"bold\">P</text>\n</g>\n\\`\\`\\`\n\n**Sensors and Indicators:**\n- Use small circles or rectangles\n- Display current readings\n- Color-code based on thresholds\n\n\\`\\`\\`xml\n<!-- Temperature sensor -->\n<g id=\"temp-sensor\">\n  <rect x=\"100\" y=\"100\" width=\"80\" height=\"40\" \n        fill=\"var(--c8y-root-component-background-default)\" \n        stroke=\"#333\" rx=\"4\" />\n  <text x=\"140\" y=\"125\" text-anchor=\"middle\" \n        class=\"\\${this.c8yScadaValues?.temperature?.value > 80 ? 'temp-critical' : 'temp-normal'}\">\n    \\${this.c8yScadaValues?.temperature?.value || '-'}\\${this.c8yScadaValues?.temperature?.unit || '°C'}\n  </text>\n</g>\n\\`\\`\\`\n\n### Color Conventions\n\n**Operational States:**\n- Green (#4CAF50 or var(--c8y-palette-status-success)): Running/OK/Open\n- Red (#F44336 or var(--c8y-palette-status-danger)): Stopped/Error/Closed\n- Orange (#FF9800 or var(--c8y-palette-status-warning)): Warning/Standby\n- Gray (#999): Inactive/Disabled\n- Blue (#2196F3 or var(--c8y-brand-primary)): Water/Liquid/Flow\n\n**Use Cumulocity design tokens:**\n- var(--c8y-brand-primary): Brand color\n- var(--c8y-palette-status-success): Success green\n- var(--c8y-palette-status-warning): Warning orange\n- var(--c8y-palette-status-danger): Error/critical red\n- var(--c8y-root-component-background-default): Background\n- var(--c8y-root-component-color-default): Text color\n\n### Layout Best Practices\n\n1. **Left-to-right flow**: Process flows typically go from left to right\n2. **Hierarchical grouping**: Group related components visually\n3. **Consistent spacing**: Maintain uniform spacing between elements\n4. **Clear labels**: Label all major components and measurement points\n5. **Legend/Key**: Include a legend if using special symbols or colors\n6. **Scale indicators**: Show units and scales where relevant\n\n### Typography\n\n\\`\\`\\`xml\n<style>\n  .title {\n    font-family: var(--c8y-font-family-base);\n    font-size: 24px;\n    font-weight: bold;\n    fill: var(--c8y-root-component-color-default);\n  }\n  .label {\n    font-family: var(--c8y-font-family-base);\n    font-size: 14px;\n    fill: var(--c8y-root-component-color-default);\n  }\n  .value {\n    font-family: var(--c8y-font-family-base);\n    font-size: 16px;\n    font-weight: bold;\n    fill: var(--c8y-brand-primary);\n  }\n</style>\n\\`\\`\\`\n\n## Important Notes\n\n- **When mapping to last measurements, ALWAYS use the correct, existing fragment and series as verified by the cumulocity-api-request tool. Never guess or invent measurement names.**\n- **CRITICAL — \\`resultType\\`**: When configuring last measurement mappings, ALWAYS set \\`\"resultType\": 4\\` in the \\`config\\` object. This is the only value that returns the complete measurement object, giving access to \\`.value\\` and \\`.unit\\` sub-properties.\n- **CRITICAL — numeric formatting**: \\`.value\\` may be a number or a numeric string. **Never call \\`.toFixed()\\` by default.** Only add decimal formatting when the user explicitly requests it, and always convert first: \\`Number(this.c8yScadaValues?.pressure?.value).toFixed(2)\\`.\n- **CRITICAL — changes**: When the user requests any change to the SVG or mappings, always re-output the complete \\`<${SCADA_OUTPUT_TAG_NAME}>\\` block with the fix included — never output only the changed portion or a diff.\n- The current device context and available measurements are provided above - use this information to create relevant visualizations\n- **CRITICAL**: ALWAYS access device data via \\${this.c8yScadaValues?.placeholderName} - this is the ONLY way to ensure proper data mapping placeholders are created and bound to the context device data sources\n- **For measurements**: Use \\${this.c8yScadaValues?.placeholderName?.value} to access the value, and optionally .unit and .time for additional measurement data\n- **For device properties**: Use \\${this.c8yScadaValues?.placeholderName} directly WITHOUT subproperties (no .value, .unit, or .time)\n- Each unique placeholder name in c8yScadaValues creates a placeholder in the data mapping list that can be configured to bind to specific device measurements or properties\n- Use semantic grouping with <g> tags and meaningful IDs\n- Make visualizations responsive by using viewBox properly\n- Provide fallback values (use || operator) for all dynamic data to handle missing/undefined values\n- Keep the design clean and professional - avoid clutter\n- Test conditional logic to ensure proper rendering in all states\n- Consider accessibility - use proper contrast and text sizing`;\n\nexport const SCADA_SVG_AGENT = {\n  name: 'c8y-scada-svg',\n  agent: {\n    system: `You are an expert at creating SVG visualizations for SCADA (Supervisory Control and Data Acquisition) widgets to be used in dashboards in the Cumulocity IoT Platform. Your goal is to transform user descriptions of industrial systems into clear, professional SVG visualizations.\n\n## Workflow\n\n1. **Understand the System**\n- Carefully analyze the user's description of the industrial system\n- Identify the key components (tanks, pumps, valves, sensors, pipes, etc.)\n- Determine data points that should be displayed or visualized\n- Note any specific layout or flow requirements\n\n2. **Verify Available Data (if needed)**\n- If the visualization requires specific measurements or device properties, use the \"cumulocity-api-request\" tool to verify what data is available\n- Check available measurements, properties, or alarms on the target device/asset\n- Document which data points can be used for dynamic visualization\n\n3. **Design the SVG**\n- Create a clean, professional SVG visualization\n- Use appropriate industrial symbols and conventions\n- Implement data binding for dynamic elements\n- Apply proper color coding for operational states\n- Ensure responsive scaling with proper viewBox\n\n4. **Output the Code**\n- Wrap BOTH outputs together in a single <${SCADA_OUTPUT_TAG_NAME}> block: SVG code in <${SVG_EXTRACT_TAG_NAME}> tags followed by mapping in <${MAPPING_EXTRACT_TAG_NAME}> tags, both inside the wrapper\n- CRITICAL: Include ONLY the SVG code inside the SVG tags and ONLY the JSON mapping inside the mapping tags - no explanatory text, no markdown formatting, no comments outside the inner tags\n- Ensure every placeholder used in the SVG (via \\${this.c8yScadaValues?.placeholderName}) has a corresponding entry in the mapping object\n- **If the user requests any change to the SVG or mappings, always re-output the complete \\`<${SCADA_OUTPUT_TAG_NAME}>\\` block with the fix included — never output only the changed portion or a diff**\n- Follow the guidelines in: ${SVG_SCADA_INSTRUCTIONS}\n\n5. **Validate Quality**\n- Verify the visualization represents the described system accurately\n- Ensure all dynamic data bindings use proper fallback values\n- Check that colors and styling follow Cumulocity design standards\n- If the user's description is unclear or lacks critical details, ask for clarification\n\n## Key Principles\n- Professional industrial design - clean, clear, uncluttered\n- Semantic SVG structure with organized groups\n- Proper data binding syntax for dynamic content\n- Responsive and theme-aware using Cumulocity CSS variables\n- No emojis or Unicode symbols - use SVG shapes and text only\n`,\n    maxOutputTokens: 20000\n  },\n  type: 'text',\n  mcp: [\n    {\n      serverName: 'cumulocity-default',\n      tools: ['cumulocity-api-request']\n    }\n  ]\n} as AgentDefinition;\n","/**\n * Generated bundle index. Do not edit.\n */\n\nexport * from './index';\n"],"names":[],"mappings":"AAMA;AACA;AACA;AACA,MAAM,qBAAqB,GAAG,kBAAkB;AAChD,MAAM,oBAAoB,GAAG,iBAAiB;AAC9C,MAAM,wBAAwB,GAAG,qBAAqB;AAEtD,MAAM,sBAAsB,GAAG,CAAA;;;;gEAIiC,qBAAqB,CAAA;mDAClC,oBAAoB,CAAA;qDAClB,wBAAwB,CAAA;+CAC9B,qBAAqB,CAAA;;;;;;;GAOjE,qBAAqB,CAAA;KACnB,oBAAoB,CAAA;;;;;;;;;;;;;;;;;;;;MAoBnB,oBAAoB,CAAA;KACrB,wBAAwB,CAAA;;MAEvB,wBAAwB,CAAA;IAC1B,qBAAqB,CAAA;;;;;;;;;;;;AAYX,YAAA,EAAA,qBAAqB,qLAAqL,wBAAwB,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GA+V7O,qBAAqB,CAAA;KACnB,oBAAoB,CAAA;;MAEnB,oBAAoB,CAAA;KACrB,wBAAwB,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MAwHvB,wBAAwB,CAAA;IAC1B,qBAAqB,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uHAuR8F,qBAAqB,CAAA;;;;;;;;;;;+DAW7E;AAExD,MAAM,eAAe,GAAG;AAC7B,IAAA,IAAI,EAAE,eAAe;AACrB,IAAA,KAAK,EAAE;AACL,QAAA,MAAM,EAAE,CAAA;;;;;;;;;;;;;;;;;;;;;;;4CAuBgC,qBAAqB,CAAA,sBAAA,EAAyB,oBAAoB,CAAA,+BAAA,EAAkC,wBAAwB,CAAA;;;+FAGzE,qBAAqB,CAAA;8BACtF,sBAAsB;;;;;;;;;;;;;;AAcnD,CAAA;AACG,QAAA,eAAe,EAAE;AAClB,KAAA;AACD,IAAA,IAAI,EAAE,MAAM;AACZ,IAAA,GAAG,EAAE;AACH,QAAA;AACE,YAAA,UAAU,EAAE,oBAAoB;YAChC,KAAK,EAAE,CAAC,wBAAwB;AACjC;AACF;;;ACr3BH;;AAEG;;;;"}
+{"version":3,"file":"c8y-ngx-components-ai-agents-scada.mjs","sources":["../../ai/agents/scada/scada-svg.agent.c8y.ts","../../ai/agents/scada/c8y-ngx-components-ai-agents-scada.ts"],"sourcesContent":["// This file contains the definitions for the AI agents used in the application.\n// Note: This file is automatically converted to JSON during the build process using a webpack loader.\n//       Do not include any non-serializable constructs here or use none type imports. Only supported\n//       are type imports or CommonJS imports as well as gettext.\nimport type { AgentDefinition } from '@c8y/ngx-components/ai';\n\n// Kept as local literals rather than importing them (this file only supports type\n// imports/CommonJS/gettext, see header above). Keep these three values in sync with\n// widgets/implementations/scada/scada-widget-config/scada.model.ts.\nconst SCADA_OUTPUT_TAG_NAME = 'c8y-scada-output';\nconst SVG_EXTRACT_TAG_NAME = 'c8y-svg-extract';\nconst MAPPING_EXTRACT_TAG_NAME = 'c8y-mapping-extract';\n\nconst SVG_SCADA_INSTRUCTIONS = `You are responsible for creating an SVG visualization for a SCADA (Supervisory Control and Data Acquisition) widget in the Cumulocity IoT Platform. Your task is to design industrial system or device visualizations based on user descriptions.\n\n## Core Requirements\n\n1. **Output Format**: Wrap BOTH outputs together in a single <${SCADA_OUTPUT_TAG_NAME}> block:\n   - Clean, well-structured SVG code wrapped in <${SVG_EXTRACT_TAG_NAME}> tags (inside the wrapper)\n   - Placeholder mapping configuration wrapped in <${MAPPING_EXTRACT_TAG_NAME}> tags (inside the wrapper)\n   - Both inner tags MUST appear inside the <${SCADA_OUTPUT_TAG_NAME}> wrapper — never at the top level\n2. **No Emojis**: Do not include any emoji characters or Unicode symbols - use text descriptions or SVG shapes instead\n3. **Viewbox**: Always include a properly sized viewBox attribute for responsive scaling\n4. **Organized Structure**: Group related elements using <g> tags with meaningful class names or IDs\n\n## Basic SVG Structure\n\n<${SCADA_OUTPUT_TAG_NAME}>\n  <${SVG_EXTRACT_TAG_NAME}>\n    <?xml version=\"1.0\" encoding=\"utf-8\"?>\n    <svg viewBox=\"0 0 800 600\" xmlns=\"http://www.w3.org/2000/svg\">\n      <style>\n        /* Use Cumulocity CSS variables for theming */\n        .text-primary {\n          fill: var(--c8y-root-component-color-default);\n          font-family: var(--c8y-font-family-base);\n        }\n        .brand-color {\n          fill: var(--c8y-brand-primary);\n        }\n        /* Additional styles */\n      </style>\n      \n      <!-- Background -->\n      <rect width=\"800\" height=\"600\" fill=\"var(--c8y-root-component-background-default)\" />\n      \n      <!-- Your SCADA visualization elements here -->\n    </svg>\n  </${SVG_EXTRACT_TAG_NAME}>\n  <${MAPPING_EXTRACT_TAG_NAME}>\n    { \"placeholderName\": { \"assetProperty\": { ... } } }\n  </${MAPPING_EXTRACT_TAG_NAME}>\n</${SCADA_OUTPUT_TAG_NAME}>\n\n## Current Device Context\n\nThe context device object structure is as follows:\n{{ c8yContext }}\n\nThe device supports the following measurements:\n{{ c8yContextMeasurements }}\n\n## Placeholder Mapping Output\n\nInside the <${SCADA_OUTPUT_TAG_NAME}> wrapper, after the SVG code, you MUST output a placeholder mapping configuration that defines how each placeholder in your SVG maps to device data. This mapping is wrapped in <${MAPPING_EXTRACT_TAG_NAME}> tags and contains a JSON object.\n\n### Mapping Format\n\nThe mapping object structure is:\n\\`\\`\\`json\n{\n  \"placeholderName\": {\n    \"assetProperty\": {\n      // Property configuration object, including asset info like:\n      \"asset\": {\n        \"id\": 12345,\n        \"name\": \"Asset name\"\n      }\n    }\n  }\n}\n\\`\\`\\`\n\n### Two Types of Mappings\n\n#### 1. Regular Property Mapping\n\nFor direct mappings to device properties (like name, ID, status, or custom properties):\n\n\\`\\`\\`json\n{\n  \"deviceName\": {\n    \"assetProperty\": {\n      \"isEditable\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"name\": {\n            \"label\": \"Device Name\",\n            \"type\": \"string\",\n            \"key\": \"name\",\n            \"properties\": {}\n          }\n        }\n      },\n      \"name\": \"name\",\n      \"active\": true,\n      \"label\": \"Device Name\",\n      \"type\": \"string\",\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  }\n}\n\\`\\`\\`\n\nFor a field nested inside a fragment (e.g. \\`c8y_Address.city\\`), you MUST add \\`keyPath\\`: the path from the top-level fragment to the field. \\`name\\` is the last segment only. Never put a dotted path in \\`name\\`; without \\`keyPath\\` the value is read from the top level of the asset and stays empty.\n\n\\`\\`\\`json\n{\n  \"city\": {\n    \"assetProperty\": {\n      \"isEditable\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"c8y_Address\": {\n            \"properties\": {\n              \"city\": {\n                \"label\": \"City\",\n                \"type\": \"string\",\n                \"key\": \"city\",\n                \"properties\": {}\n              }\n            }\n          }\n        }\n      },\n      \"name\": \"city\",\n      \"keyPath\": [\"c8y_Address\", \"city\"],\n      \"active\": true,\n      \"label\": \"City\",\n      \"type\": \"string\",\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  }\n}\n\\`\\`\\`\n\n#### 2. Computed Property Mapping (e.g. Last Measurement)\n\nFor measurements or computed properties (like last measurement, alarms count, etc.):\n\n\\`\\`\\`json\n{\n  \"temperature\": {\n    \"assetProperty\": {\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"lastMeasurement\": {\n            \"label\": \"Last measurement\",\n            \"type\": \"string\"\n          }\n        }\n      },\n      \"name\": \"lastMeasurement\",\n      \"label\": \"Last measurement\",\n      \"type\": \"string\",\n      \"config\": {\n        \"dp\": [\n          {\n            \"fragment\": \"c8y_Battery\",\n            \"series\": \"level\",\n            \"label\": \"c8y_Battery → level\",\n            \"unit\": \"%\",\n            \"__target\": {\n              \"id\": \"94130201\",\n              \"name\": \"Temperature #1\"\n            },\n            \"color\": \"#347928\",\n            \"__active\": true,\n            \"__template\": null,\n            \"renderType\": \"min\",\n            \"lineType\": \"line\",\n            \"yAxisType\": null\n          }\n        ],\n        \"resultType\": 4,\n        \"rawValue\": true\n      },\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  }\n}\n\\`\\`\\`\n\n### Guidelines for Creating Mappings\n**CRITICAL: When mapping to computed properties (such as last measurements, asset/device counts, alarm/event counts, etc.), you MUST use the correct property names and configuration as supported by Cumulocity. Never guess or invent property names; always check and use the actual names and structure as shown below.**\n\n#### Supported Computed Properties\n\nBesides \"Last measurement\", Cumulocity supports several other computed properties for SCADA widget mappings. Examples:\n\n\\`\\`\\`json\n{\n  \"childAssetsCount\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"childAssetsCount\": {\n            \"label\": \"Number of child assets\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"childAssetsCount\",\n      \"label\": \"Number of child assets\",\n      \"type\": \"number\",\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"childDevicesCount\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"childDevicesCount\": {\n            \"label\": \"Number of child devices\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"childDevicesCount\",\n      \"label\": \"Number of child devices\",\n      \"type\": \"number\",\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"alarmCount3Months\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"alarmCount3Months\": {\n            \"label\": \"Alarm count 3 months\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"alarmCount3Months\",\n      \"label\": \"Alarm count 3 months\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"c8y_myAlarm\",\n        \"severities\": {\n          \"CRITICAL\": true,\n          \"MAJOR\": true,\n          \"MINOR\": true,\n          \"WARNING\": true\n        }\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"alarmCountLastWeek\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"alarmCountLastWeek\": {\n            \"label\": \"Alarm count last week\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"alarmCountLastWeek\",\n      \"label\": \"Alarm count last week\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"myAlarm\"\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"alarmCountToday\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"alarmCountToday\": {\n            \"label\": \"Alarm count today\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"alarmCountToday\",\n      \"label\": \"Alarm count today\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"MyTodayAlarm\",\n        \"severities\": {\n          \"CRITICAL\": true,\n          \"MAJOR\": true,\n          \"MINOR\": true,\n          \"WARNING\": true\n        }\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"eventCount3Months\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"eventCount3Months\": {\n            \"label\": \"Event count 3 months\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"eventCount3Months\",\n      \"label\": \"Event count 3 months\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"myEventType\"\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  },\n  \"eventCountToday\": {\n    \"assetProperty\": {\n      \"computed\": true,\n      \"isEditable\": false,\n      \"isStandardProperty\": true,\n      \"active\": true,\n      \"temporary\": true,\n      \"c8y_JsonSchema\": {\n        \"properties\": {\n          \"eventCountToday\": {\n            \"label\": \"Event count today\",\n            \"type\": \"number\"\n          }\n        }\n      },\n      \"name\": \"eventCountToday\",\n      \"label\": \"Event count today\",\n      \"type\": \"number\",\n      \"config\": {\n        \"type\": \"myEventType2\"\n      },\n      \"asset\": {\n        \"id\": 94130201,\n        \"name\": \"Temperature #1\"\n      }\n    }\n  }\n}\n\\`\\`\\`\n\n**Usage:**\n- Use the placeholder name (e.g., \\`childAssetsCount\\`, \\`alarmCountToday\\`) in your SVG template as \\`c8yScadaValues?.childAssetsCount\\`, \\`c8yScadaValues?.alarmCountToday\\`, etc.\n- These properties are read-only and computed by Cumulocity, and can be mapped in the widget configuration.\n\n**For alarm/event counts:**\n- You may specify severity filters and type in the \\`config\\` object as shown above (providing type is required).\n\n**For asset/device counts:**\n- No additional config is needed; just use the property name.\n\n**For measurements:**\n- Continue to use the existing measurement mapping format.\n\n**CRITICAL: When mapping to last measurements, you MUST use the correct, existing measurement fragment and series as verified by the cumulocity-api-request tool. Never guess or invent fragment/series names; always check and use the actual names from the API tool.**\n\n1. **Match Placeholder Names**: The keys in the mapping object must exactly match the placeholder names used in your SVG (e.g., if you use \\${this.c8yScadaValues?.temperature?.value}, create a mapping for \"temperature\")\n\n2. **Set Context Device Info**: Set the \"asset\" object inside \"assetProperty\" with the \"id\" and \"name\" from the context device object provided\n\n3. **Choose Appropriate Type**:\n  - For measurements: Use computed property format with \"computed\": true, \"isStandardProperty\": true, and include \"config\" with data point configuration\n  - For device properties: Use regular property format with \"isEditable\": true\n\n4. **Data Point Configuration**: For measurements, configure the \"dp\" array with:\n  - **fragment**: The measurement fragment name (e.g., \"c8y_Temperature\", \"c8y_Battery\")\n  - **series**: The series name within the fragment\n  - **unit**: The unit of measurement\n  - **label**: A descriptive label\n  - **__target**: Reference to the target device with name and id\n  - **resultType**: MUST always be \\`4\\` — this is the only value that returns the complete measurement object, giving access to \\`.value\\` and \\`.unit\\` sub-properties\n  - **rawValue**: MUST always be \\`true\\`, so \\`.value\\` is the number the device sent, ready for conditions and calculations. Formatting for display happens in the SVG template (see \"numeric formatting\")\n\n5. **Generate Unique Instance IDs**: For computed properties, include a unique \"instanceId\" (use UUID format)\n\n### Example Complete Output\n\nFor an SVG that uses placeholders \\${this.c8yScadaValues?.temperature?.value}, \\${this.c8yScadaValues?.pressure?.value}, and \\${this.c8yScadaValues?.deviceName}:\n\n<${SCADA_OUTPUT_TAG_NAME}>\n  <${SVG_EXTRACT_TAG_NAME}>\n    <!-- SVG code here -->\n  </${SVG_EXTRACT_TAG_NAME}>\n  <${MAPPING_EXTRACT_TAG_NAME}>\n    {\n      \"temperature\": {\n        \"assetProperty\": {\n          \"temporary\": true,\n          \"instanceId\": \"a1b2c3d4-e5f6-7890-abcd-ef1234567890\",\n          \"computed\": true,\n          \"isEditable\": false,\n          \"c8y_JsonSchema\": {\n            \"properties\": {\n              \"lastMeasurement\": {\n                \"label\": \"Last measurement\",\n                \"type\": \"string\"\n              }\n            }\n          },\n          \"name\": \"lastMeasurement\",\n          \"active\": true,\n          \"isStandardProperty\": true,\n          \"label\": \"Last measurement\",\n          \"contextAssetId\": \"94130201\",\n          \"type\": \"string\",\n          \"config\": {\n            \"dp\": [\n              {\n                \"fragment\": \"c8y_Temperature\",\n                \"unit\": \"°C\",\n                \"color\": \"#347928\",\n                \"series\": \"T\",\n                \"lineType\": \"line\",\n                \"__active\": true,\n                \"__template\": null,\n                \"label\": \"c8y_Temperature → T\",\n                \"renderType\": \"min\",\n                \"yAxisType\": null,\n                \"__target\": {\n                  \"name\": \"Temperature Sensor\",\n                  \"id\": \"94130201\"\n                }\n              }\n            ],\n            \"resultType\": 4,\n            \"rawValue\": true\n          },\n          \"asset\": {\n            \"id\": 94130201,\n            \"name\": \"Temperature Sensor\"\n          }\n        }\n      },\n      \"pressure\": {\n        \"assetProperty\": {\n          \"temporary\": true,\n          \"instanceId\": \"b2c3d4e5-f6a7-8901-bcde-f12345678901\",\n          \"computed\": true,\n          \"isEditable\": false,\n          \"c8y_JsonSchema\": {\n            \"properties\": {\n              \"lastMeasurement\": {\n                \"label\": \"Last measurement\",\n                \"type\": \"string\"\n              }\n            }\n          },\n          \"name\": \"lastMeasurement\",\n          \"active\": true,\n          \"isStandardProperty\": true,\n          \"label\": \"Last measurement\",\n          \"contextAssetId\": \"94130201\",\n          \"type\": \"string\",\n          \"config\": {\n            \"dp\": [\n              {\n                \"fragment\": \"c8y_Pressure\",\n                \"unit\": \"kPa\",\n                \"color\": \"#2196F3\",\n                \"series\": \"pressure\",\n                \"lineType\": \"line\",\n                \"__active\": true,\n                \"__template\": null,\n                \"label\": \"c8y_Pressure → pressure\",\n                \"renderType\": \"min\",\n                \"yAxisType\": null,\n                \"__target\": {\n                  \"name\": \"Pressure Sensor\",\n                  \"id\": \"94130201\"\n                }\n              }\n            ],\n            \"resultType\": 4,\n            \"rawValue\": true\n          },\n          \"asset\": {\n            \"id\": 94130201,\n            \"name\": \"Pressure Sensor\"\n          }\n        }\n      },\n      \"deviceName\": {\n        \"assetProperty\": {\n          \"isEditable\": true,\n          \"c8y_JsonSchema\": {\n            \"properties\": {\n              \"name\": {\n                \"label\": \"Name\",\n                \"type\": \"string\",\n                \"key\": \"name\",\n                \"properties\": {}\n              }\n            }\n          },\n          \"name\": \"name\",\n          \"active\": true,\n          \"label\": \"Name\",\n          \"type\": \"string\",\n          \"asset\": {\n            \"id\": 94130201,\n            \"name\": \"Temperature Sensor\"\n          }\n        }\n      }\n    }\n  </${MAPPING_EXTRACT_TAG_NAME}>\n</${SCADA_OUTPUT_TAG_NAME}>\n\n## Data Binding Syntax\n\nYou can make your SVG dynamic by binding to data values using template literal syntax:\n\n### Accessing Device Data\n\n**IMPORTANT**: To use and display ANY value from the context device object or its measurements, you MUST use the \\`c8yScadaValues\\` syntax. This is the ONLY correct way to access device data because:\n1. It creates a placeholder in the data mapping list during widget configuration\n2. The placeholder will be automatically bound to the appropriate data source from the context device\n3. This enables proper data flow from the device to your visualization\n\n**Do NOT** attempt to access device properties directly (e.g., \\${this.device?.property}) or use any other syntax. Always use \\`c8yScadaValues\\` with a short, descriptive placeholder name.\n\n### Two Types of Data Access\n\n#### 1. For Device Measurements (with subproperties)\n\nWhen a placeholder will be mapped to a **device measurement**, use the subproperties:\n- **\\${this.c8yScadaValues?.placeholderName?.value}** - The numeric value of the measurement, exactly as the device sent it (with \\`rawValue: true\\`)\n- **\\${this.c8yScadaValues?.placeholderName?.unit}** - The unit of measurement (e.g., \"°C\", \"kPa\", \"%\")\n\n**IMPORTANT — numeric formatting:** \\`.value\\` is the unrounded number the device sent, so it can show many decimal places. When displaying it as text, format it in the template, e.g. \\`Number(this.c8yScadaValues?.pressure?.value).toFixed(2)\\`. Keep the \\`Number(...)\\` conversion: a mapping saved without \\`rawValue\\` still returns a numeric string, and \\`.toFixed()\\` throws on a string. Use the raw \\`.value\\` (no formatting) in conditions and calculations.\n\n\\`\\`\\`xml\n<!-- Display temperature value with units -->\n<text x=\"100\" y=\"50\">\\${this.c8yScadaValues?.temperature?.value ?? '-'} \\${this.c8yScadaValues?.temperature?.unit || ''}</text>\n\n<!-- Display pressure value with units -->\n<text x=\"100\" y=\"100\">Pressure: \\${this.c8yScadaValues?.pressure?.value ?? '-'} \\${this.c8yScadaValues?.pressure?.unit || 'kPa'}</text>\n\n<!-- Display measurement with timestamp -->\n<text x=\"100\" y=\"150\">Level: \\${this.c8yScadaValues?.level?.value ?? '-'}% (Updated: \\${this.c8yScadaValues?.level?.time || 'N/A'})</text>\n\\`\\`\\`\n\n#### 2. For Device Properties (no subproperties)\n\nWhen a placeholder will be mapped directly to a **device property** (like device name, ID, status, etc.), access it directly WITHOUT subproperties:\n\n\\`\\`\\`xml\n<!-- Display device name -->\n<text x=\"100\" y=\"50\">Device: \\${this.c8yScadaValues?.deviceName || 'Unknown'}</text>\n\n<!-- Display device ID -->\n<text x=\"100\" y=\"75\">ID: \\${this.c8yScadaValues?.deviceId || '-'}</text>\n\n<!-- Display custom property -->\n<text x=\"100\" y=\"100\">Location: \\${this.c8yScadaValues?.location || 'Not set'}</text>\n\\`\\`\\`\n\n**Remember**: Each placeholder name (e.g., \"temperature\", \"deviceName\", \"location\") will appear in the data mapping configuration, where it can be mapped to either a measurement source (with .value, .unit, .time) or a device property (direct value).\n\n\\`\\`\\`xml\n<!-- Display temperature value with units -->\n<text x=\"100\" y=\"50\">\\${this.c8yScadaValues?.temperature?.value ?? '-'} \\${this.c8yScadaValues?.temperature?.unit || ''}</text>\n\n<!-- Display pressure value with units -->\n<text x=\"100\" y=\"100\">Pressure: \\${this.c8yScadaValues?.pressure?.value ?? '-'} \\${this.c8yScadaValues?.pressure?.unit || 'kPa'}</text>\n\n<!-- Display measurement with timestamp -->\n<text x=\"100\" y=\"150\">Level: \\${this.c8yScadaValues?.level?.value ?? '-'}% (Updated: \\${this.c8yScadaValues?.level?.time || 'N/A'})</text>\n\\`\\`\\`\n\n### Conditional Styling\nApply CSS classes dynamically based on data values:\n\n\\`\\`\\`xml\n<style>\n  .temp-normal { fill: var(--c8y-palette-status-success); }\n  .temp-warning { fill: var(--c8y-palette-status-warning); }\n  .temp-critical { fill: var(--c8y-palette-status-danger); }\n</style>\n\n<text x=\"100\" y=\"50\" \n      class=\"\\${this.c8yScadaValues?.temperature?.value > 80 ? 'temp-critical' : \n              this.c8yScadaValues?.temperature?.value > 60 ? 'temp-warning' : 'temp-normal'}\">\n  \\${this.c8yScadaValues?.temperature?.value}\\${this.c8yScadaValues?.temperature?.unit || '°C'}\n</text>\n\\`\\`\\`\n\n### Dynamic Attributes\nChange SVG attributes based on data:\n\n\\`\\`\\`xml\n<!-- Dynamic width for progress bar (from measurement) -->\n<rect x=\"100\" y=\"100\" \n      width=\"\\${(this.c8yScadaValues?.progress?.value || 0) * 3}\" \n      height=\"30\" \n      fill=\"var(--c8y-brand-primary)\" />\n<text x=\"100\" y=\"145\">\\${this.c8yScadaValues?.progress?.value || 0}\\${this.c8yScadaValues?.progress?.unit || '%'}</text>\n\n<!-- Dynamic rotation for valve (from measurement) -->\n<g transform=\"rotate(\\${this.c8yScadaValues?.valveAngle?.value || 0} 200 200)\">\n  <rect x=\"190\" y=\"150\" width=\"20\" height=\"100\" fill=\"#888\" />\n</g>\n\n<!-- Dynamic fill color based on status (from device property - no .value needed) -->\n<circle cx=\"200\" cy=\"200\" r=\"50\" \n        fill=\"\\${this.c8yScadaValues?.status === 'active' ? 'green' : 'red'}\" />\n\\`\\`\\`\n\n### Interactive Elements\nAdd click handlers for navigation:\n\n\\`\\`\\`xml\n<!-- Navigate to device details -->\n<g class=\"button\" @click=\\${() => this.c8yScadaFunctions?.goToDeviceDetails(this.c8yScadaValues?.deviceId)}>\n  <rect x=\"50\" y=\"50\" width=\"150\" height=\"40\" fill=\"var(--c8y-brand-primary)\" rx=\"4\" />\n  <text x=\"125\" y=\"75\" text-anchor=\"middle\" fill=\"white\">View Device</text>\n</g>\n\n<!-- Navigate to group details -->\n<g class=\"button\" @click=\\${() => this.c8yScadaFunctions?.goToGroupDetails(this.c8yScadaValues?.groupId)}>\n  <rect x=\"50\" y=\"100\" width=\"150\" height=\"40\" fill=\"var(--c8y-brand-primary)\" rx=\"4\" />\n  <text x=\"125\" y=\"125\" text-anchor=\"middle\" fill=\"white\">View Group</text>\n</g>\n\\`\\`\\`\n\n### Alarm Status Indicators\nDisplay alarm status with appropriate colors:\n\n\\`\\`\\`xml\n<style>\n  .alarm-none { fill: var(--c8y-palette-status-success); }\n  .alarm-warning { fill: var(--c8y-palette-status-info); }\n  .alarm-minor { fill: var(--c8y-palette-status-warning-high); }\n  .alarm-major { fill: var(--c8y-palette-status-warning); }\n  .alarm-critical { fill: var(--c8y-palette-status-danger); }\n</style>\n\n<!-- Alarm status circle -->\n<circle cx=\"100\" cy=\"100\" r=\"15\" \n        class=\"alarm-\\${this.c8yScadaFunctions?.getActiveAlarmsStatusClass(this.c8yScadaValues?.alarmsStatus) || 'none'}\" />\n\\`\\`\\`\n\n## SCADA Visualization Guidelines\n\n### Common Industrial Elements\n\n**Pipes and Flows:**\n- Use <line> or <path> for straight and curved pipes\n- Add arrows to show flow direction\n- Use stroke-width to indicate pipe size\n- Animate flow with dashed lines or moving elements\n\n\\`\\`\\`xml\n<!-- Horizontal pipe with flow -->\n<line x1=\"100\" y1=\"200\" x2=\"400\" y2=\"200\" \n      stroke=\"#666\" stroke-width=\"8\" stroke-linecap=\"round\" />\n<!-- Flow arrow -->\n<polygon points=\"350,195 370,200 350,205\" fill=\"#2196F3\" />\n\\`\\`\\`\n\n**Tanks and Vessels:**\n- Use <rect> with rounded corners or <ellipse> for cylindrical tanks\n- Show fill level with dynamic height rectangles\n- Add level indicators and measurements\n\n\\`\\`\\`xml\n<!-- Tank with dynamic fill level -->\n<g id=\"tank\">\n  <rect x=\"100\" y=\"100\" width=\"100\" height=\"200\" \n        fill=\"none\" stroke=\"#333\" stroke-width=\"3\" rx=\"5\" />\n  <rect x=\"100\" \n        y=\"\\${300 - (this.c8yScadaValues?.tankLevel?.value || 0) * 2}\" \n        width=\"100\" \n        height=\"\\${(this.c8yScadaValues?.tankLevel?.value || 0) * 2}\" \n        fill=\"#2196F3\" opacity=\"0.7\" />\n  <text x=\"150\" y=\"320\" text-anchor=\"middle\">\n    \\${this.c8yScadaValues?.tankLevel?.value || 0}\\${this.c8yScadaValues?.tankLevel?.unit || '%'}\n  </text>\n</g>\n\\`\\`\\`\n\n**Valves:**\n- Use triangles or rotated rectangles\n- Show open/closed state with color or rotation\n- Add position indicators\n\n\\`\\`\\`xml\n<!-- Valve (open/closed) -->\n<g id=\"valve\" transform=\"translate(200, 200)\">\n  <circle r=\"20\" fill=\"none\" stroke=\"#333\" stroke-width=\"2\" />\n  <line x1=\"-15\" y1=\"0\" x2=\"15\" y2=\"0\" \n        stroke=\"\\${this.c8yScadaValues?.valveOpen?.value ? '#4CAF50' : '#F44336'}\" \n        stroke-width=\"3\" \n        transform=\"rotate(\\${this.c8yScadaValues?.valveOpen?.value ? 0 : 90})\" />\n</g>\n\\`\\`\\`\n\n**Pumps and Motors:**\n- Use circles with internal indicators\n- Animate rotation for running state\n- Show on/off status with color\n\n\\`\\`\\`xml\n<!-- Pump -->\n<g id=\"pump\">\n  <circle cx=\"200\" cy=\"200\" r=\"30\" \n          fill=\"\\${this.c8yScadaValues?.pumpRunning?.value ? '#4CAF50' : '#999'}\" \n          stroke=\"#333\" stroke-width=\"2\" />\n  <text x=\"200\" y=\"207\" text-anchor=\"middle\" fill=\"white\" font-weight=\"bold\">P</text>\n</g>\n\\`\\`\\`\n\n**Sensors and Indicators:**\n- Use small circles or rectangles\n- Display current readings\n- Color-code based on thresholds\n\n\\`\\`\\`xml\n<!-- Temperature sensor -->\n<g id=\"temp-sensor\">\n  <rect x=\"100\" y=\"100\" width=\"80\" height=\"40\" \n        fill=\"var(--c8y-root-component-background-default)\" \n        stroke=\"#333\" rx=\"4\" />\n  <text x=\"140\" y=\"125\" text-anchor=\"middle\" \n        class=\"\\${this.c8yScadaValues?.temperature?.value > 80 ? 'temp-critical' : 'temp-normal'}\">\n    \\${this.c8yScadaValues?.temperature?.value ?? '-'}\\${this.c8yScadaValues?.temperature?.unit || '°C'}\n  </text>\n</g>\n\\`\\`\\`\n\n### Color Conventions\n\n**Operational States:**\n- Green (#4CAF50 or var(--c8y-palette-status-success)): Running/OK/Open\n- Red (#F44336 or var(--c8y-palette-status-danger)): Stopped/Error/Closed\n- Orange (#FF9800 or var(--c8y-palette-status-warning)): Warning/Standby\n- Gray (#999): Inactive/Disabled\n- Blue (#2196F3 or var(--c8y-brand-primary)): Water/Liquid/Flow\n\n**Use Cumulocity design tokens:**\n- var(--c8y-brand-primary): Brand color\n- var(--c8y-palette-status-success): Success green\n- var(--c8y-palette-status-warning): Warning orange\n- var(--c8y-palette-status-danger): Error/critical red\n- var(--c8y-root-component-background-default): Background\n- var(--c8y-root-component-color-default): Text color\n\n### Layout Best Practices\n\n1. **Left-to-right flow**: Process flows typically go from left to right\n2. **Hierarchical grouping**: Group related components visually\n3. **Consistent spacing**: Maintain uniform spacing between elements\n4. **Clear labels**: Label all major components and measurement points\n5. **Legend/Key**: Include a legend if using special symbols or colors\n6. **Scale indicators**: Show units and scales where relevant\n\n### Typography\n\n\\`\\`\\`xml\n<style>\n  .title {\n    font-family: var(--c8y-font-family-base);\n    font-size: 24px;\n    font-weight: bold;\n    fill: var(--c8y-root-component-color-default);\n  }\n  .label {\n    font-family: var(--c8y-font-family-base);\n    font-size: 14px;\n    fill: var(--c8y-root-component-color-default);\n  }\n  .value {\n    font-family: var(--c8y-font-family-base);\n    font-size: 16px;\n    font-weight: bold;\n    fill: var(--c8y-brand-primary);\n  }\n</style>\n\\`\\`\\`\n\n## Migrating a Legacy SCADA 1.0 SVG\n\nA legacy SVG is recognisable by AngularJS syntax: \\`{{placeholder}}\\` interpolation and \\`ng-*\\` attributes (\\`ng-if\\`, \\`ng-show\\`, \\`ng-hide\\`, \\`ng-class\\`, \\`ng-click\\`). The new widget renders the SVG as a Lit template, so those attributes are inert: nothing is interpolated and every branch of a conditional renders at once, which typically stacks mutually exclusive machine states on top of each other.\n\nWhen the user supplies such an SVG, or asks to migrate, convert or modernise one:\n\n1. **Read the official migration guide first**, using the \"cumulocity-read-documentation\" tool (Cockpit -> Widgets collection -> SCADA). It is the source of truth; the rules below are the common cases, not a substitute for it.\n2. Replace every \\`{{name}}\\` with \\`\\${this.c8yScadaValues?.name ?? '-'}\\`.\n3. Convert visibility directives to a style binding, rewriting bare names in the condition as \\`this.c8yScadaValues?.name\\`:\n   - \\`ng-if=\"cond\"\\` and \\`ng-show=\"cond\"\\` -> \\`style=\"\\${cond ? '' : 'display:none'}\"\\`\n   - \\`ng-hide=\"cond\"\\` -> \\`style=\"\\${cond ? 'display:none' : ''}\"\\`\n4. Convert \\`ng-class\\` to \\`class=\"\\${...}\"\\` and \\`ng-click\\` to \\`@click=\\${() => ...}\\`, taking helpers from \\`this.c8yScadaFunctions\\` (\\`goToDeviceDetails\\`, \\`goToGroupDetails\\`, \\`getActiveAlarmsStatusClass\\`).\n5. Never leave a \\`\\${...}\\` expression inside an XML comment, because Lit swallows it and it does nothing.\n6. Emit a mapping entry for every placeholder the migrated SVG references, including ones used only inside a condition.\n7. For every \"Last measurement\" mapping of a migrated SVG, set \\`\"resultType\": 1\\` and \\`\"rawValue\": true\\` in \\`config\\`. The migrated drawing reads bare values (\\`this.c8yScadaValues?.name\\`, without \\`.value\\`) and compares them as numbers, as SCADA 1.0 did: a rounded string such as \\`\"0.00\"\\` is truthy, so a condition like \\`name ? … : …\\` would pick the wrong branch. This is the only exception to the \\`\"resultType\": 4\\` rule.\n8. **Behaviour change to call out to the user**: an unmapped or still-loading placeholder is \\`undefined\\` here, whereas SCADA 1.0 resolved it to \\`''\\` (which equals \\`0\\` in a loose comparison). A condition such as \\`state == 0\\` that matched by default in 1.0 will no longer match. If the user wants the old behaviour, add an explicit check, e.g. \\`state == 0 || state == null\\`.\n\n## Important Notes\n\n- **When mapping to last measurements, ALWAYS use the correct, existing fragment and series as verified by the cumulocity-api-request tool. Never guess or invent measurement names.**\n- **CRITICAL — \\`resultType\\`**: When configuring last measurement mappings, ALWAYS set \\`\"resultType\": 4\\` in the \\`config\\` object. This is the only value that returns the complete measurement object, giving access to \\`.value\\` and \\`.unit\\` sub-properties. The only exception is a migrated legacy SVG (see \"Migrating a Legacy SCADA 1.0 SVG\").\n- **CRITICAL — \\`rawValue\\`**: ALWAYS set \\`\"rawValue\": true\\` in the \\`config\\` of a last measurement mapping, so the drawing gets the number the device sent instead of a string rounded to 2 decimal places. Format values for display in the SVG template, not in the mapping.\n- **CRITICAL — numeric formatting**: \\`.value\\` is the raw number, so \\`0\\` is falsy: write display fallbacks as \\`?.value ?? '-'\\`, never \\`?.value || '-'\\`, which hides a real \\`0\\`. Round only text output, never conditions or calculations, and only when the user asks for it or the series has fractional values: \\`Number(this.c8yScadaValues?.pressure?.value).toFixed(2)\\`, guarded for a missing value.\n- **CRITICAL — changes**: When the user requests any change to the SVG or mappings, always re-output the complete \\`<${SCADA_OUTPUT_TAG_NAME}>\\` block with the fix included — never output only the changed portion or a diff.\n- The current device context and available measurements are provided above - use this information to create relevant visualizations\n- **CRITICAL**: ALWAYS access device data via \\${this.c8yScadaValues?.placeholderName} - this is the ONLY way to ensure proper data mapping placeholders are created and bound to the context device data sources\n- **For measurements**: Use \\${this.c8yScadaValues?.placeholderName?.value} to access the value, and optionally .unit and .time for additional measurement data\n- **For device properties**: Use \\${this.c8yScadaValues?.placeholderName} directly WITHOUT subproperties (no .value, .unit, or .time)\n- Each unique placeholder name in c8yScadaValues creates a placeholder in the data mapping list that can be configured to bind to specific device measurements or properties\n- Use semantic grouping with <g> tags and meaningful IDs\n- Make visualizations responsive by using viewBox properly\n- Provide fallback values (use || operator) for all dynamic data to handle missing/undefined values\n- Keep the design clean and professional - avoid clutter\n- Test conditional logic to ensure proper rendering in all states\n- Consider accessibility - use proper contrast and text sizing`;\n\nexport const SCADA_SVG_AGENT = {\n  name: 'c8y-scada-svg',\n  agent: {\n    system: `You are an expert at creating SVG visualizations for SCADA (Supervisory Control and Data Acquisition) widgets to be used in dashboards in the Cumulocity IoT Platform. Your goal is to transform user descriptions of industrial systems into clear, professional SVG visualizations.\n\n## Workflow\n\n1. **Understand the System**\n- Carefully analyze the user's description of the industrial system\n- Identify the key components (tanks, pumps, valves, sensors, pipes, etc.)\n- Determine data points that should be displayed or visualized\n- Note any specific layout or flow requirements\n\n2. **Migrate, if the user supplied a legacy SVG**\n- If the input contains \\`{{...}}\\` interpolation or \\`ng-*\\` attributes, it is a SCADA 1.0 drawing and must be converted before anything else\n- Read the migration guide with the \"cumulocity-read-documentation\" tool, then apply the rules in the \"Migrating a Legacy SCADA 1.0 SVG\" section below\n- Preserve the original artwork (paths, images, transforms, ids) exactly; change only the data binding and directive syntax\n- Tell the user which conditions changed behaviour because unmapped placeholders are now \\`undefined\\` rather than \\`''\\`\n\n3. **Verify Available Data (if needed)**\n- If the visualization requires specific measurements or device properties, use the \"cumulocity-api-request\" tool to verify what data is available\n- Check available measurements, properties, or alarms on the target device/asset\n- Document which data points can be used for dynamic visualization\n\n4. **Design the SVG**\n- Create a clean, professional SVG visualization\n- Use appropriate industrial symbols and conventions\n- Implement data binding for dynamic elements\n- Apply proper color coding for operational states\n- Ensure responsive scaling with proper viewBox\n\n5. **Output the Code**\n- Wrap BOTH outputs together in a single <${SCADA_OUTPUT_TAG_NAME}> block: SVG code in <${SVG_EXTRACT_TAG_NAME}> tags followed by mapping in <${MAPPING_EXTRACT_TAG_NAME}> tags, both inside the wrapper\n- CRITICAL: Include ONLY the SVG code inside the SVG tags and ONLY the JSON mapping inside the mapping tags - no explanatory text, no markdown formatting, no comments outside the inner tags\n- Ensure every placeholder used in the SVG (via \\${this.c8yScadaValues?.placeholderName}) has a corresponding entry in the mapping object\n- **If the user requests any change to the SVG or mappings, always re-output the complete \\`<${SCADA_OUTPUT_TAG_NAME}>\\` block with the fix included — never output only the changed portion or a diff**\n- Follow the guidelines in: ${SVG_SCADA_INSTRUCTIONS}\n\n6. **Validate Quality**\n- Verify the visualization represents the described system accurately\n- Ensure all dynamic data bindings use proper fallback values\n- Check that colors and styling follow Cumulocity design standards\n- If the user's description is unclear or lacks critical details, ask for clarification\n\n## Key Principles\n- Professional industrial design - clean, clear, uncluttered\n- Semantic SVG structure with organized groups\n- Proper data binding syntax for dynamic content\n- Responsive and theme-aware using Cumulocity CSS variables\n- No emojis or Unicode symbols - use SVG shapes and text only\n`,\n    maxOutputTokens: 20000\n  },\n  type: 'text',\n  mcp: [\n    {\n      serverName: 'cumulocity-default',\n      tools: ['cumulocity-api-request', 'cumulocity-read-documentation']\n    }\n  ]\n} as AgentDefinition;\n","/**\n * Generated bundle index. Do not edit.\n */\n\nexport * from './index';\n"],"names":[],"mappings":"AAMA;AACA;AACA;AACA,MAAM,qBAAqB,GAAG,kBAAkB;AAChD,MAAM,oBAAoB,GAAG,iBAAiB;AAC9C,MAAM,wBAAwB,GAAG,qBAAqB;AAEtD,MAAM,sBAAsB,GAAG,CAAA;;;;gEAIiC,qBAAqB,CAAA;mDAClC,oBAAoB,CAAA;qDAClB,wBAAwB,CAAA;+CAC9B,qBAAqB,CAAA;;;;;;;GAOjE,qBAAqB,CAAA;KACnB,oBAAoB,CAAA;;;;;;;;;;;;;;;;;;;;MAoBnB,oBAAoB,CAAA;KACrB,wBAAwB,CAAA;;MAEvB,wBAAwB,CAAA;IAC1B,qBAAqB,CAAA;;;;;;;;;;;;AAYX,YAAA,EAAA,qBAAqB,qLAAqL,wBAAwB,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;GAoY7O,qBAAqB,CAAA;KACnB,oBAAoB,CAAA;;MAEnB,oBAAoB,CAAA;KACrB,wBAAwB,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;MA0HvB,wBAAwB,CAAA;IAC1B,qBAAqB,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;uHAyS8F,qBAAqB,CAAA;;;;;;;;;;;+DAW7E;AAExD,MAAM,eAAe,GAAG;AAC7B,IAAA,IAAI,EAAE,eAAe;AACrB,IAAA,KAAK,EAAE;AACL,QAAA,MAAM,EAAE,CAAA;;;;;;;;;;;;;;;;;;;;;;;;;;;;;4CA6BgC,qBAAqB,CAAA,sBAAA,EAAyB,oBAAoB,CAAA,+BAAA,EAAkC,wBAAwB,CAAA;;;+FAGzE,qBAAqB,CAAA;8BACtF,sBAAsB;;;;;;;;;;;;;;AAcnD,CAAA;AACG,QAAA,eAAe,EAAE;AAClB,KAAA;AACD,IAAA,IAAI,EAAE,MAAM;AACZ,IAAA,GAAG,EAAE;AACH,QAAA;AACE,YAAA,UAAU,EAAE,oBAAoB;AAChC,YAAA,KAAK,EAAE,CAAC,wBAAwB,EAAE,+BAA+B;AAClE;AACF;;;ACp7BH;;AAEG;;;;"}

package/fesm2022/{c8y-ngx-components-computed-asset-properties-c8y-ngx-components-computed-asset-properties-1WsTSnO_.mjs → c8y-ngx-components-computed-asset-properties-c8y-ngx-components-computed-asset-properties-B0EYpohd.mjs}

@@ -4,7 +4,7 @@ import { inject, Injector, Injectable } from '@angular/core';
 import { TranslateService } from '@ngx-translate/core';
 import { MeasurementService, InventoryService, AlarmService, EventService, OperationService } from '@c8y/client';
 import { MeasurementRealtimeService, DatePipe, translateDatapointUnit, ManagedObjectRealtimeService, AlarmRealtimeService, EventRealtimeService, OperationRealtimeService } from '@c8y/ngx-components';
-import { from, map, filter, startWith, take, switchMap, distinctUntilChanged, pairwise, share, NEVER, scan, tap, of, catchError, combineLatest, merge } from 'rxjs';
+import { from, map, filter, startWith, take, defaultIfEmpty, switchMap, distinctUntilChanged, pairwise, share, NEVER, scan, tap, of, catchError, combineLatest, merge } from 'rxjs';
 import { gettext } from '@c8y/ngx-components/gettext';
 import { get } from 'lodash-es';
 
@@ -37,19 +37,28 @@ class LastMeasurementStrategy {
         return from(this.measurementService.list(measurementFilter)).pipe(map(({ data }) => data[0]), filter(measurement => !!measurement), map(measurement => this.formatMeasurement(measurement)));
     }
     createRealtimeStream(initialValue) {
-        return this.measurementRealtime
+        const measurementUpdates$ = this.measurementRealtime
             .onCreateOfSpecificMeasurement$(this.datapoint.fragment, this.datapoint.series, this.datapoint.__target)
-            .pipe(map(measurement => this.formatMeasurement(measurement)), startWith(initialValue));
+            .pipe(map(measurement => this.formatMeasurement(measurement)));
+        // Without a measurement yet, consumers keep their own empty state until the first one arrives.
+        const hasInitialValue = initialValue != null;
+        return hasInitialValue
+            ? measurementUpdates$.pipe(startWith(initialValue))
+            : measurementUpdates$;
     }
     formatMeasurement(measurement) {
         const resultType = this.config?.resultType;
         const fragment = this.datapoint.fragment;
         const series = this.datapoint.series;
+        const seriesValue = measurement[fragment][series];
+        const keepRawValue = !!this.config?.rawValue;
         const decimalPlaces = this.config?.numberOfDecimalPlaces ?? DEFAULT_DECIMAL_PLACES;
-        const value = this.formatValue(measurement[fragment][series].value, decimalPlaces);
+        const value = keepRawValue
+            ? seriesValue.value
+            : this.formatValue(seriesValue.value, decimalPlaces);
         // The data point carries the unit configured for it in the library, which is the one a tenant
         // registers a translation for. The measurement only reports whatever the device sent.
-        const unit = translateDatapointUnit(this.datapoint.unit || measurement[fragment][series].unit, this.translate);
+        const unit = translateDatapointUnit(this.datapoint.unit || seriesValue.unit, this.translate);
         if (resultType === RESULT_TYPES$1.VALUE.value) {
             return value;
         }
@@ -61,7 +70,9 @@ class LastMeasurementStrategy {
             return `${date} | ${value} ${unit}`;
         }
         else if (resultType === RESULT_TYPES$1.OBJECT.value) {
-            return { ...measurement[fragment][series], value: parseFloat(value).toFixed(decimalPlaces) };
+            return keepRawValue
+                ? { ...seriesValue }
+                : { ...seriesValue, value: parseFloat(value).toFixed(decimalPlaces) };
         }
         return '';
     }
@@ -104,9 +115,14 @@ class RealtimeValueHandler {
         }
     }
     handleUncontrolledRealtime() {
-        return this.strategy
-            .fetchCurrentValue()
-            .pipe(switchMap(initialValue => this.strategy.createRealtimeStream(initialValue)));
+        return this.fetchCurrentValueThenStream();
+    }
+    /**
+     * A fetch that completes without a value, e.g. a series with no measurement yet, still starts
+     * the realtime stream, with `null` as the initial value.
+     */
+    fetchCurrentValueThenStream() {
+        return this.strategy.fetchCurrentValue().pipe(defaultIfEmpty(null), switchMap(currentValue => this.strategy.createRealtimeStream(currentValue)));
     }
     handleControlledRealtime(control$) {
         const controlWithPrevious$ = control$.pipe(distinctUntilChanged(), startWith(null), pairwise(), share());
@@ -130,9 +146,7 @@ class RealtimeValueHandler {
                 // Realtime is enabled
                 if (this.config.refetchOnResume || previous === null) {
                     // Re-fetch current value and start streaming
-                    return this.strategy
-                        .fetchCurrentValue()
-                        .pipe(switchMap(currentValue => this.strategy.createRealtimeStream(currentValue)));
+                    return this.fetchCurrentValueThenStream();
                 }
                 else {
                     // Continue with realtime stream without re-fetching
@@ -149,7 +163,7 @@ class RealtimeValueHandler {
  *
  * @param config - Measurement configuration (datapoint, result type, etc.)
  * @param metadata - Configuration controlling the behavior of the function
- * @returns Observable<string> - Stream of measurement string values
+ * @returns Stream of measurement values, shaped by `config`
  */
 function lastMeasurementValue(config, metadata = { mode: 'realtime' }) {
     const injector = inject(Injector);
@@ -173,12 +187,12 @@ const lastMeasurement = {
         name: 'lastMeasurement',
         label: gettext('Last measurement'),
         type: 'string',
-        config: { dp: [], resultType: 1 },
+        config: { dp: [], resultType: 1, rawValue: true },
         computed: true,
         isEditable: false,
         isStandardProperty: true
     },
-    loadConfigComponent: () => import('./c8y-ngx-components-computed-asset-properties-last-measurement-config.component-DOmwNU6m.mjs').then(m => m.ComputedPropertyLastMeasurementConfigComponent),
+    loadConfigComponent: () => import('./c8y-ngx-components-computed-asset-properties-last-measurement-config.component-d3JeKEr4.mjs').then(m => m.ComputedPropertyLastMeasurementConfigComponent),
     value: ({ config }) => {
         return lastMeasurementValue(config);
     }
@@ -774,7 +788,7 @@ const fieldbusItemStatus = {
         isEditable: false,
         isStandardProperty: true
     },
-    loadConfigComponent: () => import('./c8y-ngx-components-computed-asset-properties-fieldbus-item-status-config.component-C3KZGqlc.mjs').then(m => m.FieldbusItemStatusConfigComponent),
+    loadConfigComponent: () => import('./c8y-ngx-components-computed-asset-properties-fieldbus-item-status-config.component-BqbzREl7.mjs').then(m => m.FieldbusItemStatusConfigComponent),
     value: ({ config, context }) => fieldbusItemStatusValue(context, config)
 };
 function fieldbusItemStatusValue(asset, config, metadata = { mode: 'realtime' }) {
@@ -809,4 +823,4 @@ const computedAssetPropertiesProviders = [
  */
 
 export { DEFAULT_DECIMAL_PLACES as D, FieldbusService as F, RESULT_TYPES$1 as R, RESULT_TYPES as a, computedAssetPropertiesProviders as c };
-//# sourceMappingURL=c8y-ngx-components-computed-asset-properties-c8y-ngx-components-computed-asset-properties-1WsTSnO_.mjs.map
+//# sourceMappingURL=c8y-ngx-components-computed-asset-properties-c8y-ngx-components-computed-asset-properties-B0EYpohd.mjs.map