homebridge-denon-tv
homebridge-denon-tv copied to clipboard
AxiosError: read ETIMEDOUT at Function.AxiosError.from
Hi Sadly i still get the Axios error, it doesnt fail as bad as the previous anymore however it still stops working.
i get the following
[18/10/2022, 07:40:04] [homebridge-denon-tv] This plugin slows down Homebridge. The write handler for the characteristic 'Active Identifier' on the accessory 'G666 AV Receiver 792E' didn't respond at all!. Please check that you properly call the callback! See https://homebridge.io/w/JtMGR for more info.
[18/10/2022, 07:41:08] [DenonTv] Device: 192.168.2.32 G666 AV Receiver, Send command error: Error: read ETIMEDOUT
[18/10/2022, 07:41:08] [DenonTv] Device: 192.168.2.32 G666 AV Receiver, can not set Input. Might be due to a wrong settings in config, error: AxiosError: read ETIMEDOUT
at Function.AxiosError.from (/usr/lib/node_modules/homebridge-denon-tv/node_modules/axios/lib/core/AxiosError.js:89:14)
at RedirectableRequest.handleRequestError (/usr/lib/node_modules/homebridge-denon-tv/node_modules/axios/lib/adapters/http.js:515:25)
at RedirectableRequest.emit (node:events:513:28)
at ClientRequest.eventHandlers.
followed by
[18/10/2022, 07:41:13] [DenonTv] Device: 192.168.2.32 G666 AV Receiver, State error: Error: read ETIMEDOUT, reconnect in 15s.
when i make the reciever powerless and turn it back on it works again for a while untill it doesnt.
This must be your specific problem in local network environment or problem with the AVR server. The plugin just have no access to your AVR, the server just not response. I don’t observe this issue on my side, my Denon working without any issue.
It has something to do with zone 2, as when the problem is there zone 2 is activated. the original app shows heos is activated. Why this happens I have no clue
Can you post your config?
"devices": [ { "name": "G666 AV Receiver", "host": "192.168.2.32", "port": 8080, "zoneControl": 0, "volumeControl": 2, "masterPower": true, "masterVolume": true, "masterMute": false, "infoButtonCommand": "MNINF", "disableLogInfo": false, "disableLogDeviceInfo": false, "enableDebugMode": false, "inputs": [ { "name": "Tv", "reference": "TV", "mode": "SI", "displayType": 0 }, { "name": "KPN", "reference": "SAT/CBL", "mode": "SI" }, { "name": "NintendoSwitch ", "reference": "GAME", "mode": "SI" }, { "name": "Spotify", "reference": "SPOTIFY", "mode": "SI" }, { "name": "AirPlay ", "reference": "NET", "mode": "SI" }, { "name": "OnlineMusic", "reference": "FVP", "mode": "SI" } ], "buttonsMainZone": [ { "name": "Power on Denon", "reference": "ZMON", "displayType": 0 }, { "name": "Power off denon", "reference": "ZMOFF", "displayType": 0 }, { "name": "DTS", "reference": "MSDTS SURROUND", "displayType": 1 }, { "name": "STEREO", "reference": "MSMCH STEREO", "displayType": 1 }, { "name": "ROCK", "reference": "MSROCK ARENA", "displayType": 1 } ], "enableMqtt": false, "mqttAuth": false, "mqttDebug": false } ], "platform": "DenonTv" },
Here is no zone 2 configured
I don’t use the zone 2 at all but somehow it gets selected. I could try and configure a zone 2? See if that solves the issues
I was having a similar issue here and the issue was that my IP address had changed. Double check and make sure that your config is using the correct IP address for your device.
I was having a similar issue here and the issue was that my IP address had changed. Double check and make sure that your config is using the correct IP address for your device.
i use DHCP reservations for all my home automated devices. so thats not it. i could try and switch to wifi as i now have an wired connection but i rather not..
@Garia666 I have the same issue on wifi connection. I think that switch from wired connection doesn't help.
You may want to try reseting the network module. I did and have not had an error with the current version. See this thread: https://www.avsforum.com/threads/the-official-2016-denon-s-series-x-series-avr-owners-thread-faq.2444306/
Network reset didn’t work, I have switched from Ethernet to WiFi and so far no more crashes. The crashes were building up getting more often. I have no clue as why this would even work. Anyway I’ll give it some time.
Sadly it has come back on WiFi, is there any other way I can help troubleshooting this issue?
I have updates all iPads and iPhones to the latest iOS versions. Maybe that helps
There has been een firmware update for the Denon receiver, finger crossed. I also updated everything to 16.2. I am hoping this will resolve my issues
Adding myself to this thread as I am seeing the same issue. Note: I did not experience errors controlling the receiver (Marantz SR1603) until I upgraded my devices to iOS/tvOS 16.2 and upgraded my Home.
Adding myself to this thread as I am seeing the same issue. Note: I did not experience errors controlling the receiver (Marantz SR1603) until I upgraded my devices to iOS/tvOS 16.2 and upgraded my Home.
After pulling the power cord and restarting, this error went away for me.
Sadly it came back, everything is up to date, latest architecture, updated firmware of the Denon receiver. Out for the blue it starts and then keep building up crashing faster and faster. I can probably downgrade to an very old version and see if that keeps stable.
Adding myself to this thread as I am seeing the same issue. Note: I did not experience errors controlling the receiver (Marantz SR1603) until I upgraded my devices to iOS/tvOS 16.2 and upgraded my Home.
After pulling the power cord and restarting, this error went away for me.
This just works temporary
The problem is in AVR server, it’s freezes after couple of times. To fixed it need to power cycle the AVR. In my environment with AVR-X6300H no any crash or freezing observed. I’m connected with LAN and use DHC on AVR side and reserve address on router side. I will add in next release the possibility to set custom polling time, may be this help someone.
In 3.18.7 added possibility to set custom data refresh time in plugin settings advanced section. This can help to fix AVR server freezing.
Thanks allot man I am testing it right now! If it works I’ll make another donation
Well it’s been a while and the error has not reoccurred after that, I changed the setting to the max possible. So it safe to say it’s fixed. And like I promised I’ll make another small donation to the project. Thanks man