Beatify
mholzi/beatify · vv4.8.5
🎵 Music quiz party game for Home Assistant with two modes, guess the release year or name the title and artist. Streams from Spotify, Apple Music, Tidal, Deezer, YouTube Music and Amazon Music, or plays your own library via Plex, Jellyfin and local files. Runs on Sonos, Alexa and any Music Assistant speaker.
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 |
|---|---|---|
binary_sensor | Sensor (motion, contact, leak, smoke…) | |
sensor | Sensor (temperature, humidity, air quality…) |
What people report
Party game that plays music through HA media players; Music Assistant, Sonos and Alexa players are supported while plain Cast devices are hidden.
- Works3
- Won’t be supported1
| Device | In Home Assistant | In Apple Home | What they said | Source |
|---|---|---|---|---|
| Amazon Echo via Alexa Media Player | Works | Supported player platformSaved copySupported devices: Integration; Music Assistant; Sonos; Alexa Media Player; Cast (Chromecast/Nest/Google TV); HomePod; ✅ Supported players show with a platform badge (Music Assistant, Sonos, Alexa); ❌ Unsupported players (Cast, etc.) are hidden with a hint to use Music Assistant; Protocol; HTTP/HTTPS; WebSocket; The QR code uses the HA URL as seen by the admin's browser, make sure that URL is reachable from the guest network; If using a reverse proxy (nginx/Caddy), ensure WebSocket upgrades are allowed for /beatify/ws (standard HA proxy configs already handle this); If using HTTPS with a … Excerpt saved from the README on 2026-10-23. | README | |
| Apple HomePod | Works | Listed among supported playersSaved copySupported devices: Integration; Music Assistant; Sonos; Alexa Media Player; Cast (Chromecast/Nest/Google TV); HomePod; ✅ Supported players show with a platform badge (Music Assistant, Sonos, Alexa); ❌ Unsupported players (Cast, etc.) are hidden with a hint to use Music Assistant; Protocol; HTTP/HTTPS; WebSocket; The QR code uses the HA URL as seen by the admin's browser, make sure that URL is reachable from the guest network; If using a reverse proxy (nginx/Caddy), ensure WebSocket upgrades are allowed for /beatify/ws (standard HA proxy configs already handle this); If using HTTPS with a … Excerpt saved from the README on 2026-10-23. | README | |
| Sonos speakers | Works | Supported player platformSaved copySupported devices: Integration; Music Assistant; Sonos; Alexa Media Player; Cast (Chromecast/Nest/Google TV); HomePod; ✅ Supported players show with a platform badge (Music Assistant, Sonos, Alexa); ❌ Unsupported players (Cast, etc.) are hidden with a hint to use Music Assistant; Protocol; HTTP/HTTPS; WebSocket; The QR code uses the HA URL as seen by the admin's browser, make sure that URL is reachable from the guest network; If using a reverse proxy (nginx/Caddy), ensure WebSocket upgrades are allowed for /beatify/ws (standard HA proxy configs already handle this); If using HTTPS with a … Excerpt saved from the README on 2026-10-23. | README | |
| Chromecast / Nest / Google TV (Cast) | Won’t be supported | Hidden; use Music Assistant insteadSaved copySupported devices: Integration; Music Assistant; Sonos; Alexa Media Player; Cast (Chromecast/Nest/Google TV); HomePod; ✅ Supported players show with a platform badge (Music Assistant, Sonos, Alexa); ❌ Unsupported players (Cast, etc.) are hidden with a hint to use Music Assistant; Protocol; HTTP/HTTPS; WebSocket; The QR code uses the HA URL as seen by the admin's browser, make sure that URL is reachable from the guest network; If using a reverse proxy (nginx/Caddy), ensure WebSocket upgrades are allowed for /beatify/ws (standard HA proxy configs already handle this); If using HTTPS with a … Excerpt saved from the README on 2026-10-23. | README |
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.
Details
| Installs (analytics) | 530 (0.07%) |
|---|---|
| GitHub stars | 230 |
| Latest version | v4.8.5 (2026-10-23) |
| Set up in the UI | Yes |
| Maintainers | @mholzi |
| License | MIT |
Devices listed in its README
- Integration
- Music Assistant
- Sonos
- Alexa Media Player
- Cast (Chromecast/Nest/Google TV)
- HomePod
- âś… Supported players show with a platform badge (Music Assistant, Sonos, Alexa)
- ❌ Unsupported players (Cast, etc.) are hidden with a hint to use Music Assistant
- Protocol
- HTTP/HTTPS
- WebSocket
- The QR code uses the HA URL as seen by the admin's browser, make sure that URL is reachable from the guest network
- If using a reverse proxy (nginx/Caddy), ensure WebSocket upgrades are allowed for /beatify/ws (standard HA proxy configs already handle this)
- If using HTTPS with a self-signed cert, guests may need to accept it once
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.
Sources
- Documentation: https://github.com/mholzi/beatify
- Source code: https://github.com/mholzi/beatify
- Issues: https://github.com/mholzi/beatify/issues
- HACS: https://hacs.xyz
