Can't use TX-NR676

[rosorrentino]

Confirm you have checked the WIKI for troubleshooting first
_Fill out and check ([x]) the boxes which apply.

• Homebridge version:
  1.0.4
• Plugin version:
  0.7.17
• OS, including release name/version:
• Homebridge-Onkyo installed via OS/distribution mechanisms
• You installed using homebridge-config-ui-x
• You enabled homebridge debug output

Describe the bug
A clear and concise description of what the bug is.
When I try to add the model 'TX-NR676' the plugin fails to load, if I try 609 works, but them it don't support the same inputs

To Reproduce
Information on your Onkyo receiver:

1. Model information
   TX-NR676
   Information on your configuration:
2. Homebridge config
   {
   "platforms": [
   {
   "platform": "Onkyo",
   "map_volume_100": false,
   "volume_dimmer": false,
   "switch_service": false,
   "filter_inputs": true,
   "receivers": [{
   "model": "TX-NR676",
   "ip_address": "192.168.1.60",
   "poll_status_interval": "3000",
   "name": "Receiver",
   "zone": "main",
   "default_input": "video4",
   "default_volume": "10",
   "max_volume": "40",
   "inputs": [{
   "input_name": "TV",
   "display_name": "TV"
   },
   {
   "input_name": "video4",
   "display_name": "AppleTV"
   }
   ]
   }]
   }
   ]
   }
   Information from the log:
3. Homebridge log file showing relevant information. Experienced users are asked to turn debug on.
   Hint: The more information you provide here, the easier it is to help you. Do NOT provide only a single line showing an error message - give the develpers a chance by providing a full log.
   ERROR: Your configuration is missing the parameter "volume_dimmer". Assuming "false".
   [4/30/2020, 10:16:45 PM] [Onkyo] ERROR: Your configuration is missing the parameter "filter_inputs". Assuming "false".
   [4/30/2020, 10:16:46 PM] SyntaxError: Unexpected token ] in JSON at position 13
   at JSON.parse ()
   at OnkyoAccessory.createRxInput (/usr/lib/node_modules/homebridge-onkyo/index.js:241:19)
   at OnkyoAccessory.setUp (/usr/lib/node_modules/homebridge-onkyo/index.js:180:8)
   at new OnkyoAccessory (/usr/lib/node_modules/homebridge-onkyo/index.js:176:8)
   at /usr/lib/node_modules/homebridge-onkyo/index.js:36:22
   at Array.forEach ()
   at OnkyoPlatform.createAccessories (/usr/lib/node_modules/homebridge-onkyo/index.js:35:13)
   at new OnkyoPlatform (/usr/lib/node_modules/homebridge-onkyo/index.js:28:8)
   at /usr/lib/node_modules/homebridge/src/server.ts:396:40
   at Array.forEach ()

Expected behavior
A clear and concise description of what you expected to happen.
Support TX-NR676
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[rosorrentino]

I can see the problem is with the dependency on https://github.com/ToddGreenfield/homebridge-onkyo/blob/master/package.json
I don't really understand how all this work but somehow I found it it's based on a project that is being maintained again at https://github.com/miracle2k/onkyo-eiscp
Can't you get something from there? (again, I am not sure)

[cbrandlehner]

@rosorrentino the hadware support comes from https://github.com/tillbaks/node-eiscp which is, unfortunately, not currently maintained.
The onkyo-eiscp project you linked looks promising, but is not a JavaScript library.

[solowalker27]

My PR #80 includes an updated eiscp.js that I found which has support for the TX-NR676. You could test that PR or wait until it's merged.

[solowalker27]

`npm install -g solowalker27/homebridge-onkyo#0.8.0` should do it. https://stackoverflow.com/questions/17509669/how-to-install-an-npm-package-from-github-directly

…

On Jun 6, 2020, at 2:05 AM, Tom2Drake ***@***.***> wrote:  How to test your PR? npm install -g git+https://github.com/solowalker27/homebridge-onkyo.git? — You are receiving this because you commented. Reply to this email directly, view it on GitHub, or unsubscribe.

[solowalker27]

Since this issue is stale and should/could have been resolved with an update, I'm closing this. If it's still a problem, reopen (or file a issue) and give updated details describing the problem and what version of the plug-in you're currently using.