home-assistant
Volume issue after integration into Config.Yaml
The problem
After integrating into Yaml and restart , HA indeed finds my Pioneer AVR 930. For one or another reason when playing music using Cast or Music Assistant the music volume increases in little steps while doing nothing. After a few minutes , no more sound , volume gets set to 0... When i delete the integration the problem is gone.
What version of Home Assistant Core has the issue?
2024.10.2
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Pioneer
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
This is what I added…
media_player: - platform : pioneer host : 192.168.1.199
Restarted HA and the AVR 930 becomes available. I can switch it on and off. I can select all the sources. You can not select media. But… Once playing music using Cast or Music Assistant on a HA media player the volume of the AVR 930 decreases by itself up to 0 after a few minutes. You turn the volume up manually and afterwards it decreases once again by itself. Strange… When I delete the Pioneer integration this strange effect disappears.
Le dim. 13 oct. 2024 à 21:59, Michael @.***> a écrit :
Please provide the part you've add to your configuration.yaml, thx
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2409105505, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FQFDREYPSFB35HQTODZ3LGK3AVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBZGEYDKNJQGU . You are receiving this because you authored the thread.Message ID: @.***>
I'm confused - you add the pioneer config, than your AVR 930 becomes available, but its volume "goes crazy" at some point in time? Than your write, that you remove the pioneer config and this issue stops happening? But how do you still play something on this AVR 930, when it is not integrated anymore?
Hello Michael.
The AVR 930 is internet connected and Airplay compatible. On Home Assistant I use Music Assistant. Music Assistant is an integration which searches on your local internet all of the devices that are Cast , ChromeCast and Airplay compatible. I can play music on my AVR 930 because Music Assistant controls it using Airplay. Once the AVR 930 gets a signal from Music Assistant using Airplay it automatically turns on and plays music. The reason why I wanted to add your integration as well was just to have the possibility to control the sources from the AVR 930 in Home Assistant so I could use them in automations to create other possibilities.
Regards.
JS.
Le lun. 14 oct. 2024 à 22:23, Michael @.***> a écrit :
I'm confused - you add the pioneer config, than your AVR 930 becomes available, but its volume "goes crazy" at some point in time? Than your write, that you remove the pioneer config and this issue stops happening? But how do you still play something on this AVR 930, when it is not integrated anymore?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2412157254, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FSF4SGVG23BZNAXA7TZ3QR2JAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJSGE2TOMRVGQ . You are receiving this because you authored the thread.Message ID: @.***>
Music Assistant is a custom component, which is not maintained by the homeassistant project. Do you encounter the same issue, when removing the AVR 930 from the control of this Music Assistant?
I don’t know… If I do in can not play music on it using HA. The pioneer integration only gives you the possibility to switch it on or off and select sources. There is no media select.
Le mar. 15 oct. 2024 à 19:24, Michael @.***> a écrit :
Music Assistant is a custom component, which is not maintained by the homeassistant project. Do you encounter the same issue, when removing the AVR 930 from the control of this Music Assistant?
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2414601355, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FXJDQA3X7IWVNN4SALZ3VFWNAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMJUGYYDCMZVGU . You are receiving this because you authored the thread.Message ID: @.***>
![home-assistant[bot] avatar](https://avatars.githubusercontent.com/in/97978?v=4 "Published by a pub.dev verified publisher"){kind=small}
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
![issue-triage-workflows[bot] avatar](https://avatars.githubusercontent.com/u/13844975?v=4 "Published by a pub.dev verified publisher"){kind=small}
No, it has not.
Le mer. 30 oct. 2024 à 09:08, issue-triage-workflows[bot] < @.***> a écrit :
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2446117696, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FUKCVV752EVOV75R7TZ6CHYNAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINBWGEYTONRZGY . You are receiving this because you authored the thread.Message ID: @.***>
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Hello.
This issue is not resolved.
Regards.
JS.
Le mer. 13 nov. 2024 à 11:07, issue-triage-workflows[bot] < @.***> a écrit :
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2473062285, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FUHZWAVLCER53Z34UL2AMQE3AVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZTGA3DEMRYGU . You are receiving this because you authored the thread.Message ID: @.***>
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Doesn’t work for me.
Le mer. 27 nov. 2024 à 12:07, issue-triage-workflows[bot] < @.***> a écrit :
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2503587283, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FXN5E7WAZZ76XA7ZGL2CWRVTAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMBTGU4DOMRYGM . You are receiving this because you authored the thread.Message ID: @.***>
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Still not working…
Le mer. 11 déc. 2024 à 07:11, issue-triage-workflows[bot] < @.***> a écrit :
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2535820674, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FSFOHIBAXCZIQSKP4L2FATVXAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZVHAZDANRXGQ . You are receiving this because you authored the thread.Message ID: @.***>
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
Still doesn’t work for me…
Le mer. 25 déc. 2024 à 08:06, issue-triage-workflows[bot] < @.***> a écrit :
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2561904359, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FVX6L4EU6IGI5DOLAT2HK3WLAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRRHEYDIMZVHE . You are receiving this because you authored the thread.Message ID: @.***>
Same problem with my VSX-930, the reason seems to be the Pioneer integration --> https://github.com/music-assistant/support/issues/3484. When I remove the integration, this issue disappears. There seem to be a conflict between Pioneer integration in HA core and AirPlay device from Music Assistant regarding the volume control.
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
👍
Le lun. 21 avr. 2025 à 01:06, issue-triage-workflows[bot] < @.***> a écrit :
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2817380436, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FSCIQBOP6TZEO3B7YT22QR7ZAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJXGM4DANBTGY . You are receiving this because you authored the thread.Message ID: @.***> issue-triage-workflows[bot] left a comment (home-assistant/core#128249) https://github.com/home-assistant/core/issues/128249#issuecomment-2817380436
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-2817380436, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FSCIQBOP6TZEO3B7YT22QR7ZAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQMJXGM4DANBTGY . You are receiving this because you authored the thread.Message ID: @.***>
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
👍
Le dim. 20 juil. 2025 à 16:06, issue-triage-workflows[bot] < @.***> a écrit :
issue-triage-workflows[bot] left a comment (home-assistant/core#128249) https://github.com/home-assistant/core/issues/128249#issuecomment-3094556646
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-3094556646, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FVB4ZUWWFPH2HSU2LL3JOO6NAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTAOJUGU2TMNRUGY . You are receiving this because you authored the thread.Message ID: @.***>
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
👍
Le sam. 18 oct. 2025 à 17:06, issue-triage-workflows[bot] < @.***> a écrit :
issue-triage-workflows[bot] left a comment (home-assistant/core#128249) https://github.com/home-assistant/core/issues/128249#issuecomment-3418548288
There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.
— Reply to this email directly, view it on GitHub https://github.com/home-assistant/core/issues/128249#issuecomment-3418548288, or unsubscribe https://github.com/notifications/unsubscribe-auth/BGEH4FQ3O7OARI6DDVMNJHT3YJJPTAVCNFSM6AAAAABP2R7F3GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTIMJYGU2DQMRYHA . You are receiving this because you authored the thread.Message ID: @.***>