Skip to content

v1.6.0-RC2 — The House Plays Along (release candidate)

Pre-release
Pre-release

Choose a tag to compare

@mholzi mholzi released this 06 Jul 19:02

Release candidate for 1.6.0 — "The House Plays Along". The whole smart home
becomes part of the game show, question selection stays fresh across game
nights, and hosts can drive the game hands-free via HA services.

Added

  • The House Plays Along (#494) — an immersive whole-home game-show mode,
    off by default behind the house_events_enabled master toggle. Three
    layers ride a new quizify_* HA event backbone that fires at every game
    milestone: (1) the event backbone itself (#366/#495) so hosts can wire
    their own automations; (2) "Game Show" light choreography (#496) — party
    lights react to game beats with transient accents; (3) room sound effects
    (#497) at reveal, streak and winner, each cue resolvable from an override
    URL or a bundled default.
  • Countdown pulse + finale scene (#280) — the party lights "breathe"
    faster in the final seconds of a question (new additive
    quizify_time_running_out event), and an options-flow finale scene
    selector
    fires a user-built scene.* when the winner is decided.
  • Freshness engine (#436) — question selection now weights against
    recently shown questions (exponential decay + a hard-exclude window with a
    pool-size guard) so repeat game nights feel new. New "Avoid recent repeats"
    options toggle (on by default; off restores the previous ordering exactly).
  • Game-control HA services (#367)quizify.start_game,
    quizify.next_round, quizify.pause, quizify.resume and
    quizify.end_game expose the host controls as HA services, so the game can
    be driven from Assist voice ("Hey Nabu, next question"), a Zigbee remote, a
    dashboard button or an automation. Bad-phase calls raise a clear
    ServiceValidationError.

Fixed

  • TTS engine + speaker dropdowns showed "None found" (RC2). The admin
    quiz-setup dropdowns load from the admin-token-gated tts-entities endpoint
    (#356) at page-init, before the admin session token arrives over the
    WebSocket — so the first request 401'd and both dropdowns fell back to "None
    found" even with TTS engines and media players configured. They now refetch
    once the token lands.