thingsboard-cli 4.3.1.5__tar.gz → 4.4.0.1__tar.gz

thingsboard_cli-4.4.0.1/CHANGELOG.md

@@ -0,0 +1,268 @@
+# Changelog
+
+All notable changes to ThingsBoard CLI are documented in this file.
+
+## [4.4.0.1] — Unreleased
+
+First-run usability release.
+
+### Added
+
+- **`tb config --browser`.** Connect on a local web page instead of the
+  terminal, in two steps: select ThingsBoard Cloud (North America),
+  ThingsBoard Cloud (Europe), or your own server; then paste an API key.
+  For your own server, `https://` is optional: the CLI tries HTTPS first,
+  then HTTP, and warns when the key would travel over plain HTTP. AI agents run commands
+  without an interactive terminal, so they cannot type into the wizard. The
+  page runs on `127.0.0.1` with a one-time token, tests the connection, and
+  closes after 15 minutes. The key never appears in the terminal, the chat,
+  or the logs, and the browser does not offer to save it as a password.
+- **`tb init` connects the CLI and shows the next steps.** `tb init` checks
+  the ThingsBoard connection and prints `Connected to <url>`. If the CLI is
+  not connected, an interactive `tb init` offers to connect: it opens the API
+  keys page and tests the key. `--browser` uses the local web page instead
+  (for AI agents). At the end, `tb init` shows how to start the agent and an
+  example prompt. Non-interactive runs never wait for input; `--skip-config`
+  skips the connection step.
+- **`tb emulator run [SOLUTION]`.** Sends live demo data to ThingsBoard for a
+  limited time (`--duration`, default 10 minutes; `--interval`, default 5
+  seconds) from the solution's emulators, so the dashboard changes while you
+  watch it. Each device continues from its latest stored value. The command
+  shows the dashboard links at the start. Press Ctrl+C to stop.
+- **`tb init <folder>`.** Creates the project in a new or existing folder.
+- **`tb init --guided`.** Asks for the project folder and offers to start
+  Claude Code or Antigravity in it. The one-line installer uses this option.
+
+### Changed
+
+- **Clear connection errors.** A failed connection now says what to fix: an
+  invalid or expired API key, a user without permissions, a URL that is not a
+  ThingsBoard server, a host that was not found, a connection or TLS problem.
+  Before, the message was only `HTTP 401` or a raw network error.
+- **The `tb config` wizard lets you try again.** On a failed connection in an
+  interactive terminal, the wizard asks `Try again?` and does not save a
+  broken profile unless you confirm. Piped input keeps the previous behavior.
+  The wizard also shows the page where you create an API key.
+- **The agent deploys after you confirm.** At the end of a build, update, or
+  standalone change, the agent asks once: "Deploy to ThingsBoard and stream
+  live demo data for 5 minutes?" On approval it runs `tb push --run-tasks`,
+  starts `tb emulator run` in the background, and shows the dashboard links.
+  Progress notices in the middle of a build no longer tell you to push.
+- **Demo history follows the solution.** The design picks how many days of
+  history the emulators write (7 by default; 30 for monthly patterns such as
+  billing or consumption; up to 90 for seasonal trends). Generated dashboards
+  open on a realtime window of the same length, so charts show the whole
+  history and keep moving when live data arrives.
+- **README:** one-line installers, `tb init`, and the `TB_URL`, `TB_API_KEY`,
+  `TB_PROFILE`, `TB_CONFIG_HOME` and `TB_DEBUG` environment variables.
+- **Dashboards use HTML pages by default.** On ThingsBoard 4.4.0.1 and later
+  (and when the version is unknown), the agent builds every dashboard state as
+  an HTML page. Stock widgets appear only in embedded helper states: maps, and
+  the alarm table when users acknowledge or clear alarms. Pages open the stock
+  entity dialogs from their own buttons. On older servers the agent keeps
+  the previous behavior: stock widgets in a grid, custom content only on
+  request. Existing dashboards keep their layout; only new or rebuilt states
+  follow the new default.
+- **Quick builds for small requests.** "My sensor sends {…}. Show it on a
+  dashboard." now builds only the device, the alarm you asked for, demo
+  data and one dashboard — no interview, no approval stops, and no made-up
+  customers, roles or users. Say "full solution" for the full design flow.
+  Grow a quick build later with `update-solution`: when you add the first
+  customer, user group or role, the agent writes the full role design and
+  moves the existing dashboard to the new administrator role instead of
+  creating a second one.
+- **No empty folders in new projects.** `tb init` and `tb solution new` no
+  longer create every entity folder up front; the CLI creates a folder when
+  it saves the first file there. The empty root folders next to
+  `solutions/<name>/` looked like a second copy of the solution. `tb init`
+  also writes a short `README.md` that explains the project layout (an
+  existing README is kept). Existing projects are not changed.
+
+### Fixed
+
+- **Embedded charts no longer show "No data" for a selected device.** The
+  agent could name a state alias parameter `entityId` while the page
+  published the device as the default state entity, so the alias resolved to
+  nothing. The alias template, the composition rules and a new validation
+  check now keep the two in step.
+- **Standalone dashboards no longer look for a missing dashboard group.**
+  They are built for the built-in tenant administrator, who sees every tenant
+  dashboard, so the agent no longer needs a "Dashboards for Default" group.
+- **Feedback is asked only after the user sees a result.** `tb validate` no
+  longer flags a feedback ask. The agent runs `validate` in the middle of a
+  solution build, so the question appeared before the dashboards existed.
+  Only a successful `tb push` flags the ask now.
+  The agent asks at least 15 minutes after the push, so you can look at the
+  result first, and only at the end of its reply — it handles your request
+  first.
+- **`tb push --run-tasks` prints the dashboard links last.** The links came
+  before the emulators and the calculated field reprocessing ran, so a quick
+  click could show an empty dashboard.
+
+## [Unreleased] — Pre-v1 Release Audit Fixes
+
+This release closes all 71 findings from the Pre-v1 release audit
+(`docs/audit/2026-04-29-cli-release-audit.md`). The audit document has been
+annotated with a `Status:` line per finding pointing at the closing commit.
+
+### Security
+
+- **Redact sensitive values in `--debug` output.** A new redactor walks the
+  request/response payload printed by the debug logger and masks values for
+  keys matching a denylist (`password`, `accessToken`, `refreshToken`,
+  `apiKey`, `Authorization`, etc.). Pasting `--debug` output into a Slack
+  thread or bug report no longer leaks live credentials. (CC-01)
+- **Hide credential prompts.** The interactive `tb config` wizard's API-key
+  prompt now uses `hide_input=True`, matching the password prompt. (P0-08)
+- **Compact connectivity-error formatting.** Failed `tb config` connectivity
+  tests no longer dump the upstream HTML body or HTTP header dictionary.
+  Errors collapse to `HTTP <status> <reason>` for `ApiException`, or a
+  truncated `str(exc)` for everything else. (P0-15)
+
+### Correctness — broken commands now work
+
+- **`tb role list`, `tb entity-group list`, `tb telemetry get --limit`** were
+  broken with a Pydantic-strict `Input should be a valid string` error
+  because the SDK declares pagination params as `str` but the CLI passed
+  `int`. New `coerce_page_kwargs` helper introspects the SDK signature and
+  casts where needed. (P0-01, P0-02, P0-03)
+- **`tb telemetry keys`, `tb calculated-field save`, `tb alarm-rule save`**
+  failed because camelCase JSON dicts were passed straight into Pydantic
+  models that only declared a `serialization_alias`. New `dict_to_model`
+  helper routes save payloads through the SDK's `from_dict()` classmethod,
+  which translates camelCase→snake_case and dispatches discriminated
+  unions correctly. Also covers the `save-permission` and `share` payloads.
+  (P0-04, P0-06, P0-07, CC-06)
+- **`tb telemetry get -f json`** silently dropped the `ts` timestamp on every
+  datapoint. Output now preserves `{"ts": ..., "value": ...}` per key.
+  (P0-05)
+- **`tb push <unknown-solution>`** silently fell back to pushing root
+  entities. It now exits non-zero and lists available solutions. Same for
+  `tb validate`. (P0-09)
+- **`tb device list`** showed `Active: -` and a duplicated `Type`/`Profile`
+  column. The list now calls `get_all_device_infos` so `Active` populates,
+  and the `Type` column is removed (`device.type` IS the profile name in
+  TB 4.3+). (P0-10, P0-11)
+- **`tb device credentials`** showed `Credentials Value: -` for ACCESS_TOKEN
+  credentials. Output is now type-aware: tokens render under an `Access
+  Token:` label. (P0-13)
+- **`tb relation find-from`/`find-to`** had blank `To`/`To Type`/`To Name`
+  columns due to wrong accessors. Fixed to read `.var_from`, `.to`,
+  `.from_name`, `.to_name`. (P0-14)
+- **`tb asset list`/`get`** dropped the duplicated `Type` column. (P0-12)
+- **`tb alarm-rule list`/`get`** read `.entity_id.entity_type` instead of
+  the non-existent `.entity_type` field. (P1-06, P1-09)
+
+### New commands
+
+- **`tb alarm save | ack | clear | assign | unassign`** — full alarm
+  lifecycle. (P2-09)
+- **`tb attributes get | list | delete`** — read and remove attributes per
+  scope. (P1-10)
+- **`tb dashboard assign-customer | unassign-customer | add-to-group |
+  remove-from-group`** — wrap the entity-group membership API used by
+  TB 4.3+ for dashboard assignment. (P2-10)
+- **`tb rule-chain export <id> [--output PATH]`** — dump a rule chain plus
+  metadata as JSON. (P2-14)
+- **`tb solution list | delete`** — discover and remove solutions inside a
+  project. (P2-29)
+- **`tb telemetry delete <ENTITY_TYPE> <ENTITY_ID> --keys ...`** — delete
+  timeseries by key with optional time range. (P2-15)
+
+### UX & polish
+
+- **Standardize `--type` flag.** `--types` and `--type-list` now exist as
+  deprecated aliases on `tb alarm list` and `tb calculated-field list`;
+  using either prints a deprecation warning to stderr. (P1-12)
+- **Standardize `--format` flag.** `--format` is now a Choice over
+  `{table, json}` enforced by Typer; `--help` enumerates the values; invalid
+  values exit non-zero before the network. (CC-03, P2-27)
+- **Standardize `--sort-order` flag.** Now a Choice over `{ASC, DESC}`,
+  validated client-side. (CC-09)
+- **Friendlier validation errors for `--json`.** Invalid inline JSON shows
+  `Invalid JSON in --json: <msg> (line N, column N)` without the bare
+  `JSONDecodeError:` prefix. Path-like inputs that don't exist show
+  `JSON file '<path>' not found`. (P2-02, P2-05, P2-18)
+- **Tighter delete UX.** `tb <entity> delete <not-a-uuid>` now exits non-zero
+  with a hint pointing at `tb <entity> get '<value>' -f json | jq -r '.id.id'`
+  before any confirmation prompt. Applied to `device`, `asset`, `customer`.
+  (P1-02)
+- **`--name-conflict-policy` validation.** Invalid values are rejected with
+  the allowed list before the SDK is called. (P1-01)
+- **`-H` falls back to `--help` for non-API commands.** `tb config show -H`,
+  `tb init -H`, `tb push -H` now print the regular `--help` instead of
+  exiting silently. (P2-19)
+- **Empty results render as "No results found"** instead of a blank table
+  with `Page 1 of 0`. (CC-04)
+- **Past-last-page warning.** Requesting a page beyond the last now prints
+  a yellow warning above the footer. (P2-01)
+- **ISO-8601 timestamps with epoch.** `Created` rows show
+  `2026-04-29T14:30:45.123Z (1714403445123)` — human-readable plus
+  grep-able. Applied across device/asset/customer/user/profile detail
+  views. (P1-03)
+- **Bare enum rendering.** SDK enum values render as `ACCESS_TOKEN`, not
+  `DeviceCredentialsType.ACCESS_TOKEN`. (CC-02)
+- **Conditional "entity files" hint.** Pydantic ValidationError no longer
+  appends a misleading "Check that entity files have required fields" hint
+  to errors that came from CLI args, only file-loaded entities. (CC-05)
+- **`tb config show` Mode row.** When run inside a project, `tb config show`
+  appends `Mode: local|remote`. (P2-21)
+- **`tb config remove` cleanup.** Removing the current default profile
+  clears or auto-picks `default_profile`; removing a nonexistent profile
+  lists available profiles. (P1-14, P2-20)
+- **Better default `.gitignore`.** `tb init` writes a richer default
+  including `__pycache__/`, `*.pyc`, `.venv/`, `.DS_Store`, `solution.json`,
+  `*.local.*`. (P2-22)
+- **`init` success polish.** Path uses `Path.relative_to`; output lists
+  `tasks/` and the gitignore status. (P2-16, P2-23)
+- **`push` always emits per-entity-type counts.** `created`/`updated`/
+  `unchanged` lines on idempotent re-pushes, on `--all`, and with
+  `--skip-validate`. (P2-24, P2-25, P2-26)
+- **`tb user save` UX.** `--authority` Choice flag (default `TENANT_ADMIN`),
+  email shown in the success line, and the
+  `--send-activation-mail/--no-send-activation-mail` flag was renamed to
+  `--activation-mail/--no-activation-mail` to fit the help table.
+  (P1-04, P1-05, P2-03)
+- **`tb dashboard list` Customers column.** Renamed from `Assigned`,
+  populated with assigned customer titles when present. (P2-07)
+- **`tb dashboard get` description fixed.** `-H` no longer claims it
+  excludes configuration JSON. (P2-06)
+- **`tb device-profile list` / `tb asset-profile list` column parity.**
+  Aligned to `ID | Name | Type | Default`. (P2-04)
+- **`tb entity-group list` zero-args usability.** `OWNER_TYPE` defaults
+  to `TENANT`, `OWNER_ID` defaults to the current tenant via
+  `client.get_user()`, `GROUP_TYPE` becomes a `--type` flag. (P1-13)
+- **`tb entity-group save` --type pre-validation.** Missing `--type` is
+  rejected client-side before tb-pe-client validation. (P2-13)
+- **`tb customer get <title>` resolution by title.** Added title-based
+  lookup alongside UUID. (CC-07)
+- **`tb alarm-rule debug` empty response.** Now prints "No debug events
+  available" instead of an empty string. (P1-07)
+- **Help generator `r"""` docstrings.** Generated SDK model docstrings
+  with backslash sequences (`List\<String\>`) no longer trigger
+  `SyntaxWarning` on import. (CC-08)
+
+### Internals
+
+- **`TB_CONFIG_HOME` env var override.** `ConfigManager` honors
+  `TB_CONFIG_HOME` to redirect the config root, unblocking isolated E2E
+  config tests. (P1-17)
+- **Consolidated `_get_client(ctx)`.** Moved 16 duplicate function bodies
+  into a single `core.client.get_client_from_ctx`. (P1-18)
+- **Cleaned up `hasattr` patterns** across every per-group list/detail
+  render. (P2-28)
+
+### Test coverage
+
+- 732 unit tests pass (up from a pre-audit baseline) with 87% code
+  coverage on changed paths.
+- Every modified command ships with new or extended unit tests AND E2E
+  tests in the same commit. E2E tests skip cleanly without
+  `TB_URL`/`TB_API_KEY`.
+
+---
+
+## Earlier releases
+
+See git history for releases prior to this audit-fix cycle (4.3.1.2 and
+earlier).

