feat: add support for disableOptimisticValueUpdate driver option

robertsLando · robertsLando · commit 081ed2977827 · 2025-05-29T15:06:49.000+02:00
Fixes #4247
diff --git a/api/lib/ZwaveClient.ts b/api/lib/ZwaveClient.ts
@@ -613,6 +613,7 @@ export type ZwaveConfig = {
 	sendToSleepTimeout?: number
 	responseTimeout?: number
 	enableStatistics?: boolean
+	disableOptimisticValueUpdate?: boolean
 	disclaimerVersion?: number
 	options?: ZWaveOptions
 	// healNetwork?: boolean
@@ -2192,6 +2193,7 @@ class ZwaveClient extends TypedEventEmitter<ZwaveClientEventCallbacks> {
 			userAgent: {
 				[utils.pkgJson.name]: utils.pkgJson.version,
 			},
+			disableOptimisticValueUpdate: this.cfg.disableOptimisticValueUpdate,
 		}
 
 		// when no env is specified copy config db to store dir
diff --git a/src/stores/base.js b/src/stores/base.js
@@ -55,6 +55,7 @@ const useBaseStore = defineStore('base', {
 			serverEnabled: false,
 			serverServiceDiscoveryDisabled: false,
 			enableSoftReset: true,
+			disableOptimisticValueUpdate: false,
 			enableStatistics: undefined, // keep it undefined so the user dialog will show up
 			serverPort: 3000,
 			serverHost: undefined,
diff --git a/src/views/Settings.vue b/src/views/Settings.vue
@@ -1028,6 +1028,18 @@
 												Misc settings
 											</v-subheader>
 										</v-col>
+
+										<v-col cols="12" sm="6">
+											<v-switch
+												hint="Some SET-type commands optimistically update the current value to match the target value when the device acknowledges the command. While this generally makes UIs feel more responsive, it is not necessary for devices which report their status on their own and can lead to confusing behavior when dealing with slow devices like blinds."
+												persistent-hint
+												label="Disable optimistic value updates"
+												v-model="
+													newZwave.disableOptimisticValueUpdate
+												"
+											></v-switch>
+										</v-col>
+
 										<v-col cols="12" sm="6">
 											<v-switch
 												hint="Usage statistics allows us to gain insight how `zwave-js` is used, which manufacturers and devices are most prevalent and where to best focus our efforts in order to improve `zwave-js` the most. We do not store any personal information. Details can be found under https://zwave-js.github.io/node-zwave-js/#/data-collection/data-collection?id=usage-statistics"
