Current value != target value

[alcalzone]

Current value != target value

[AlCalzone]

No matter if I write 100 or 99 into target value - current value stays at 0 (script driven). If I manually (by hand) write 99 into target value then the current value shows the correct value.

1. 100 is not a valid value
2. Do the devices do anything when you change targetValue by script? Please share the exact command you use.

[mediaDS]

Well, yes, they do as they should. But as I said - once in a while - they don't. It is hard to replicate, but for two days they show the correct values but today they don't. What I did not mention is that the shutter is actually driving into the desired position - if the shutter is in the 100% position (fully open) the current value still shows 0 - as shown in the image.

[AlCalzone]

I see - I'm working on similar problems right now - should be fixed in the next version.

Side note: you don't need to use getState in a trigger when you already have the desired value in obj.state.val. And you don't need async if you're not using await. This is enough:

on({id: 'var.0.Rolladen.Pos_Technik_EG', change: "ne"}, function (obj) {
  setState("zwave2.0.Node_037.Multilevel_Switch.targetValue_001"/*Target value (Endpoint 1)*/, obj.state.val);
});

(or was this a Blockly export?)

[mediaDS]

Yep, it is a Blockly script (I just love Blockly :)

I will look forward to the next version then, will report back if anything weird happens. Have a nice day.

[mediaDS]

I installed 1.8.9 now and so far no problem, good job, thank you. I'll keep an eye on it and will report any misbehauviour asap.

Again, thanks for the work you do, have fun

Dieter

[AlCalzone]

Ok I'll close this for now then.

[mediaDS]

Hi,

the bug is still there - see screenshot. As before - if I enter the target value manually, the current value is set properly. Maybe there is a timing problem while writing the values? Would be nice if you could fix this once and for all.

General System Information:

System: ioBroker
Hostname: Casper
Platform: Linux arm64 @ Odroid-C2
Memory: 2 GB
Node.js: 12.21.0
NPM: 6.14.11
JS-Controller: 3.2.16
Admin Adapter: 4.2.1
JS Script Engine: 5.0.5

Adapter Information:

Z-Wave Adapter: 1.8.12
Zigbee Adapter: 1.4.4
MQTT Adapter: 2.3.5 (Broker)
Z-Wave Controller: USB ZME-UZB1
Zigbee Controller: CC2531 PCB zStack12 v2.0.2.6.3

Z-Wave Devices (24):

7 x Roller Shutter Controller: Fibaro FGRM-222
1 x Multisensor: Aotec MS ZW100
2 x Multisensor: DB5
4 x Multisensor: Fibaro FGMS-001
1 x Siren: Everspring SE812
1 x Water Sensor: Everspring ST812
1 x Water Sensor: Fibaro FGFS-101
3 x Dimmer: Fibaro FGD-212
2 x Main Switches: Greenwave NS310
1 x Window Sensor: Schwaiger ZHS09
1 x Smoke Detector: Vision ZS6101

Zigbee Devices (14):

1 x Mueller Color LED A60 ZBT-Extended Color
2 x Philips Hue Motion Sensr SML001
6 x Philips Hue White Single Bulb B22 LWB010
1 x Philips Hue White Ambience E14 LTW012
1 x Philips Hue White and Color LCT010
3 x Philips Hue White A60 LWA001

WiFi Devices:

1 x Weather station ESP32 via MQTT
1 x Radar Motion Sensor ESP8266 via MQTT

Visualisation Displays:

2 x Waveshare 10.1" Touch Display, Raspbian Buster @ Raspberry 3B+

[AlCalzone]

Do you have the option "improve compatibility for legacy switches" set in the adapter config?

[mediaDS]

I just looked and no, I did not. I did now and will observe if this fixes the problem. If so - thanks so much. If not I'll report back.

[AlCalzone]

it should, even without the script