Let's start talking about the new Z-wave JS integration

Configuration Z-Wave
303

not biting the bait here, but characterizing the mqtt layer as a ‘between layer’ in my instance is not correct.
First of all, the Mqtt isn’t ‘between’ the Z-wave and HA at all, it is ‘next’ to it on the single instance. Second to that, mqtt is only used to communicate the Z-wave states to other instances. Whichever they are, wherever they are.

If one would only use the ZwaveJS integration and add-on on 1 single production system, the mqtt addition (explicitly not calling it a ‘layer’) would not be necessary at all. If one needs it to do more than that, and publish states to other devices, one needs some sort of publishing layer.

Mqtt is clean as a whistle and defacto industry standard, or should I say purposely created for that. Using more than 1 hardware device for these purposes is simply a way to up the control in Risk management, especially if one want to be their HA system more than a Hobby, and wants it to be as secure was possible. A pure necessity imho, especially given the control over our homes we hand to it…

Being married to a professional Risk manager/enterprise architect forces me to hand over my architectural decisions every once in a while, to get the green light for future investments. Talking about the WAF :wink:

Not even talking about the proverbial Garagedoor opening while on holiday, because the Z-wave instance acted up…

304

Where do I post for door lock logging embellishment or do I just wait…patiently?

image
image709×281 17.8 KB

305

2nd question…what’s the purpose of this configuration item?

image

306

any reason why you would start on 1 instance now, and separate later? I mean, if making the transition to the new JS implementation, why not do it in the foreseen way at once?

Mainly because I really like the low maintenance approach of HA with regard to running the ZJS server as an add-on and thought it might be easier for first steps as I am not much of a Linux / Docker guru (meaning: I basically have no clue… :slight_smile:). I guess I could use the HA image on the RasPi, use the ZJS add-on and then connect from a different HA install?

Well, I just buy a Z-Stick and do some testing… :slight_smile:

307

My Kwikset 910 is not updating after a one-time state change.
I guess I’ll have to continue running HomeSeer (and a separate Z-Wave network) for my two Z-Wave locks… :pensive:

308

Thank you, this was the solution!

This works:

- alias: livingroom_tv_scene_activation_triple_click
  trigger:
  - platform: event
    event_type: zwave_js_event
    event_data:
      node_id: 2
      property_name: sceneId
      value: 25
309

I was able to integrate my Fibaro Roller Shutter 3’s but open and close are not working. I can set a specific position without problems. What abour yours?

310

Same problem here, there is no cover function… yet. I switched back to the old Zwave deprecated system… :weary:

311

same here…

Possible to fix this?

312

I have migrated successfully from OZW but my Yale lock no longer has alarmType and alarmLevel, I use to determine which user has unlocked the door.

This is in zwave js log when an event happens it is the user code, any idea if this will be added back or any other way to capture it ? I’ve tried the event listener zwave_js_event

14:22:31.934 CNTRLR « [Node 074] received unsupported notification {
                          "nodeId": 74,
                          "ccId": "Notification",
                          "ccCommand": "0x05",
                          "alarmType": 144,
                          "alarmLevel": 3
                      }

Seems the Conexis L1 is on the import list so I’ll just have to wait:

313

I switched to the new integration yesterday (from OZW) and did not encounter and unexpected issues. I have dimmers, contact sensors, thermostat, and a kwikset lock. All worked as expected. I took a snapshot before doing anything. It’s a great integration and I look forward to future updates!

I knew going into the change that setting config parameters was not supported yet (like changing the color of Inovelli LED status bars). So this was just a temporary change to play with the new integration. I took a snapshot again after playing with the new integration for a day. Then I reloaded the snapshot with the old integration (OZW) and everything worked as it had before the change.

Overall ZwaveJS is awesome for being version 1, and I’ll switch my main HA location to it full time as soon as setting config parameters through automations is added. I have three other locations with Home Assistant and will be moving some of them to ZwaveJS for further testing since they only have a few, non-critical, zwave devices.

1 Like
314

Does anyone know where the naming convention is decided in the zwave js server?

My node shows up in HA via mqtt using the json values set in the homeassistant portion of the node config.

But for the WS portion the entity has a very “unhelpful” name:

ex
ex378×517 10.1 KB

ex1

and here is the node info in zwavejs control panel:

ex2
ex2968×153 6.24 KB

I would have thought that the name would be at least linked somehow to the node info in the UI but it doesn’t seem to have any correlation.

315

I just want to thank Daniel Lando (the developer) of this new integration and all the additional develpers/testers involved in adding this to Home Assistant in record time.

I finally can see the light at the end of the tunnel, as this first release of the zwavejs integration/addon is already way better than the previous lacking two other zwave integration attempts.

With this new integration I can finally have a working center of the house remote zwave interface, which is published via Ser2Net, communicating correctly with Home Assistant, by using “tcp://remote interface ip:remote interface port” as the path for the “USB” adapter when first installing the zwavejz addon. FINALLY!!!

Good work you all !

316

That device isn’t in the config database yet. I created one for that same company’s indoor plug yesterday that got merged into the master. Looks like they are working on a massive import from ZWave alliance that should have that device in there.

317

When you say massive import, does that include devices that aren’t working properly as well, such as Yale YRD220 locks? Asking for a friend :slight_smile:

318

I was thinking that ZWAVE JS and ZWAVE JS To MQTT could be installed together for having the great interface of ZWAVE JS To MQTT.
But if i do that, my usb key cannot be share between the two containers.

So, i understand that i’m not understanding anything ? :smiley:

319

Yes, looks like there is an open pull request for the Yale YRM276 now. So other models should work their way in there.

1 Like
320

Yeah, I realize that the device isn’t in the DB yet (I offered to add it a couple of weeks back but was told to wait) but the question was more about the naming convention and what it was based on.

I named the node in the UI but for some reason it didn’t get transferred to HA.

321

yeah I had that today too, on a brand new device of which I already had setup several (Sensative Strips Guard). So deleted again, after which the second include went successful. And came up with several more sensors;-)

Apparently the type of sensors was alright, only the name and brand etc had not come across correctly. As said, it did on second try.

322

I was under the impression that that is why the name in HA is “None: Current Value”. There is no product type mapped to that product code. So the default if there is no mapping is “Current Value” Also expand the node in the CP, the binary switch is name Current Value