Hi,

I'm brand new to IoX and node servers, so please bear with me! I'm trying to get AVRemote working reliably with my Marantz SR6011, and would appreciate some guidance.

My setup

• Controller: eisy / IoX 6.0.5

• Polyglot PG3x: 3.4.18

• Node server: AVRemote 2.0.18 (Free/Production)

• Receiver: Marantz SR6011

• Receiver IP: 192.168.1.105

• Connection: TCP port 23

• Receiver's Network Control setting: Always On

• AVRemote's Connect On Demand setting: true

What happens

• AVRemote initially showed the receiver as off even when it was on.

• Changing Connect On Demand from false to true and restarting AVRemote improved power-status reporting. It now correctly shows the receiver as on.

• Volume readings have sometimes appeared incorrect, but subsequently matched the receiver after I changed the volume at the receiver itself.

• Commands from IoX are unreliable. Set Volume and Input have not produced the expected changes at the receiver. Mute has worked intermittently.

• Responses and status updates can be slow.

Relevant log errors

The latest debug log contains:

ConnectionRefusedError: [Errno 61] Connection refused

This occurs when AVRemote attempts to connect to 192.168.1.105:23 to send a volume command.

It also contains:

OSError: [Errno 9] Bad file descriptor

This occurs during recv() while AVRemote is polling receiver state, including Zone 3.

The logs also show some successful communication—for example, AVRemote sends SI? and receives SISAT/CBL—so communication is not failing consistently.

What I've tried

• Verified the receiver IP address and port 23 in AVRemote configuration.

• Confirmed Network Control is set to Always On.

• Changed Connect On Demand to true and restarted AVRemote.

• Restarted AVRemote and tested Power, Volume, Input, and Mute controls.

• Downloaded fresh debug and Polyglot log files.

I have attached the latest debug log package.

Could these errors indicate a connection-management or concurrent polling issue in AVRemote's Denon/Marantz driver? What would you recommend trying next?

Thanks for your time and for maintaining AVRemote. I'm happy to follow step-by-step instructions, but I'm not experienced with command-line troubleshooting.

AVRemote_10-24-2026_52456_PM.zip

Seems like your receiver just doesn't respond to Zone3 commands. Do you have zone3? If you do, you can shut off AVRemote and just connect via telnet cmd line and try running some of Z3 commands. See what you get as a response.

Thanks for the response. My receiver is configured as a 7.1.2 Atmos system, with all nine internal amplifier channels assigned to the Main Zone. I checked Marantz's documentation, which indicates that the SR6011 does not support Zone 3.

Since the SR6011 supports the Main Zone and Zone 2, but not Zone 3, could you confirm which zone commands AVRemote is sending? Is it issuing Zone 3 commands as part of its normal initialization or status polling, even though the receiver doesn't support Zone 3?

Today, I tried an experiment in the AVRemote PG3x Nodes page: I deleted both Zone 2 and 3 by clicking the X in the Delete column.

The debug log confirms both nodes were marked as removed. In the subsequent entries, the Zone 3 polling errors no longer appear, but intermittent errors continue for the main Marantz SR6011 node.

The two continuing errors are:

• ConnectionRefusedError: [Errno 61] Connection refused — during self.conn.connect() while refreshing the main receiver's input source (e.g., 13:38:23).

• OSError: [Errno 9] Bad file descriptor — during self.conn.recv(self.BUF_SIZE).decode() while refreshing the main receiver's state (e.g., 13:39:23).

Other main-zone polling requests continue to succeed between these errors; the receiver appeared fairly responsive in limited testing.

Deleting the zone nodes appears to have eliminated the Zone 3-specific errors, but has not resolved the intermittent main-zone connection errors. I can provide the full debug log if it would be helpful.

I'm also unsure whether manually deleting these nodes is a durable solution. The log suggests the Zone 3 deletion survived an AVRemote restart, but I haven't tested whether the deletions persist through an eisy reboot, plugin update, or rediscovery. Would you expect these nodes to remain deleted, or could AVRemote recreate them?

Is there a more efficient way or configuration setting to make have AVRemote only talk to the main zone (I don't care about Zone 2 or 3)?

Removing zone nodes is not going to do much. Technically you can ssh into eisy and remove corresponding lines from yaml config file. I will add checkbox for zone3 when I get a chance. You'll just have to be a beta tester.

Thanks, I appreciate your willingness to help me on this. I've left AVRemote turned off for now, and I'll leave the YAML editing to those who know what they're doing — Python isn't in my toolkit!

For reference, my eisy|lite is running the current releases: PG3x 3.4.28 and IoX 6.1.2_10.

I'd be happy to help test a beta version when you have one available. Ideally, it would provide a way to disable Zone 3 for the SR6011 and also address the intermittent ConnectionRefusedError and Bad file descriptor errors affecting the main zone. The receiver does respond successfully to many of the polling requests, so hopefully there's something that can be learned from testing.

Let me know when you're ready for a willing tester. Thanks again!