Skip to content

Updated HTTP Integration#422

Open
stitenko wants to merge 2 commits into
thingsboard:mainfrom
stitenko:05.2026/HTTP-integration
Open

Updated HTTP Integration#422
stitenko wants to merge 2 commits into
thingsboard:mainfrom
stitenko:05.2026/HTTP-integration

Conversation

@stitenko
Copy link
Copy Markdown
Contributor

Description

Type of change

  • New / updated documentation page (src/content/docs/**)
  • Shared include file (src/content/_includes/**)
  • Component, layout, or styling change (src/components/**, src/styles/**)
  • Landing / use-case / case-study page (src/pages/**, src/data/**)
  • Redirects (src/data/redirects.ts)
  • Version bump / release (see release skill)
  • Build, CI, scripts, or tooling
  • Other (please describe)

Affected products

Related issues

  • Closes #

Checklist

  • pnpm check passes (Astro / TypeScript)
  • pnpm lint:eslint passes
  • pnpm lint:slugcheck passes (required if pages were added/renamed/moved across languages)
  • pnpm lint:linkcheck passes locally — required to merge; run it before requesting review (use pnpm lint:linkcheck:nobuild if you already ran a build)
  • Renamed/removed pages have a redirect in src/data/redirects.ts, and pnpm generate:redirects was run
  • No hardcoded versions — values come from src/data/versions.ts
  • Screenshots attached for visual changes

Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR refreshes the HTTP Integration documentation and uplink data converter include to better explain converter behavior, provide reusable scripting patterns, and keep navigation/diagram anchors aligned.

Changes:

  • Expanded the uplink data converter include with a short explanation + example and a new “Common Scripting Patterns” section.
  • Reworked the HTTP integration include: prerequisites, clearer converter explanation, updated setup steps, security/header filter guidance, and troubleshooting.
  • Updated the HTTP integration architecture SVG link to target the new section anchor.

Reviewed changes

Copilot reviewed 2 out of 7 changed files in this pull request and generated 3 comments.

File Description
src/content/_includes/docs/user-guide/integrations/uplink-data-converter.mdx Adds intro/example and a new “Common Scripting Patterns” section for generic converters.
src/content/_includes/docs/user-guide/integrations/http.mdx Restructures HTTP integration guide; adds prerequisites, converter-focused explanations, security and troubleshooting sections.
src/assets/images/user-guide/integrations/http-integration.svg Updates the diagram hyperlink anchor to match the revised HTTP docs heading.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +15 to +19
Without an uplink converter, ThingsBoard cannot understand how external HTTP payloads should be interpreted and processed internally.

Example:

Incoming HTTP payload:
Comment on lines +133 to +139
| Payload field | ThingsBoard field | Output type | Notes |
|---------------|-------------------|-------------|-------|
| `data.deviceName` | `deviceName` | — | Device identifier; auto-creates the device on first uplink |
| `data.deviceType` | `deviceType` | — | Device profile name |
| `data.model` | `model` | attribute | |
| `data.param2` | `serialNumber` | attribute | Field is renamed in the output |
| `data.temperature` | `temperature` | telemetry | |
| Symptom | Likely cause | Fix |
|---------|-------------|-----|
| Telemetry missing in ThingsBoard | Wrong field path in the script | Check **Out** in converter events; verify `data.yourField` matches the actual JSON key |
| Device not created, `deviceName` is null | Field doesn't exist or has a different name | Add a fallback: `var deviceName = data.id \|\| 'Unknown';` |
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants