How to connect uHoo sensors to Infodeck
The uHoo Cloud connector retrieves readings for uHoo devices already registered and linked in Infodeck. Use it with provider access and an Asset Type decoder confirmed for your installation.
Quick summary: Confirm compatibility with Support, save the uHoo Client ID, register each sensor with its agreed device identity, then verify readings after the scheduled collection.
Before you begin
You need:
- Permission to view, create and update integrations, and to register assets in the relevant location.
- A uHoo device already connected to its cloud service and reporting there.
- A Client ID issued for the uHoo integration supported by Infodeck.
- The device's MAC address in the representation agreed for that integration.
- An IoT Asset Type whose decoder supports the uHoo response and expected measurements.
Ask your uHoo administrator and Infodeck Support to confirm that this connector can access readings for your account and device model using the issued credential. A working uHoo dashboard alone does not establish compatibility. Do not substitute unrelated account credentials for Client ID.
uHoo describes polling API access in its official support information. Confirm the access available to your own account before setup.
What this connector does
Infodeck uses the saved Client ID to obtain provider access and periodically request readings for linked devices. It does not automatically discover and register every sensor in your uHoo account.
Collection is scheduled hourly. It is not an immediate sync when you save, and it does not provide minute-by-minute delivery even though the provider request uses minute data.
Register one sensor first and verify its actual readings before adding a larger group.
1. Create the connector
- Open Settings → Integrations.
- Click Add connector, select IoT networks, then choose uHoo Cloud.
- Enter a Connector name, such as
Office air quality. - Add a Description if helpful.
- Click Create and continue.
A newly created record still needs its connection settings. Creating it alone does not begin a working collection.
2. Save the provider credential
- In Complete connector setup, find Connection settings.
- Enter the issued Client ID.
- Click Save changes.
Saving a Client ID enables the configured hourly collection schedule. It does not test whether uHoo accepts the credential or whether a device can be read.
Keep the Client ID confidential. This connector retrieves readings from uHoo; there is no uHoo incoming Webhook URL to configure in this setup.
Connector field reference
| Field | Required | What to enter |
|---|---|---|
| Connector name | Yes | Recognizable name, up to 256 characters. |
| Description | No | Optional context, up to 1,000 characters. |
| Client ID | Yes | Credential issued for the compatible uHoo integration, confirmed with your administrator. |
3. Register the first sensor
- Open Assets and start registering an asset.
- Select the agreed uHoo Asset Type.
- Enter an Asset Name, such as
Meeting room air quality. - Select your uHoo connector in Integration Service.
- Enter the agreed MAC-based identity in Device UUID.
- Select the sensor's Location, then click Register Asset.
The registration field accepts letters and numbers, not colons, hyphens or spaces. Confirm the separator-free MAC representation with Support before registering. Do not invent an identifier or enter the device's display name: collection uses the linked device identity to request uHoo data.
Sensor field reference
| Field | Required | What to choose |
|---|---|---|
| Asset Type | Yes | IoT type with the matching uHoo decoder and measurement fields. |
| Asset Name | Yes | Name identifying the installed sensor. |
| Integration Service | Yes | The uHoo connector you configured. |
| Device UUID | Yes | Confirmed MAC-based identity; letters and numbers only, up to 90 characters. |
| Location | Yes | Where the sensor is installed. |
| Active Timeout (minutes) | No | Optional reporting allowance; account for hourly collection when choosing it. |
4. Verify scheduled readings
- Confirm that the sensor has a recent reading in uHoo.
- Allow the next hourly collection to run.
- Open the sensor in Infodeck and check its current measurements and Reading history.
- Compare the expected measurements and units with the provider's readings.
The connector's saved settings or linked-device count does not prove that collection succeeded. Check a new reading for the individual sensor. There is no manual Sync now step in this setup.
Update settings later
Open Settings → Integrations → your connector → Edit connector. Update the Connector name, Description or Client ID, then click Save changes.
If the existing Client ID is masked, leaving the field blank preserves it. Saving changes can move the minute at which the hourly collection runs; it does not force an immediate reading.
Troubleshooting
| What you see | What to check |
|---|---|
| Client ID is required | Obtain the supported integration credential from your administrator. |
| No devices appear automatically | Register each intended sensor in Infodeck and select this connector. |
| No reading immediately after saving | Collection is hourly. Confirm a new provider reading and allow the next collection. |
| No reading after a collection window | Ask Support to check credential acceptance, collection execution, device access and MAC representation. |
| Values are missing or incorrect | Confirm the Asset Type decoder, provider response format, measurement fields and units. |
| Device UUID is rejected | Confirm the agreed alphanumeric MAC representation without punctuation. |
Example: meeting room air quality
After Support confirms access and the decoder, create Office air quality. Register Meeting room air quality in its room location using the confirmed device identity. After a scheduled collection, compare the expected air-quality measurements with uHoo before registering the remaining rooms.
Related guides
Need help confirming uHoo compatibility? Contact Infodeck Support.