Reference · built on requestConnectorSensors, meters & gateways

SensorPush

Temperature, humidity, dew point, VPD, and pressure samples from SensorPush sensors through the G1 gateway and Gateway Cloud API.

Request accessPricing ↗

About

SensorPush sells the HT1, HT.w, and HTP.xw Bluetooth sensors and the G1 WiFi Gateway, which relays their readings to the SensorPush cloud about once a minute. The Gateway Cloud API at api.sensorpush.com lists sensors and gateways and returns samples by sensor, time window, or tag. Temperature and dew point arrive in Fahrenheit, pressure in inches of mercury.

Through Fibric, an operator polls samples at the once-per-minute pace the API allows, checks them against your limits, and proposes the alert, the log entry, or a tag that groups sensors by room. You approve and the record shows what was read.

This is a reference listing. It documents what Fibric would read from SensorPush and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Sensors through POST /devices/sensors: id, deviceId, name, type, address, active, battery_voltage, rssi, alerts, calibration, and tags
  • Gateways through POST /devices/gateways: name, version, paired, last_seen, last_alert, and message
  • Samples through POST /samples with startTime, stopTime, limit, sensors, tags, and measures
  • Each sample's observed time, temperature, humidity, dewpoint, vpd, barometric_pressure, and altitude
  • Bulk report files through POST /reports/list and POST /reports/download
  • Gateway health from last_seen, which SensorPush suggests reading about every 15 minutes

Proposed actions

  • Target capability: propose tags on sensors through POST /tags, so samples can be queried by room or asset
  • Target capability: propose a bulk report request through POST /samples with bulk set to true, queued and emailed to the primary account holder

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Keep a food safety temperature log

    Samples for each cooler sensor are appended to your log at the interval you set. The operator proposes the corrective-action entry when a temperature leaves the range, with the observed timestamp.

    With Food Safety Log

  • Catch a cooler failing overnight

    A run of rising temperature samples from one sensor is compared with your limit. The operator proposes the escalation, naming the sensor and its last observed reading.

    With Cold Room Watch

  • Prove a shipment stayed cold

    Samples from the sensor riding with the goods are queried by startTime and stopTime. The operator proposes the excursion report, or a clean record, for the file.

    With Cold Chain Excursion

  • Replace batteries before the gaps start

    battery_voltage and rssi per sensor, and last_seen per gateway, feed a health list. The operator proposes a battery swap or a gateway check for any device trending down.

    With Sensor Health

Requirements

  • A SensorPush account with a G1 WiFi Gateway paired to the sensors
  • API access activated by logging in to the Gateway Cloud Dashboard once and agreeing to the terms of service
  • For the /oauth/token flow with refresh tokens, a client_id registered by emailing support@sensorpush.com
Authentication
An email and password posted to /oauth/authorize for an authorization code valid 24 hours, exchanged at /oauth/accesstoken for an access token valid 12 hours and sent in the Authorization header; /oauth/token adds refresh tokens for registered client IDs.

Limits

  • Requests may be made no more than once per minute
  • A samples query is truncated near 5 MB; the response sets truncated true, and the data is split evenly across sensors unless you name them
  • Bulk reports are processed within 24 hours and delivered by email, not in the response
  • Some measures, such as vpd and barometric_pressure, are not available on older devices

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SensorPush ↗

Questions and answers

How often can I call the API?
No more than once per minute. The gateway itself relays sensor data roughly every minute and checks in with the cloud periodically, so SensorPush suggests reading a gateway's last_seen about every 15 minutes for a dependable status.
What units do samples use?
temperature and dewpoint are in Fahrenheit, humidity in percent, barometric_pressure in inches of mercury, altitude in feet, and vpd in kPa. Each sample carries an observed timestamp. Conversions to Celsius or hectopascals happen on your side.
What happens when a query returns too much data?
Results over about 5 MB are truncated and the response sets truncated to true. Without a sensors list the budget is split evenly across sensors; naming one sensor gives it the whole budget. Page by passing last_time as the next startTime, or set bulk to true for an emailed report.
Ask about SensorPush

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SensorPush through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy