No Device found after some updates

[rhaamo]

nOnkyo GUI was working perfectly, didn't used for a few time then upgraded windows 10 (1709) and now my AV isn't detected anymore (TX-NR609).

I tryied to add to NOnkyoWpfGui.exe.config the following without success:

      <setting name="DevicePort" serializeAs="String">
        <value>60128</value>
      </setting>
      <setting name="DeviceIP" serializeAs="String">
        <value>192.168.10.25</value>
      </setting>
      <setting name="UsedFixedIP" serializeAs="String">
        <value>True</value>
      </setting>

The AV web-ui is accessible, and I can use ISCP from another host without issues. (I don't have another ISCP tool on the windows box)

Is there a log somewhere with more informations ?

[PinBack23]

The AV receiver allows only one connection via the ISCP protocol.
Try turning off all other transmitters and restarting the receiver.

I also installed the latest version of Windows 10. I think that shouldn't be the reason for your issue.
I hope this helps to solve the problem.

[syserr0r]

I'm was having the same problem, also on Windows 10, while my wife's PC did not (both PCs running version 1709 build 16299.125).

After disabling the vEthernet (Default Switch) network adaptor on my PC the problem was resolved (a more permenant fix is to remove 'Hyper-V' from Control Panel > Programs and Features > Turn Windows Features on or off) nOnkyo started working again. My wife's PC did not have this network adaptor (nor the Hyper-V feature enabled).

I'm not entirely sure why my PC had Hyper-V added to it when my wife's did not 😕

It would appear nOnkyo possibly does not use the correct network when more than one is available?

[rhaamo]

@syserr0r I haven't think about that...
I just disabled "VirtualBox Host-Only Network" and nOnkyo works perfectly fine.

The protocol does support multiple client without issues, I think nOnkyo is picking the "first" network adapter it found and it isn't the right one :(

[syserr0r]

The following SO post may be relevant: https://stackoverflow.com/questions/19623804/udp-networking-with-multiple-network

I'll attempt to make a patch if I get time

[PinBack23]

@syserr0r I cannot test your changes at the moment because my onkyo receiver is not connected. If that solves your problem, I'll take over the code.

[syserr0r]

I'll test tonight as I don't have a compiler to hand and I'm not at home with my receiver

[syserr0r]

I set-up a VPN to home to test, it turns out all that is needed to make it connect was either increasing the 1000ms sleep to 3000ms or moving it into the for loop (increasing the delay for each network that is attempted; setting the sleep to 2000ms was not enough [this machine has 4 BroadcastAddresses as well as localhost])

It might be worth adding something like this to the Where() in AllBroadcastAddresses to exclude the IPv4 loopback interface:
&& !uaddress.Address.Address.ToString().StartsWith("127.")))

[PinBack23]

Sorry for the delay
I also installed Hyper V and now I additionally installed Virtual Box.
Now I have 6 network adapter but I still can't reproduce the error.

Nevertheless, I have now added a timeout for the device search.
Download: https://github.com/PinBack23/nonkyo/releases/tag/0.15
TimeoutDeviceSearch (Waiting for the reply in ms)

      <setting name="TimeoutDeviceSearch" serializeAs="String">
        <value>1000</value>
      </setting>

Could you give it a try? Increase the timeout and check again.

[syserr0r]

My receiver has died so I'm unable to preform any more testing for the moment.

I'll get back to you as soon as I can.