8000 Sonos Device Name · Issue #10015 · home-assistant/core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Sonos Device Name #10015

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
geekofweek opened this issue Oct 22, 2017 · 3 comments
Closed

Sonos Device Name #10015

geekofweek opened this issue Oct 22, 2017 · 3 comments

Comments

@geekofweek
Copy link
Contributor
geekofweek commented Oct 22, 2017

Make sure you are running the latest version of Home Assistant before reporting an issue.

You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:

Home Assistant release (hass --version):
0.56.0

Python release (python3 --version):
Python 3.6.3

Component/platform:
Sonos

Description of problem:
Sonos device names no longer properly populated. Instead devices show up as media_player.unnamed_device

Expected:
Device name should reflect Sonos name

Example: media_player.living_room

Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

Using the Docker image.
No errors present in logs, happens with or without discovery component.
New issue with 0.56.0, not present on previous releases.

@bachya
Copy link
Contributor
bachya commented Oct 22, 2017

This is happening with Nest thermostats, as well.

@bachya
Copy link
Contributor
bachya commented Oct 22, 2017

Seems like this PR caused this issue, given that it touched the base media player entity.

@DubhAd
Copy link
Contributor
DubhAd commented Oct 22, 2017

I'm seeing exactly the same behaviour on 0.56

@home-assistant home-assistant locked and limited conversation to collaborators Mar 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants
0