Move Television services to external accessory

[sander1988]

Due to HomeKit limitations you only have one television for each platform. Otherwise the (Apple TV) remote won't work with the 2nd TV. So by creating a special platform accessory for each TV we can get around this problem/limitation.

Please give me some time to make this change. I will create a pull request when it's ready.

[sander1988]

There is a test version available here: https://github.com/sander1988/homebridge-edomoticz/tree/issue217_tvservices_external_platform

I will be testing this update for a few days before creating a pull request. Help with testing is appreciated, but only for those who use one or more televisions with HomeBridge.

Please note that you have to add a 2nd platform definition to your HomeBridge config file in order to enable this feature. Something like this after the existing eDomoticz platform:

{
        "platform": "eDomoticzTV",
        "name": "eDomoticzTV",
        "server": "127.0.0.1",
        "port": "8080",
        "ssl": 0,
        "roomid": 0,
        "mqtt": 1
}

[ProBatou]

It works great thanks @sander1988, I got my icon in the app. @PatchworkBoy is it possible to add to future releases

[PatchworkBoy]

In progress... using the built in this.api.publishExternalAccessory method rather than having to spool up a 2nd platform. Also adds Category.TELEVISION as appropriate. Just testing at the mo.

[PatchworkBoy]

Think I need to make some changes @sander1988… for both my TVs, the input selector is on a different hwId to the rest of the controls (ir blaster controlling a 4x4 hdmi matrix switch for the inputs, and a custom implementation of Kodi Media Server protocol for the rest). Fudged round it by pulling device.description and passing thru as this.descript, then adding same string to the Domoticz device descriptions that should be combined into one accessory (eg: LRTV)

[PatchworkBoy]

Think all these are resolved now. Open new issue if not after installing 2.1.40 from NPM...