Thermostat randomly becoming unvailable

My CT101 thermostat has recently (last 3 days) randomly started to become unavailable in ZwaveJS. No change were made to my HA instance or the thermostat itself. It’s mains powered so battery is not in play here.

A ping from zwave will wake the device up and it will then become available for an undetermined amount of time. A few hours, a day…I never know. It eventually fails again though. This is becoming a problem with cooling the house on schedule because my automations are failing when it’s unavailable.

This is what I"m seeing in the ZwaveJS Logs:

2023-05-08T23:15:02.591Z CNTRLR   [Node 004] Mapping unsolicited report from root device to endpoint #1
2023-05-08T23:15:02.606Z CNTRLR   [Node 004] Mapping unsolicited report from root device to endpoint #1
2023-05-08T23:30:59.361Z CNTRLR   [Node 004] did not respond after 1/3 attempts. Scheduling next try in 500 ms.
2023-05-08T23:31:00.134Z CNTRLR   [Node 004] did not respond after 2/3 attempts. Scheduling next try in 500 ms.
2023-05-08T23:31:00.880Z CNTRLR   [Node 004] The node did not respond after 3 attempts, it is presumed dead
2023-05-08T23:31:00.881Z CNTRLR   [Node 004] The node is now dead.
Z-Wave error ZWaveError: Failed to send the command after 3 attempts (Status NoAck) (ZW0204)
    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4196:23)
    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4389:28)
    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4500:15)
    at ThermostatSetpointCCAPI.set (/usr/src/node_modules/@zwave-js/cc/src/cc/ThermostatSetpointCC.ts:229:24)
    at Proxy.ThermostatSetpointCCAPI.<computed> (/usr/src/node_modules/@zwave-js/cc/src/cc/ThermostatSetpointCC.ts:148:29)
    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:969:29)
    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:23:38)
    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:41:96)
    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:106:99)
    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:50:45) {
  code: 204,
  context: SendDataRequestTransmitReport {
    host: [Driver],
    type: 0,
    functionType: 19,
    payload: <Buffer ba 01>,
    _callbackId: 186,
    transmitStatus: 1,
    txReport: undefined
  },
  transactionSource: '    at Driver.sendMessage (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4196:23)\n' +
    '    at Driver.sendCommandInternal (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4389:28)\n' +
    '    at Driver.sendCommand (/usr/src/node_modules/zwave-js/src/lib/driver/Driver.ts:4500:15)\n' +
    '    at ThermostatSetpointCCAPI.set (/usr/src/node_modules/@zwave-js/cc/src/cc/ThermostatSetpointCC.ts:229:24)\n' +
    '    at Proxy.ThermostatSetpointCCAPI.<computed> (/usr/src/node_modules/@zwave-js/cc/src/cc/ThermostatSetpointCC.ts:148:29)\n' +
    '    at ZWaveNode.setValue (/usr/src/node_modules/zwave-js/src/lib/node/Node.ts:969:29)\n' +
    '    at NodeMessageHandler.handle (/usr/src/node_modules/@zwave-js/server/dist/lib/node/message_handler.js:23:38)\n' +
    '    at Object.node (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:41:96)\n' +
    '    at Client.receiveMessage (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:106:99)\n' +
    '    at WebSocket.<anonymous> (/usr/src/node_modules/@zwave-js/server/dist/lib/server.js:50:45)'
}

Any help would be appreciated. Reboot of HA and of the host (Rpi 4 with HUSBZB-1 controller) hasn’t made any difference.