Input Controls Missing

Updated to 0.9 last night and tried enabling input controls but had no controls show up in Eve or Home. I’ve tried unpairing and re-pairing, as well as setting up a separate Apple TV to avoid any accessory cache, but still haven’t gotten the input controls to show up at all. Here’s my config:

        {
            "platform": "DACP",
            "devices": [
                {
                    "name": "Bedroom Apple TV",
                    "pairing": "VALID",
                    "serviceName": "VALID",
                    "features": {
                        "no-volume-controls": true,
                        "alternate-playpause-switch": true,
                        "alternate-input-controls": true,
                        "album-artwork": "/tmp/nowplaying.png"
                    }
                }
            ]
        }

I tried many other configs to try and get something to show up, but was never able to. Here are some example feature configs I’ve tried:

"features": {
    "no-volume-controls": true,
    "alternate-input-controls": true
}

"features": {
    "alternate-input-controls": true
}

"features": {
    "input-controls": true
}

"features": {
    "input-controls": ["menu", "topmenu"]
}

Thanks for any support you can provide!

[StewartSnow]

Just +1-ing this. I’m seeing the exact same issue using alternate-input-controls:true on v 0.9.1 :

/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:150
      if (service.subtype.toString() === existing.subtype.toString())
                                                          ^
TypeError: Cannot read property 'toString' of undefined

Remove that feature and it’s fine. Same behaviour if you specify individual buttons instead of just true.

[stephenwoodford]

I’m now receiving a new error when starting homebridge. I haven’t had a chance to do much troubleshooting yet but wanted to see if it was related to this. I don’t believe I’ve changed anything else besides updating to 0.9.1. My config is same as above.

[2/27/2018, 6:37:29 PM] [DACP] Initializing DACP platform...
[2/27/2018, 6:37:29 PM] [DACP] DACP Platform Plugin Loaded - Version 0.9.1
[2/27/2018, 6:37:29 PM] [DACP] Found accessory in config: "Bedroom Apple TV"
[2/27/2018, 6:37:29 PM] [DACP] Initializing platform accessory 'Bedroom Apple TV'...

/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:150
      if (service.subtype.toString() === existing.subtype.toString())
                                                          ^
TypeError: Cannot read property 'toString' of undefined
    at Accessory.addService (/usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/Accessory.js:150:59)
    at /usr/local/lib/node_modules/homebridge/lib/server.js:432:19
    at Array.forEach (<anonymous>)
    at Server._createAccessory (/usr/local/lib/node_modules/homebridge/lib/server.js:412:14)
    at Server.<anonymous> (/usr/local/lib/node_modules/homebridge/lib/server.js:374:32)
    at /usr/local/lib/node_modules/homebridge/node_modules/hap-nodejs/lib/util/once.js:16:19
    at DacpPlatform.accessories (/usr/local/lib/node_modules/homebridge-dacp/src/index.js:195:5)
    at Server._loadPlatformAccessories (/usr/local/lib/node_modules/homebridge/lib/server.js:364:20)
    at Server._loadPlatforms (/usr/local/lib/node_modules/homebridge/lib/server.js:308:16)
    at Server.run (/usr/local/lib/node_modules/homebridge/lib/server.js:85:36)
    at module.exports (/usr/local/lib/node_modules/homebridge/lib/cli.js:40:10)
    at Object.<anonymous> (/usr/local/lib/node_modules/homebridge/bin/homebridge:17:22)
    at Module._compile (module.js:660:30)
    at Object.Module._extensions..js (module.js:671:10)
    at Module.load (module.js:573:32)
    at tryModuleLoad (module.js:513:12)

EDIT after some troubleshooting:

Modifying my config to remove any DACP devices allows homebridge to start, so seems to be something with DACP.

        {
            "platform": "DACP",
            "devices": []
        }

EDIT 2:

Just removing "alternate-input-controls": true fixes it, so seems to be something with the input control accessories. On the bright side, regular “input-controls” does seem to be working.