HyperHDR
Shaffer-Softworks/hyperhdr-ha · vv1.2.1
HyperHDR custom component for 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 |
|---|---|---|
light | Light | |
switch | Switch or outlet | |
camera | Camera | Needs its own HomeKit Bridge in accessory mode |
sensor | Sensor (temperature, humidity, air quality…) | |
button | Button (as a switch) | |
select | Mode picker (as switches) |
1 report below say how a device from this integration behaves in the Home app.
What people report
HyperHDR works locally; advanced HDR switches live under Configuration and could not be exposed in HomeKit.
- Works1
- Partly works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| HyperHDR ambient lighting | Works Local | Local push; password, LED colors camera and average colour fixes addedSaved copySummary - Fix Average Color sensor to use HyperHDR-valid `current-state` / `average-color` (via `hyperhdr-py-sickkick==0.2.2`), parsing `{red,green,blue}`. - Remove invalid `ledcolors` / `currentColors` polling that caused #110 validation warnings (regression from #94). - Lazy-start LED Colors / Gradient WebSockets on first camera view; stop reconnect spam via library 0.2.2. - Options/setup: reject admin passwords shorter than 8 characters; empty field clears stored password. - Docs for #90/#110 and wiki Average Color sources. Depends on hyperhdr-py#12 being merged and tagged `v0.2.2` (PyPI). … Excerpt saved from GitHub on 2026-10-23. | PR #111 · 2026-08 | |
| HyperHDR HDR processing switch | Partly works Local | Broken in Home HDR toggle not exposed to Apple Home; needs template switch proxy | Configuration entities not exposed to dashboard or HomeKit; template switch workaroundSaved copyI have been using this integration to control the HyperHDR on another RPI. It works well. I only have a problem with "advanced" features. They are categorized in "Configuration" entity tab in the device. I believe Configuration is the wrong place for these variables. I often need to switch HDR processing on or off (as there is not automatic detecting in HyperHDR). Therefore I need this switch in homekit, which is my frontend. As this is set to Configuration category, I can not expose it to homekit (or the default dashboard) because it ignores this category. Will this be changed in the code, … Excerpt saved from GitHub on 2026-10-23. | Issue #37 · 2025-06 |
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 push
Talks to the device on your network, and the device tells Home Assistant the moment something changes.
Found automatically over
- SSDP/UPnP
Details
| Installs (analytics) | 564 (0.08%) |
|---|---|
| GitHub stars | 100 |
| Latest version | v1.2.1 (2026-09-30) |
| Set up in the UI | Yes |
| Maintainers | @mjoshd, @sickkick |
| License | MIT |
Notable forks
Forks with stars, or with code pushed at least 90 days after the original’s last push. Useful when the original goes quiet.
| Fork | Stars | Last push | Description |
|---|---|---|---|
| andrew-kennedy/hyperhdr-ha | ★ 3 | 2024-04-24 | HyperHDR custom component for Home Assistant |
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.
