Most of the discussion happened on Discord. We opted for the qt-openzwave route because it is maintained directly by the OpenZWave lead developer and ties in directly to OpenZWave, whereas Zwave2mqtt is a nodejs wrapper on top of OpenZWave maintained by someone else. I believe the plan is for qt-openzwave to be the base for the new official OpenZWave control panel as well, so it should be kept up to date a lot better than Zwave2mqtt.