Switching from OpenZwave (Beta) to ZWave JS UI (formerly ZwaveJS2MQTT)

Community Guides
41

I did, yes. I started with HA a few weeks ago. I started with the Z-wave integration, then OZW beta, then ZwaveJS and now ZwaveJS2MQTT. I’ve run the gauntlet and I’m anxious to get to a stable/consistent configuration! I’ll put this down for awhile and come back to it later, thanks.

EDIT: after a few hours I got impatient and bumped each node with a re-interview. Most of them came back up within a few minutes. One node is giving me some issues and is physically within a few feet of another functional node, so I’m going to have to investigate that one.

42

Everyone with this problem,.
this what i did,

a0d7b954_zwavejs2mqtt (this is what you copy from the URL. but in fact if you actually read the instruction is as to be
a0d7b954-zwavejs2mqtt (the diference is the - instead of _ )

1 Like
43

Hi,

great howto! Thanks for that.
I migrated to MQTT, rather than using the WebSocket, and with ZwaveJS on a dedicated raspi.
I used to have this in my zwave configuration

device_config:
  cover.roller_shutter:
    invert_openclose_buttons: true
    invert_percent: true

Is there something similar for ZwaveJS, and maybe also ZwaveJS over MQTT ?

Thanks in advance.

44

I found that when I added the integration it asked me if I wanted to use the “Supervisor Add on” which is a little ambiguous when there is a “ZWave JS” addon and a “ZWaveJS2MQTT” one.

So if you come across this you want to untickthe box to use the supervisor addon - it wil lthen prompt you for a hostname - this can be found on the Supervisor ZWaveJS2MQtt add on page.

45

The template step, to dump Z-Wave nodes and related entities, is very useful! But I can’t quite figure out how to get similar output from the new ZwaveJS integration once I’ve completed the migration. Does anyone have a working template for this?

46

It’s not possible because the entities do not store zwave node information. You have to follow step 11 for the renaming process.

47

I am having an interesting issue. I tried migrating from the OZW beta to Z-Wave JS to MQTT. I was able to install the add-on successfully and it discovered my only device, a Schlage BE469ZP, but when I create the integration for ZWave JS in HA using the WebSocket, I dont get anything.!

firefox_ZSVXBb4fcs
firefox_ZSVXBb4fcs1844×682 98.7 KB

The only difference is that instead of using device by-id my only option was /dev/ttyACM0

48

I had this same issue and found the fix in the addons docs. Maybe this can be added to the guide.

49

Changing from an underscore to a dash worked for me. Thank you.

In short:

  • New Install
  • Install zwavejs2mqtt and set usb path and network key
  • Begin Install of Z-Wave JS Integration
  • Uncheck Use Supervisor
  • Use url from zwavejs2mqtt with - instead of _.
  • Lights detected and added to Home Assistant.
2 Likes
50

You have to follow step 11 for the renaming process.

Step 11 just says, “Rename Devices using the text file as a reference”. So no way to get any dump of current zwave entities?

51

That was steps 1 through 4 of the preparation section…

52

Yes, that script works for ozw. I’m using zwave js and would like to move to zwavejs2mqtt so would like to dump current zwave js things.

53

You don’t have to do anything when switching from zwave js to zwavejs2mqtt. Everything should be named the same after switching.

54

Petro, now youre here. I am planning on running a 2nd zwave network zwavjs (or js2mqtt) on a separate stick next to ozw. That will not bite will it?

Currently testing on my test system and switching between js and j2mqtt is painless. Although I do not know why I would ever switch back to js as I cannot configure any parameter there…

55

That’s all coming at some point.

I’m not sure, the signals crossing might cause issues. That’s something you’d have to experiment with long term.

56

Ah, gotcha, thanks for your quick response!

57

I currently have two operating zwave and zigbee sticks less than 6 inches apart and have never had any obvious interference between the two of either protocol.

58

That’s fortunate as they do not operate on the same frequency ! :stuck_out_tongue:

59

The two zwave sticks run on the same frequency.

The two zigbee sticks run on the same frequency.

I think you missed that I have two of each protocol sticks (three sticks total - one zwave, one zigbee, and one zwave/zigbee combo) and all running within 6 inches of each other with no obvious interference.

1 Like
60

After some recent ZWave issues, I moved from OZW to ZwaveJS and then to ZwaveJSMQTT pretty quick after that. I was please to see that ZwaveJSMQTT found many of my items that regular JS was having trouble with. I’m having a little trouble with a couple of my battery Zwave items retrieving all the sensors and payload data right. When on OZW for these items [Everspring ST812 flood sensor, Kwikset 910 door locks & Nortek NGD00Z-4 garage door openers] to get them fully populating in my old smartthings and for the past couple years in HA I would put Zwave in inclusion and wake up the device. Often this would be repeatedly until finally all the features appeared.

With ZwaveJSMQTT I read a few times that I just need to wake it up and it will poll the device or I could re-interview through the control panel. I’ve tried both a couple times and they just don’t seem to be getting any new information. For the flood sensors for example I can refresh the battery levels fine every time the device wakes up but the most important sensor the “leak_state” isn’t appearing. I tried with one of these flood sensors to update it by putting the network into inclusion mode but it just refresh the same sensors again.

Should I need to do any of these extra steps or is repeatedly waking the device and letting ZwaveJSMQTT manage it from there the best route? All in all though I really like this version as it seems to offer a good mix of options not yet seen on the regular JS version.

1 Like