Examples

Copy-paste examples for the MQTT-discovered Glucose sensor. See Configuration for the full sensor and attribute reference.

Attribution. The sensor.gluco_hub_*_glucose entity is published by the upstream gluco-hub-rs bridge via MQTT discovery. This add-on wires HA Ingress and translates add-on options into the upstream config.

Quick reference

EX-01 — Alert automation

What it does

Fires a persistent notification and mobile push when glucose drops below 70 or rises above 180 mg/dL. Both triggers watch the sensor state — the current glucose reading in your configured unit.

Code

alias: Glucose high / low alert
description: >
  Fires a persistent notification and mobile push when glucose
  leaves the 70–180 mg/dL range.
trigger:
  - platform: numeric_state
    entity_id: sensor.gluco_hub_ha_glucose
    below: 70
    id: low
  - platform: numeric_state
    entity_id: sensor.gluco_hub_ha_glucose
    above: 180
    id: high
action:
  - choose:
      - conditions:
          - condition: trigger
            id: low
        sequence:
          - action: persistent_notification.create
            data:
              title: "Glucose low"
              message: >
                Glucose is {{ states('sensor.gluco_hub_ha_glucose') }}
                — below 70.
          - action: notify.mobile_app_your_phone
            data:
              title: "Low glucose"
              message: >
                {{ states('sensor.gluco_hub_ha_glucose') }} — below 70
      - conditions:
          - condition: trigger
            id: high
        sequence:
          - action: persistent_notification.create
            data:
              title: "Glucose high"
              message: >
                Glucose is {{ states('sensor.gluco_hub_ha_glucose') }}
                — above 180.
          - action: notify.mobile_app_your_phone
            data:
              title: "High glucose"
              message: >
                {{ states('sensor.gluco_hub_ha_glucose') }} — above 180
mode: single

Notes

• Entity naming. sensor.gluco_hub_ha_glucose uses the default client_id: ha. Replace ha with your configured client_id value — the entity name follows the pattern sensor.gluco_hub_<client_id>_glucose.
• Notify service. Replace notify.mobile_app_your_phone with your device's notify service (Settings → Devices & Services → Mobile App).

• Trigger targets the state, not attributes. Do not use attribute: mgdl in the trigger; the state already holds the value in your configured unit.

EX-02 — Dashboard gauge card

What it does

A Lovelace gauge card with color-coded severity bands. Add with the + Add card button — no HACS or custom card required.

Code

type: gauge
entity: sensor.gluco_hub_ha_glucose
name: Glucose
min: 40
max: 300
needle: true
severity:
  green: 70
  yellow: 180
  red: 40

Notes

• Severity colors. The severity map sets the lower bound of each colored band. With the values above the gauge shows: red from 40 → 70, green from 70 → 180, yellow from 180 → 300.
• Entity. Replace sensor.gluco_hub_ha_glucose using the same <client_id> convention as in EX-01.

EX-03 — Multi-account configuration

What it does

Polls multiple LibreLink Up accounts simultaneously with per-source MQTT topics. See Multi-account setup for the full field reference.

Add-on options (llu_accounts)

llu_accounts:
  - name: alex
    email: alex@example.com
    password: "hunter2"
    region: EU
    timezone: Europe/Berlin
  - name: sam
    email: sam@example.com
    password: "correct-horse"
    region: US
    timezone: America/New_York
    patient_id: "00000000-0000-0000-0000-000000000001"

Per-source topic topology

With llu_accounts the add-on sets per_source = true in the upstream config. Each source publishes to its own path:

The shared <prefix>/glucose topic is not published in multi-account mode. Target the per-source entity in your automations and dashboard cards (e.g. sensor.gluco_hub_ha_alex_glucose).

Generated TOML

Generated by the add-on at startup and validated with gluco-hub check-config:

[poller]
interval_secs = 60

[http]
bind = "0.0.0.0:8080"

[state]
dir = "/data/state"

[sink.mqtt]
broker_host = "mqtt.local"
broker_port = 1883
username = "mosquitto"
password = "mqttpass"
topic_prefix = "gluco-hub/ha"
client_id = "ha"
discovery_enabled = true
per_source = true

[source.sources.alex]
email = "alex@example.com"
password = "hunter2"
region = "EU"
timezone = "Europe/Berlin"

[source.sources.sam]
email = "sam@example.com"
password = "correct-horse"
region = "US"
timezone = "America/New_York"
patient_id = "00000000-0000-0000-0000-000000000001"

Notes

• Multi-account limitations. The generated TOML hard-codes client_id = "ha" and does not include discovery_unit — so MQTT discovery always advertises mg/dL regardless of your glucose_unit setting. The client_id and discovery_unit single-account options are not carried into multi-account mode.
• Validation. Validated against the pinned upstream image ghcr.io/micschr0/gluco-hub:2026.621.0 and returned configuration ok.