thingsboard_cli-4.4.0.1/PKG-INFO

@@ -0,0 +1,106 @@
+Metadata-Version: 2.4
+Name: thingsboard-cli
+Version: 4.4.0.1
+Summary: CLI tool for managing ThingsBoard resources
+Project-URL: Homepage, https://github.com/thingsboard/thingsboard-cli
+Project-URL: Source, https://github.com/thingsboard/thingsboard-cli
+Project-URL: Issues, https://github.com/thingsboard/thingsboard-cli/issues
+Requires-Python: <3.15,>=3.11
+Requires-Dist: click<9.0,>=8.1
+Requires-Dist: filelock<4.0,>=3.13
+Requires-Dist: httpx<1.0,>=0.28
+Requires-Dist: packaging>=24.0
+Requires-Dist: pydantic-settings<3.0,>=2.13
+Requires-Dist: pydantic<3.0,>=2.12
+Requires-Dist: questionary<3.0,>=2.0
+Requires-Dist: rich<15.0,>=14.0
+Requires-Dist: tb-pe-client==4.4.0
+Requires-Dist: textual<2.0,>=0.83
+Requires-Dist: typer<1.0,>=0.24.1
+Requires-Dist: tzdata>=2024.1
+Description-Content-Type: text/markdown
+
+# ThingsBoard CLI
+
+CLI tool for managing ThingsBoard resources from the terminal.
+
+## Installation
+
+Run one command. It installs [uv](https://docs.astral.sh/uv/) if it is missing, installs the CLI, and starts the guided setup:
+
+```bash
+# macOS and Linux
+curl -LsSf https://thingsboard.io/cli/install.sh | sh
+```
+
+```powershell
+# Windows
+powershell -ExecutionPolicy ByPass -c "irm https://thingsboard.io/cli/install.ps1 | iex"
+```
+
+Or install with uv yourself:
+
+```bash
+uv tool install thingsboard-cli
+```
+
+### Upgrading
+
+The CLI checks for updates automatically on launch and prompts to upgrade. You can also upgrade manually:
+
+```bash
+tb update
+```
+
+### Shell Completion
+
+```bash
+# Bash
+tb --install-completion bash
+
+# Zsh
+tb --install-completion zsh
+
+# Fish
+tb --install-completion fish
+```
+
+Restart your terminal after installing completion.
+
+## Usage
+
+```bash
+tb init my-project      # create a project, connect to ThingsBoard, and see the next steps
+tb config               # connect to ThingsBoard (add --browser when an AI agent runs it)
+tb device list
+tb --help
+```
+
+## Environment Variables
+
+| Variable | Purpose |
+|---|---|
+| `TB_URL` | ThingsBoard URL. Overrides the URL of the active profile. |
+| `TB_API_KEY` | API key. Overrides the credentials of the active profile. Use it with `TB_URL` in CI. |
+| `TB_PROFILE` | Name of the profile to use, the same as `--profile`. |
+| `TB_CONFIG_HOME` | Folder for profiles and settings. Default: `~/.thingsboard`. |
+| `TB_DEBUG` | Set to `1` to print every HTTP request and response, the same as `--debug`. |
+
+Example for CI:
+
+```bash
+TB_URL=https://thingsboard.cloud TB_API_KEY=$TB_API_KEY tb push my-solution
+```
+
+## Verbose Help
+
+Use `-H` or `--help-verbose` on any command to see detailed API documentation, JSON schemas, and field descriptions:
+
+```bash
+tb device create -H
+tb dashboard save -H
+```
+
+## Contributing
+
+For local development setup, editable installs, regenerating help text, and publishing, see [CONTRIBUTING.md](https://github.com/thingsboard/thingsboard-cli/blob/master/CONTRIBUTING.md).

thingsboard_cli-4.4.0.1/README.md

@@ -0,0 +1,84 @@
+# ThingsBoard CLI
+
+CLI tool for managing ThingsBoard resources from the terminal.
+
+## Installation
+
+Run one command. It installs [uv](https://docs.astral.sh/uv/) if it is missing, installs the CLI, and starts the guided setup:
+
+```bash
+# macOS and Linux
+curl -LsSf https://thingsboard.io/cli/install.sh | sh
+```
+
+```powershell
+# Windows
+powershell -ExecutionPolicy ByPass -c "irm https://thingsboard.io/cli/install.ps1 | iex"
+```
+
+Or install with uv yourself:
+
+```bash
+uv tool install thingsboard-cli
+```
+
+### Upgrading
+
+The CLI checks for updates automatically on launch and prompts to upgrade. You can also upgrade manually:
+
+```bash
+tb update
+```
+
+### Shell Completion
+
+```bash
+# Bash
+tb --install-completion bash
+
+# Zsh
+tb --install-completion zsh
+
+# Fish
+tb --install-completion fish
+```
+
+Restart your terminal after installing completion.
+
+## Usage
+
+```bash
+tb init my-project      # create a project, connect to ThingsBoard, and see the next steps
+tb config               # connect to ThingsBoard (add --browser when an AI agent runs it)
+tb device list
+tb --help
+```
+
+## Environment Variables
+
+| Variable | Purpose |
+|---|---|
+| `TB_URL` | ThingsBoard URL. Overrides the URL of the active profile. |
+| `TB_API_KEY` | API key. Overrides the credentials of the active profile. Use it with `TB_URL` in CI. |
+| `TB_PROFILE` | Name of the profile to use, the same as `--profile`. |
+| `TB_CONFIG_HOME` | Folder for profiles and settings. Default: `~/.thingsboard`. |
+| `TB_DEBUG` | Set to `1` to print every HTTP request and response, the same as `--debug`. |
+
+Example for CI:
+
+```bash
+TB_URL=https://thingsboard.cloud TB_API_KEY=$TB_API_KEY tb push my-solution
+```
+
+## Verbose Help
+
+Use `-H` or `--help-verbose` on any command to see detailed API documentation, JSON schemas, and field descriptions:
+
+```bash
+tb device create -H
+tb dashboard save -H
+```
+
+## Contributing
+
+For local development setup, editable installs, regenerating help text, and publishing, see [CONTRIBUTING.md](https://github.com/thingsboard/thingsboard-cli/blob/master/CONTRIBUTING.md).

thingsboard_cli-4.4.0.1/extension-starter/extension/target/thingsboard-extension-1.0.0-SNAPSHOT.jar

@@ -0,0 +1,4 @@
+[diffend] Oversized file quarantined before diffing.
+name: thingsboard_cli-4.4.0.1/extension-starter/extension/target/thingsboard-extension-1.0.0-SNAPSHOT.jar
+size: 39342529 bytes
+sha256: b2a093f7037d1d4fcc9b196d9bd5412a02920a181b39e2d02cf54939630a6d7d

thingsboard_cli-4.4.0.1/pyproject.toml

@@ -0,0 +1,90 @@
+[project]
+name = "thingsboard-cli"
+version = "4.4.0.1"
+description = "CLI tool for managing ThingsBoard resources"
+readme = "README.md"
+requires-python = ">=3.11,<3.15"
+dependencies = [
+    "typer>=0.24.1,<1.0",
+    "click>=8.1,<9.0",
+    "pydantic>=2.12,<3.0",
+    "pydantic-settings>=2.13,<3.0",
+    "rich>=14.0,<15.0",
+    "textual>=0.83,<2.0",
+    "questionary>=2.0,<3.0",
+    "httpx>=0.28,<1.0",
+    "tb-pe-client==4.4.0",
+    "packaging>=24.0",
+    "filelock>=3.13,<4.0",
+    # IANA time-zone database for `zoneinfo`. Windows ships no system tz data,
+    # so emulator timeZone validation (ZoneInfo("UTC")) fails without this.
+    "tzdata>=2024.1",
+]
+
+[project.urls]
+Homepage = "https://github.com/thingsboard/thingsboard-cli"
+Source = "https://github.com/thingsboard/thingsboard-cli"
+Issues = "https://github.com/thingsboard/thingsboard-cli/issues"
+
+[project.scripts]
+thingsboard = "thingsboard_cli.main:app"
+tb = "thingsboard_cli.main:app"
+
+[build-system]
+requires = ["hatchling"]
+build-backend = "hatchling.build"
+
+# Pin the core metadata version. hatchling >=1.32 defaults to Metadata-Version
+# 2.5, which twine 6.x rejects (it caps validation at 2.4), so uploads fail.
+# 2.4 is what the whole packaging ecosystem accepts today.
+[tool.hatch.build.targets.sdist]
+core-metadata-version = "2.4"
+
+[tool.hatch.build.targets.wheel]
+core-metadata-version = "2.4"
+packages = ["src/thingsboard_cli"]
+
+[tool.hatch.build.targets.wheel.force-include]
+"scaffold" = "thingsboard_cli/scaffold"
+"extension-starter" = "thingsboard_cli/extension-starter"
+
+[tool.ruff]
+target-version = "py311"
+line-length = 120
+src = ["src", "tests"]
+exclude = ["src/thingsboard_cli/help/_generated"]
+
+[tool.ruff.lint]
+select = ["E", "F", "W", "UP", "B", "SIM", "RUF", "I"]
+
+[tool.mypy]
+python_version = "3.11"
+strict = true
+plugins = ["pydantic.mypy"]
+exclude = ["src/thingsboard_cli/help/_generated"]
+disallow_any_generics = false
+warn_return_any = false
+
+[[tool.mypy.overrides]]
+module = "tb_pe_client.*"
+ignore_missing_imports = true
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]
+markers = [
+    "e2e: end-to-end tests requiring real ThingsBoard instance",
+    "requires_tb: e2e tests that require TB_URL/TB_API_KEY (auto-applied to most e2e files; test_extension.py opts out)",
+    "maven_e2e: e2e tests that require a working Maven wrapper + JDK 17+",
+    "docker_e2e: e2e tests that require a reachable Docker daemon",
+]
+
+[dependency-groups]
+dev = [
+    "mypy>=1.20.0",
+    "pytest>=9.0.2",
+    "pytest-asyncio>=0.24",
+    "pytest-cov>=7.1.0",
+    "pytest-mock>=3.15.1",
+    "respx>=0.22.0",
+    "ruff>=0.15.8",
+]

thingsboard_cli-4.4.0.1/roadmap/connectivity.md

@@ -0,0 +1,111 @@
+# ThingsBoard CLI: device connectivity roadmap
+
+## Goal
+
+The user connects a real device to a solution that the agent built. The user sees live data on the dashboard.
+Later, the agent does most of this work for the user.
+
+## When
+
+This work starts after the release `4.4.0.1`. That release adds the configuration fixes, the live emulator (`tb emulator run`) and the new docs at `/docs/cli/`.
+
+## Current state (CLI 4.4.0)
+
+- `tb device credentials <device-id>` accepts only a device UUID. It shows only the access token.
+- No command shows how to send data from a device.
+- The emulator creates history only: 7 days, with one value each 30 minutes. It runs one time, during `tb push --run-tasks`. After that, the dashboard data does not change.
+- No agent skill helps with device connection.
+- The CLI has no commands for rule chain transformations, integrations, converters or IoT Gateway configuration.
+
+## Milestones
+
+Each milestone is a CLI release, together with its docs. Do the milestones in this order.
+
+### M1 — Connect one device by HTTP or MQTT
+
+**User result:** "I have a device. The CLI tells me exactly how to send data. I see the data on my dashboard."
+
+| # | Change | Details |
+|---|---|---|
+| M1.1 | `tb device connect <name-or-id>` | Find the device by name or UUID. Get its credentials. Show commands that are ready to run: `curl` for HTTP and `mosquitto_pub` for MQTT. Use the host from the active profile. Add `--transport http\|mqtt` and `--format json` (for agents). |
+| M1.2 | Example payload | Make the example payload from the device's emulator definition. If there is none, use the telemetry keys of the device profile. If there are no keys, use `{"temperature": 25}`. |
+| M1.3 | Credential types | Support `ACCESS_TOKEN` and `MQTT_BASIC` fully. For `X509_CERTIFICATE`, show the required files and link to the docs. Do not show secrets unless the user adds `--show-secrets`. |
+| M1.4 | Host and port | HTTP: use the profile URL. MQTT: use the host of the profile URL with port 1883, or port 8883 with `--tls`. Add `--host` and `--port` for self-hosted instances with a different setup. **Verify the MQTT hosts for Cloud NA and Cloud EU before release.** |
+| M1.5 | `tb device connect --wait` | After the commands are shown, wait for the first telemetry from the device (default timeout: 5 minutes). Then show "Data received: temperature=22.5 …" and the dashboard link. This gives the user a clear success message. |
+| M1.6 | `tb device credentials` accepts a name | A small change. It makes the command the same as `tb device get`. |
+| M1.7 | Agent skill `connect-real-device` | The user asks "How do I connect my sensor?" The agent runs `tb device connect --format json`. Then it explains the steps and runs `--wait` while the user sends data. |
+| M1.8 | Skills show the next step | After `tb push`, the standalone skills and the solution skills tell the user: "To send real data, run `tb device connect <name>`." |
+
+**Docs:** the guide "Connect your real device". Add a "Next step" link from the Quickstart.
+
+**Done when:** a new user sends one value with `curl` and sees it on the dashboard in 3 minutes or less.
+
+### M2 — Live emulator as a real device
+
+The first release (`4.4.0.1`) adds `tb emulator run`. That command sends data through the tenant REST API. This milestone changes it to send data the same way a real device does.
+
+**User result:** "The emulator tests my device credentials and my device profile before I connect real hardware."
+
+| # | Change | Details |
+|---|---|---|
+| M2.1 | Send through the device API | Use the device credentials and the host logic from M1.4. Keep the tenant REST API as a fallback with `--via rest`. |
+| M2.2 | Choose the transport | Add `--transport http\|mqtt`. Use the same transport as the device profile by default. |
+| M2.3 | Show errors per device | If a device cannot send, show the device name and the reason, for example "invalid token". Continue with the other devices. |
+
+**Docs:** add the transport options to the emulator section of the Commands reference.
+
+### M3 — Data from devices that does not match the model
+
+**User result:** "My device sends nested JSON or other units. The agent adapts the data, so the dashboard shows the correct values."
+
+| # | Change | Details |
+|---|---|---|
+| M3.1 | Rule chain skill | Add an agent skill that creates and changes rule chains with TBEL transformation nodes. The `tb rule-chain` command exists, but no skill uses it. |
+| M3.2 | Payload analysis | The user gives an example payload. The agent compares it with the device profile. Then the agent suggests one of these: a calculated field, a TBEL transformation, or a change to the model. |
+| M3.3 | Test the transformation locally | Run a TBEL script on an example payload before the push. Check that `tb system test-script` (or a similar command) does this. |
+
+**Docs:** the guide "Adapt your device payload".
+
+### M4 — Many devices
+
+**User result:** "I connect 50 devices without manual work for each device."
+
+| # | Change | Details |
+|---|---|---|
+| M4.1 | Device provisioning | Enable provisioning on a device profile. Show the provision key and the provision secret. Show the device-side request. |
+| M4.2 | Export credentials | `tb device credentials --solution <slug> --format csv`, for factory and installer workflows. |
+| M4.3 | Agent skill | "Prepare my fleet of 50 sensors for connection." The agent selects bulk creation or provisioning. |
+
+**Docs:** the guide "Connect many devices".
+
+### M5 — Gateways and integrations
+
+**User result:** "My devices use Modbus, OPC-UA, LoRaWAN or a vendor cloud. The agent configures the connection."
+
+| # | Change | Details |
+|---|---|---|
+| M5.1 | Integrations and converters | Add CLI commands and a skill for integrations and uplink/downlink converters. Start with HTTP, The Things Stack (TTN) and ChirpStack. This is a large task. Discuss it with the platform team first. |
+| M5.2 | IoT Gateway configuration | The agent creates an IoT Gateway connector configuration (Modbus, OPC-UA, BACnet) from a short description. |
+
+**Docs:** the guides "Connect LoRaWAN devices" and "Connect devices through IoT Gateway".
+
+### M6 — The agent connects the device
+
+**User result:** "I describe my device. The agent connects it."
+
+| # | Change | Details |
+|---|---|---|
+| M6.1 | Firmware and script examples | The agent creates device-side code for common platforms: Arduino/ESP32, Python, Node-RED. It uses the ThingsBoard SDK docs. |
+| M6.2 | Check the full path | The agent runs `tb device connect --wait` and checks the dashboard values. |
+| M6.3 | Research | Find out if the agent can find devices on the local network, or set up a device that the user connected to the computer. |
+
+## Out of scope
+
+- Browser login. It is a separate configuration task.
+- Notifications (email, Slack, Teams). This is a separate roadmap item.
+
+## Open questions
+
+1. What are the MQTT hosts and ports for Cloud NA and Cloud EU? Is TLS required?
+2. Who in the platform team owns the integration APIs for M5?
+3. Do we show device secrets in the terminal by default? Current plan: no.