thingsboard-cli 4.3.1.2__py3-none-any.whl

thingsboard_cli/resources/prompts/solutions/dashboard/resources/state-datasource/relations-query/datasource-schema.json

@@ -0,0 +1,54 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "title": "Relations query datasource",
+  "description": "Schema for relationsQuery datasource configuration",
+  "type": "object",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "datasourceType": {
+      "enum": ["relationsQuery"]
+    },
+    "rootEntity": {
+      "type": "string"
+    },
+    "rootEntityProfile": {
+      "type": "string"
+    },
+    "relationFilters": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "properties": {
+          "relationType": {
+            "type": "string"
+          },
+          "entityTypes": {
+            "type": "array",
+            "items": {
+              "type": "string",
+              "enum": [
+                "DEVICE",
+                "ASSET",
+                "CUSTOMER",
+                "TENANT",
+                "USER"
+              ]
+            }
+          }
+        },
+        "required": [
+          "relationType",
+          "entityTypes"
+        ]
+      }
+    }
+  },
+  "required": [
+    "id",
+    "datasourceType",
+    "rootEntity",
+    "relationFilters"
+  ]
+}

thingsboard_cli/resources/prompts/solutions/dashboard/resources/state-datasource/single-entity/datasource-capabilities.md

@@ -0,0 +1,30 @@
+# Single Entity Datasource
+
+## Overview
+
+The `singleEntity` datasource targets the single known root entity in a single-root solution. It is used when the dashboard is built for exactly one asset or device at the top of the hierarchy, and that entity is shown directly without browsing or selection.
+
+## When to Use
+
+- Root states in single-root solutions where the dashboard opens directly on one entity's details.
+- Widgets that display data (attributes, telemetry, or configuration) for the single root entity.
+- Do NOT use in detail states or multi-entity root states.
+
+## Configuration
+
+- `id`: Unique datasource identifier from the overview.
+- `datasourceType`: `"singleEntity"`
+- `entityType`: The ThingsBoard entity type — `"ASSET"` or `"DEVICE"`. Use the entity type that corresponds to the root entity in the solution descriptor.
+- `entityProfile`: Use the entity profile that corresponds to the root entity in the solution descriptor.
+
+## Examples
+
+Single asset at the root of the solution:
+```json
+{"id": "root-factory", "datasourceType": "singleEntity", "entityType": "ASSET", "entityProfile": "Facility"}
+```
+
+Single device at the root of the solution:
+```json
+{"id": "root-device", "datasourceType": "singleEntity", "entityType": "DEVICE", "entityProfile": "Meter"}
+```

thingsboard_cli/resources/prompts/solutions/dashboard/resources/state-datasource/single-entity/datasource-schema.json

@@ -0,0 +1,27 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "title": "Single entity datasource",
+  "description": "Schema for singleEntity datasource configuration",
+  "type": "object",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "datasourceType": {
+      "enum": ["singleEntity"]
+    },
+    "entityType": {
+      "type": "string",
+      "enum": ["DEVICE", "ASSET"]
+    },
+    "entityProfile": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "datasourceType",
+    "entityType",
+    "entityProfile"
+  ]
+}

thingsboard_cli/resources/prompts/solutions/dashboard/resources/state-datasource/state-entity/datasource-capabilities.md

@@ -0,0 +1,35 @@
+# State Entity Datasource
+
+## Overview
+
+The `stateEntity` datasource points to the entity that was selected by the user in a previous widget action (e.g., via drillDown or changeState navigation). It represents the currently navigated-to entity.
+
+## When to Use
+
+- Detail states where you need to display data for the entity the user navigated to.
+- Showing entity header cards, detail forms, or entity-specific telemetry.
+- Always include in detail states for the selected entity itself.
+
+## Configuration
+
+- `id`: Unique datasource identifier from the overview.
+- `datasourceType`: `"stateEntity"`
+- `stateEntity`: The state entity name — use the `rootStateEntity` value from the request exactly. Do NOT invent a different name.
+
+## Important Rules
+
+- The `stateEntity` value MUST match the `rootStateEntity` from the request.
+- Only use this datasource type in detail states where `rootStateEntity` is not null.
+- This datasource returns a single entity — the one the user navigated to.
+
+## Examples
+
+Selected customer entity (rootStateEntity = "selectedCustomer"):
+```json
+{"id": "selected-customer", "datasourceType": "stateEntity", "stateEntity": "selectedCustomer"}
+```
+
+Selected device entity (rootStateEntity = "selectedDevice"):
+```json
+{"id": "selected-device", "datasourceType": "stateEntity", "stateEntity": "selectedDevice"}
+```

