Homeseer with 2 interfaces yields Z-Tool issue

There seems to be a bug in Homeseer where instead of using the bind address specified on the config page

It uses the first interface it finds as its primary. In this case 192.168.2.45 instead of 10.10.1.45. Normally this is not an issue as setting to (No Binding) lets it work with either address. A problem arises however when using the Z-tool app on the 10.10 network as it will connect to the server on the 10.10 network but it reports back the 192 network which then fails to find any Z-Nets. It seems the only way around this is to disable the 192 network before starting Homeseer.

A similar issue you may encounter is having to log in even though No Password Required for Local/Same Network Login (Web Browser/HSTouch) is checked. Note this must be checked for Z-Tool to work.

You can enable the 192 network once you are done using the Z-Tool app.

Update:

It seems this also causes a problem with the Sonos plugin as well as it only does discovery on the first network it finds. So I went in search of a better solution and found this info on How to change the network connection priority in Windows 7 which seems to be a better solution. For Windows 10 it is just a bit different of course. See this document How to change network connection priority in Windows 10

The summary for both is get to the window showing your adapters and use the ALT key to expose a hidden Advanced menu, select Advanced Settings on that menu, then alter the order of adapters in the list to put the one with you IoT network on top.