2.13.0

[Koenkk]

Feel free to discuss the 2.13.0 release here!

[Ruud-C]

I upgraded to this version, now the system doesn't start anymore (running as an LXC container). When I tried to start it manually from the console, this is the output I get:

zigbee2mqtt@2.13.0 start
node index.js

Starting Zigbee2MQTT without watchdog.
Building Zigbee2MQTT... (initial build), failed
node:internal/errors:985
const err = new Error(message);
^

Error: Command failed: pnpm run prepack
[WARN] The "pnpm" field in package.json is no longer read by pnpm. The following keys were ignored: "pnpm.overrides", "pnpm.onlyBuiltDependencies". See https://pnpm.io/settings for the new home of each setting.
sh: 1: tsc: not found

at genericNodeError (node:internal/errors:985:15)
at wrappedFn (node:internal/errors:539:14)
at ChildProcess.exithandler (node:child_process:417:12)
at ChildProcess.emit (node:events:509:28)
at maybeClose (node:internal/child_process:1124:16)
at ChildProcess._handle.onexit (node:internal/child_process:306:5) {

code: 1,
killed: false,
signal: null,
cmd: 'pnpm run prepack'
}

Node.js v24.18.1

[Nerivec]

Check your pnpm version, seems you might be on 11 (which has breaking changes and isn't supported yet):

pnpm --version

zigbee2mqtt/package.json

Line 7 in fcbb7ff

"packageManager": "pnpm@10.18.3",

[drauziooppenheimer]

After the update I've noticed that my light groups states are getting inconsistent if you turn them on and off rapidly.

When testing on a Philips Hue group that have 2 lights, for example, the commands will go through correctly to the lights but the group state won't update correctly. I have QoS and Optimistic set to true in the group, and by disabling the Optimistic behavior it seems to have fixed it, but it never happened in previous versions.

It seems to me that the optimistic values are lagging behind the actual state update of the device, and overriding it when they arrive later on, causing the device/group to be inconsistent.