media_player.squeezebox: Do not fail in case no players are connected, in which case squeezeserver will return a result without player_loop.#7617
Conversation
Do not fail in case no players are connected, in which case squeezeserver will return a result without player_loop.
|
@molobrakos, thanks for your PR! By analyzing the history of the files in this pull request, we identified @persandstrom, @dasos and @fabaff to be potential reviewers. |
|
Stack trace for reference: |
|
Can you also add the available property to entity? |
|
Ping |
|
I guess that should be possible ... maybe for another pr later? |
|
I'm fine with that for a future PR. |
|
this solves issue #6569 (but not the flaw that the component only looks for players exactly once at startup) |
|
I agree it would be nice if the component checked for players more than once at startup. And also provided the available property as (suggested above). |
|
I haven't tested this (not at home), but the periodically checking of newly connected players might already work because of netdisco/discovery sending out discovery requests periodically? |
|
I think the component needs to listen to the discovery event:
https://home-assistant.io/developers/component_discovery/
…On 05/06/2017 17:01, Erik Eriksson wrote:
I haven't tested this (not at home), but the periodically checking of
newly connected players might already work because of
netdisco/discovery sending out discovery requests periodically?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7617 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AG7zxxJqdXoxc4kMSt1h7PJtq9ah_rbhks5sBCZ0gaJpZM4NczEo>.
|
Do not fail in case no players are connected, in which case squeezeserver will return a result without player_loop.
Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for
configuration.yaml(if applicable):Checklist:
If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
toxrun successfully. Your PR cannot be merged unless tests passREQUIREMENTSvariable (example).requirements_all.txtby runningscript/gen_requirements_all.py..coveragerc.If the code does not interact with devices:
toxrun successfully. Your PR cannot be merged unless tests pass