# \[ANNOUNCE - MAJOR UPDATE\] : node-red-contrib-zwave-js : Version 11

**URL:** <https://discourse.nodered.org/t/announce-major-update-node-red-contrib-zwave-js-version-11/100680>\
**Category:** Share Your Nodes\
**Tags:** zwave, zwave-js\
**Created:** [29 March 2026 15:48 UTC](https://discourse.nodered.org/t/announce-major-update-node-red-contrib-zwave-js-version-11/100680 "2026-03-29T15:48:21Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [29 March 2026 15:48 UTC](https://discourse.nodered.org/t/announce-major-update-node-red-contrib-zwave-js-version-11/100680/1 "2026-03-29T15:48:22Z")

</div>

Well!..... Here it is - The **Big One**!

I will include the release notes below, but I'll cut to the chase.

- V11 contains **many** breaking changes, and is deemed not a simple "Upgrade"  
Your network configuration will remain unaffected - But **you will** need to re-engineer your flows

I'm truly sorry

* * *

This has been a major task of mine, and I am happy to finally finish the transition to a new unified ZWave Stack directly in Node RED. 🤓

I wish to thank @E1cid for the BETA testing, and for the massive involvement and discussion. 🙏

* * *

- 11.0.0

**New Side Bar UI screenshots!**

* * *

 ![UI](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/e/5/e55365135b08a66dbd2f1841101e720387612564.jpeg)

> **[node-red-contrib-zwave-js](https://flows.nodered.org/node/node-red-contrib-zwave-js)**
>
> The most powerful, high performing and highly polished Z-Wave node for Node-RED based on Z-Wave JS. If you want a fully featured Z-Wave framework in your Node-RED instance, you have found it.

---

<div class="post-metadata">

**Author:** ![magicman](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@magicman](https://discourse.nodered.org/u/magicman)\
**Post date:** [1 April 2026 15:29 UTC](https://discourse.nodered.org/t/announce-major-update-node-red-contrib-zwave-js-version-11/100680/2 "2026-04-01T15:29:14Z")

</div>

Excited as i am for this update, i have so many flows using the previous version.  
Can you if you have time talk me through what i have to do to update?

Thanks

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [1 April 2026 16:24 UTC](https://discourse.nodered.org/t/announce-major-update-node-red-contrib-zwave-js-version-11/100680/3 "2026-04-01T16:24:43Z")

</div>

Hi @magicman

It's not actually that daunting when you get into it:

**1st**

1. Backup your SO, S2 Keys.
2. Backup your Filter Node(s) JSON Descriptors.  
You will use these to understand how to recreate the filters (now splitters) using the new Node  
(If you use them).

**2nd**

1. After installing the latest update (Restart Node RED, Refresh Browser),  
All previous version nodes will not be recognised (ID's have changed).
2. The Device Node & Controller Node - now require a config Node  
(previously the config lived on the Controller Node).

**3rd**

1. Controller Node, no longer emits events for devices, the controller Node only emits network level events.
2. Its only the Device Nodes that emit device level events

**4th**

1. Events & Commands have been updated.

- [Event Manual](https://github.com/zwave-js/node-red-contrib-zwave-js/blob/main/Event%20Manual.md)
- [Command Manual](https://github.com/zwave-js/node-red-contrib-zwave-js/blob/main/Command%20Manual.md)  
Example new `payload` for a command

```js
{
    cmd: {
        api: 'VALUE',
        method: 'setValue'
    },
    cmdProperties: {
        nodeId: 10,
        valueId: {...},
        value: 100
    }
}

```

Example new `payload` for an event

```js
{
    event: 'VALUE_UPDATED',
    timestamp: 1234567890,
    nodeId: 10,
    nodeName: 'My Node',
    nodeLocation: 'My Location',
    eventBody: {
        valueId: {...},
        newValue:100, 
        prevValue: 50
    }
}

```

**The Gist:**

* * *

Install update, replace the now invalid Nodes with the new versions.  
Where you were using a single `controller` Node to receive events for all devices, replace them with `Device` Nodes (set to receive events for all Nodes)

When adding a `Controller` OR `Device` Node - you will get the opportunity to create the config Node, once created the `Controller` and / or `Device` node doesn't need to remain - only where you need it.

When recreating the filter (Now splitter) nodes.  
Click a value in the side bar, and choose to add it to a Splitter Node (most be in your flow)

The JSON Descriptor you backed up, will help you name them, as they were, and so you can understand the original property you filtered on.

 ![Screenshot 2026-04-01 at 17.14.32](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/3X/9/c/9c8159b7d77a5f31f748becc10603423354032fd.png)

Sounds more daunting than it actually is, its mainly the updating your commands.  
**BUT** if you were using the CMD Factory - this was already using the new format (in V9)

I hope this helps 😃  
Happy to answer any questions

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [1 April 2026 16:39 UTC](https://discourse.nodered.org/t/announce-major-update-node-red-contrib-zwave-js-version-11/100680/4 "2026-04-01T16:39:00Z")

</div>

Oh and @knolleary...

Please don't screw around with the SideBar / Tray to much in V5 - I now depend on it like my wife depends on me being out the house for peace 😁

(but I have tested in V5 - and all good, thus far)

---

<div class="post-metadata">

**Author:** ![marcus-j-davies](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/marcus-j-davies/32/103435_2.png) [@marcus-j-davies](https://discourse.nodered.org/u/marcus-j-davies)\
**Post date:** [4 April 2026 10:42 UTC](https://discourse.nodered.org/t/announce-major-update-node-red-contrib-zwave-js-version-11/100680/5 "2026-04-04T10:42:57Z")

</div>

**V11.0.1** Released.

just some snagging to take care off

**Bug Fixes**

- Ensure `lastSeen` is available before using it (Node List)
- Restore value lables in Side Bar (where available)

**Changes**

- Update `README` badges
- Reimplement npm pubhlish via `OIDC`

> **[node-red-contrib-zwave-js](https://flows.nodered.org/node/node-red-contrib-zwave-js)**
>
> The most powerful, high performing and highly polished Z-Wave node for Node-RED based on Z-Wave JS. If you want a fully featured Z-Wave framework in your Node-RED instance, you have found it.

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [30 April 2026 09:57 UTC](https://discourse.nodered.org/t/announce-major-update-node-red-contrib-zwave-js-version-11/100680/6 "2026-04-30T09:57:56Z")

</div>

2 posts were split to a new topic: [Using transitionDuration with ZwaveJS node V11](https://discourse.nodered.org/t/using-transitionduration-with-zwavejs-node-v11/100873)

To make finding issues and fixes easier, I recommend starting new topics when issues arise.  
Post bugs issues with the released node here, not general usage issues.

---

<div class="post-metadata">

**Author:** ![E1cid](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/e1cid/32/77971_2.png) [@E1cid](https://discourse.nodered.org/u/E1cid)\
**Post date:** [30 April 2026 09:59 UTC](https://discourse.nodered.org/t/announce-major-update-node-red-contrib-zwave-js-version-11/100680/8 "2026-04-30T09:59:43Z")

</div>

3 posts were split to a new topic: [Failed to initialize the driver: ZWaveError](https://discourse.nodered.org/t/failed-to-initialize-the-driver-zwaveerror/100874)

This one could well have been a bug, I think moving to own topic will help others find the fix easier.