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

gregg098 · February 6, 2021, 7:30pm

Was anyone able to get First Alert ZCOMBO Smoke/CO detectors working? They are a major PITA to get ZwaveJS (OZW too…) just to recognize them. I finally got them working, but only battery sensors are operational. There were some hidden alarm level and alarm type sensors necessary to determine if its a test, CO, and Smoke. I enabled them but they never show anything except “Unknown” for a state.

I had a heck of a time getting all my devices recognized (~50 devices, lots of miscellaneous devices, lots of battery powered devices), figuring out scenes for my switches and things like that. This was true when I migrated to OZW so its not ZwaveJS specific. I finally switched back though after I couldnt get the ZCOMBO devices to work. That was the deal breaker for now. I guess if I want to try again I can at least just restart the ZwaveJS container and start over on renaming my Hass entities, but shouldnt have to go through the hell of trying to get it to re-interview everything.

finity · February 6, 2021, 7:48pm

I haven’t tried but I’ve got a couple of those too.

that’s why I’m waiting to fully switch - to find others experiences with these types of devices (or just in general).

Have you tried to actually do a test of the sensor to see if the “unknown” changes to something else when there is actual data to send?

How did you “enable” those other sensors?

freshcoast · February 6, 2021, 8:02pm

There’s a bug fix for that, probably next patch.

kklicker · February 6, 2021, 8:07pm

Hi. Recently switched over to Z-wave JS. Most of my devices function as expected, but I’ve recently got a couple of these GoControl remote switches, WA00Z-1, and have been using them to dim and brighten non-Zwave bulbs, Tuya-based. Was working pretty good using the zwave.scene_activated event. However, I’ve been listening for zwave_js_event on the Dev Tools, and I don’t get any info when I click, double-click and release the buttons. Does anybody know if these devices are supported? If not, would it be difficult to get support for these? Thanks.

ctowers · February 6, 2021, 8:21pm

I could have just gotten lucky after the 6th or 7th attempt… but all my 13 devices(wink motion sensors, go control led bulbs and climate control, greenwave power strips, kwikset 912 locks) are working and reporting in like normal. Pulled the trigger and migrated over upon learning of the improved speeds and I can confirm z-wave JS is indeed faster. However, I had to scorch earth the zwave network and start anew because my locks wouldn’t show up initially. That meant factory resetting everything. Here’s a few takeaways:

Back up your zwave network if you can- aeotech provides a tool for their stick, not sure if others do, helped restore things to a working state, while still being able to troubleshoot effectively.
Be Patient: This is especially true with the secure nodes, it just takes much longer to handshake in context to anything unsecure.
Added the secure nodes(locks: kwikset SmartCode 912) last- also restarted HA and the add-on, not sure why this ultimately helped my migration, maybe someone more familiar can provide additional insight, could have just been luck…
Replaced old batteries- again not sure how much impact this had but if you’re already resetting stuff, I can’t imagine this can hurt.

gregg098 · February 6, 2021, 8:25pm

I did try a test. Doing a test alert on the monitor itself usually issues a specific alarm type and level. I tried a few times after restarts and things like that.

I enabled them by going into the ZwaveJS integration, finding that device, then there were a list of disabled entities. Just went into each one and selected enable. I had to do the same thing when I moved to OZW, except I got values.

gregg098 · February 6, 2021, 8:26pm

Good to hear. Just wondering, new Home Assistant version or ZWaveJS version?

freshcoast · February 6, 2021, 8:42pm

Fix is in HA.

finity · February 6, 2021, 8:51pm

that does bring up another question…

how tightly are the underlying server updates tied to the HA integration updates/functionality?

As an example specifically in this instance it sounds like the problem is in the HA side but if the problem is in the zwave js server side are the zwave js server folks keeping development moving forward based on feedback from HA users?

I (think) that the zwavejs2mqtt updates are (loosely?) tied to the underlying server updates but are the issues HA users are reporting getting relayed to the zwave js server developers and getting addressed or is that a separate track of development?

I’m not sure how to ask the question so I’m hoping you understand what I’m asking.

truglodite · February 6, 2021, 11:43pm

Along these lines, I have found the following references for supported devices and command classes:

Supported Commands:

github.com/zwave-js/node-zwave-js

[Tracking] Implementation status of Command Classes

opened 01:35PM - 19 Mar 19 UTC

AlCalzone

help wanted infrastructure

