Denon AVR Driver issue

[accd2793e8934ca914d6]

A couple of weeks ago I setup a Denon AVR device, using the built-in driver. It worked great for oh...about a week. I was only using it for power on/off status. Then mysteriously it stopped working. The IP address of the AVR has not changed.

Tonight I fiddled with the "initialize" and "refresh" buttons in the virtual device, and after a bit it did see I had the receiver on. However, that was just a fluke as on/off don't work and the driver state is not in sync with the receiver's state.

Under "events" only two are logged tonight (power on, volume), despite the receiver being turned on and off manually multiple times.

Here's a sample of the logs during one of the few times the driver is communicating with the receiver:

Any ideas? There are also sporadic telnet connection refused messages in the log too.

dev:5802022-10-12 07:52:16.379 PMdebugtelnetStatus:send error: Broken pipe (Write failed)
dev:5802022-10-12 07:49:44.043 PMdebugparse- cmd:ZM, params:OFF
dev:5802022-10-12 07:49:44.042 PMdebugparse- raw:[90, 77, 79, 70, 70]
dev:5802022-10-12 07:49:43.434 PMdebugparse- cmd:ZM, params:ON
dev:5802022-10-12 07:49:43.433 PMdebugparse- raw:[90, 77, 79, 78]
dev:5802022-10-12 07:49:38.154 PMdebugparse- cmd:ZM, params:OFF
dev:5802022-10-12 07:49:38.153 PMdebugparse- raw:[90, 77, 79, 70, 70]
dev:5802022-10-12 07:49:26.511 PMdebugparse- cmd:ZM, params:ON
dev:5802022-10-12 07:49:26.510 PMdebugparse- raw:[90, 77, 79, 78]
dev:5802022-10-12 07:49:10.328 PMdebugparse- cmd:ZM, params:OFF
dev:5802022-10-12 07:49:10.327 PMdebugparse- raw:[90, 77, 79, 70, 70]
dev:5802022-10-12 07:48:36.456 PMdebugparse- cmd:ZM, params:ON
dev:5802022-10-12 07:48:36.455 PMdebugparse- raw:[90, 77, 79, 78]
dev:5802022-10-12 07:48:32.360 PMdebugparse- cmd:MV, params:MAX 98
dev:5802022-10-12 07:48:32.359 PMdebugparse- raw:[77, 86, 77, 65, 88, 32, 57, 56]
dev:5802022-10-12 07:48:32.312 PMinfoDenon Receiver volume is 50
dev:5802022-10-12 07:48:32.311 PMdebugparse- cmd:MV, params:50
dev:5802022-10-12 07:48:32.311 PMdebugparse- raw:[77, 86, 53, 48]
dev:5802022-10-12 07:48:32.254 PMdebugparse- cmd:SV, params:OFF
dev:5802022-10-12 07:48:32.253 PMdebugparse- raw:[83, 86, 79, 70, 70]
dev:5802022-10-12 07:48:32.216 PMinfoDenon Receiver is unmuted
dev:5802022-10-12 07:48:32.215 PMdebugparse- cmd:MU, params:OFF
dev:5802022-10-12 07:48:32.214 PMdebugparse- raw:[77, 85, 79, 70, 70]
dev:5802022-10-12 07:48:32.153 PMwarnparse- ignored:cmd:Z3, params:ON
dev:5802022-10-12 07:48:32.152 PMdebugparse- cmd:Z3, params:ON
dev:5802022-10-12 07:48:32.151 PMdebugparse- raw:[90, 51, 79, 78]
dev:5802022-10-12 07:48:32.104 PMwarnparse- ignored:cmd:Z2, params:ON
dev:5802022-10-12 07:48:32.103 PMdebugparse- cmd:Z2, params:ON
dev:5802022-10-12 07:48:32.102 PMdebugparse- raw:[90, 50, 79, 78]
dev:5802022-10-12 07:48:32.051 PMinfoDenon Receiver is on
dev:5802022-10-12 07:48:32.051 PMdebugparse- cmd:PW, params:ON
dev:5802022-10-12 07:48:32.050 PMdebugparse- raw:[80, 87, 79, 78]
dev:5802022-10-12 07:48:31.996 PMinfoDenon Receiver input is Input 1
dev:5802022-10-12 07:48:31.995 PMdebugparse- cmd:SI, params:GAME
dev:5802022-10-12 07:48:31.994 PMdebugparse- raw:[83, 73, 71, 65, 77, 69]
dev:5802022-10-12 07:48:30.133 PMdebugparse- cmd:MV, params:MAX 98
dev:5802022-10-12 07:48:30.132 PMdebugparse- raw:[77, 86, 77, 65, 88, 32, 57, 56]
dev:5802022-10-12 07:48:30.117 PMinfoDenon Receiver volume is 50
dev:5802022-10-12 07:48:30.116 PMdebugparse- cmd:MV, params:50
dev:5802022-10-12 07:48:30.115 PMdebugparse- raw:[77, 86, 53, 48]
dev:5802022-10-12 07:48:30.044 PMdebugparse- cmd:SV, params:OFF
dev:5802022-10-12 07:48:30.043 PMdebugparse- raw:[83, 86, 79, 70, 70]
dev:5802022-10-12 07:48:30.023 PMinfoDenon Receiver is unmuted
dev:5802022-10-12 07:48:30.022 PMdebugparse- cmd:MU, params:OFF
dev:5802022-10-12 07:48:30.021 PMdebugparse- raw:[77, 85, 79, 70, 70]
dev:5802022-10-12 07:48:29.942 PMwarnparse- ignored:cmd:Z3, params:ON
dev:5802022-10-12 07:48:29.941 PMdebugparse- cmd:Z3, params:ON
dev:5802022-10-12 07:48:29.940 PMdebugparse- raw:[90, 51, 79, 78]
dev:5802022-10-12 07:48:29.894 PMwarnparse- ignored:cmd:Z2, params:ON
dev:5802022-10-12 07:48:29.893 PMdebugparse- cmd:Z2, params:ON
dev:5802022-10-12 07:48:29.892 PMdebugparse- raw:[90, 50, 79, 78]
dev:5802022-10-12 07:48:29.863 PMinfoDenon Receiver is on
dev:5802022-10-12 07:48:29.862 PMdebugparse- cmd:PW, params:ON
dev:5802022-10-12 07:48:29.861 PMdebugparse- raw:[80, 87, 79, 78]
dev:5802022-10-12 07:48:29.814 PMinfoDenon Receiver input is Input 1
dev:5802022-10-12 07:48:29.812 PMdebugparse- cmd:SI, params:GAME
dev:5802022-10-12 07:48:29.811 PMdebugparse- raw:[83, 73, 71, 65, 77, 69]

