Service.InputSource use case?
See original GitHub issueLooking at the new Television services added:
Can you please explain Service.InputSource, how and what it can be used for? What use-case is there for:
Characteristic.InputSourceType and Characteristic.InputDeviceType
/**
* Service "Input Source"
*/
Service.InputSource = function(displayName, subtype) {
Service.call(this, displayName, '000000D9-0000-1000-8000-0026BB765291', subtype);
// Required Characteristics
this.addCharacteristic(Characteristic.ConfiguredName);
this.addCharacteristic(Characteristic.InputSourceType);
this.addCharacteristic(Characteristic.IsConfigured);
this.addCharacteristic(Characteristic.CurrentVisibilityState);
// Optional Characteristics
this.addOptionalCharacteristic(Characteristic.Identifier);
this.addOptionalCharacteristic(Characteristic.InputDeviceType);
this.addOptionalCharacteristic(Characteristic.TargetVisibilityState);
this.addOptionalCharacteristic(Characteristic.Name);
};
inherits(Service.InputSource, Service);
Service.InputSource.UUID = '000000D9-0000-1000-8000-0026BB765291';
Thanks for the info 😃
Issue Analytics
- State:
- Created 5 years ago
- Comments:22 (9 by maintainers)
Top Results From Across the Web
InputSource - Java in a Nutshell, 5th Edition [Book] - O'Reilly
This class allows you to specify more than one input source. The XMLReader will first call getCharacterStream( ) and use the returned Reader...
Read more >What is the difference between InputSource and InputStream?
An InputSource can read from an InputStream , but it can also read from a Reader or direct from a URL (opening the...
Read more >InputSource (Java Platform SE 7 ) - Oracle Help Center
This class allows a SAX application to encapsulate information about an ... The SAX parser will use the InputSource object to determine how...
Read more >InputSource (Org.XML.SAX Package)
Extends java.lang.object. A single input source for an XML entity. ... The SAX parser will use the InputSource object to determine how to...
Read more >Develop a TV input service
The TIF Companion Library is a framework that provides extensible implementations of common TV input service features. It is meant to be used...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’ve developed two accessories since teh initial support for TVs was added… One for my Sony Bravia TV and the other for my Denon AVR (Even though not a TV, its create to be able to select Input sources and use those in HomeKit scenes. Happy to share the code if anyones interested in playing with what developed
I doubt whether it’s because of the same IP address (you could check by running both homebridge instances on you mac), but it might have to do with the Remote app not liking multiple TVs behind the same Bonjour service.
Somewhere in the fine print, the HAP spec states that a HomeKit bridge is only to be used for accessories that don’t natively talk IP. I’ve never encountered a smart TV that used another protocol, so it might very well be that Apple simply doesn’t cater for the use case of (multiple) TV accessories behind a HomeKit bridge (Bonjour service). Meaning it might not be fixed in the beta cycle…