Telemetry2U Technical Bulletin

Connect Telemetry2U to the Helium Network on AU915

Configure a Dragino LHT65 for AU915 sub-band 2, register it in Telemetry2U and the hosted Helium Console, create the HTTP integration and confirm that sensor data is reaching the Telemetry2U platform.

Network: Helium IoT Region: AU915 sub-band 2 Example device: Dragino LHT65 Access: Telemetry2U Admin and Helium Console

Prepare the Accounts, Device and Network Coverage

This procedure documents the hosted Helium Console workflow used by the existing Telemetry2U integration. It uses a Dragino LHT65 temperature and humidity sensor as the example, but the platform-registration and HTTP integration stages also apply to other compatible LoRaWAN devices.

Helium network-server options: Helium also supports managed and self-hosted LoRaWAN network servers. Those services use different onboarding and integration steps; refer to the current Helium network-server guidance when you are not using the hosted Helium Console.

Telemetry2U account

Use an account with access to Admin > Node Maintenance and Admin > Setup Integration.

Helium Console account

Sign in to the Helium Console organisation that will manage the device, integration and data flow.

LoRaWAN device and configuration lead

The LHT65 example requires current firmware and a compatible USB-to-serial converter for terminal access.

Helium coverage

Confirm that the installation location is within range of an active Helium IoT Hotspot using the current Helium coverage tools.

1. Configure the Dragino LHT65 for AU915 Sub-Band 2

Connect the LHT65 to a computer and open a serial terminal such as RealTerm or PuTTY. The example device communicates at 9600 baud.

  1. Connect the LHT65 through the USB-to-serial converter.
  2. Open a serial session at 9600 baud.
  3. Send the password 123456 to initialise the terminal session.
  4. Review the current configuration with .
  5. Configure AU915 sub-band 2 with .
  6. Restart the device with or hold the device button for approximately five seconds when prompted.
  7. Run AT+CFG again and confirm that the channel setting has been retained.

Record the Device EUI (DevEUI), Application EUI (AppEUI) and Application Key (AppKey). Enter each value without spaces when registering the device in both systems. Newer LoRaWAN documentation may refer to the AppEUI as the JoinEUI.

Optional radio settings: Adaptive Data Rate (ADR) is enabled by default on the example configuration and confirmed messages are disabled. Change these only when the deployment requires different behaviour.

RealTerm window showing Dragino LHT65 device credentials, AU915 frequency plan and channel group 2
Confirm the device credentials and the AU915 channel-group setting before continuing.

2. Register the Device in Telemetry2U

Sign in to Telemetry2U, open Admin > Node Maintenance and select Create New.

  1. Enter a unique, recognisable value in Description.
  2. Select AU915 as the profile for this Australian example.
  3. Enter the device's Device EUI.
  4. Select Helium as the Network Provider.
  5. Select the matching Device Configuration, such as Dragino LHT65 Temperature Sensor V1.5 for the device shown.
  6. Complete any required notification, asset and location fields, then select Create.

Device configuration not listed? Create or assign the required payload decoder and downlink commands before relying on decoded readings. See the custom payload decoder example for the current Telemetry2U workflow.

Telemetry2U Create Node form with AU915 profile, Helium network provider and Dragino LHT65 device configuration selected
Match the regional profile, network provider and decoder configuration to the physical device.

3. Create the Helium Profile and Register the Device

Keep Telemetry2U open in one browser tab and sign in to the hosted Helium Console in another. Create the device profile first, because it is selected during device registration.

Create the Device Profile

Helium Console profile form showing ADR, Join-Accept CFList and Rx1 delay settings
Profile settings control ADR and the receive-window timing used by the device.
  1. Open Profiles and select Add New Profile.
  2. Enter a unique profile name.
  3. Enable Allow ADR when ADR is enabled on the device.
  4. Leave Enable Join-Accept CFList off for this AU915 example.
  5. Set the delay before the Rx1 window to 2 seconds.
  6. Select Create Profile.

Register the LoRaWAN Device