thingsboard_cli/resources/prompts/solutions/dashboard/resources/state-datasource/state-entity/datasource-schema.json

@@ -0,0 +1,22 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "title": "State entity datasource",
+  "description": "Schema for stateEntity datasource configuration",
+  "type": "object",
+  "properties": {
+    "id": {
+      "type": "string"
+    },
+    "datasourceType": {
+      "enum": ["stateEntity"]
+    },
+    "stateEntity": {
+      "type": "string"
+    }
+  },
+  "required": [
+    "id",
+    "datasourceType",
+    "stateEntity"
+  ]
+}

thingsboard_cli/resources/prompts/solutions/dashboard/resources/state-layout/dashboard-state-layout-capabilities.md

@@ -0,0 +1,413 @@
+# Dashboard State Layout Generation
+
+## 1. Grid Fundamentals
+
+### 1.1 Column & Row System
+
+The dashboard uses a responsive grid:
+- **Columns**: 24 total (indices 0–23)
+- **Rows**: Unlimited, starting from 0
+- **Constraint**: `col + sizeX` must not exceed 24
+
+### 1.2 Position Properties
+
+**Required for every widget:**
+
+| Property | Description |
+|----------|-------------|
+| `row` | Starting row (0-based) |
+| `col` | Starting column (0–23) |
+| `sizeX` | Width in columns |
+| `sizeY` | Height in rows |
+
+### 1.3 Row Budget
+
+`autoFillHeight: true` (always enabled) stretches all rows proportionally to fill the full screen height. The **total number of rows** you use directly controls each row's pixel height — more rows = shorter rows, fewer rows = taller rows.
+
+Always target the row budget for the state type:
+
+| State type | Header rows | Body rows | Total |
+|------------|-------------|----|-------|
+| `standardDetail` | 1 | 11 | 12    |
+| `switcherDetail` | 1 | 0  | 1     |
+| `collection` | 0 | 12 | 12 |
+| `overview` | 0 | 11 | 11    |
+| `statistics` | 0 | 11 | 11    |
+
+**Calculating body sizeY (11-row budget):**
+- 1 full-body widget: `sizeY: 11`
+- 2 stacked sections: `sizeY: 5` + `sizeY: 6`
+- 3 stacked sections: `sizeY: 3` + `sizeY: 4` + `sizeY: 4`
+- Widgets sharing the same row count once toward the total
+
+---
+
+## 2. Widget Catalog
+
+Single source of truth for each widget's size constraints, forbidden uses, and pairing rules.
+
+### 2.1 Structural Widgets
+
+Only allowed in the **header zone** (row 0). Never place in the body zone.
+
+| Widget | sizeX | sizeY | Rules                                                                                                                                                                                                                                                                                              |
+|--------|-------|-------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
+| `headerCard` | 6–24 | 1 | Use `sizeX: 24` only when no `navigationWidget`, `actionButton` or `connectRealDevices` is present in the header row. Otherwise leave space for them on the right.                                                                                                                                 |
+| `navigationWidget` | 1–4 | 1 | One per sibling state. Right-aligned. All `navigationWidget`s in the same header row must have identical `sizeX`.                                                                                                                                                                                  |
+| `actionButton` | 1 | 1 | Maximum 1 per header. Must be the rightmost widget (`col + 1 = 24`).                                                                                                                                                                                                                               |
+| `connectRealDevices` | 4 | 1 | Header zone only (row 0). When no `actionButton` is present, must be the rightmost widget (`col + sizeX = 24`). When an `actionButton` is present, place immediately before it (e.g. `col: 19, sizeX: 4` with `actionButton` at `col: 23, sizeX: 1`).                                              |
+
+### 2.2 Data Display Widgets
+
+| Widget | sizeX | sizeY | Rules |
+|--------|-------|-------|-------|
+| `horizontalValueCard` | 6–12 | 1–2 (max 2) | **Preferred value card type.** Never use `simpleGauge` as a substitute. Placement rules in Section 4.5. |
+| `infoCard` | 8–12 | 3 (≤5 keys) or 4 (>5 keys) | Body zone only. Anchored to left (`col: 0`) or right (`col + sizeX = 24`) corner. Never placed in the middle of a row. Must start at the first body row. |
+| `alarmCount` | 2–24 | 1–2 (max 2; recommended: 1) | Combined with other widgets: `sizeX 2–4, sizeY 1`. Alone in its row: expand `sizeX` to fill available columns. Never taller than 2 rows. |
+
+### 2.3 Map & Table Widgets
+
+| Widget | sizeX | sizeY | Rules |
+|--------|-------|-------|-------|
+| `outdoorMap` / `indoorMap` | 12–24 | 6–10 | Full width (`sizeX: 24`) only when sole large widget in the state. |
+| `entityTable` | 12–24 | 5–8 | Full width only when sole large widget in the state. Absorbs extra vertical space. |
+| `alarmTable` | 12–24 | 5+ | Prefer `sizeX: 12` paired with another widget filling the remaining 12 columns. Full width (`sizeX: 24`) is acceptable when the state has few other widgets and no suitable pairing widget exists. Absorbs all extra vertical space — can be very tall; this is correct. |
+
+### 2.4 Chart Widgets
+
+Primary content of `statistics` states. Also valid as secondary widgets in the `standardDetail` body zone.
+
+| Widget | sizeX | sizeY |
+|--------|-------|-------|
+| `chart` / `stateChart` / `rangeChart` | 8–12 | 4–6 |
+| `valueChartCard` | 4–8 | 2–3 |
+| `pieChart` | 6–12 (max 12) | 3–6 (min 3) |
+
+### 2.5 Gauge Widgets
+
+| Widget | sizeX | sizeY | Rules |
+|--------|-------|-------|-------|
+| `simpleGauge` | 4–8 | 4–6 | **Never full width** (`sizeX: 24`). **Never use as a value card substitute** — use `horizontalValueCard` instead. If a gauge row has unused columns, fill them with a map or table. |
+
+### 2.6 Status & Progress Widgets
+
+| Widget | sizeX | sizeY | Rules |
+|--------|-------|-------|-------|
+| `batteryLevel` | 4–6 | 2 (min 2) | Must use **identical sizeX and sizeY** as `signalStrength`. Always placed adjacent to each other. |
+| `signalStrength` | 4–6 | 2 | Must use **identical sizeX and sizeY** as `batteryLevel`. Always placed adjacent to each other. |
+| `progressBar` | 6–8 | 2 (always) | Default `sizeX: 6` (1/4 of grid). May increase to `sizeX: 8` for equal distribution (e.g. 3 bars filling a full row). Group into as few rows as possible. See Section 4.5. |
+
+---
+
+## 3. State Types
+
+### 3.1 `collection`
+
+- **Purpose**: High-level overview of all entities — geographical distribution and entity lists.
+- **Row budget**: 11 rows (body only, starts at row 0).
+- **FORBIDDEN**: `headerCard`, `navigationWidget`, `actionButton`.
+- **Key content**: Large maps, entity tables, aggregated summary cards. No chart widgets.
+
+### 3.2 `standardDetail`
+
+- **Purpose**: In-depth view of a selected entity with **3 or fewer telemetry keys**.
+- **Row budget**: 1 header + 11 body = 12 total.
+
+**Header Zone (row 0, sizeY: 1)**
+- `headerCard` at `col: 0`. Use `sizeX: 24` only when no `actionButton` or `connectRealDevices` is present.
+- `connectRealDevices` (if present): `sizeX: 4`. When no `actionButton` is present, rightmost widget (`col: 20, sizeX: 4`). When `actionButton` is present, place immediately before it (`col: 19, sizeX: 4`).
+- `actionButton` (if any) at far right: `col + sizeX = 24`.
+- Empty columns between `headerCard` and the right-aligned widgets are acceptable.
+- **FORBIDDEN**: Any data widget — value cards, charts, tables, maps, gauges, `navigationWidget`.
+
+**Body Zone (starts at row 1)**
+
+Top-to-bottom widget priority (see Section 4.2):
+1. **Value Cards** (`horizontalValueCard`) — always first. See Section 4.5 for placement rules.
+2. **Map + Entity Table** — immediately after cards.
+3. **Alarm Table / Charts** — below map and entity table.
+
+### 3.3 `switcherDetail`
+
+- **Purpose**: Navigation hub for an entity with **more than 3 telemetry keys**. Contains **no data widgets**.
+- **Row budget**: 1 row only. Set `autoFillHeight: false`.
+
+**Header Row (row 0, sizeY: 1)**
+- `headerCard` at `col: 0`.
+- `navigationWidget`(s) right-aligned, one per sibling state, `sizeX 1–4`.
+- `connectRealDevices` (if present): `sizeX: 4`. Placed after `navigationWidget`(s) and before `actionButton` (if present). When no `actionButton`, it is the rightmost widget.
+- `actionButton` (optional, max 1) as rightmost widget: `col + sizeX = 24`.
+- Empty columns between `headerCard` and the navigation group are acceptable.
+- **FORBIDDEN**: Any data widget.
+
+```
+// 2 siblings + action button
+Row 0: [headerCard col=0 sizeX=15][nav col=15 sizeX=4][nav col=19 sizeX=4][btn col=23 sizeX=1]
+
+// 2 siblings + connectRealDevices + action button
+Row 0: [headerCard col=0 sizeX=11][nav col=11 sizeX=4][nav col=15 sizeX=4][conDev col=19 sizeX=4][btn col=23 sizeX=1]
+
+// 2 siblings, no action button
+Row 0: [headerCard col=0 sizeX=16][nav col=16 sizeX=4][nav col=20 sizeX=4]
+
+// 2 siblings + connectRealDevices, no action button
+Row 0: [headerCard col=0 sizeX=12][nav col=12 sizeX=4][nav col=16 sizeX=4][conDev col=20 sizeX=4]
+```
+
+### 3.4 `overview`
+
+- **Purpose**: Data view with latest values, alarms, and status — no header, no navigation, no charts.
+- **Row budget**: 11 rows (body only, starts at row 0).
+- **FORBIDDEN**: `headerCard`, `navigationWidget`, `actionButton`, and all chart widgets (`chart`, `stateChart`, `rangeChart`, `valueChartCard`, `pieChart`).
+- **Key content**: Value cards, gauges, tables, info cards, alarm counts, battery/signal, progress bars.
+- Body zone placement follows the same top-to-bottom priority defined in Section 4.2.
+- **CRITICAL**: All widgets combined must fill exactly 11 rows.
+
+### 3.5 `statistics`
+
+- **Purpose**: Chart-only analytics view — no header, no navigation, no non-chart widgets.
+- **Row budget**: 11 rows (body only, starts at row 0).
+- **FORBIDDEN**: `headerCard`, `navigationWidget`, `actionButton`, and all non-chart widgets (`horizontalValueCard`, `infoCard`, `alarmCount`, `batteryLevel`, `signalStrength`, `progressBar`, `simpleGauge`, `entityTable`, `alarmTable`, maps).
+- **Required content**: Chart widgets only (`chart`, `stateChart`, `rangeChart`, `valueChartCard`, `pieChart`).
+- **CRITICAL**: All widgets combined must fill exactly 11 rows.
+
+---
+
+## 4. Layout Composition Rules
+
+### 4.1 Global Constraints
+
+1. **Full row coverage**: Sum of `sizeX` for all widgets in a row must equal 24. No empty columns.
+   - **Exception**: The header row in `switcherDetail` is intentionally partial.
+2. **No empty gaps**: No unused rows between widgets.
+3. **No overlaps**: Widgets cannot share the same grid cells.
+4. **Grouping**: Place related widgets adjacent to each other.
+
+### 4.2 Widget Placement Hierarchy
+
+Within the body zone, always arrange widgets in this top-to-bottom order:
+
+1. **Cards** (`horizontalValueCard`, `infoCard`, `alarmCount`, `batteryLevel`, `signalStrength`) — always at the very top.
+2. **Map + Entity Table** — immediately after cards; primary data views.
+3. **Alarm Table / Charts** — below map and entity table; secondary content.
+
+Never place an alarm table or chart above a map or entity table. Never place a map or entity table above cards.
+
+### 4.3 Width Rules
+
+- **Large widget full width** (`sizeX: 24`): Only allowed when it is the **sole** large widget in the state.
+- **2 large widgets**: Each `sizeX: 12`, placed side by side.
+- **3+ large widgets**: Reduce both `sizeX` and `sizeY` of each large widget so they all fit within the row budget. Do **not** give every large widget `sizeX: 12` — when the state has many large widgets, they must share space equally. Arrange in a grid: pair widgets side by side (`sizeX: 12` each) and stack pairs vertically, reducing `sizeY` per widget proportionally. With 4 large widgets, use 2 rows of 2; with 5+, use 3 rows and shrink `sizeY` further (minimum `sizeY: 3` for any large widget). An odd last widget may take full width only if no peer can be placed beside it.
+- **4+ large widgets — compact mode**: Maps, entity tables, and alarm tables must all use the **minimum viable sizeY** (maps: `sizeY: 4–5`, entity tables: `sizeY: 4–5`, alarm tables: `sizeY: 3–4`) so every widget fits within the row budget. Do not let any single widget dominate the layout.
+
+### 4.4 Space Absorption
+
+Only large widgets (maps, tables) absorb extra vertical space. Small widgets must stay within their size guidelines.
+
+- ✅ Increase `sizeY` of `alarmTable`, `entityTable`, or a map to fill remaining rows.
+- ❌ Never increase `sizeY` of `horizontalValueCard`, `simpleGauge`, `infoCard`, `batteryLevel`, `signalStrength`, `alarmCount`, or chart widgets beyond their guidelines.
+
+When small widgets and a large table coexist: pack small widgets at their natural size at the top, give all remaining vertical space to the table.
+
+### 4.5 Widget Combination Rules
+
+**Value Cards (`horizontalValueCard`)**
+
+Always occupy the **first row(s) of the Body Zone** before any other content. Max `sizeY: 1`. Min `sizeX: 6` per card. Never more than 4 cards per row. Never more than 2 cards in a half-row (12 columns).
+
+| Quantity | Layout |
+|----------|--------|
+| 1–2 cards | Left half only (`col 0–11`). 1 card → `sizeX: 12`; 2 cards → `sizeX: 6` each. Fill right half (`col: 12, sizeX: 12`) with another widget. |
+| 3–4 cards | Full row only (no other widget shares the row). 3 cards → `sizeX: 8` each; 4 cards → `sizeX: 6` each. |
+| 5+ cards | Continue into a second card row at top, same rules per row. |
+
+**Progress Bars**
+
+Each `progressBar` always has `sizeX: 6` and `sizeY: 2`. Group into as few rows as possible.
+
+| Quantity | Layout |
+|----------|--------|
+| 1 | `sizeX: 6`. Fill remaining 18 columns with other widget(s). |
+| 2 | Both in 1 row (`sizeX: 6` each). Fill remaining 12 columns with another widget. |
+| 3 | All in 1 row (`sizeX: 8` each, full 24 columns). |
+| 4 | Option A (preferred): all in 1 row (`sizeX: 6` each). Option B: 2 per row, fill right half with another widget each row. |
+| Odd count | Distribute evenly in 1 row: `sizeX = 24 / count`. |
+
+**Alarm Table + Small Widgets**
+
+Place all small widgets at their natural/minimum size at the top. Give all remaining vertical space to the alarm table — it can be very tall; this is correct.
+
+**Paired Small Widgets + Large Table (Vertical Split)**
+
+For an even number of small/medium widgets alongside a large table:
+- **Left half** (`col 0–11, sizeX: 12`): stack all small/medium widgets in pairs at their natural size.
+- **Right half** (`col 12–23, sizeX: 12`): assign entirely to the large table, stretching it to fill all available rows.
+
+---
+
+## 5. Layout Patterns
+
+Reference layouts for common widget combinations. Match by checking the **Condition**.
+
+---
+
+### Pattern 1 — Single Hero
+
+**Condition**: Exactly 1 large widget, no other large widgets in the state.
+
+```
+Row 0:  [ entityTable col=0, sizeX=24, sizeY=11 ]
+```
+
+---
+
+### Pattern 2 — Dual Hero
+
+**Condition**: Exactly 2 large widgets of the same type or map + table.
+
+```
+Row 0:  [ map col=0, sizeX=12, sizeY=11 ][ entityTable col=12, sizeX=12, sizeY=11 ]
+```
+
+---
+
+### Pattern 3 — Map + 2 Tables
+
+**Condition**: 1 map + 2 entity tables, map spans full height, tables stack on the right.
+
+```
+Row 0:  [ map col=0, sizeX=12, sizeY=11 ][ entityTable col=12, sizeX=12, sizeY=6 ]
+Row 6:  [ map (continues)               ][ entityTable col=12, sizeX=12, sizeY=5 ]
+```
+
+---
+
+### Pattern 4 — Value Cards + Hero(es)
+
+**Condition**: Value cards above 1 or 2 large widgets.
+
+```
+// 3 value cards + map + entityTable (total: 1 + 10 = 11 rows)
+Row 0:  [ card col=0, sizeX=8, sizeY=1 ][ card col=8, sizeX=8, sizeY=1 ][ card col=16, sizeX=8, sizeY=1 ]
+Row 1:  [ map col=0, sizeX=12, sizeY=10 ][ entityTable col=12, sizeX=12, sizeY=10 ]
+```
+
+---
+
+### Pattern 5 — Map + Entity Table + Secondary
+
+**Condition**: Map and entity table as primary view, alarm table or chart below.
+
+```
+// No cards — map + entityTable + alarmTable + chart (total: 6 + 5 = 11 rows)
+Row 0:  [ map col=0, sizeX=12, sizeY=6 ][ entityTable col=12, sizeX=12, sizeY=6 ]
+Row 6:  [ alarmTable col=0, sizeX=12, sizeY=5 ][ chart col=12, sizeX=12, sizeY=5 ]
+
+// 2 value cards + map + entityTable + alarmTable (total: 1 + 5 + 5 = 11 rows)
+// alarmTable alone in last row — full width acceptable here (few widgets, no pairing candidate)
+Row 0:  [ card col=0, sizeX=12, sizeY=1 ][ card col=12, sizeX=12, sizeY=1 ]
+Row 1:  [ map col=0, sizeX=12, sizeY=5 ][ entityTable col=12, sizeX=12, sizeY=5 ]
+Row 6:  [ alarmTable col=0, sizeX=24, sizeY=5 ]
+```
+
+---
+
+### Pattern 6 — Table + Alarm Table
+
+**Condition**: Entity list with alarm monitoring, no map.
+
+```
+// total: 11 rows
+Row 0:  [ entityTable col=0, sizeX=12, sizeY=11 ][ alarmTable col=12, sizeX=12, sizeY=11 ]
+```
+
+---
+
+### Pattern 7 — Table + Chart
+
+**Condition**: Entity list with a business metric chart, no map.
+
+```
+// total: 11 rows
+Row 0:  [ entityTable col=0, sizeX=12, sizeY=11 ][ chart col=12, sizeX=12, sizeY=11 ]
+```
+
+---
+
+### Pattern 8 — Multiple Charts
+
+**Condition**: `statistics` state — chart widgets only.
+
+```
+// 4 charts (total: 6 + 5 = 11 rows)
+Row 0:  [ chart col=0, sizeX=12, sizeY=6 ][ stateChart col=12, sizeX=12, sizeY=6 ]
+Row 6:  [ rangeChart col=0, sizeX=12, sizeY=5 ][ chart col=12, sizeX=12, sizeY=5 ]
+
+// 2 charts (total: 11 rows)
+Row 0:  [ chart col=0, sizeX=12, sizeY=11 ][ stateChart col=12, sizeX=12, sizeY=11 ]
+```
+
+---
+
+### Pattern 9 — Gauges + Info Card
+
+**Condition**: `overview` state or `standardDetail` body with entity attributes and few telemetry values.
+
+```
+// infoCard + 2 gauges on top, 3 gauges below, alarmTable absorbs rest (total: 4 + 4 + 3 = 11 rows)
+// alarmTable alone in last row — full width acceptable here (few widgets, no pairing candidate)
+Row 0:  [ infoCard col=0, sizeX=12, sizeY=4 ][ simpleGauge col=12, sizeX=6, sizeY=4 ][ simpleGauge col=18, sizeX=6, sizeY=4 ]
+Row 4:  [ simpleGauge col=0, sizeX=8, sizeY=4 ][ simpleGauge col=8, sizeX=8, sizeY=4 ][ simpleGauge col=16, sizeX=8, sizeY=4 ]
+Row 8:  [ alarmTable col=0, sizeX=24, sizeY=3 ]
+```
+
+---
+
+### Pattern 10 — Alarm Table + Small Widgets
+
+**Condition**: Alarm table is the primary content, accompanied by a few small widgets.
+
+```
+// infoCard + 2 value cards + battery + signal + alarmTable (total: 3 + 8 = 11 rows)
+// alarmTable alone in last row — full width acceptable here (few widgets, no pairing candidate)
+Row 0:  [ infoCard col=0, sizeX=12, sizeY=3 ][ horizontalValueCard col=12, sizeX=12, sizeY=1 ]
+Row 1:  [ infoCard (continues)               ][ horizontalValueCard col=12, sizeX=12, sizeY=1 ]
+Row 2:  [ infoCard (continues)               ][ batteryLevel col=12, sizeX=6, sizeY=2 ][ signalStrength col=18, sizeX=6, sizeY=2 ]
+Row 3:  [ alarmTable col=0, sizeX=24, sizeY=8 ]
+```
+
+---
+
+### Pattern 11 — Paired Small Widgets + Large Table (Vertical Split)
+
+**Condition**: Even number of small/medium widgets alongside a large table.
+
+```
+// 4 value cards + 2 gauge pairs on left; alarmTable on right (total: left = 1+1+4+5 = 11, right alarmTable sizeY=11)
+Row 0:  [ horizontalValueCard col=0, sizeX=6, sizeY=1 ][ horizontalValueCard col=6, sizeX=6, sizeY=1 ][ alarmTable col=12, sizeX=12, sizeY=11 ]
+Row 1:  [ horizontalValueCard col=0, sizeX=6, sizeY=1 ][ horizontalValueCard col=6, sizeX=6, sizeY=1 ][ alarmTable (continues)                ]
+Row 2:  [ simpleGauge col=0, sizeX=6, sizeY=4        ][ simpleGauge col=6, sizeX=6, sizeY=4         ][ alarmTable (continues)                ]
+Row 6:  [ simpleGauge col=0, sizeX=6, sizeY=5        ][ simpleGauge col=6, sizeX=6, sizeY=5         ][ alarmTable (continues)                ]
+// Left half: 1+1+4+5 = 11 rows. Small widgets were NOT stretched (sizeY: 5 is within gauge guideline of 4–6).
+```
+
+---
+
+### Pattern 12 — Many Large Widgets (Map + Alarm + Multiple Tables)
+
+**Condition**: 4+ large widgets on a single state (e.g., 1 map + 1 alarm table + 3 entity tables). Too many large widgets to give each half the screen — use compact layout.
+
+```
+// map + alarmTable on top row, 3 entityTables equally split on bottom row (total: 6 + 5 = 11 rows)
+Row 0:  [ map col=0, sizeX=12, sizeY=6 ][ alarmTable col=12, sizeX=12, sizeY=6 ]
+Row 6:  [ entityTable col=0, sizeX=8, sizeY=5 ][ entityTable col=8, sizeX=8, sizeY=5 ][ entityTable col=16, sizeX=8, sizeY=5 ]
+
+// map + alarmTable on top row, 2 entityTables equally split on bottom row (total: 6 + 5 = 11 rows)
+Row 0:  [ map col=0, sizeX=12, sizeY=6 ][ alarmTable col=12, sizeX=12, sizeY=6 ]
+Row 6:  [ entityTable col=0, sizeX=12, sizeY=5 ][ entityTable col=12, sizeX=12, sizeY=5 ]
+```
+
+**Rules for this pattern:**
+- Top row: map and alarm table side by side, each `sizeX: 12, sizeY: 6`.
+- Bottom row: entity tables share the full width equally (`sizeX = 24 / count`). For 3 tables: `sizeX: 8` each. For 2 tables: `sizeX: 12` each.
+- All bottom-row tables have identical `sizeX` and `sizeY`.

