To summarize what I mentioned above, personally, I like recommend these type of setups in general:
-
If want to use Home Assistant’s ZHA integration then it is today highly recommended to use a Zigbee Coordinator USB adapter based Silicon Labs EFR32MG21/EFR32MG13, Texas Instruments CC2652/CC1352, or ConBee II (dresden-elektronik), in that specific order if stability is your highest requirement. ZHA also support other Zigbee Coordinator adapters but they are either older or not supported as well. See https://www.home-assistant.io/integrations/zha#recommended-zigbee-radio-adapters-and-modules
-
If want to use Zigbee2MQTT instead then it is today highly recommended to use a Zigbee Coordinator USB adapter based on Texas Instruments CC2652P/CC1352P or ConBee 2 if stability is your highest requirement. Zigbee2MQTT also support other Zigbee Coordinator adapters but they are either older or not supported as well (e.g. “experimental”). See https://www.zigbee2mqtt.io/guide/adapters/#recommended
-
I personally recommend using a single dedicated radio USB adapter for each separate wireless protocol as it both decreases complexity and at least on paper should offer better performance.
- So a tip is to use a single dedicated Home Assistant SkyConnect USB dongle for Thread (and Matter over Thread) and then buy another separate single dedicated Home Assistant SkyConnect USB dongle (or other Silicon Labs EFR32MG21 based USB adapter) with ZHA or alternatively a separate single dedicated Texas Instruments CC2652P USB adapter instead if using Zigbee2MQTT.
-
If not absolutely necessary try to avoid internally connected Zigbee Coordinator adapters that are mounted inside the computer case since that will increase interference and decrease reception.
-
If not absolutely necessary try to avoid network-attached Zigbee Coordinator adapters today because they will add unnecessary complexity. Instead recommend just using a Zigbee USB adapter with very long USB extension cable if possible, read → Zigbee networks: how to guide for avoiding interference and optimize for getting better range + coverage - #3 by Hedda
- If you absolutely have to use network-attached Zigbee Coordinator adapter then do not use them user a Wi-Fi connection since the serial-protocols used on Zigbee Coordinator adapters are not robust enough to deal with latency, out-of-order-packages, dropped packages, or connection loss that occurs when serial-over-IP briding solutions is used over WiFi. See ZHA and Zigbee2MQTT warning about that → https://www.home-assistant.io/integrations/zha#warning-about-wi-fi-based-zigbee-to-serial-bridgesgateways and https://www.zigbee2mqtt.io/advanced/remote-adapter/connect_to_a_remote_adapter.html
Regardless of Zigbee solution read/follow all of these generic guidelines → Zigbee networks: how to guide for avoiding interference and optimize for getting better range + coverage
I would not personally install Z2M on Windows OS but otherwise think you got the gist of Zigbee2MQTT, though there is also an (easier) option to Zigbee2MQTT via the addon if want to run it on the same machine as your Home Assistant OS or a Supervised Home Assistant instance, but then you loose your wanted feature of running it as stand-alone on a other machines on the your local network.
Better would be to buy and use a single-board computer (SBC) with Linux OS to run Zigbee2MQTT, such as example an Raspberry Pi or Hardkernel ODROID and use that as a dedicated appliance for just for that purpose. You should then also be able to squeeze in for example ZWaveJSMQTT (ZWave JS MQTT) on the same computer with a Z-Wave 700 USB dongle like the Aeotec Z-Stick 7.