8000 Add Bose soundtouch discovery support and upgrade libsoundtouch library by CharlesBlonde · Pull Request #7005 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add Bose soundtouch discovery support and upgrade libsoundtouch library #7005

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

Merged
merged 3 commits into from
Apr 20, 2017

Conversation

CharlesBlonde
Copy link
Contributor
@CharlesBlonde CharlesBlonde commented Apr 9, 2017

Description:

Update Bose Soundtouch component to:

  • Support Home Assistant discovery
  • Upgrade libsoundtouch library to 0.3.0 (fix encoding issues with non ASCII characters)

Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.io#2401

Checklist:

If user exposed functionality or configuration variables are added/changed:

If the code communicates with devices, web services, or third-party tools:

  • Local tests with tox run successfully. Your PR cannot be merged unless tests pass
  • New dependencies have been added to the REQUIREMENTS variable (example).
  • New dependencies are only imported inside functions that use them (example).
  • New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
  • New files were added to .coveragerc.

If the code does not interact with devices:

  • Local tests with tox run successfully. Your PR cannot be merged unless tests pass
  • Tests have been added to verify that the new code works.

@homeassistant
Copy link
Contributor

Hi @CharlesBlonde,

It seems you haven't yet signed a CLA. Please do so here.

Once you do that we will be able to review and accept this pull request.

Thanks!

@mention-bot
Copy link

@CharlesBlonde, thanks for your PR! By analyzing the history of the files in this pull request, we identified @fabaff, @balloob and @rmkraus to be potential reviewers.

Copy link
Member
@pvizeli pvizeli left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use hass.data instead global DEVICE over your code. That would be greate 👍

@CharlesBlonde
Copy link
Contributor Author
CharlesBlonde commented Apr 12, 2017

Following your remark, I removed the global DEVICE variable... and it was a massive refactoring :)
But I agree, it's better without this variable.

Besides, I updated media_player services.yaml because the Soundtouch part was totally wrong (it was my work, month ago). But I'm not sure to understand where it is used: Even with wrong data inside, it was working fine.

Edited: The Travis job failed but it has nothing to do with my work and since a few hours every jobs failed with the same Alexa tests so I think the error is somewhere else :)

@CharlesBlonde
Copy link
Contributor Author

I just commit a small rewording and push force to trigger a new Travis build.


if discovery_info:
# Discovery
host = discovery_info[0]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Discovery info is a dictionary. Make sure your local dev environment has the latest netdisco (as required by the latest HASS)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ho S****, you are right. I should be using an old version in my Virtualenv because when I did my tests, it was a tuple and not a dictionary.
It should be better now.

@balloob
Copy link
Member
balloob commented Apr 16, 2017

Besides, I updated media_player services.yaml because the Soundtouch part was totally wrong (it was my work, month ago). But I'm not sure to understand where it is used: Even with wrong data inside, it was working fine.

It is shown in the service dev tool in the frontend. (and maybe one day in a config GUI)

Copy link
Member
@balloob balloob left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Awesome 🐬

@balloob balloob dismissed pvizeli’s stale review April 20, 2017 04:52

Comment addressed

@balloob balloob merged commit 931fce8 into home-assistant:dev Apr 20, 2017
@balloob balloob mentioned this pull request Apr 21, 2017
@home-assistant home-assistant locked and limited conversation to collaborators Aug 12, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants
0