8000 Sony Songpal errors every time I start HA, never goes away. · Issue #24269 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Sony Songpal errors every time I start HA, never goes away. #24269

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
recklessnl opened this issue Jun 2, 2019 · 5 comments · Fixed by #27398
Closed

Sony Songpal errors every time I start HA, never goes away. #24269

recklessnl opened this issue Jun 2, 2019 · 5 comments · Fixed by #27398
Assignees

Comments

@recklessnl
Copy link
recklessnl commented Jun 2, 2019

Home Assistant release with the issue: 0.92.3

Last working Home Assistant release (if known): I've always had this error, ever since 0.70.

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

Component/platform: Sony Songpal: https://www.home-assistant.io/components/songpal/

Description of problem:
I have a Sony STR-DN 1080 AVR connected to my TV. Since it's a Sony model, I linked it to Home Assistant. All the controls work fine (muting, volume changing, input changing) so I can use the device just fine. The only bug that I have is that the correct on / off state is not being transmitted properly. I keep mine in standby mode, so that when the TV goes on, the AVR will go on too (due to HDMI ARC). This works great, so I want to keep this. However, it seems that HA does not correctly register whether or not the device is actually on. Additionally, I get tons of errors every single time I reboot HA.

This is what I have configured in configuration.yaml:

media_player:
  - platform: songpal
    name: Sony AVR
    endpoint: http://192.168.1.23:10000/sony

And these are the HA log errors I get every single time I boot HA:

2019-06-02 16:29:07 WARNING (MainThread) [songpal.service] Got duplicate signature for MethodSignature(name='getSourceList', input={'scheme': <class 'str'>}, output={'source': <class 'str'>, 'title': <class 'str'>, 'isPlayable': 'bool', 'isBrowsable': 'bool', 'playAction': <class 'str'>, 'outputs': 'string*', 'meta': <class 'str'>, 'iconUrl': <class 'str'>, 'protocols': 'string*', 'upnpOperationInfo': 'UpnpOperationInfo'}, version='1.2'), existing was <Method avContent.getSourceList({'scheme': <class 'str'>}) -> {'iconUrl': <class 'str'>,
 'isBrowsable': 'bool',
 'isPlayable': 'bool',
 'meta': <class 'str'>,
 'outputs': 'string*',
 'playAction': <class 'str'>,
 'source': <class 'str'>,
 'title': <class 'str'>}>. Keeping the existing one
2019-06-02 16:29:08 WARNING (MainThread) [songpal.service] Got duplicate signature for MethodSignature(name='getStorageList', input={'uri': <class 'str'>, 'isRegistered': <class 'str'>}, output={'uri': <class 'str'>, 'deviceName': <class 'str'>, 'volumeLabel': <class 'str'>, 'permission': <class 'str'>, 'position': <class 'str'>, 'formattable': <class 'str'>, 'mounted': <class 'str'>, 'wholeCapacityMB': <class 'int'>, 'freeCapacityMB': <class 'int'>, 'systemAreaCapacityMB': <class 'int'>, 'isAvailable': <class 'str'>, 'lun': <class 'int'>, 'type': <class 'str'>, 'protocol': <class 'str'>, 'format': <class 'str'>, 'error': <class 'str'>, 'isRegistered': <class 'str'>, 'registrationDate': <class 'str'>, 'isSqvSupported': <class 'str'>, 'hasNonStandardData': <class 'str'>, 'isProtected': <class 'str'>, 'isLocked': <class 'str'>, 'formatStatus': <class 'str'>, 'finalizeStatus': <class 'str'>, 'timeSecToFinalize': <class 'int'>, 'isSelfRecorded': <class 'str'>, 'isManagementInfoFull': <class 'str'>, 'timeSecToGetContents': <class 'int'>, 'hasUnsupportedContents': <class 'str'>, 'usbDeviceType': <class 'str'>, 'fileSystem': <class 'str'>}, version='1.2'), existing was <Method system.getStorageList({'uri': <class 'str'>}) -> {'deviceName': <class 'str'>,
 'error': <class 'str'>,
 'format': <class 'str'>,
 'formattable': <class 'str'>,
 'formatting': <class 'str'>,
 'freeCapacityMB': <class 'int'>,
 'isAvailable': <class 'str'>,
 'lun': <class 'int'>,
 'mounted': <class 'str'>,
 'permission': <class 'str'>,
 'position': <class 'str'>,
 'systemAreaCapacityMB': <class 'int'>,
 'type': <class 'str'>,
 'uri': <class 'str'>,
 'volumeLabel': <class 'str'>,
 'wholeCapacityMB': <class 'int'>}>. Keeping the existing one
