ACDR / homebridge-yamaha-avr

homebridge-plugin for Yamaha AVR. Audio Receiver Accessory with Power, Input, Volume & Remote Control
Apache License 2.0
45 stars 6 forks source link

Homebridge crashes on 3.0.2 #80

Open BradJMelb opened 2 years ago

BradJMelb commented 2 years ago

Describe The Bug: I started testing 3.0.2 last week and initially it worked mostly fine. The only thing unexpected was that my inputs reverted to their default names instead of what they are called on the receiver (HDMI2 instead of AppleTV, etc). after a couple of hours though I found that homebridge was no longer running and the below error was in the log.

I’m running the latest release of homebridge and I have an RXA1070 which seems to be compatible with the new API V3 uses.

I’ve returned to version 2.1.1 and cleared out my cached input names and homebridge no longer crashes and my input names come through properly once again.

Is this a case of error handling if the device isn’t available for a period of time. I have seen this before but previous releases seem to be ok with it.

Thanks, Brad.

Logs:

`at processTicksAndRejections (node:internal/process/task_queues:83:21)
[9/19/2022, 3:36:49 AM] FetchError: request to http://192.168.0.1/YamahaExtendedControl/v1/main/getStatus failed, reason: connect EHOSTUNREACH x.x.x.x:80
    at ClientRequest.<anonymous> (file:///usr/local/lib/node_modules/homebridge-yamaha-avr/node_modules/node-fetch/src/index.js:108:11)
    at ClientRequest.emit (node:events:513:28)
    at Socket.socketErrorListener (node:_http_client:481:9)
    at Socket.emit (node:events:513:28)
    at emitErrorNT (node:internal/streams/destroy:157:8)
    at emitErrorCloseNT (node:internal/streams/destroy:122:3)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)`

Plugin Config:

        {
            "platform": "yamaha-avr",
            "name": "Receiver",
            "ip": "x.x.x.x",
            "volumeAccessoryEnabled": true,
            "zone2Enabled": false,
            "zone3Enabled": false,
            "zone4Enabled": false
        },

Environment:

adrianopery commented 1 year ago

I’ve receiving the same error. Now I did the same as you described, but for me, the AVR is showing on Homebridge Dashboard but not appears on app Home (homekit). There is no error on the LOG. I restarted the homekit and homebridge, but still missed the device on app home.

adrianopery commented 1 year ago

does this plugin having support yet?