| | CC name | Version | Interview? | API? | setValue? | pollValue? | | --- | --…- | --- | --- | --- | --- | --- | | ✔ | Alarm Sensor (deprecated) | 1 (1) | ✔ | ✔ | ✔ | ❌ | | ❌ | Alarm Silence | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Anti-Theft | - (3) | ❌ | ❌ | ❌ | ❌ | | ❌ | Application Status | - (1) | ❌ | ❌ | ❌ | ❌ | | ✔ | Association | 3 (3) | ✔ | ✔ | ✔ | ❌ | | ❌ | Association Command Configuration | - (1) | ❌ | ❌ | ❌ | ❌ | | ✔ | Association Group Information | 3 (3) | ✔ | ✔ | ✔ | ❌ | | ❌ | Authentication | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Authentication Media Write | - (1) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Barrier Operator | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Basic | 2 (2) | ✔ | ✔ | ❌ | ❌ | | ❌ | Basic Tariff Information | - (1) | ❌ | ❌ | ❌ | ❌ | | ✔ | Battery | 3 (3) | ✔ | ✔ | ✔ | ❌ | | ✔ | Binary Sensor (deprecated) | 2 (2) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Binary Switch | 2 (2) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Climate Control Schedule (deprecated) | 1 (1) | ❌ | ✔ | ❌ | ❌ | | ✍🏻 | Central Scene | 3 (3) | ✔ | ✔ | ❌ | ❌ | | ✔ | Clock | 1 (1) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Color Switch | 3 (3) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Configuration | 4 (4) | ✔ | ✔ | ❌ | ❌ | | ❌ | Controller Replication | - (1) | ❌ | ❌ | ❌ | ❌ | | ✔ | CRC-16 Encapsulation (deprecated) | 1 (1) | ✔ | ✔ | ✔ | ❌ | | ❌ | Demand Control Plan Configuration | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Demand Control Plan Monitor | - (1) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Device Reset Locally | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Door Lock | 4 (4) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Door Lock Logging | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Energy Production | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Entry Control | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✔ | Firmware Update Meta Data | 7 (7) | ✔ | ✔ | ✔ | ❌ | | ❌ | Generic Schedule | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Geographic Location | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Grouping Name (deprecated) | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | HRV Status | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | HRV Control | - (1) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Humidity Control Mode | 2 (2) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Humidity Control Operating State | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Humidity Control Setpoint | 2 (2) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Inclusion Controller | 1 (1) | ❌ | ✔ | ❌ | ❌ | | ✍🏻 | Indicator | 4 (4) | ✔ | ✔ | ❌ | ❌ | | ❌ | IP Association | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | IR Repeater | - (1) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Irrigation | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✔ | Language | 1 (1) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Lock (deprecated) | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ❌ | Mailbox | - (2) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Manufacturer Proprietary | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✔ | Manufacturer Specific | 2 (2) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Meter | 6 (6) | ✔ | ✔ | ❌ | ❌ | | ❌ | Meter Table Configuration | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Meter Table Monitor | - (3) | ❌ | ❌ | ❌ | ❌ | | ❌ | Meter Table Push Configuration | - (1) | ❌ | ❌ | ❌ | ❌ | | ✔ | Multi Channel | 4 (4) | ✔ | ✔ | ✔ | ❌ | | ✔ | Multi Channel Association | 4 (4) | ✔ | ✔ | ✔ | ❌ | | ✔ | Multi Command | 1 (1) | ✔ | ✔ | ✔ | ❌ | | ✔ | Multilevel Sensor | 11 (11) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Multilevel Switch | 4 (4) | ✔ | ✔ | ❌ | ❌ | | ❌ | Multilevel Toggle Switch (deprecated) | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Network Management Basic Node | - (2) | ❌ | ❌ | ❌ | ❌ | | ❌ | Network Management Inclusion | - (3) | ❌ | ❌ | ❌ | ❌ | | ❌ | Network Management Installation and Maintenance | - (2) | ❌ | ❌ | ❌ | ❌ | | ❌ | Network Management Proxy | - (3) | ❌ | ❌ | ❌ | ❌ | | ✔ | No Operation | 1 (1) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Node Naming and Location | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ❌ | Node Provisioning | - (1) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Notification | 8 (8) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Powerlevel | 1 (1) | ❌ | ✔ | ❌ | ❌ | | ❌ | Prepayment | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Prepayment Encapsulation | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Proprietary (deprecated) | - (1) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Protection | 2 (2) | ✔ | ✔ | ❌ | ❌ | | ❌ | Pulse Meter (deprecated) | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Rate Table Configuration | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Rate Table Monitor | - (1) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Scene Activation | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Scene Actuator Configuration | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Scene Controller Configuration | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ❌ | Schedule | - (4) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Schedule Entry Lock (deprecated) | 3 (3) | ✔ | ✔ | ❌ | ❌ | | ❌ | Screen Attributes | - (2) | ❌ | ❌ | ❌ | ❌ | | ❌ | Screen Meta Data | - (2) | ❌ | ❌ | ❌ | ❌ | | ✔ | Security | 1 (1) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Security 2 | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ❌ | Simple AV Control | - (4) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Sound Switch | 2 (2) | ✔ | ✔ | ❌ | ❌ | | ✔ | Supervision | 2 (2) | ✔ | ✔ | ✔ | ❌ | | ❌ | Tariff Table Configuration | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Tariff Table Monitor | - (1) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | Thermostat Fan Mode | 5 (5) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Thermostat Fan State | 2 (2) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Thermostat Mode | 3 (3) | ✔ | ✔ | ❌ | ❌ | | ✔ | Thermostat Operating State | 2 (2) | ✔ | ✔ | ✔ | ❌ | | ✔ | Thermostat Setback | 1 (1) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Thermostat Setpoint | 3 (3) | ✔ | ✔ | ❌ | ❌ | | ✔ | Time | 2 (2) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Time Parameters | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Transport Service | 2 (2) | ❌ | ❌ | ❌ | ❌ | | ✍🏻 | User Code | 2 (2) | ✔ | ✔ | ❌ | ❌ | | ✔ | Version | 3 (3) | ✔ | ✔ | ✔ | ❌ | | ✍🏻 | Wake Up | 3 (3) | ✔ | ✔ | ❌ | ❌ | | ✍🏻 | Window Covering | 1 (1) | ✔ | ✔ | ❌ | ❌ | | ❌ | Z/IP | - (4) | ❌ | ❌ | ❌ | ❌ | | ❌ | Z/IP 6LoWPAN | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Z/IP Gateway | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Z/IP Naming and Location | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Z/IP ND | - (1) | ❌ | ❌ | ❌ | ❌ | | ❌ | Z/IP Portal | - (1) | ❌ | ❌ | ❌ | ❌ | | ✔ | Z-Wave Plus Info | 2 (2) | ✔ | ✔ | ✔ | ❌ |

