How to connect ChirpStack v4 sensors to Infodeck

Use an HTTP integration in ChirpStack v4 to forward readings from an existing application to Infodeck.

Quick summary: Create the connector, configure JSON HTTP forwarding in ChirpStack, register the sensors as Infodeck assets and check a new reading.

Before you begin

You need:

• Permission to view, create and update integrations, register assets and use the relevant locations and Asset Types.
• Access to manage the ChirpStack application's integrations and obtain a suitable provider API key.
• A sensor already registered and transmitting in ChirpStack v4, with its DevEUI available.
• An IoT Asset Type with the correct decoder and measurement fields for that sensor model.
• A network administrator to confirm the ChirpStack gRPC host, port and connection compatibility with Infodeck.

Start with one sensor. This guide connects an existing network; creating the connector does not automatically import the application's device inventory.

1. Create the connector

1. Open Settings → Integrations.
2. Click Add connector, select IoT networks, then choose ChirpStack v4.
3. Enter a Connector name, such as Building sensors, and an optional Description.
4. Click Create and continue.
5. In Host, enter the gRPC host and port supplied by your network administrator.
6. In API key, paste the ChirpStack API key with access to the intended tenant and devices.
7. Click Save changes.

Use a host-and-port value, not a browser page URL, REST endpoint or Infodeck webhook URL. ChirpStack documents its API in the gRPC guide. Ask your administrator or Support to confirm a protected, compatible connection before relying on provider commands.

Receiving and commands use different settings

Host and API key are for Infodeck's provider access, including supported device commands. Incoming readings arrive through Provider webhook, configured in the next step. Supplying the API key alone does not enable forwarding.

2. Add HTTP forwarding in ChirpStack

1. In Infodeck, open your connector and click Edit connector.
2. Under Provider webhook, use Copy webhook URL and Copy authorization.
3. In ChirpStack, open the application containing your sensor and its Integrations page. Add an HTTP integration.
4. Choose JSON as the payload encoding or marshaler.
5. Set the event endpoint URL to the copied Infodeck Webhook URL.
6. Add an Authorization header with the complete copied authorization value. Do not add another prefix or use the ChirpStack API key here.
7. Save the HTTP integration.

ChirpStack adds an event query parameter to its requests. Infodeck processes the up event for sensor readings. Other events, such as joins, are not measurement records. See ChirpStack's HTTP integration guide.

Keep the standard JSON uplink message, including its raw sensor data and device information. Protobuf or a custom decoded-only message will not match this connector. Preserve any other application integrations that are still needed.

3. Register the sensor in Infodeck

1. Open Assets and click Register Asset.
2. Select the sensor's IoT Asset Type and enter an Asset Name, such as Plant room temperature sensor.
3. Set Integration Service to your ChirpStack connector.
4. In Device UUID, enter the sensor's DevEUI from ChirpStack: 16 hexadecimal characters, without spaces or separators. Preserve leading zeros.
5. Select its Location, complete any other required fields and click Register Asset.

Device UUID must contain the DevEUI, not a device name or application identifier. The Asset Type determines how the sensor's message becomes measurements; choose the type for its actual model and message format.

Registering a previously deleted DevEUI creates a new asset. Previous history and associations are not restored; update dashboards and associations to use the new asset where needed.

Field reference

Field	Required	What to enter
Connector name	Yes	A recognizable label, up to 256 characters.
Description	No	Helpful context, up to 1,000 characters.
Host	Yes for connector setup	The compatible ChirpStack gRPC host and port.
API key	Yes for connector setup	The provider key for the intended tenant and devices.
Webhook URL	Copy only	The destination for ChirpStack's HTTP integration.
Authorization	Copy only	Infodeck's incoming-request credential for the HTTP header.
Asset Type	Yes	An IoT type with the appropriate decoder.
Asset Name	Yes	A name that identifies this sensor.
Integration Service	Yes	Your ChirpStack connector.
Device UUID	Yes	The sensor's DevEUI.
Location	Yes	Where the sensor is installed.
Active Timeout (minutes)	No	Reporting interval allowance, if used by your installation.

4. Confirm a real reading

1. Wait for the next sensor transmission or use its normal test function.
2. Confirm a new uplink appears in ChirpStack.
3. In Infodeck, open the asset and check IoT Status → Last Uplink.
4. Confirm the timestamp advances and check Reading history, current values and units.

A saved connector or successful HTTP delivery is not proof of stored measurements. Check the actual sensor before expanding to the rest of the application.

Correct a mistake later

Open Settings → Integrations → your connector → Edit connector, update the fields and click Save changes. Leaving an already stored API key's masked field blank preserves it. Paste a new key to replace it.

Changes to the HTTP destination, header or JSON encoding must be made in ChirpStack. Infodeck does not update that remote configuration when you edit the connector.

Troubleshooting

What you see	What to check
Complete connector setup is still shown	Supply both Host and API key, then save.
HTTP authorization fails	Copy authorization from the matching Infodeck connector and check the ChirpStack HTTP header.
ChirpStack receives uplinks but Infodeck has none	Confirm the application HTTP integration uses JSON, the correct destination and up events. Match the asset's DevEUI and connector.
Readings are missing or incorrect after delivery	Keep the standard raw uplink data and choose the correct Asset Type decoder.
Host works in a browser but commands fail	Ask your administrator to check gRPC reachability and compatibility, provider permissions and the device's command support.
Registration asks for an earlier identity record to be checked	Contact your administrator or Support; repeated registration attempts will not repair that record.

Example: plant room temperature

Create Building sensors and configure JSON HTTP forwarding on the ChirpStack application. Register Plant room temperature sensor using the matching IoT Asset Type, its DevEUI in Device UUID and the plant room location. Confirm a fresh temperature value and timestamp before registering the rest of the sensors.

Related guides

• Register an asset
• Asset Types
• Sensor data
• Integrations & Connectors

Need help with connection compatibility or the decoder? Contact Infodeck Support.