When I started my journey with HA couple of years ago I went for the standard implementation.
Later on Zwave2mqtt got release together with open zwave.
today we have Zwave JS & Zwave JS to MQTT. which I must say is throwing a lot of confusion to me.
So the question here is, which project do we have to use and which one has the most chances to last in time ?
I would say that zwavejs is the most likely to be maintained going forward since that is now the new âofficial path forwardâ.
The only downside right now is that the zwavejs integration using the zwavejs add-on doesnât have much of a control panel so you canât do many âadvancedâ things.
Zwavejs2mqtt has a control panel built in to the add-on/container so it offers advanced config options for your devices.
As far as going forward with zwavejs2mqtt I doubt that will be abandoned anytime soon since HA is building itâs zwave integration on the same control infrastructure that it uses. And there are a lot of HA users who donât run a Supervised install so they wonât have the add-on availability. For those people zwavejs2mqtt is the easiest/best way to get the zwavejs functionality.
But in the end itâs up to you. Do you need advanced config controls now? use zwaqvejs2mqtt. If you donât need them now then use zwavejs since that is supposed to have similar functionality to zwavejs2mqtt in the future.