0.1.0a43
The diagnosis survives a Windows console.
On a legacy Windows console the diagnosis could stop printing part way
through: a device name or a network record holding bytes that are not text
raised an encoding error, and everything after it was lost -- including, in
one measured case, every Sungrow record. The listing looked short and
complete. Every entry point now forces UTF-8 before it prints, so a few
unreadable fields come out as mojibake instead of costing you the rest of
the run.
On Windows, choose "Allow access" if the firewall asks when the diagnosis
starts. Declining does not stop it; it quietly thins what it hears on the
network, so a device that is there can come out missing.
Adding an inverter: where a Modbus proxy and the inverter both answer, the
proxy is now named as one. It is recognised by its network hardware -- a
virtual machine's address, or a known hypervisor's -- and not only when the
proxy runs on Home Assistant itself. Where two cards still cannot be told
apart, they are offered by address rather than alphabetically.
A diagnosis now records whether the machine that ran it was on the device's
own network, and how many network records it heard in all. An empty result
from a machine that could not have heard anything is no longer mistaken for
a device that said nothing.