Pascucci (aromi.ai)

cloudby aromi.ai

What it adds to a house

adds appliances.

How a person connects it

Method: form. A personal API key from your aromi.ai dashboard, under API keys. ALYT checks it with one call before keeping it, and it can be revoked there at any time.

Field	Kind	Required
aromi.ai API key (`apiKey`)	password, secret	yes

What it can look for

Yes: “Look for machines”.

What stops working when it is disconnected

The things it brought stop answering until it is connected again.

The descriptor

Connection fields are served for a program at /connectors/aromi.json.

{
  "source": "built-in",
  "visibility": "public",
  "listed": true,
  "version": "1.0.0",
  "docsUrl": "https://developers.alyt.com/connectors/aromi",
  "kind": "AROMI",
  "logo": {
    "url": "/integrations/logos/aromi.svg",
    "color": "#00AF76",
    "ratio": 1,
    "background": "#00AF76",
    "inset": 0,
    "scale": 1
  },
  "name": "Pascucci (aromi.ai)",
  "icon": "coffee",
  "connectivity": "cloud",
  "brings": [
    "appliance"
  ],
  "connect": {
    "method": "form",
    "help": "A personal API key from your aromi.ai dashboard, under API keys. ALYT checks it with one call before keeping it, and it can be revoked there at any time.",
    "fields": [
      {
        "key": "apiKey",
        "label": "aromi.ai API key",
        "kind": "password",
        "secret": true,
        "required": true
      }
    ]
  },
  "discovery": {
    "verb": "Look for machines"
  },
  "disconnect": {
    "consequence": "{count} {things} stop answering until it is connected again."
  },
  "author": {
    "kind": "brand",
    "name": "aromi.ai",
    "url": "https://aromi.ai"
  }
}

The guide

Pascucci (aromi.ai) is a cloud-connected coffee appliance connector. A household connects it with an aromi.ai API key, ALYT checks that key before keeping it, and the connector then discovers the machines that account can see. It exposes coffee machine power, brew, stop, state, temperatures, pod count, and the machine’s own Wi‑Fi signal details. Because it is cloud-class, every command and read depends on aromi.ai being reachable; if the provider or network is unavailable, the connector cannot act.

Connect and discover

Connection uses a form with one required field: the personal apiKey from the aromi.ai dashboard. ALYT checks the key with one call before storing it, and the key can be revoked in aromi.ai at any time. After connection, discovery looks for machines visible to that account and adds them as appliances.

When discovery succeeds, each machine is identified by aromi.ai’s machine id. The connector reads the machine list through the cloud, so if aromi.ai is down or the account cannot be reached, discovery fails with the provider’s error or a connectivity failure.

What the connector shows

The exposed appliance state maps to the coffee_machine capability. A machine can show:

power on or off
brewing status
machine state
current temperature
target temperature
resettable pod count

It also exposes the machine’s Wi‑Fi strength in dBm through the link reading, and the machine’s Wi‑Fi MAC address when aromi.ai returns it. Those values come from the machine’s own status response, so they reflect what the machine reports at read time.

The visible coffee words are derived from the machine’s state and temperatures. Ready appears when the machine reports ready or when the current temperature has reached the target temperature. Warming up appears when the machine is on and still below target. Brewing appears while brewing is active, and Off appears when power is off.

Controls and timing

The connector supports these coffee actions:

set power on or off
start brew
stop brew
set target temperature

Temperature requests are clamped to 70..105 °C before they go to aromi.ai.

Small brews stop after 30 seconds; Big brews stop after 55 seconds. Tap a cup once to start, and tap the active cup again to stop early. The active stop is server-owned, so closing the screen does not cancel it. If a stop cannot be confirmed, another brew is blocked until a manual Stop confirms.

For writes, ALYT does not trust the initial HTTP acceptance alone. It waits for the machine to reflect the change, either from a signed push delivery or from a readback. Power confirms when the machine reports power on or off, brew and stop confirm from brewing status, and target temperature uses a single read because there is no quick terminal state to wait for.

What it cannot do

This connector does not talk to the local network. It cannot work while aromi.ai’s cloud path is unavailable, and it cannot discover or control machines outside the account that owns the API key. It also cannot do controls other than the ones above; if a requested capability or control name is not coffee_machine, the request is rejected.

When it fails

Check these first:

The API key is still valid in the aromi.ai dashboard.
aromi.ai is reachable from your network.
The machine is online in aromi.ai.
For brew or power actions, the machine is actually changing state; confirmation waits for the machine’s own report.
If a write seems stuck, look for a missing confirmation or a stop that needs manual confirmation before another brew can start.

If the connector can connect but discovery is empty, the account likely cannot see any machines. If a command times out, the cloud may be slow or unavailable, or the machine may not have reflected the change within the confirmation window.

Last updated September 23, 2026