Sorry to hear you are having issues!
Since you have so many adapters, there's not a good way that auto-config can know which one to pick, so it just picks the first one in the sorted order. Not sorting it will cause the list to be in whatever order the devices get enumerated or were added, which might not be right either. So in your situation, you'll need to pick the "List my network adapters" option in Settings and manually select the correct ones you want to monitor. I added the "List" option specifically for folks in your situation.
shoek wrote:For instance, I found for the auto-config, if I take out the Sort -Property InterfaceDescription from the powershell command it does detect the correct adapter. Is there a better way to do that than just sorting the interfaces alphabetically and picking the first? For instance, when I use the config "List my network adapters" link it does show my primary/gateway connection as the first one.
Unfortunately, while the "List" option is showing the correct adapter first in your case, this is actually a bug on my part. The command is sorting the list by "InterfaceName" instead of "InterfaceDescription". InterfaceName is just a string like "ethernet_32769" or "wireless_32768", which was not my intent. I'll correct the command file in a future release (the skins are correct, the command file is not).
For your other issue, [MeasureAdapterName] is a plain old Rainmeter SysInfo measure that is supposed to return the name of the "Best" (or active) network interface. I've never seen it return a blank, that is strange! So, for your question...
shoek wrote:I frequently see the Network Monitor Pro 's MeasureAdapterName calculated to 0 on my system, and thus the MeasureInterfaceName is blank.
Is there anyway to see what SysInfo is returning and why the gadget is getting confused?
...SysInfo is in fact returning a blank (and thus a 0) for that measure, something that is very odd.
As you noted, because this measure is blank, the Gadget is not going to display the active adapter or your network connection name. or know if your adapter is ethernet, wireless, etc., so it might not configure its display properly.
I appreciate you offer to help debug this situation. First, the auto-config issue does not have a solution in your case because you have multiple adapters; there's no way to know the "right" one, so the end result is that you'll need manually configure the gadget. That's a one-time thing, so it should not be too big of a problem. However, the big issue is why SysInfo's ADAPTER_DESCRIPTION option (and I assume ADAPTER_TYPE if it were used) is returning blanks/zeros. That's my biggest concern. We'll need to narrow that down.
The good news is that these issues should not affect the ability of the Gadget to monitor your network adapter traffic since you are using the "Pro" version. It will only affect the display of the current adapter name/connection, which is certainly annoying, but not fatal.