2019-06-02 16:29:08 WARNING (MainThread) [songpal.service] Got duplicate signature for MethodSignature(name='getSystemInformation', input=None, output={'product': <class 'str'>, 'region': <class 'str'>, 'language': <class 'str'>, 'model': <class 'str'>, 'serial': <class 'str'>, 'macAddr': <class 'str'>, 'name': <class 'str'>, 'generation': <class 'str'>, 'area': <class 'str'>, 'cid': <class 'str'>, 'helpUrl': <class 'str'>, 'deviceID': <class 'str'>, 'version': <class 'str'>, 'duid': <class 'str'>, 'wirelessMacAddr': <class 'str'>, 'esn': <class 'str'>, 'iconUrl': <class 'str'>, 'ssid': <class 'str'>, 'bdAddr': <class 'str'>, 'initialPowerOnTime': <class 'str'>, 'lastPowerOnTime': <class 'str'>, 'bleID': <class 'str'>}, version='1.4'), existing was <Method system.getSystemInformation(None) -> {'area': <class 'str'>,
 'bdAddr': <class 'str'>,
 'cid': <class 'str'>,
 'deviceID': <class 'str'>,
 'duid': <class 'str'>,
 'esn': <class 'str'>,
 'generation': <class 'str'>,
 'helpUrl': <class 'str'>,
 'iconUrl': <class 'str'>,
 'language': <class 'str'>,
 'macAddr': <class 'str'>,
 'model': <class 'str'>,
 'name': <class 'str'>,
 'product': <class 'str'>,
 'region': <class 'str'>,
 'serial': <class 'str'>,
 'ssid': <class 'str'>,
 'updatableVersion': <class 'str'>,
 'version': <class 'str'>,
 'wirelessMacAddr': <class 'str'>}>. Keeping the existing one

I figured it would eventually be fixed but after months of these errors I figure I should share this. Again, mostly everything works, except that HA never gets the correct on / off state of the AVR (if I turn the AVR off, HA says it's still on).

@mammuth
Copy link
Contributor
mammuth commented Jul 7, 2019

I can confirm that this seems to be a general issue. It also occurs in my setup (different soundbar, hassio setup).

@rytilahti
Copy link
Member

Hi there, first of all, I'm happy to hear that there are users using this integration! :-)

Those warnings you posted are related to the backend library not handling multiple versions of the same command as offered by the device. I preferred to make it visible in case someone wants to look into implementing extra features (where available), but I think that could be converted to a debug logger...

For your real problem (not detecting the off/on state), could you enable songpal and homeassistant.components.songpal loggers with level debug in your configuration? The integration has two ways of knowing if a device is offline:

  1. communication with the device is not possible, or
  2. the device report its power state to be "active".

Considering that it stays "on" even if it is off, I think your device keeps reporting that it is active.. So more information how to fix this would be helpfuly, thanks!

@rytilahti rytilahti self-assigned this Jul 18, 2019
@recklessnl
Copy link
Author

Hi @rytilahti, thanks for making this component! I'm using it a lot, really glad that you made it part of Home Assistant!

Would you explain how to enable those loggers with level debug? I will definitely do this and share the log results, but I'm currently not sure how to enable it like you want to. If you could explain how to do so, I'll get on it asap!

@mammuth
Copy link
Contributor
mammuth commented Aug 22, 2019

@recklessnl this is how you enable different logging for a given component:

logger: 
    default: warn
    logs:
        homeassistant.components.songpal: debug

Logs are written to home-assistant.log in your configuration directory (next to your configuration.yaml) by default.

@rytilahti I could imagine a lot of people are using your work 😉 🎉
Integration usage statistics are tracked, so if you want to know how many people are using it, I'm sure you'll get an answer if you ask one of the core devs (best chance via discord probably).

@rytilahti
Copy link
Member

Thanks for your kind words! I finally found some time to sit down and do a new release and make a PR to get it updated 🎉

balloob pushed a commit that referenced this issue Oct 10, 2019
Fixes #24269 and fixes #26776 - potentially also #22116
balloob pushed a commit that referenced this issue Oct 13, 2019
Fixes #24269 and fixes #26776 - potentially also #22116
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants
0