IoT Creators Integration - #591
Conversation
There was a problem hiding this comment.
🟡 Not ready to approve
The IoT Creators integration page contains several internal documentation inconsistencies/incorrect references (captured in PR comments) that should be corrected to avoid misleading readers.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.
Pull request overview
Updates the ThingsBoard documentation site to add a substantially expanded IoT Creators (T‑Mobile IoT CDP) integration guide, refresh the related SODAQ Universal Tracker partner sample, and include a new architecture diagram asset.
Changes:
- Expanded the IoT Creators integration include with architecture, setup steps, testing, downlink guidance, and troubleshooting.
- Updated the SODAQ Universal Tracker sample include and its page TOC/headings to align with the new IoT Creators flow and improved decoder examples.
- Added a new SVG architecture diagram for the IoT Creators integration.
File summaries
| File | Description |
|---|---|
| src/pages/partners/hardware/sodaq/samples/sodaq-universal-tracker.astro | Updates the manual headings/TOC entries to match the revised SODAQ sample content structure. |
| src/content/_includes/docs/user-guide/integrations/iotcreators.mdx | Major rewrite/expansion of the IoT Creators integration documentation, including new sections and visuals. |
| src/content/_includes/docs/partners/hardware/sodaq/samples/sodaq-universal-tracker.mdx | Refreshes the SODAQ tracker guide content and decoder examples to align with IoT Creators terminology and flow. |
| src/assets/images/user-guide/integrations/iotcreators-integration-architecture.svg | Adds a new architecture diagram used by the IoT Creators integration guide. |
Review details
Comments suppressed due to low confidence (1)
src/content/_includes/docs/user-guide/integrations/iotcreators.mdx:426
- The troubleshooting rows refer to
decodePayloadandbody.reports, but the decoder example on this page doesn’t definedecodePayloadand usesdata.reports. These references should be updated so readers can map the advice to the shown script.
| Uplink received but telemetry is empty | The hex layout in the decoder does not match the actual `value` | Inspect **Events → In** on the converter, read the actual `value`, then align the offsets in `decodePayload`. |
| Only the first message of a batch is decoded | The decoder reads `reports[0]` instead of iterating | Loop over the entire `body.reports` array. |
- Files reviewed: 3/7 changed files
- Comments generated: 2
- Review effort level: Low
We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.
Description
Type of change
src/content/docs/**)src/content/_includes/**)src/components/**,src/styles/**)src/pages/**,src/data/**)src/data/redirects.ts)releaseskill)Affected products
Related issues
Checklist
pnpm checkpasses (Astro / TypeScript)pnpm lint:eslintpassespnpm lint:slugcheckpasses (required if pages were added/renamed/moved across languages)pnpm lint:linkcheckpasses locally — required to merge; run it before requesting review (usepnpm lint:linkcheck:nobuildif you already ran a build)src/data/redirects.ts, andpnpm generate:redirectswas runsrc/data/versions.ts