Red dimmer's no longer reliably respond to scene changes from homeassistant via zwave-js

My setup uses aeotec gen5+ stick, zwave-js-ui, homeassistant, node-red.
From Node-Red I make service calls to home assistant onward to zwave-js-ui and a handful of Inovelli Red Dimmers.

I have started seeing this error message below in the zwave-js logs when a call is made to set the brightness of the switch. It’s sporatic. The call works the first time, but then fails on subsequent calls. I’ve inspected the raw JSON being sent from node-red. It is consistently the same.

This strikes me as something to do with the switch itself. That is, it receives one message, works, then receives an identical message and fails.

Has anyone seen similar?

zwavejs-zwave-1 | 2023-08-22 04:09:02.976 ERROR Z-WAVE-SERVER: The node failed to decode the message. (ZW1405)
zwavejs-zwave-1 | ZWaveError: The node failed to decode the message. (ZW1405)
zwavejs-zwave-1 | at Driver.sendMessage (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4768:23)
zwavejs-zwave-1 | at Driver.sendCommandInternal (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:4965:28)
zwavejs-zwave-1 | at Driver.sendSupervisedCommand (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:5010:27)
zwavejs-zwave-1 | at Driver.sendCommand (/usr/src/app/node_modules/zwave-js/src/lib/driver/Driver.ts:5058:30)
zwavejs-zwave-1 | at Proxy.set (/usr/src/app/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:251:24)
zwavejs-zwave-1 | at Proxy. (/usr/src/app/node_modules/@zwave-js/cc/src/cc/MultilevelSwitchCC.ts:327:17)
zwavejs-zwave-1 | at ZWaveNode.setValue (/usr/src/app/node_modules/zwave-js/src/lib/node/Node.ts:1123:39)
zwavejs-zwave-1 | at NodeMessageHandler.handle (/usr/src/app/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:20:43)
zwavejs-zwave-1 | at Object.node (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:42:96)
zwavejs-zwave-1 | at Client.receiveMessage (/usr/src/app/node_modules/@zwave-js/server/dist/lib/server.js:107:99)

I’m seeing the same error message. I can’t quite pinpoint a version of software where it started happening. I’ve seen it with every zwave-js-ui version between 8.23.0 and 8.25.0.