currentValue does not match targetValue

[Anzic23]

Describe the bug
sometimes currentValue matches targetValue, and sometimes it takes some strange value that differs from the real one and does not match targetValue
To Reproduce
Steps to reproduce the behavior:

1. Set targetValue to arbitrary value
2. Observe currentValue
3. See error

Expected behavior
I would like currentValue to match the real value

Screenshots & Logfiles

2022-04-24T20:02:24.798Z SERIAL « 0x01090004003803260328c4                                            (11 bytes)
2022-04-24T20:03:05.068Z SERIAL » 0x010a00133803260150256ce3                                          (12 bytes)
2022-04-24T20:03:05.073Z DRIVER » [Node 056] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      108
                                  └─[MultilevelSwitchCCSet]
                                      target value: 80
2022-04-24T20:03:05.078Z SERIAL « [ACK]                                                                   (0x06)
2022-04-24T20:03:05.083Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-04-24T20:03:05.084Z SERIAL » [ACK]                                                                   (0x06)
2022-04-24T20:03:05.087Z DRIVER « [RES] [SendData]
                                    was sent: true
2022-04-24T20:03:05.121Z SERIAL » [ACK]                                                                   (0x06)
2022-04-24T20:03:05.123Z DRIVER « [REQ] [SendData]
                                    callback id:     108
                                    transmit status: OK
2022-04-24T20:03:05.142Z CNTRLR   [Node 056] [~] [Multilevel Switch] currentValue: 40 => 80         [Endpoint 0]
2022-04-24T20:03:10.169Z SERIAL » 0x0109001338022602256db3                                            (11 bytes)
2022-04-24T20:03:10.174Z DRIVER » [Node 056] [REQ] [SendData]
                                  │ transmit options: 0x25
                                  │ callback id:      109
                                  └─[MultilevelSwitchCCGet]
2022-04-24T20:03:10.179Z SERIAL « [ACK]                                                                   (0x06)
2022-04-24T20:03:10.185Z SERIAL « 0x0104011301e8                                                       (6 bytes)
2022-04-24T20:03:10.186Z SERIAL » [ACK]                                                                   (0x06)
2022-04-24T20:03:10.223Z SERIAL « 0x010700136d00000482                                                 (9 bytes)
2022-04-24T20:03:10.226Z SERIAL » [ACK]                                                                   (0x06)
2022-04-24T20:03:10.229Z DRIVER « [REQ] [SendData]
                                    callback id:     109
                                    transmit status: OK
2022-04-24T20:03:10.274Z CNTRLR   [Node 056] [~] [Multilevel Switch] currentValue: 80 => 59         [Endpoint 0]
2022-04-24T20:03:10.277Z SERIAL » [ACK]                                                                   (0x06)
2022-04-24T20:03:10.281Z DRIVER « [Node 056] [REQ] [ApplicationCommand]
                                  └─[MultilevelSwitchCCReport]
                                      current value: 59
2022-04-24T20:03:10.351Z SERIAL « 0x0109000400380326033bd7                                            (11 bytes)

Versions:

• Adapter version: 2.5.0
• JS-Controller version: 4.0.21
• Node version: v14.19.0
• Operating system: Master in docker + slave on RPI 3 b+ (adapter on slave)
• device: Electronic Solutions DBMZ EU

Additional context
By the way, the logs inside the admin tab are not displayed, they are partially displayed in a new window (if the theme is light), and they are also partially displayed in a dark one.

[AlCalzone]

Sorry, seems I missed this. What kind of device is this? 59 is the value reported by the device when the adapter requests the current value after 5s. Maybe it is not done transitioning yet?

[Anzic23]

Sorry, seems I missed this. What kind of device is this? 59 is the value reported by the device when the adapter requests the current value after 5s. Maybe it is not done transitioning yet?

curtain control Electronic Solutions DBMZ EU
it is possible, but then it may be necessary to create something like a timer for transmitting a report from the device, so that the adapter checks whether the device sends any other values. The curtain moves for more than 5 seconds

[AlCalzone]

Is it possible to control this device manually without Z-Wave? Does it send correct status updates then?

[Anzic23]

yes, can control it by pressing the buttons on the device itself. I will check this moment and write.

[AlCalzone]

Please re-test with v3.0.0

[Anzic23]

Please re-test with v3.0.0

Now it's ok!

[AlCalzone]

Also the currentValue / targetValue issue?