Core: Sound mode errors in HA log

Created on 21 Jul 2018  Â·  23Comments  Â·  Source: home-assistant/core

Home Assistant release with the issue:

0.74

Last working Home Assistant release (if known):
0.73

Operating environment (Hass.io/Docker/Windows/etc.):

Docker

Component/platform:

DenonAVR
https://www.home-assistant.io/components/media_player.denonavr/

Description of problem:
Log is spammed with errors about sound mode

2018-07-20 21:51:12 WARNING (SyncWorker_9) [DenonAVR] Not able to match sound mode, returning raw sound mode.
2018-07-20 21:51:23 WARNING (SyncWorker_13) [DenonAVR] Not able to match sound mode, returning raw sound mode.
2018-07-20 21:51:34 WARNING (SyncWorker_5) [DenonAVR] Not able to match sound mode, returning raw sound mode.
2018-07-20 21:51:45 WARNING (SyncWorker_7) [DenonAVR] Not able to match sound mode, returning raw sound mode.
2018-07-20 21:51:56 WARNING (SyncWorker_17) [DenonAVR] Not able to match sound mode, returning raw sound mode.
2018-07-20 21:52:07 WARNING (SyncWorker_3) [DenonAVR] Not able to match sound mode, returning raw sound mode.
2018-07-20 21:52:18 WARNING (SyncWorker_17) [DenonAVR] Not able to match sound mode, returning raw sound mode.
2018-07-20 21:52:29 WARNING (SyncWorker_14) [DenonAVR] Not able to match sound mode, returning raw sound mode.
2018-07-20 21:52:40 WARNING (SyncWorker_12) [DenonAVR] Not able to match sound mode, returning raw sound mode.

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Media_player:
 platform: denonavr
    host: 172.19.3.13
    name: Denon Receiver
    show_all_sources: False
    timeout: 2

Traceback (if applicable):


Additional information:
Device is turned off

Most helpful comment

@balloob I already have a pull request in the denonavr library from a few days ago to incorperate which sound mode was not alle to be matched. I already realised that that would be handy.

My appologies for generating so much error. That was of course not my intention.
Today I am not home, but I will make a pull request tommorrow to get rid of duplicaten errors and only show the error once.

All 23 comments

Have the same issue. The warnings disappear once the receiver is turned on and off again.

When the receiver is turned on the errors keeps appearing

Strange, for me the message appeared after upgrading to 0.74. Once I turned the receiver on and off via HA the warnings haven’t appeared anymore.

Edit: After a few days the logs are filled with these warnings. Turned the receiver on/off and they disappeared again for now.

I'm also receiving this warning with HassOS 1.7 and HA 0.74. I'm getting this message while my Marantz SR7005 is off. I've do not have zones specified in my config. as I don't use them. But I have verified that no zones are on. After turning on the receiver, home assistant showed no sound mode in the card details and I continued to get the warning. The iOS Marantz app showed 'Standard(Dolby)'. After switching channels on my DVR the sound mode switched to 'Stereo', the home assistant card details matched and I stopped getting the message.

I do not want to use sound mode aspecially not Stereo on the device.

I have deleted a comment by @squeepip and blocked him for 7 days for violating our Code of Conduct.

I did not mean to be rude only clearify that i am not using the sound mode at all as far as i beleive and do not like to set some mode on Stereo just to avoid any errors in the log. I could see the advantange of the sound mode, but i think it should not generate such amount of errors in the HA log.

Don't worry @Martinvdm, it was not rude at all.

@starkillerOG, looks like a check should be added so it only logs a warning once. It should also log what sound mode it couldn't find.

@balloob I already have a pull request in the denonavr library from a few days ago to incorperate which sound mode was not alle to be matched. I already realised that that would be handy.

My appologies for generating so much error. That was of course not my intention.
Today I am not home, but I will make a pull request tommorrow to get rid of duplicaten errors and only show the error once.

As for everyone that experiences this error: please go to states and look up the value of "sound_mode_raw" for each sound mode that gives this error, and report that error in this issue, or make a new issue on the denonavr library, as is stated in the homeassistant.io documents.
You can also wait until the new PR is merged and the sound_mode_raw will be stated in the error message.

For your information, you can just ignore this error in the meantime. It will not affect the operation of Home assistant or your AVR. The only thing this error indicaties is that on the front pannel the sound mode box will be empty because it could not determine which value of that listbox fits the sound mode that your AVR reporter. This is simply fixed by adding that raw_sound_mode in the key list of sound_modes.

Perhaps i dont fully understand the sound_mode, but my receiver is turned off. There is No states about the the sound_mode and the error is continuous repeating in the HA log. Isn’t a better approuch not trying to match a sound_mode when the device is turned off in the first place?

@Martinvdm The receiver will actually report its full status including things like volume level, input source, sound mode, mute on/off etc. even if the receiver is turend off.
All this information is provided in the status xml of the receiver and is available regardless if the receiver is on or off.
Allmost all properties of the receiver are updated continuesly even if the receiver is turned off. This is done because we need to poll the on/off status of the receiver constantly if the receiver is turned off to determine if the receiver is beeing turned on by the remote or through some other method.
This is done by requesting the status xml of the receiver that contains the on/off status. This same xml document also contains all other properties like the sound mode. Since this status xml has already been polled for the on/off status, we might as well update all other information in this xml. it does not require any extra comunication to the receiver and parsing the information hardly costs any resources. so why would we not update the sound_mode if the receiver is off?

As for the warnings you get, that will be fixed shortly to not show any duplicates, so you will only get 1 warning regardless of the power status of the receiver.

@balloob I just made an update to the PR for the denonavr library.
That will fix the duplicate warnings as soon as @scarface-4711 merges it.

As for everyone that experiences this error: please go to states and look up the value of "sound_mode_raw" for each sound mode that gives this error,

sound_mode_raw: Dolby Surround

@technicalpickles "Dolby Surround" has been added to the PR for the denonavr library, as soon as that is merged it will be fixed for you.

@balloob just made a PR in Home assistant that fixes this issue.
(Fix has been merged in the denonavr library version 0.7.5)
Can jou merge it and close this issue?

upgraded to 0.75, still the error; but a lot less indead. I think you are missing:

DTS Neural:X
DTS Surround

 [DenonAVR] Not able to match sound mode: 'DTS Surround', returning raw sound mode.

I've found another some more on my receiver
sound_mode_raw: Pure_Direct sound_mode_raw: Standard(DTS) sound_mode_raw: Neural sound_mode_raw: Multi_CH_Stereo
I went through every mode this time, so this should be it for my Marantz.

Edit: my bad, I'm putting this on the dennonavr repo.

@Martinvdm @jasonehines, see this PR in the denonavr library. That schould add all those sound modes.

@starkillerOG
Great! But isn’t that you are removing ‘DTS NEURAL:X’ with this code? I can only find ‘DTS + NEURAL:X’ in the code now.

@martinvdm nope, line 48 is unchanged so DTS NEURAL:X is still their. Just look a bit closer.

AH you right, overlooked

Was this page helpful?
0 / 5 - 0 ratings

Related issues

bdraco picture bdraco  Â·  3Comments

sh0rez picture sh0rez  Â·  3Comments

kirichkov picture kirichkov  Â·  3Comments

missedtheapex picture missedtheapex  Â·  3Comments

piitaya picture piitaya  Â·  3Comments