← All drivers

Climate

Aqara Cloud

An Aqara hub's IR remotes, through Aqara's cloud: air conditioners, fans and anything else switched with a button. Everything else from Aqara comes locally, from the HomeKit driver. It needs internet and an Aqara developer account.

What it does

  • A stateful air conditioner: on, off, mode, temperature and fan, as far as that model takes them.
  • Any other remote with a power key: on and off, in automations too.
  • The account's link lasts 30 days and renews itself.

Worth knowing

  • IR does not answer: a command counts once Aqara accepts it, and the state is what was sent, not what the hub read.
  • It needs internet, and a free developer account links only the devices of its own Aqara account.
  • Aqara's documents list IR only for the M2 hub and the P3. A remote's other keys, besides power, do not come in yet.
  • Tested only against a fake cloud built from Aqara's documents.

Setup guide

Driver: systems.arvio.aqara. Through Aqara's cloud: it needs the internet and an Aqara developer account. Tested only against a fake cloud built from Aqara's documents.

An Aqara hub's IR remotes have no local path: HomeKit does not carry them. Everything else from Aqara (the hubs, their Zigbee devices, the cameras and the G4 doorbell) comes locally, through the HomeKit driver.

What you need

  • The IR remotes already set up in the Aqara Home app, on a hub that has IR.
  • The login of the Aqara account that owns the hub, the one you use in Aqara Home.
  • A developer account at developer.aqara.com on that same Aqara account. Aqara reviews a new one before it works.
  • Someone who can read a code Aqara sends to that account by SMS or email, within 10 minutes.

How to connect

The Partner screen for this driver is not there yet. For now, SFK connects it on the hub.

  1. Sign in at developer.aqara.com with the Aqara account that owns the hub, and wait until Aqara approves the account.
  2. In Console, then Project Management, open the default project. Note its AppId, and under Key Management its KeyId and AppKey.
  3. Pass them to SFK safely. They stay sealed on the hub and are never shown again.
  4. SFK asks Aqara for a code. Read it from the SMS or email and give it to SFK within 10 minutes. The link then lasts 30 days and renews itself.
  5. Say which remotes to add. Each one goes into a room.

A free developer account links only its own Aqara account. Linking a customer's account needs a paid account with Aqara.

What works

  • A stateful air conditioner: on, off, mode, temperature and fan, as far as that model takes them.
  • Any other remote with a power key: on and off, in automations too.
  • The account's link lasts 30 days and renews itself.

Limits

  • IR does not answer. A command counts once Aqara accepts it, and the state is what was sent, not what the hub read. If someone uses the physical remote, an air conditioner shows it only if Aqara's app did the sending.
  • It needs the internet. Without it the remotes show as unavailable.
  • Aqara's documents list IR only for the M2 hub and the P3 air conditioning controller.
  • A remote's other keys, besides power, do not come in yet.
  • Aqara's free quota: 100,000 calls a month and 300 every 5 minutes. A remote uses a call only when pressed, and an air conditioner's state is read every 5 minutes.

Troubleshooting

  • Aqara says the account is not registered → use the account that owns the hub in Aqara Home.
  • The code is refused → it lasts 10 minutes. Ask for a new one.
  • Everything shows as unavailable after a month → the link could not renew. Link the account again with a new code.
  • A remote does not appear → it is not on a hub that has IR, or it has no power key.