mirror of
https://github.com/home-assistant/supervisor.git
synced 2026-10-10 04:40:46 +01:00
Stefan AgnerandClaude Opus 5
ace2ec2cf5
Discovery messages are keyed by uuid across all apps, so restoring a message whose uuid is already taken silently dropped the message it collided with, including one belonging to another app. Skip such a message instead, and log it as it points at a corrupt backup. The set of services which already have a message was also built once before the loop, so a backup listing the same service twice ended up with two messages for it. Only one of the two can ever be updated or removed again, since send() and remove() match on app and service, while both are handed to Home Assistant. Grow the set while restoring so that the first message for a service wins. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Home Assistant Supervisor
First private cloud solution for home automation
Home Assistant (former Hass.io) is a container-based system for managing your Home Assistant Core installation and related applications. The system is controlled via Home Assistant which communicates with the Supervisor. The Supervisor provides an API to manage the installation. This includes changing network settings or installing and updating software.
Installation
Installation instructions can be found at https://home-assistant.io/getting-started.
Development
For small changes and bugfixes you can just follow this, but for significant changes open a RFC first. Development instructions can be found here.
Release
Releases are done in 3 stages (channels) with this structure:
- Pull requests are merged to the
mainbranch. - A new build is pushed to the
devstage. - Releases are published.
- A new build is pushed to the
betastage. - The
stable.jsonfile is updated. - The build that was pushed to
betawill now be pushed tostable.
