Closed DMcWetty closed 2 years ago
Can you ping the device on this port?
Seems to be pinging just fine. Here’s the terminal feedback:
ping 192.168.5.141 PING 192.168.5.141 (192.168.5.141): 56 data bytes 64 bytes from 192.168.5.141: icmp_seq=0 ttl=64 time=12.982 ms 64 bytes from 192.168.5.141: icmp_seq=1 ttl=64 time=11.038 ms 64 bytes from 192.168.5.141: icmp_seq=2 ttl=64 time=7.406 ms 64 bytes from 192.168.5.141: icmp_seq=3 ttl=64 time=16.979 ms 64 bytes from 192.168.5.141: icmp_seq=4 ttl=64 time=9.425 ms 64 bytes from 192.168.5.141: icmp_seq=5 ttl=64 time=8.156 ms 64 bytes from 192.168.5.141: icmp_seq=6 ttl=64 time=6.964 ms ^C --- 192.168.5.141 ping statistics --- 7 packets transmitted, 7 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 6.964/10.421/16.979/3.319 ms
Do I need to bother adding the :9034 port?
Dave On Aug 26, 2022, 10:27 AM -0400, Grzegorz @.***>, wrote:
Can you ping the device on this port? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Please Ping with the port 9034
@. ~ % ping 192.168.5.141:8080 ping: cannot resolve 192.168.5.141:8080: Unknown host @. ~ % ping 192.168.5.141:9034 ping: cannot resolve 192.168.5.141:9034: Unknown host
Seems to be a no-go.
Dave On Aug 27, 2022, 3:55 PM -0400, Grzegorz @.***>, wrote:
Please Ping with the port 9034 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
So, it’s Your local network problem.
I attached a SS of the Eero app with the port forwarded. I tried 9034 -> 8080 and 9034 -> 9034
Dave On Aug 27, 2022, 3:56 PM -0400, David Wetty @.***>, wrote:
@. ~ % ping 192.168.5.141:8080 ping: cannot resolve 192.168.5.141:8080: Unknown host @. ~ % ping 192.168.5.141:9034 ping: cannot resolve 192.168.5.141:9034: Unknown host
Seems to be a no-go.
Dave On Aug 27, 2022, 3:55 PM -0400, Grzegorz @.***>, wrote:
Please Ping with the port 9034 — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Why you forward the port, is the Homebridge not on the same network as the AV Receiver?
I got the two denon avr working. Still can’t get the Marantz to work. But I’m sure it’s not an issue with the plug-in. Thanks.
Dave On Aug 27, 2022 at 4:01 PM -0400, Grzegorz @.***>, wrote:
Why you forward the port, is the Homebridge not on the same network as the AV Receiver? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
I wanted to add on some of my research and see if I could find a solution.
It seems newer model Marantz and Denon amps use HEOS for IP control. This means that port 80 is no longer accessible which is why I wasn’t able to setup the Marantz PM7000N in your plugin. I was getting a "403 Forbidden" error code in the web browser. So I found THIS PAGE discussing how to access IP control for HEOS platforms. It seems port 1255 must be open for telnet control. I get a bit out of my depth so I defer to you; is there some setting I need to change to enable accessing telnet/HEOS control?
Ultimately, all I want is to setup automation commands in HomeKit so I can use Siri to turn on my amp, set the input to Phono automatically, and power up the turntable.
Thanks for your efforts.
Dave On Aug 27, 2022, 4:01 PM -0400, Grzegorz @.***>, wrote:
Why you forward the port, is the Homebridge not on the same network as the AV Receiver? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Are you check both ports 80 and 8080? Is the remote control enabled in the AVR. Has the AVR dedicated app?
I tried 80, 8080, 23, and 1255.
Dave On Aug 29, 2022 at 12:49 PM -0400, Grzegorz @.***>, wrote:
Are you check both ports 80 and 8080? Is the remote control enabled in the AVR. Has the AVR dedicated app? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
I tried 80, 8080, 23, and 1255. The Marantz uses the HEOS app just like the Denons.
Dave On Aug 29, 2022 at 12:49 PM -0400, David Wetty @.***>, wrote:
I tried 80, 8080, 23, and 1255
I just hit “open a port” on Eero router. I tried 8080 but that’s already occupied by my weather device. I guess I’m doing something wrong. Homebridge is on the NAS (ethernet). Marantz Amp is Wifi.
Sorry, I’m a noob at networking.
Dave On Aug 27, 2022, 4:01 PM -0400, Grzegorz @.***>, wrote:
Why you forward the port, is the Homebridge not on the same network as the AV Receiver? — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>
Hi. Thanks so much for developing this plugin.
Plugin looks like exactly what I needed. Got everything setup but I'm getting "[8/23/2022, 10:54:42 AM] [homebridge-denon-tv] Device: 192.168.5.141 Marantz Amp, Device info error: Error: connect ECONNREFUSED 192.168.5.141:9034" in the log. I had to open up a new port (9034) and forwarded it to 8080 after making an IP reservation. Wondering if it was the Marantz, I tried it on my S760 and X3400 as well... similar errors: "[8/23/2022, 10:59:23 AM] [homebridge-denon-tv] Device: 192.168.7.16 Office Denon, Device info error: Error: connect ECONNREFUSED 192.168.7.16:9134" and "[8/23/2022, 11:01:56 AM] [homebridge-denon-tv] Device: 192.168.6.193 Theater Denon, Device info error: Error: connect ECONNREFUSED 192.168.6.193:9234 ". Suggestion?