[Rxich]

seen this issue reported before.
Try this

[RELEASE] - Denon HEOS Integration

I've decided to build a Denon HEOS integration. I had currently been using the DLNA integrations available which isn't great. I recently discovered the HEOS CLI and it's pretty straightforward. I also seem some drama around Sonos and figured why not? One thing I need help with, I want to make it similar to the Sonos integration. However, I don't really know what the Sonos integration has as features. Can anyone share some info? Should be a fun project, I haven't yet played with SSDP, XML, and …

[marktheknife]

I would avoid using the HEOS integration developed by @dman2306 if all one wants to do is control basic functions of a Denon AVR.

The code for that integration is no longer maintained, since the dev moved on from Hubitat earlier this year. It still works (and is great for HEOS-specific features), but if Denon ever changes something in the HEOS API, it might break the integration.

More importantly, the HEOS API is not local, it’s cloud-based. Why go through the cloud when there’s a perfectly good means to communicate locally with the AVR via its Telnet connection, which is what the built-in integration uses.

Speaking of that, it sounds like something might be up with the hub’s Telnet connection to the receiver? I’m not sure what that error means in your logs. Maybe @mike.maxwell can help.

[ritchierich]

The issue with Denon receivers is they only allow a single telnet connection at a time and if that breaks you have to reinitialize. Other telnet integrations like Onkyo and Lutron allow multiple. I worked with @mike.maxwell in 2018 on testing this driver and it’s worked great for me and stays connected.

I do occasionally have the “Broken pipe” error but that is caused by my own doing like unplugging the Denon AVR or network switch within my AV cabinet or occasionally restarting my network equipment. Otherwise it stays connected.

Is your Ethernet connection from the Denon to your network equipment stable? Again any break in that will cause issues.

I’d be curious if @mike.maxwell could implement better error handling on the telnet connection to detect if it’s broken and try to reinitialize it. Happy to work with him if interested.

[accd2793e8934ca914d6]

Well I rebooted my Hubitat, and now the Denon device is working fine. So ya, it would be great if there was better error handling with the telnet issues.