search

unfoldedcircle / feature-and-bug-tracker

Feature and bug tracker repository for Unfolded Circle products
21 stars 0 forks source link

[bug] Denon auto-discovery different subnets #342

Open henrikwidlund opened 3 months ago

henrikwidlund commented 3 months ago

Is there an existing issue for this?

Description

My remote and receiver are on different subnets which I suspect is causing the auto-discovery to not find the receiver. After pressing next without specifying an IP the dialog displays the error NOT_FOUND. By specifying the IP the receiver is found and can be configured.

Based on the code here I expected No AVRs discovered to show up in the logs, but no such entry exists.

It is a bit unclear if this scenario is supported or not. Please also note that it's speculative if this actually is caused by the devices being on different subnets as I haven't tested putting them on the same network (device isolation on the network that the Denon receiver is on prevents me from putting the remote on that network as the remote and dock needs to be on the same network and be able to talk to each other).

UCR2_logs_2024-03-10-2.txt

How to Reproduce

  1. Put the remote and receiver on different networks
  2. Configure the Denon integration without specifying an IP
  3. Observe that after approximately 2 seconds the dialog displays NOT_FOUND

Expected behavior

Receiver is found, or that some information about what could cause devices to not be discovered is shown and what you could do about it (ports that should be open, whether or not different subnets are supported etc).

System version

1.7.4

What part of the system affected by the problem?

Integration

Additional context

No response

zehnm commented 3 months ago

For auto-discovery to work, the receiver must be in the same network. Denon is not using mDNS but UPnP SSDP. Feel free to close this issue, otherwise I'll keep it open until we add the discovery limitations to the setup screen and add a support article.