Helium Console Add New Device form showing device name, DevEUI, AppEUI, AppKey and profile fields
Use the same DevEUI, AppEUI and AppKey recorded from the physical device.
  1. Open Devices and select Add New Device.
  2. Enter a unique device name.
  3. Paste the DevEUI, AppEUI and AppKey without spaces.
  4. Select the profile created for this device.
  5. Select Save Device.

The device may remain in a pending state while the Console updates its routing information. Allow up to 30 minutes before treating this as a fault.

4. Create the Helium HTTP Integration

Generate the account-specific integration credentials in Telemetry2U, then use them to create a custom HTTP integration in Helium Console.

Generate Telemetry2U Details

Telemetry2U Setup Integration page with Helium selected as the network provider
Telemetry2U supplies the endpoint and account-specific Authorization value.
  1. Open Admin > Setup Integration.
  2. Select Helium as the network provider.
  3. Select Add Integration if a Helium integration does not already exist.
  4. Keep this page open while configuring Helium Console.

Create the Helium HTTP Endpoint

Helium Console HTTP integration form showing endpoint URL and Authorization header fields
Add the Telemetry2U endpoint and the generated Basic Authorization value.
  1. Open Integrations and select New Integration.
  2. Under custom integrations, select HTTP.
  3. Enter the endpoint:
  4. Add an HTTP header with as the key.
  5. Paste the full value generated by Telemetry2U, including the Basic prefix.
  6. Name the integration and select Add Integration.

Complete the Downlink Configuration

After the integration is created, copy its Helium downlink URL and save it in the Telemetry2U integration record. This allows Telemetry2U downlink commands to be returned through the same network-server workflow.

Copy the Helium Downlink URL

Helium Console integration details page showing the generated downlink URL
Copy the complete downlink URL from the Helium integration details.

Open the new integration and copy the displayed Downlink URL.

Save the URL in Telemetry2U

Telemetry2U Helium integration form with the Downlink URL field completed
Paste the complete URL into Telemetry2U and save the integration.

Return to Telemetry2U, paste the URL into Downlink URL and select Save.

5. Connect the Device and Integration in a Helium Flow

The device will not forward uplinks to Telemetry2U until it is connected to the HTTP integration in the Helium Console Flow workspace.

  1. Open Flows in Helium Console.
  2. Add the registered Device to the canvas.
  3. Add the Telemetry2U Integration to the canvas.
  4. Drag from the device connector to the integration connector.
  5. Confirm that the connection line remains visible between the two blocks.
Helium Console Flow canvas with the Dragino LHT65 device connected to the Telemetry2U HTTP integration
The connection line completes the uplink path from the device to Telemetry2U.

6. Verify Data in Telemetry2U and Helium Console

Allow at least one normal transmission interval, then confirm the complete path in both systems. Telemetry2U verifies decoding and storage; Helium Console helps confirm that the network server received and forwarded the uplink.

Telemetry2U Reports

Telemetry2U Reports page displaying incoming readings from the Helium-connected Dragino LHT65
Decoded readings in Reports confirm that Telemetry2U received and processed the uplink.

Open Reports, select the node and check for new readings. Use Raw Data when you need to inspect the payload, port, data rate or decoder result.

Helium Device Status

Helium Console device page showing received packets and device activity statistics
Helium device activity confirms that the network server received the transmission.

Open the device in Helium Console and review its event or packet information. ADR changes are not immediate, so review several transmissions before assessing the final data rate.

No data in Telemetry2U? Check the device channel group and credentials first, then confirm that the device is connected to the correct HTTP integration in Flows. If Helium receives uplinks but Telemetry2U does not, recheck the endpoint, Authorization header and Telemetry2U downlink URL.

Related Telemetry2U and Helium Resources

Custom Payload Decoder Example Create a Telemetry2U decoder when the required LoRaWAN device configuration is not already available. LoRaWAN Glossary of Terms Review DevEUI, AppEUI, AppKey, ADR, uplink, downlink and other terms used in this guide. Telemetry2U Technical Bulletins Browse additional platform, gateway, decoder and LoRaWAN configuration guides. Helium LoRaWAN Network Servers Review Helium's current managed and self-hosted network-server options.