aREST
arest
There is currently support for the following device types within Home Assistant:
In Apple Home through HomeKit Bridge
What HomeKit Bridge makes of each kind of entity this integration creates, read from its source code. A device only gets the ones that apply to it.
| Entity | Shows up as | Note |
|---|---|---|
switch | Switch or outlet | |
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) |
2 reports below say how a device from this integration behaves in the Home app.
What people report
aREST devices are polled locally; sensors don't appear in HomeKit without a device class.
- Partly works2
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| aREST temperature/humidity sensors | Partly works Local | Partly in Home Sensors not shown until device_class set in customize | Integration has no HomeKit support; set device class via customizeSaved copyThe problem aREST temp / humidity sensors do not show up in Homekit ## Environment HassOS 4.11 - Home Assistant Core release with the issue: 4.11 - Last working Home Assistant Core release (if known): N/A - Operating environment (OS/Container/Supervised/Core): Core - Integration causing this issue: aREST - Link to integration documentation on our website: https://www.home-assistant.io/integrations/arest/ ## Problem-relevant `configuration.yaml` My config: [code] The response from that URL: [code] ## Traceback/Error logs [code] ## Additional information Excerpt saved from GitHub on 2026-10-23. | Issue #39537 · 2020-08 |
| aREST temperature/humidity sensors | Partly works Local | Broken in Home Sensors don't show up until device_class customized | arest has no HomeKit supportSaved copyThe problem aREST temp / humidity sensors do not show up in Homekit ## Environment HassOS 4.11 - Home Assistant Core release with the issue: 4.11 - Last working Home Assistant Core release (if known): N/A - Operating environment (OS/Container/Supervised/Core): Core - Integration causing this issue: aREST - Link to integration documentation on our website: https://www.home-assistant.io/integrations/arest/ ## Problem-relevant `configuration.yaml` My config: [code] The response from that URL: [code] ## Traceback/Error logs [code] ## Additional information Excerpt saved from GitHub on 2026-10-23. | Issue #39537 · 2020-08 |
Gathered from GitHub issues, pull requests, discussions and docs, and from r/homeassistant. These are individual reports, so check the linked thread and the date before you buy.
How it connects
Local polling
Talks to the device on your network, asking it for updates every so often.
Details
| Installs (analytics) | 3 |
|---|---|
| Quality scale | Legacy |
| Added in | Home Assistant 0.9 |
| Set up in the UI | No, YAML |
In ReReHome
Whatever HomeKit Bridge shares reaches Apple Home as normal HomeKit accessories behind your Home Assistant bridge, so ReReHome shows and controls them like any other.
Bridges get their own settings page listing the accessories behind them.
