0.9.1

What's Changed

• New service send_command that sends defined commands to the AVR. See the Pioneer documentation linked from the aiopioneer references for the parameters accepted for each command. Fixes #41

All Changes

• Update Makefile to support local repo e99590f
• Use TunerBand enum in service select_tuner_band 93f9382
• Don't shutdown or del pioneer if it was never created 84c875a
• Fix passing of exception text when aborting
• Moved async yield to PioneerAVR.shutdown 9af9d58
• Add send_command service d023af3
• Add strings for PioneerAVR exceptions
• Remove asyncio import a19b091
• Fix select_tuner_band API call 9a37dd9
• Remove return code checking from PioneerAVR method calls ae450c0
• Move exception checking and translation to PioneerEntityBase.pioneer_command ae450c0

0.9.0

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 and display, 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 and media_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 and signal_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 to select_tuner_preset, and the set_tuner_band service has been renamed to select_tuner_band

Full Changelog: 0.8.6...0.9.0

0.9.0rc1

⚠️ 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 and display, 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 and media_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 and signal_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 to select_tuner_preset, and the set_tuner_band service has been renamed to select_tuner_band

Full Changelog: 0.8.6...0.9.0

0.8.6

⚠️ Deprecation notice

Integration configuration via configuration.yaml will no longer be supported from the next minor release (0.9.0).

ADR10 outlines that integrations that communicate with devices, such as this one, must be configured via the UI. Also, several more recently added features, such as support for the HA device registry and dynamic integration loading/unloading, already do not work unless configured via the UI.

All configuration.yaml config options can be configured via the UI configuration now. If you believe that your current use case is not supported, then please describe your configuration in a reply to the discussion for this release, including your configuration.yaml snippet.

Given that there are not many configurable options to migrate, there won't be an automatic YAML migration path. To migrate, you will need to delete the configuration.yaml config, restart HA, remove any stale entities from Settings > Devices & Services > Entities, then configure the integration via the UI.

What's Changed

• Expose listening_mode_raw, tone and audio in main zone entity attributes
• Exclude AVR attribute state recording by recorder by default
• Support updates to disable_auto_query and get_zone_listening_modes made in aiopioneer 0.5.0
• Bump aiopioneer to 0.5.0

Full Changelog: 0.8.5...0.8.6

0.8.5

• Don't assume MediaPlayerEntityFeatures are mutually exclusive b1694fc
• Update usage of MediaPlayerEntityFeature to avoid deprecation warning in 2024.1 28abd7c

Full Changelog: 0.8.4...0.8.5

0.8.4

• Add set_tuner_band service in HA integration and aiopioneer (fe3966d)
• In configure, redisplay basic options with queried sources if query sources enabled (1459397)
• Add step on integration add to disable source query and set basic parameters (1459397)
• Fix config entry version update on migration, fixes #28 (9a4ad0c)
• Improvements in aiopioneer 0.4.3:
  • remove race condition that may have caused AVR responses to be missed
  • avoid multiple commands being executed in parallel in several situations

0.8.3

What's Changed

• Extra aiopioneer parameters can now be configured (as JSON values) via the UI
• Cleaned up debug so that commands sent are shown in debug logging without setting additional debug parameters. This should make it easier to troubleshoot AVR parser issues
• Sources queried from the AVR are now retrieved from aiopioneer

Full Changelog: 0.8.2...0.8.3

0.8.2

What's changed

• Fix default value for debug_config

Full Changelog: 0.8.1...0.8.2

0.8.1

What's Changed

• Fix 'NoneType' object has no attribute 'get' by @11harveyj in crowbarz/aiopioneer#24 fixes #25

Full Changelog: 0.8...0.8.1

0.8

What's Changed

• The options flow UI has been redesigned to use selectors. This allows graphical editing of AVR sources (no more JSON!) The options flow is also now split across multiple pages. The debug options page is shown only for users with Advanced Mode enabled in their profile
• Handling of invalid input has also been improved, and data input errors are now displayed in the UI instead of in the HA log. Previously entered values are no longer lost when invalid input is detected
• A subset of all AVR sources can now be specified for each zone. Zone 1 supports all sources, but on some AVRs only a subset of all sources are usable on other zones. You can order the sources displayed the media_player zone entities by selecting them in the desired order from the list of available sources
• More detailed debugging can now can be turned on/off on a per module basis by setting debug config

Beta Changes

• Under the hood, @11harveyj has refactored the parser for the AVR output. Many more AVR responses are now decoded and are made available as attributes of the media_player zone entity. Until the decoders are finalised, hopefully by the 0.9 release, these are subject to change with updates to aiopioneer

Breaking Changes

• For configuration.yaml users, the zone_z_sources param has been renamed to hdzone_sources to be more consistent with the rest of the integration. A warning will be displayed in the HA log on integration startup. Support for the old param will be removed in a future release

Full Changelog: 0.7.3...0.8