Skip to content
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

Yamaha or Yamaha Musiccast integration does not find zone 2 #43144

Closed
Jamezz98 opened this issue Nov 12, 2020 · 2 comments
Closed

Yamaha or Yamaha Musiccast integration does not find zone 2 #43144

Jamezz98 opened this issue Nov 12, 2020 · 2 comments

Comments

@Jamezz98
Copy link

Jamezz98 commented Nov 12, 2020

The problem

Environment

Problem-relevant configuration.yaml

media_player:
  - platform: yamaha_musiccast
    host: 192.168.1.20
  - platform: yamaha
    host: 192.168.1.20
    source_ignore:
      - "AUDIO2"
      - "AUDIO3"
      - "JUKE"
      - "Qobuz"
      - "TIDAL"
      - "TUNDER"
      - "Deezer"
      - "AV1"
      - "AV2"
      - "AV3"
      - "MusicCast Link"
      - "Server"
      - "TUNER"
      - "USB"
      - "AUX"
    source_names:
      AUDIO1: "TV"
      HDMI1: "Xbox"
      HDMI3: "Amazon"
      HDMI4: "Mediacenter"
    zone_names:
      main: "Lounge"
      zone2: "Dining Area"

Traceback/Error logs


Additional information

I have queried the device api and posted the list of what is supported in this thread: https://community.home-assistant.io/t/cant-find-my-zone-b-using-yamaha-integration/241409
I have also tested a GET request to the device API against zone2 to toggle the power which seems to work fine.

@probot-home-assistant
Copy link

Hey there @jalmeroth, mind taking a look at this issue as its been labeled with an integration (yamaha_musiccast) you are listed as a codeowner for? Thanks!
(message by CodeOwnersMention)

@github-actions
Copy link

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Feb 10, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Mar 19, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants