Release 4.3.0

4.3.0 (2021-05-19)

Bug Fixes

• ui: group editors showing associations of last expanded node (#1236) (989bb87), closes #1231
• ui: moved Value Refresh button to right on NodeDetails (#1213) (332f811)
• ui: show group id in dialog dropdown (#1239) (a41c8b3), closes #1232
• ui: zwave graph better detection of neighbors changes (#1243) (c330559)
• allow sendCommand to accept string command classes (#1230) (a2e704c), closes #1219
• better types and checks for sendCommand CC (#1234) (6df119c)

Features

• zwave-js: bump [email protected] (#1237) (7f2d7ea)

Release 4.2.1

4.2.1 (2021-05-12)

Bug Fixes

• battery devices not ready (#1195) (78dec83)

Release 4.2.0

4.2.0 (2021-05-11)

It comes with [email protected], some code refactor and improvements on Mesh UI (now neighbors should be kept always up to date correctly).

We have also fixed the update configuration problem that affected docker users, starting from this version config DB will automatically be copied on store directory and kept up to date automatically, for more info check here

Starting from this version z2m is also available in github container registry

Bug Fixes

• lint issues (6417175)
• use getNeighbors method (#1146) (fa50cf1)
• hass: sending true to MultilevelSwitchCC doesn't restore old level (#1134) (13afb0a)
• ui: typo in copy-able versions info (#1135) (8e2ccc0)

Features

• docker: push image to ghcr (#1136) (ae3af3c)

Release 4.0.1

4.0.1 (2021-05-03)

Bug Fixes

• docker: config update not working (#1128) (6fccb01), closes #1122
• ui: pretty json exports (#1129) (94e9f9c), closes #1119

Release 4.0.0

4.0.0 (2021-04-30)

Bug Fixes

• ui: hide hass tab when gw is disabled (#1117) (7116911), closes #1102
• ui: valueid label color (#1097) (9acbcad), closes #1094

Features

• allow loading custom device configs from store/config (#1096) (3988049)
• support managing associations on endpoints (#1095) (4230b64)
• zwave-js config updates (#1115) (0a65549)

BREAKING CHANGES

• Signature of methods getAssociations, addAssociations and removeAssociations have changed. This will have no effect on normal users but for the ones that are using those apis via MQTT remember to check the changes in signature, now you also have to specify source endpoint instead of just the nodeId to refer to an association

Release 3.5.0

3.5.0 (2021-04-20)

Bug Fixes

• update node groups on node ready (#1076) (f7f960c), closes #1072

Features

• ui: create new directory/files in store (#1083) (0f8a3bc)

Release 3.4.0

3.4.0 (2021-04-17)

Bug Fixes

• disable saveUninitialized in express session (#1068) (7d8814e)
• prevent 404 errors in store when using nginx (#1060) (b8dd575)
• store sessions in a dedicated folder in store (#1067) (2f2c947)

Features

• allow to send a custom function to driver (#1063) (79e50fd)
• allow to send custom Config CC get/set commands (#1064) (96e0662)

Release 3.3.0

3.3.0 (2021-04-13)

Bug Fixes

• manually add missing values on updates (#1056) (c2600df)
• notification event not publiished to mqtt (#1055) (bf8db55), closes #1044
• ui: assume controller always forwards in mesh graph (#1038) (aca4af3), closes #1034 #739
• ui-mesh: better labels color based on current theme (#1050) (2bf47d8), closes #1010

Features

• ui: refresh CC values (#1051) (b3ad1a3)

Release 3.2.1

3.2.1 (2021-04-11)

Bug Fixes

• this.stopExclusion is undefined (#1036) (58f4368), closes #1031

Release 3.2.0

3.2.0 (2021-04-07)

Opt-In versus Opt-Out. There has been some recent disagreement about whether the collection of anonymous data intriduced in 3.1.0 release regarding the number and type of devices in use by users should be opt-in or opt-out. This functionality has now been changed to be purely opt-in. We apologize for any inconvenience.
Specifically, if enabled the following data will be collected:

• A hash of your network's home ID salted with a 32 byte randomly generated number. This is used to distinguish the individual records to ensure that duplicate entries aren't made. The hash cannot be reversed to reconstruct the home ID without knowing the salt which is not collected.
• The application that uses zwave-js and its version.
• The version of zwave-js.
• The manufacturer ID, product type, product ID and firmware version that are reported by each device - in other words which devices you have.

We do not collect your IP address, nor is the IP address or any other identifying information stored and tied to a record.

For more information, please see zwave-js usage statistics docs

Bug Fixes

• ui: use transparent background on zwave graph groups (#1009) (d4b6445)
• allow accent chars in topics (#1007) (79cf699), closes #1003
• applicationName used in statistics (ada8abb)

Features

• make usage statistics opt-in (#1002) (9b75833)