HOMEii Flow Engine 1.0.0 Beta 1

HOMEii Flow Engine 1.0.0 Beta 1

Public beta — install deliberately and back up first.

Matching card: HOMEii Music Flow 6.0.0-beta.1. Install and configure the Engine before upgrading card 5.9.3. Read the full setup guide and Hebrew migration warning.

What is included

Authenticated MA connection and events, player/active-queue mapping, paginated queue and library reads, search, artwork proxy, favorites, group operations, playback controls and HA services. Stored schedules, timers and volume rules work independently of an open card while HA is running. The integration exposes sensors, switches, buttons, numbers, binary sensors and a schedule calendar. Capability-dependent features include playback preferences, spoken-media speed, announcements, Sendspin relay and configured MA AI Radio DJ access.

Required setup

The official MA HA integration must be loaded. MA API schema 63+ and a valid MA token are required; configure the actual server URL/port, not an HA ingress page. Optional features depend on MA plugins, provider/player support, TTS setup and browser permissions. The Engine is a custom integration, not an add-on or an MA replacement.

Upgrade and recovery

This labels the preceding 0.7.21 development code as the first 1.0 beta; it does not intentionally reset the storage format. Back up existing component files and HA configuration/storage, retain the existing config entry, replace the complete component and restart HA. Verify both versions and one player before expanding. Restoring an old card does not stop Engine schedules: disable unwanted beta-created tasks and restore the appropriate HA backup when reverting backend changes.

Known limits

Long-running grouping, specific DLNA hardware, mobile background audio, audible announcement restoration and broader recovery scenarios need continued testing. Use native MA as a comparison. Do not rely on this beta for critical alarms or guaranteed announcements. A beta is not a stable 1.0 release.

Publication policy

Published as a public Pre-release, not Latest. Users enabling beta updates or custom update automations control their own update policy; manual version selection is recommended for testing.

Report both component versions, HA/MA version/schema, player model/protocol, reproduction and redacted diagnostics in the Engine tracker. Never share tokens or full backups.

Onboarding

Two connection routes: automatic dedicated-token creation with MA built-in credentials, or manual long-lived token entry. Clear explanations for instance/profile identifiers and validation for Home Assistant ingress URLs. Automatic login is covered by protocol tests; broader real-installation testing remains part of this beta.