HiveHub
📡 Device not supported yet?

Your device isn't in the list yet.
Here's how to get it added.

HiveHub speaks to a fixed catalogue of wireless in-hive sensors, scales and bee counters. If yours isn't one of them, it's not a dead end — it just needs a decoder added to the firmware, and a short nRF Connect capture is all it takes to get started.

🐛 Request support on GitHub How to capture the data Full docs →
In short: open a GitHub issue asking for your device, and attach a short nRF Connect capture of what it advertises or notifies. That capture is the exact data needed to write the integration.

Already supported

Before anything else, check whether your device is one HiveHub already handles — these need no new work, just pairing from the config tool or the on-device portal.

📶 HolyIot 25015

BLE beacon — temperature, humidity, pressure and acceleration.

📶 RuuviTag

Four-in-one BLE beacon on the same scan bridge.

📳 HiveInside

In-hive vibration / FFT node — nRF54LM20A beacon, scanned passively. Visit the HiveInside site →

❤️ HiveHeart

beehivemonitoring.com in-hive sensor over GATT.

⚖️ HiveScale

beehivemonitoring.com wireless weight scale over GATT.

🐝 HiveTraffic

Wireless entrance bee counter (BLE/GATT, any hive).

Not in this list? Continue below. See the BLE sensor docs for the full details on each.

Step 1 — Request support as a GitHub issue

All support requests for new devices must be submitted as an issue on GitHub. An issue is trackable, and it's searchable by the next person with the same device — please don't send it by e-mail.

🐛 Open a new issue  Search existing issues first

Please include:

🏷️

Make & model

The device name and a link to its product page or datasheet, if any.

📊

What it measures

Temperature, humidity, weight, sound, vibration, bee count, battery… and which values you want HiveHub to store.

🔌

How it talks

An advertising beacon or a GATT device you connect to. Not sure? Step 2 tells you which.

📥

The nRF Connect capture

From Step 2 below — paste the text or attach a screenshot.

⚖️

Two known readings

e.g. empty vs. a known weight, or two temperatures. Paired captures make decoding far easier.

Step 2 — Capture the data with nRF Connect

nRF Connect for Mobile is a free Bluetooth Low Energy scanner from Nordic Semiconductor (Android · iOS). It shows exactly what your device broadcasts and exposes — precisely what HiveHub's firmware needs. Every existing HiveHub decoder was confirmed against real nRF Connect captures.

Install it, enable Bluetooth and location/nearby-devices permission, put the device next to your phone, and follow the path that matches it.

A

Find the device & its MAC

Open the Scanner tab and Scan. Spot your device by name, or by RSSI — hold it against the phone and it should be the strongest (least negative, e.g. −40 dBm) entry.

Note the MAC address (six hex pairs, e.g. AA:BB:CC:DD:EE:FF). HiveHub always needs this. On iOS the real MAC is hidden behind a random UUID — capture it anyway and mention it came from iOS.

📡 It's an advertising beacon

Broadcasts readings with no connection (like HolyIot, RuuviTag).

  1. Expand the device's entry to reveal the raw advertising data.
  2. Copy the Manufacturer data and/or Service data hex — that's the payload. The first two bytes of manufacturer data are the Company ID; note it too.
  3. If it rotates through several different frames, watch for ~30 s and capture each distinct payload.
  4. Change a real value (warm it, breathe on it, add weight) and re-capture — the bytes that move reveal the scaling.

🔗 It's a GATT device

You connect and subscribe (like HiveHeart, HiveScale).

  1. Tap CONNECT. nRF Connect lists the Services and their Characteristics, each with a UUID.
  2. Note the Service UUID and Characteristic UUID for anything with sensor data — live readings almost always have Notify or Indicate.
  3. Tap ↓ to Read, or ↓↓ to subscribe to notifications. The Value field shows the raw hex bytes.
  4. Change a real measurement and capture the new bytes so the byte positions can be decoded.

What a good capture looks like

Device:        Acme BeeScale 3000
MAC:           AA:BB:CC:DD:EE:FF   (Android)
Type:          GATT (connect + notify)
Service UUID:  0000abcd-0000-1000-8000-00805f9b34fb
Char UUID:     0000abce-0000-1000-8000-00805f9b34fb  (Notify)

Empty scale:   04 00 1a 2c 00 00 e3 07 ...
+5.00 kg:      04 00 1a 2c f4 01 e3 07 ...   (bytes 4–5 changed)
Temp ~22 °C:   ... (byte 6 = 0x16 = 22?)
Even a rougher capture than this is genuinely useful — attach whatever nRF Connect shows you and note what the real reading was, and the rest can be worked out from there.

Step 3 — What happens next

Once the issue and capture are in, the payload can be decoded and a driver added to the firmware BLE bridge. New devices are then exposed in the on-device provisioning portal and the config tool like the existing ones — just pair and go. Follow your issue for progress.

🐛 Request support on GitHub Read the full docs