thingsboard_cli/resources/prompts/solutions/dashboard/resources/state-layout/dashboard-state-layout-schema.json

@@ -0,0 +1,45 @@
+{
+  "$schema": "https://json-schema.org/draft/2020-12/schema",
+  "title": "Dashboard state layout",
+  "description": "A schema for generating dashboard state layout.",
+  "type": "object",
+  "properties": {
+    "widgetPositions": {
+      "type": "array",
+      "items": {
+        "type": "object",
+        "properties": {
+          "widgetName": {
+            "type": "string",
+            "description": "Reference to widget name from State Assistant"
+          },
+          "position": {
+            "type": "object",
+            "properties": {
+              "row": {
+                "type": "integer"
+              },
+              "col": {
+                "type": "integer"
+              },
+              "sizeX": {
+                "type": "integer"
+              },
+              "sizeY": {
+                "type": "integer"
+              }
+            },
+            "required": [
+              "row",
+              "col",
+              "sizeX",
+              "sizeY"
+            ]
+          }
+        },
+        "required": ["widgetName", "position"]
+      }
+    }
+  },
+  "required": ["widgetPositions"]
+}

thingsboard_cli/resources/prompts/solutions/dashboard/resources/state-widget/action-button/widget-capabilities.md

@@ -0,0 +1,20 @@
+### 'actionButton' widget
+
+The 'actionButton' widget displays a clickable button that triggers a user-defined action when clicked. This widget is useful to perform edit settings/set thresholds actions.
+
+Data source settings:
+* Supports a single data source and able to show multiple entities.
+
+Settings Button Example: Displays a button that opens a dialog to edit settings for a selected device. 
+```json
+{
+  "title": "Edit Device",
+  "widgetClass": "actionButton",
+  "datasource": ["selectedDevice"],
+  "iconName": "edit",
+  "actions": ["edit-device-settings"]
+}
+```
+Few things to notice:
+- The actions array must contain exactly one object with actionTrigger: "click".
+- The label property is required and must be a non-empty string.