Skip to content
Home Assistant TestFlight
Sensors

Attributes

pilotak/homeassistant-attributes · vv1.4.1

HACSAssumed state

Breaks out specified attribute from other entities to a sensor

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.

EntityShows up asNote
sensorSensor (temperature, humidity, air quality…)

1 report below say how a device from this integration behaves in the Home app.

What people report

Helper that turns attributes into sensors; a device_class option makes the sensors expose correctly in HomeKit.

  • Works1
DeviceIn Home AssistantIn Apple HomeWhat they saidSource
Attribute-derived sensors (humidity/temperature)WorksWorks in Home
With device_class set, HomeKit exposes humidity and temperature sensors correctly
device_class option added in 1.2.0
Saved copy
Some integrations use device_class to determine what to do (e.g. HomeKit uses it to expose humidity / temperature correctly). Would be great to have the ability to specify this via configuration. If the config is not specified, don't specify the device type to preserve current behaviour.

Excerpt saved from GitHub on 2026-10-23.

Issue #25 · 2021-01

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

Assumed state

Sends commands but can’t read the device’s state back, so Home Assistant assumes it worked.

Details

Installs (analytics)229 (0.03%)
GitHub stars112
Latest versionv1.4.1 (2026-10-20)
Set up in the UINo, YAML
Maintainers@pilotak
LicenseApache-2.0

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.