Question about Zooz, Aeotec, and Fibaro plugs with Energy Monitoring

[Olen]

I agree that it can be confusing. And sorry for adding to that by simply writing “ozw” rather than “qt-ozw”.

There are currently three(?) viable zwave-implementations you can use with Home Assistant.

• The “old” integrated version which runs directly in Home Aasistant as an integration
• The “new” QT-Openzwave which is a standalone application that communicates with HA using MQTT
• And confusingly enough - another “Zwave2MQTT” - which functions basically the same way, but is not as tightly integrated as QT-Openzwave.

They all use OpenZwave for the actual zwave-handling. The old integration uses an old version of Openzwave (1.4), and will not be updated much (if at all).

The new “official” way forward is to migrate to QT-Openzwave, which is currently in Beta, but works fine for most things.

The Future of Z-Wave in HA - QT-OpenZWave

Hi all, In the state of the union 2019 presentation there was a brief update on the path to Open Z-Wave 1.6. Short mention of it can be found here. [Home Assistant - State of the Union 2019] This sounds like a great path forward. There will be a separation between Home Assistant and Z-Wave meaning that restarting HA will not result in a restart of the Z-Wave network. My initial guess is this will be in a separate docker container like a Hassio addon. It will then by connected t…

It comes with the latest OpenZwave (1.6), and as such should even work better with most devices than the old integration. However, not everything is converted yet, and also some stuff is missing from the communication between the external “ozwdaemon” and Home Aassistant.

I just mirated my 50+ nodes to the new QT-openzwave yesterday, and all my devices work as expeced (mostly Fibaro and Aeon, with a few other brands thrown in just for fun…).
YMMV.