Supported Devices:

Looks like some key things are missing for me, like thermostat fan state. What is less obvious, is the current state of support for my Honeywell T6 thermostat. I have found it in the latter page as TH6320ZW, but that list of parameters is waaaay smaller than what I have right now using the 1.4 integration.

If I wanted to hold off until all of the features I use are supported, would looking at the devices support page be adequate?

I assume for example, if thermostat fan mode is not supported, I should not expect to find it in any of the devices on the latter page, correct? OTOH, if fan mode gets added to the command classes, and I find it in my T6 listing, then it’s probably good to go… versus fan mode is added but I don’t find it in the T6 page, then I have to do some work to get it working (either code myself, or at least provide data to a capable dev). Is my concept of how to watch zwavejs developement wrt supported devices correct?

majorsl · February 7, 2021, 12:30am

I have one, have a look over here… I did get my WA00Z-1 working.

kklicker · February 7, 2021, 1:46am

Hi, thanks, I did finally get some events on the zwave_js_event queue coming through. Apparently, I had an instance of my old zwave network which was blocking the events. However, I’m still having an issue. I can get the “KeyPressed” event to work, but I’m trying to get the “KeyHeldDown” event to work since I’m using it in a dimming routine. The problem is, when I’m holding down the button, the “KeyHeldDown” event shows up, but then the “KeyReleased” event shows up right away, even though I have not let go of the button yet. Have you seen this behaviour? This is not the way it was working before I switched to Z-wave JS.

kelchm · February 7, 2021, 4:31am

Had anyone had issues with zwavejs and toggling a large number of lights? It’s working flawlessly for me until I try to toggle like 15 goths at once. (IE: “okay Google turn off all the lights”) — at which point Google reports that something went wrong and usually only a handful of lights turn off.

Dansker · February 7, 2021, 9:38am

Making the switch to ZwaveJS:

How does events and data from a Ecolink PIR Motion Sensor V2.5 show up?

ZwaveJS does include the device, but no entities show up.

edit: A couple of reboots and a bit of patience, it works!

Marcus_Lundblad · February 7, 2021, 2:54pm

I don’t get any Up / Down switches for my blinds…
Qubino - ZMNHOD shutter
IS there a fix coming or do i have to do something to make them visible?

gregg098 · February 7, 2021, 4:56pm

Is there a way to monitor status of the ZWaveJS container when the network is ready or not? I dont see any events coming through when the intial scan is completed after a restart or when it goes offline. Looking for something similar to a network ready event like we used to have.

Michael_Griffin · February 7, 2021, 5:39pm

How do I use the Control Panel to lock/unlock the device? I haven’t found the button yet.

majorsl · February 7, 2021, 5:58pm

In the Node, look under Values, expand Door Lock, and set it with Target Lock Mode.

Michael_Griffin · February 7, 2021, 6:16pm

Thanks, but it doesn’t appear to be working. I’ve tried all the different states listed, but nothing seemed to change the lock state.

It might be related to the fact that my lock is actually a Kwikset 916, but it registers with the 910 profile. I submitted an issue about it on Github, but I know that my 916 lock has a lot of quirks, so I’m hoping they can figure it out.

gregg098 · February 7, 2021, 6:17pm

Anyone else having nodes get marked as dead for no reason? This morning is keeps marking my front door lock (Schlage) and a GE Outdoor Plug as dead for no reason. I can operate the lock locally and it says “awake” but then goes “dead” about 5 seconds later. Have restarted a few times. Will try re-interviewing, but seems odd that its doing that randomly.