0.9.0rc1
Pre-release⚠️ 0.9.0 Release Candidate 1
Note
This pre-release is a release candidate for the upcoming 0.9.0 release, and may contain more bugs than usual as a lot of the code has changed. It is recommended that you create a full backup of your HA configuration before you upgrade the integration to this version. The config entry generated by this version of the integration may not be compatible with previous versions, and a full restore or the removal and reinstallation of integration may be required to recover.
Warning
Configuration via configuration.yaml is no longer supported in this release. The configuration is ignored and an error is logged if YAML configuration is detected. To migrate, add the integration via the UI.
What's Changed
- AVR property groups, as well as some more useful properties such as
input_multichannel
anddisplay
, are presented as entities in HA. They can be displayed in the UI as well as used in scripts and automations. This adheres more closely to the HA architecture guidance on how attributes should be presented- The AVR property group sensor entities are considered beta and may change in the future, as it is expected that more properties will be exposed as separate entities
- System wide AVR property groups such as DSP, audio and video parameters are available as entities attached to the main Pioneer AVR device in HA. Zone specific AVR property groups are available as entities attached to the device in HA for each zone. All zone entities except for the
media_player
entity become available only when the zone is powered on - Tuner entities for preset, band and frequency can be changed via the UI, and trigger commands to the AVR when changed. They are only available when the tuner is the selected source for at least one powered on zone. There are separate entities for AM and FM frequency as they have different units of measurement
- Most of the new entities are disabled by default when the integration is added, to prevent changes from being written to the recorder. Disabled entities can be enabled by default in the entity's settings panel
- The Maximum source ID and Don't check volume when querying AVR source options can now be set when adding a new instance
- The
media_player
entity now uses the name of the zone device by default. The existing entity name should however be preserved when migrating from an older version of the integration. - Many action commands sent to the AVR (such as the ones that turn the AVR on and off) are now automatically sent up to 4 times by default (each with a 1 second delay) should they fail. The AVR sometimes refuses to execute certain actions in parallel, such as turning on/off multiple zones, and repeating the commands works around this limitation. Non-idempotent commands such as increase/decrease volume or preset are not repeated. The number of repeats can be configured through the Repeat action commands setting
- Service calls (eg.
turn_on
) that fail now generate an error message that is shown by HA in the front-end - Service calls now support using targets to specify entities
- The
media_next_track
andmedia_previous_track
services now change the tuner presets when the tuner is available - Some AVR system information (eg. software version) is not available if all AVR zones are powered off when the integration is started. The integration now re-polls system information and updates the attributes of the HA device when Zone 1 is turned on
- Documentation has been improved and should now more completely describe the integration's functionality
aiopioneer
Package Major Changes
- The tuner frequency will be set directly on AVR models that support this, instead of stepping the frequency up or down
- Some zone AVR properties such as tone settings are now polled during full updates
- Parsing issues for the
display
andsignal_input_resolution
have been fixed - For VSX-930, the power on volume bounce setting has been disabled by default, and it no longer supports polling of unsupported video properties on full updates making these complete faster
See the aiopioneer releases page for a detailed list of changes.
⚠️ Breaking Changes
- Integration configuration via
configuration.yaml
is no longer supported. ADR10 outlines that integrations that communicate with devices, such as this one, must be configured via the UI - Migration from
configuration.yaml
is not implemented. Instead, add the integration via the UI and change the settings there to match your previous configuration - As AVR properties are now available as separate entities, the corresponding AVR property groups that were previously exposed as attributes on the
media_player
entities have been removed - Some AVR properties were previously set to
---
when undefined or unknown. These properties are now set to a null value in such cases - The
set_tuner_preset
service has been renamed toselect_tuner_preset
, and theset_tuner_band
service has been renamed toselect_tuner_band
Full Changelog: 0.8.6...0.9.0