Persang Infrared
persang_infrared
The Persang Infrared integration lets you control a Persang Bluetooth speaker using any infrared transmitter previously configured in 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 |
|---|---|---|
media_player | Media player (as switches) | Only TVs and receivers get a TV tile; other players show as power and play switches; Needs its own HomeKit Bridge in accessory mode |
button | Button (as a switch) |
What people report
Persang speakers are controlled by infrared with assumed state and shared toggle commands.
- Partly works1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Persang infrared-controlled speaker | Partly works | Assumed state; power, play and mute are togglesSaved copyLimitations: The integration uses assumed state, meaning Home Assistant cannot read the actual state of the speaker (for example, whether it is on or off, or what the current volume is). Presses on the physical remote are not tracked. The integration only sends commands through an infrared transmitter, so using the remote directly leaves the entities showing whatever state Home Assistant last set. Turning on and turning off the speaker both send the same IR power toggle command, as is standard with infrared remotes. The same applies to play and pause, and to muting and unmuting. The command … Excerpt saved from home-assistant.io on 2026-10-23. | Docs |
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) | 1 |
|---|---|
| Quality scale | Bronze |
| Added in | Home Assistant 2026.10 |
| Set up in the UI | Yes |
| Maintainers | @Dr-Blank |
Limitations from the docs
- The integration uses assumed state, meaning Home Assistant cannot read the actual state of the speaker (for example, whether it is on or off, or what the current volume is).
- Presses on the physical remote are not tracked. The integration only sends commands through an infrared transmitter, so using the remote directly leaves the entities showing whatever state Home Assistant last set.
- Turning on and turning off the speaker both send the same IR power toggle command, as is standard with infrared remotes. The same applies to play and pause, and to muting and unmuting. The command is always sent, so if the speaker and Home Assistant disagree, sending the opposite command brings them back in sync.
- Volume control is step-based only; there is no way to set an absolute volume level.
- Mute is not restored after a restart.
- Source selection is not exposed, because the remote has no dedicated source buttons.
- The mode, equalizer, and repeat buttons cycle through the available settings, so Home Assistant cannot select a specific one or tell which one is active.
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.
