Pascucci (aromi.ai)

cloudProven against a real device on 2026-09-03by aromi.ai

Your Pascucci machine through aromi.ai: brew, warm up, and see what it is doing.

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

The same object the console and the phone render from, 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",
  "name": "Pascucci (aromi.ai)",
  "icon": "coffee",
  "promise": "Your Pascucci machine through aromi.ai: brew, warm up, and see what it is doing.",
  "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"
  },
  "verification": {
    "level": "proven",
    "at": "2026-09-03T21:15:00.000Z"
  }
}

The guide

Pascucci (aromi.ai) connects ALYT to a Pascucci machine through aromi.ai’s cloud. A household can see the machine’s power, brew state, temperature, target temperature, brewing status, and pod count, and can turn it on, turn it off, start brewing, stop brewing, and adjust the target temperature. The connector needs one thing at connect time: a personal aromi.ai API key. ALYT checks the key before it keeps it, and a revoked key stops working until the household connects again.

How it connects

Connect uses a form with one required secret field: apiKey. The key comes from the user’s aromi.ai dashboard, under API keys. ALYT verifies the key with aromi.ai before saving it. The connector uses the key on every call.

This is a cloud connector. The household’s machine depends on aromi.ai’s service and account access, so a cloud outage or an account problem can interrupt it. The home itself keeps working when the cloud is down, but this connector cannot read or control the machine until aromi.ai responds again. A DEV key works only in a sandbox. A LIVE key works only for its own connector.

Discovery is “Look for machines”. That means ALYT asks aromi.ai which machines the connected account can see, then adds those machines to the home.

What it exposes

This connector brings appliances through the coffee_machine capability. In the app, the household sees the machine as an appliance with:

power state
brew control
stop control
current state
current temperature
target temperature
brewing status
pod count

The machine appears unassigned until the household places it in a room. The page shows the main controls inline, with the state and temperature visible, and the target temperature under settings. Brewing status and pod count appear under More.

What it can do

The connector exposes these actions:

turn power on
turn power off
start brewing
stop brewing
set temperature, within the supported range

Readback happens after control so the household sees the updated state once aromi.ai reports it.

What it cannot do

This connector is cloud only. It does not talk to the LAN directly. It does not work without access to aromi.ai. It does not keep a revoked key alive. It does not expose anything beyond the appliance capability listed above.

When it fails

Check these first:

the apiKey is present and still valid in the aromi.ai dashboard
the aromi.ai account can still see the machine
aromi.ai is reachable
the machine is online and connected to the user’s account

If connect fails, the key may be wrong or revoked. If discovery fails, the account may not see any machines. If state or control fails after a successful connect, the cloud link or the machine’s own connection may be down. If a command seems delayed, the state may still be catching up after aromi.ai accepts the command.

Last updated September 3, 2026