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

Modes for AV Receiver inputs #85

Closed
philk opened this issue Jan 10, 2018 · 12 comments
Closed

Modes for AV Receiver inputs #85

philk opened this issue Jan 10, 2018 · 12 comments

Comments

@philk
Copy link

philk commented Jan 10, 2018

Can I put in a request for some modes for setting inputs on an AV Receiver?

Mode: input / output / source
Settings: Media Player, Chromecast, Apple TV, AM/FM, Internet Radio, Satellite, Game Console, Xbox, etc etc

If they have to be generic a decent basic list would be: tuner, media player, cable, satellite, tv, usb, internet radio, bluray, aux / auxiliary, game / game console, dvd, cd

@Fleker
Copy link
Contributor

Fleker commented Jan 10, 2018

Thanks for the feature request. I'll forward it.

@Fleker
Copy link
Contributor

Fleker commented Jan 22, 2018

I have added the following mode:

  • input source
  • output source

I have added the following settings:

  • media player
  • chromecast
  • tv
  • am fm
  • internet radio
  • satellite
  • game console

These changes will be live in a few days.

@Fleker Fleker closed this as completed Jan 22, 2018
@philk
Copy link
Author

philk commented Jan 22, 2018

Awesome, thank you!

@i8beef
Copy link

i8beef commented Feb 13, 2018

What's the correct usage here for these new mode here? I tried the following but I either don't know the magic words, or this is being silently dropped after a sync...

    "attributes": {
      "availableModes": [{
          "name": "input source",
          "name_values": [{
            "name_synonym": ["activity"],
            "lang": "en"
          }],
          "settings": [{
            "setting_name": "tv",
            "setting_values": [{
              "setting_synonym": ["tv", "television"],
              "lang": "en"
            }]
          }, {
            "setting_name": "meda player",
            "setting_values": [{
              "setting_synonym": ["chromecast"],
              "lang": "en"
            }]
          }],
          "ordered": false
        }]
    },

@peterbn
Copy link

peterbn commented Apr 12, 2018

+1 - I would also love to know how to actually use these

@i8beef
Copy link

i8beef commented Apr 12, 2018

"set (device) input source to (setting_name)"

Note that I couldn't ever get it to work by using one of the setting_synonyms.

@Fleker
Copy link
Contributor

Fleker commented Apr 12, 2018

The synonyms would need to an array of valid settings. input source is the name and the synonym. activity would not be recognized by the grammar right now.

@i8beef
Copy link

i8beef commented Apr 12, 2018

Right. It also doesn't recognize the synonyms as provided for the settings, i.e., saying "set family room tv input source to chromecast" as one might expect would be possible given my above sample code does not work either, you have to set it to "media player" specifically.

I'm assuming the synonyms are just ignored right now and are there for future expansion to this sort of functionality.

@Fleker
Copy link
Contributor

Fleker commented Apr 13, 2018

If you add a new setting with a setting_name of chromecast it should work.

@i8beef
Copy link

i8beef commented Apr 13, 2018

Really? My understanding was that you could only use the preapproved setting names listed above. If so, that's awesome and I need to make some changes.

@Fleker
Copy link
Contributor

Fleker commented Apr 13, 2018

Chromecast is an existing sensor name.

@i8beef
Copy link

i8beef commented Apr 14, 2018

Ah, I was just using that as an example, I and likely a lot of others using this are really looking for custom, arbitrary mode names and setting names, and expect the synonyms to work seamlessly with whatever we choose to put in there. Still looking forward to this being expanded!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants