Nach update 3.5.5 STATE invertiert bei Rollladen Aktoren

[Xerxes55]

describe the problem in Detail. What do you expect to happen ? What does happen ?

Beim Befehl UP zeigen die Attribute folgendes:
MOVING = UP
STATE = CLOSE

Auf Zigbee2MQTT habe ich diese Option invert_cover gefunden. Das Attribut ist bei mir nicht vorhanden.
invert_cover: Inverts the cover position, false: open=100,close=0, true: open=0,close=100 (default false). The value must be true or false
Mit send_payload {
"invert_cover": false
}
hat es auch nicht funktioniert.
Benutze verschiedene Aktoren, das Problem tritt bei allen Modellen.
Nach dem downgrade auf 3.3.5 war alles wieder ok.

Adapter version

3.5.5

Coordinator firmware version

0x26780700

Coordinator

ConBee2/RaspBee2

Setup

Raspi 4

Protocol of the error (as text, encapsulated in multiline code tags <>). Separate different occurrances into clearly split log sections

No response

[asgothian]

Please specify:

– which device is (exact device ID plus link to zigbee2mqtt.io - available from the info display of the adapter)
– Which options are offered on the device tile (see adapter documentation on how to access device options)
– Which ZHC version is installed with the adapter 3.5.5 (available on the coordinator tile of the adapter)
– which ZHC version is installed with the adapter 3.3.5

A.

P.s. see also. https://forum.iobroker.net/topic/85178/nach-update-auf-zigbee-3.5.5-l%C3%A4uft-die-jalousie-falsch-herum?_=1787056569484

[Xerxes55]

Log von Version 3.5.5

2026-08-17 19:11:16.960 - info: zigbee.0 (1710) starting. Version 3.5.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.23.2, js-controller: 7.2.2
--
2026-08-17 19:11:16.989 - info: zigbee.0 (1710) init localConfig
2026-08-17 19:11:17.028 - info: zigbee.0 (1710) Adapter ready - starting subsystems. Adapter is running in info mode.
2026-08-17 19:11:17.069 - warn: zigbee.0 (1710) possible reversed ExtPanID
2026-08-17 19:11:17.177 - info: zigbee.0 (1710) delete old Backup files. keep only last 10
2026-08-17 19:11:17.178 - info: zigbee.0 (1710) Autostart Zigbee subsystem
2026-08-17 19:11:17.180 - info: zigbee.0 (1710) Starting Adapter npm ...
2026-08-17 19:11:17.208 - info: zigbee.0 (1710) Installed Version: iobroker.zigbee@latest (Converters 26.97.0 Herdsman 10.9.0)
2026-08-17 19:11:17.213 - info: zigbee.0 (1710) configured transmit power : normal
2026-08-17 19:11:17.215 - info: zigbee.0 (1710) Starting Zigbee-Herdsman
2026-08-17 19:11:19.255 - info: zigbee.0 (1710) Zigbee-Herdsman started successfully with Coordinator firmware version: ConBee2/RaspBee2 : 0x26780700 (X-X.2.6.120)
2026-08-17 19:11:21.062 - info: zigbee.0 (1710) 65 devices and 1 group are part of the network

Log von Version 3.3.5

2026-08-18 12:07:59.686 - info: zigbee.0 (55945) starting. Version 3.3.5 in /opt/iobroker/node_modules/iobroker.zigbee, node: v22.23.2, js-controller: 7.2.2
--
2026-08-18 12:07:59.717 - info: zigbee.0 (55945) init localConfig
2026-08-18 12:07:59.766 - info: zigbee.0 (55945) Adapter ready - starting subsystems. Adapter is running in info mode.
2026-08-18 12:07:59.939 - info: zigbee.0 (55945) delete old Backup files. keep only last 10
2026-08-18 12:07:59.945 - info: zigbee.0 (55945) Autostart Zigbee subsystem
2026-08-18 12:07:59.947 - info: zigbee.0 (55945) Starting Adapter npm ...
2026-08-18 12:07:59.979 - info: zigbee.0 (55945) Installed Version: iobroker.zigbee@3.3.5 (Converters 25.112.0 Herdsman 8.1.0)
2026-08-18 12:07:59.981 - info: zigbee.0 (55945) configured transmit power : normal
2026-08-18 12:07:59.983 - info: zigbee.0 (55945) Starting Zigbee-Herdsman
2026-08-18 12:08:02.179 - info: zigbee.0 (55945) Zigbee-Herdsman started successfully with Coordinator firmware version: ConBee2/RaspBee2 : 0x26780700 (X-X.2.6.120)
2026-08-18 12:08:03.280 - info: zigbee.0 (55945) 65 devices and 1 group are part of the network

https://www.zigbee2mqtt.io/devices/MS-108ZR.html

https://www.zigbee2mqtt.io/devices/QS-Zigbee-C01.html

[asgothian]

Please provide the list of options provided by the adapter. Do read the documentation as to how to access them - the screenshots provided show a selection of states for the devices, not all states, and none of the options.

Please also test if the options listed on Z2M alter the behaviour in a way that it works for you - and if not, why that is not the case.

A.

[PastCoder]

I am facing proably the same issue.
In iobroker I see the following states:

The behavior is as follows:

• OK: If I use the buttons at the physical device itself, everything is correct: up is up, down is down, stop is stop
• OK: If I set "position, everything is as expected (=as before): 100% is open, 0% is closed, intermediate values are where I would expect the shutter to be.
• NOK: If I set "state" to "CLOSE", the shutter opens. If it is already at 100%, I see shortly "UP" in "state" before "state" changes back to "STOP". If it is at 90% it will got "UP" to 100%

As I did not change anything is my implemenation, I assume that it changed with the update of the adapter to 3.5.5. I think I used 3.5.4 before.

[asgothian]

@PastCoder : This does not seem to be the same device as the one from @Xerxes55.

Please test:

Set the model option reverse_position (see the manual on how to access the model options). No need to restart the adapter. It should fix your problem.

A.

[PastCoder]

Set the model option reverse_position

I just tried that. It does more or less fix my issue. Now I can move the shutter again up and down.
But as the direction is now reversed, I would need to change my existing implementation which worked since many moths without any problem (with the feeling that this changed behavior may change again with the next update).

Do you know if this was an intended change with 3.5.5?

[asgothian]

Do you know if this was an intended change with 3.5.5?

Yes, I know that it was not an intended change. It was actually no change in the zigbee adapter at all, but in the Zigbee-Herdsman-Converters Library. I have not been able to identify the exact change in the library due to lack of access to my development system, as well as lack of information from affected people. So far, I know of 5 people with approx. 6 different devices which show different behaviour (possibly more).

I have obtained debug logs from one user and one device (see here)

What I need:

• set the device in device_debug
• perform one action
• note which action and what the reaction of the attached hardware is (that's what I cant see from the data)
• check the debug tab of the zigbee Adapter (possibly reload data for the debug tab)
• Obtain the detail logs (as text) from the relevant entries on the debug tab. In the linked example, there is one section of logs which ends with 0 converters for .... That is an example for an entry which is most likely irrelevant.
• Post the combination (Action, Result, Log-Data) as one 'Package'.

Repeat this for a number of actions (e.g.: open by pressing a hardware button, open by changing a state, move by changing position, .....)

The documentation on how to read the device_debug Data and how to best obtain the detail logs is here: https://github.com/ioBroker/ioBroker.zigbee/wiki/Device-messaging-debug

As I see it, the changes are collateral damage of the ZHC / ZH team refactoring code and trying to unify code. It probably works well for some devices, but seems not to work so well for all of them.

A.

[PastCoder]

Here my first data. For further use cases I have to wait some time not to anoy my neighbors in the morning.
The device type is recognized as Tuya TS130F.

Use case: The adapter "shuttercontrol" did move the shutter up (by setting the position state). This is a case where everything works as expected.

Messages from 08:31:15 for device 0x000d6ffffed7b5f7

- O01: User state change of state zigbee.0.000d6ffffed7b5f7.position with value 100 (ack: false) from system.adapter.shuttercontrol.0
- O02: Change state 'position' at device 'RollladenLinks (0x000d6ffffed7b5f7)' type 'TS130F'
- O03: Publishing to 'RollladenLinks (0x000d6ffffed7b5f7)' of model TS130F with position
- Os4.0: Setting' converter to converter with key(s)'["position","tilt"]}
- O04: convert position with value 100 and options {} for device 'RollladenLinks (0x000d6ffffed7b5f7)' without Endpoint
- O05: Attempt 1 at converting data for position with preparedValue 100, meta.state {}, meta.message {"position":100}
- SUCCESS: convert result {"state":{"position":100}} for device 'RollladenLinks (0x000d6ffffed7b5f7)'

Messages from 08:31:15 for device 0x000d6ffffed7b5f7

- I01: Zigbee Event of Type attributeReport from device 'RollladenLinks (0x000d6ffffed7b5f7)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":0,"tuyaMovingState":0},"linkquality":255,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[24,6,10,8,0,32,0,0,240,48,0]},"zclTransactionSequenceNumber":6,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
- I04: value generated '255' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Link quality'
- I02: 3 converters available for 'TS130F' 'RollladenLinks (000d6ffffed7b5f7)' with cluster 'closuresWindowCovering' and type 'attributeReport'
- I02.1a: converter 1 : Cluster closuresWindowCovering
- I02.0b: data: {"currentPositionLiftPercentage":0,"tuyaMovingState":0} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"position":0,"state":"CLOSE"}
- I02.2a: converter 2 : Cluster closuresWindowCovering
- I02.1b: data: {"currentPositionLiftPercentage":0,"tuyaMovingState":0} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"moving":"UP"}
- I02.3a: converter 3 : Cluster closuresWindowCovering
- I02.2b: data: {"currentPositionLiftPercentage":0,"tuyaMovingState":0} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:undefined
- I02.3c: candidates: [{"position":0,"state":"CLOSE"},{"moving":"UP"},{}] => payload {"position":0,"state":"CLOSE","moving":"UP"}
- I03: message received '{"position":0,"state":"CLOSE","moving":"UP"}' from device 'RollladenLinks (000d6ffffed7b5f7)' type 'TS130F'
- I04-1: value generated 'CLOSE' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'state'
- I04-2: value generated '0' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Position of this cover'
- I04-3: value generated 'UP' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'moving'

Messages from 08:31:50 for device 0x000d6ffffed7b5f7

- I01: Zigbee Event of Type attributeReport from device 'RollladenLinks (0x000d6ffffed7b5f7)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":100,"tuyaMovingState":1},"linkquality":255,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[8,7,10,8,0,32,100,0,240,48,1]},"zclTransactionSequenceNumber":7,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
- I04: value generated '255' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Link quality'
- I02: 3 converters available for 'TS130F' 'RollladenLinks (000d6ffffed7b5f7)' with cluster 'closuresWindowCovering' and type 'attributeReport'
- I02.1a: converter 1 : Cluster closuresWindowCovering
- I02.0b: data: {"currentPositionLiftPercentage":100,"tuyaMovingState":1} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"position":100,"state":"OPEN"}
- I02.2a: converter 2 : Cluster closuresWindowCovering
- I02.1b: data: {"currentPositionLiftPercentage":100,"tuyaMovingState":1} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"moving":"STOP"}
- I02.3a: converter 3 : Cluster closuresWindowCovering
- I02.2b: data: {"currentPositionLiftPercentage":100,"tuyaMovingState":1} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:undefined
- I02.3c: candidates: [{"position":100,"state":"OPEN"},{"moving":"STOP"},{}] => payload {"position":100,"state":"OPEN","moving":"STOP"}
- I03: message received '{"position":100,"state":"OPEN","moving":"STOP"}' from device 'RollladenLinks (000d6ffffed7b5f7)' type 'TS130F'
- I04-1: value generated 'OPEN' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'state'
- I04-2: value generated '100' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Position of this cover'
- I04-3: value generated 'STOP' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'moving'

Additional entry in the iorboker log (if relevant):
ELEVATED:NOCONV (7128) No converter available for 'TS130F' 'RollladenLinks (000d6ffffed7b5f7)' with cluster 'genBasic' and type 'attributeReporR’

MOD-EDIT: code tags. Please copy the tags from the dialog in iobroker, they are present there.

A.

[PastCoder]

Sorry for the delay.
Here the second case: Press physical down button at the switch, shutter moves down push physical stop button, shutter stops.
This is also a case where everything works as expected.

Messages from 17:53:25 for device 0x000d6ffffed7b5f7

I01: Zigbee Event of Type attributeReport from device 'RollladenLinks (0x000d6ffffed7b5f7)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":100,"tuyaMovingState":2},"linkquality":255,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[8,80,10,8,0,32,100,0,240,48,2]},"zclTransactionSequenceNumber":80,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
I04: value generated '255' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Link quality'
I02: 3 converters available for 'TS130F' 'RollladenLinks (000d6ffffed7b5f7)' with cluster 'closuresWindowCovering' and type 'attributeReport'
I02.1a: converter 1 : Cluster closuresWindowCovering
I02.0b: data: {"currentPositionLiftPercentage":100,"tuyaMovingState":2} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"position":100,"state":"OPEN"}
I02.2a: converter 2 : Cluster closuresWindowCovering
I02.1b: data: {"currentPositionLiftPercentage":100,"tuyaMovingState":2} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"moving":"DOWN"}
I02.3a: converter 3 : Cluster closuresWindowCovering
I02.2b: data: {"currentPositionLiftPercentage":100,"tuyaMovingState":2} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:undefined
I02.3c: candidates: [{"position":100,"state":"OPEN"},{"moving":"DOWN"},{}] => payload {"position":100,"state":"OPEN","moving":"DOWN"}
I03: message received '{"position":100,"state":"OPEN","moving":"DOWN"}' from device 'RollladenLinks (000d6ffffed7b5f7)' type 'TS130F'
I04-1: value generated 'OPEN' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'state'
I04-2: value generated '100' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Position of this cover'
I04-3: value generated 'DOWN' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'moving'

Messages from 17:53:30 for device 0x000d6ffffed7b5f7

I01: Zigbee Event of Type attributeReport from device 'RollladenLinks (0x000d6ffffed7b5f7)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":85,"tuyaMovingState":1},"linkquality":255,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[8,81,10,8,0,32,85,0,240,48,1]},"zclTransactionSequenceNumber":81,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
I04: value generated '255' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Link quality'
I02: 3 converters available for 'TS130F' 'RollladenLinks (000d6ffffed7b5f7)' with cluster 'closuresWindowCovering' and type 'attributeReport'
I02.1a: converter 1 : Cluster closuresWindowCovering
I02.0b: data: {"currentPositionLiftPercentage":85,"tuyaMovingState":1} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"position":85,"state":"OPEN"}
I02.2a: converter 2 : Cluster closuresWindowCovering
I02.1b: data: {"currentPositionLiftPercentage":85,"tuyaMovingState":1} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"moving":"STOP"}
I02.3a: converter 3 : Cluster closuresWindowCovering
I02.2b: data: {"currentPositionLiftPercentage":85,"tuyaMovingState":1} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:undefined
I02.3c: candidates: [{"position":85,"state":"OPEN"},{"moving":"STOP"},{}] => payload {"position":85,"state":"OPEN","moving":"STOP"}
I03: message received '{"position":85,"state":"OPEN","moving":"STOP"}' from device 'RollladenLinks (000d6ffffed7b5f7)' type 'TS130F'
I04-1: value generated 'OPEN' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'state'
I04-2: value generated '85' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Position of this cover'
I04-3: value generated 'STOP' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'moving'

[PastCoder]

And the case NOT working as exptected: Setting the object "zigbee.0.000d6ffffed7b5f7.state" to "CLOSE".

Messages from 17:58:34 for device 0x000d6ffffed7b5f7

O01: User state change of state zigbee.0.000d6ffffed7b5f7.state with value CLOSE (ack: false) from system.adapter.admin.0
O02: Change state 'state' at device 'RollladenLinks (0x000d6ffffed7b5f7)' type 'TS130F'
O03: Publishing to 'RollladenLinks (0x000d6ffffed7b5f7)' of model TS130F with state
Os4.0: Setting' converter to converter with key(s)'["state"]}
O04: convert state with value "CLOSE" and options {} for device 'RollladenLinks (0x000d6ffffed7b5f7)' without Endpoint
O05: Attempt 1 at converting data for state with preparedValue "CLOSE", meta.state {}, meta.message {"state":"CLOSE"}
SUCCESS: convert result undefined for device 'RollladenLinks (0x000d6ffffed7b5f7)'
O06: Convert does not return a result result for state with CLOSE on device 'RollladenLinks (0x000d6ffffed7b5f7)'.

Messages from 17:58:34 for device 0x000d6ffffed7b5f7

I01: Zigbee Event of Type attributeReport from device 'RollladenLinks (0x000d6ffffed7b5f7)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":85,"tuyaMovingState":0},"linkquality":255,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[24,83,10,8,0,32,85,0,240,48,0]},"zclTransactionSequenceNumber":83,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":true,"reservedBits":0}},"endpoint_id":1}
I04: value generated '255' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Link quality'
I02: 3 converters available for 'TS130F' 'RollladenLinks (000d6ffffed7b5f7)' with cluster 'closuresWindowCovering' and type 'attributeReport'
I02.1a: converter 1 : Cluster closuresWindowCovering
I02.0b: data: {"currentPositionLiftPercentage":85,"tuyaMovingState":0} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"position":85,"state":"OPEN"}
I02.2a: converter 2 : Cluster closuresWindowCovering
I02.1b: data: {"currentPositionLiftPercentage":85,"tuyaMovingState":0} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"moving":"UP"}
I02.3a: converter 3 : Cluster closuresWindowCovering
I02.2b: data: {"currentPositionLiftPercentage":85,"tuyaMovingState":0} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:undefined
I02.3c: candidates: [{"position":85,"state":"OPEN"},{"moving":"UP"},{}] => payload {"position":85,"state":"OPEN","moving":"UP"}
I03: message received '{"position":85,"state":"OPEN","moving":"UP"}' from device 'RollladenLinks (000d6ffffed7b5f7)' type 'TS130F'
I04-1: value generated 'OPEN' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'state'
I04-2: value generated '85' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Position of this cover'
I04-3: value generated 'UP' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'moving'

Messages from 17:58:40 for device 0x000d6ffffed7b5f7

I01: Zigbee Event of Type attributeReport from device 'RollladenLinks (0x000d6ffffed7b5f7)', incoming event: {"type":"attributeReport","data":{"currentPositionLiftPercentage":100,"tuyaMovingState":1},"linkquality":255,"groupID":0,"cluster":"closuresWindowCovering","meta":{"rawData":{"type":"Buffer","data":[8,84,10,8,0,32,100,0,240,48,1]},"zclTransactionSequenceNumber":84,"frameControl":{"frameType":0,"manufacturerSpecific":false,"direction":1,"disableDefaultResponse":false,"reservedBits":0}},"endpoint_id":1}
I04: value generated '255' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Link quality'
I02: 3 converters available for 'TS130F' 'RollladenLinks (000d6ffffed7b5f7)' with cluster 'closuresWindowCovering' and type 'attributeReport'
I02.1a: converter 1 : Cluster closuresWindowCovering
I02.0b: data: {"currentPositionLiftPercentage":100,"tuyaMovingState":1} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"position":100,"state":"OPEN"}
I02.2a: converter 2 : Cluster closuresWindowCovering
I02.1b: data: {"currentPositionLiftPercentage":100,"tuyaMovingState":1} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:{"moving":"STOP"}
I02.3a: converter 3 : Cluster closuresWindowCovering
I02.2b: data: {"currentPositionLiftPercentage":100,"tuyaMovingState":1} options: {} meta:{"deviceIEEE":"0x000d6ffffed7b5f7","logger":"StatesController","state":{"state":""}} result:undefined
I02.3c: candidates: [{"position":100,"state":"OPEN"},{"moving":"STOP"},{}] => payload {"position":100,"state":"OPEN","moving":"STOP"}
I03: message received '{"position":100,"state":"OPEN","moving":"STOP"}' from device 'RollladenLinks (000d6ffffed7b5f7)' type 'TS130F'
I04-1: value generated 'OPEN' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'state'
I04-2: value generated '100' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'Position of this cover'
I04-3: value generated 'STOP' from device 'RollladenLinks (000d6ffffed7b5f7)' for 'moving'

[atifan]

Habe das genau das gleiche Problem. Seit Update des Zigbee Adapters im Iobroker sind die Fahrtrichtungen meiner Zigbee Jalousie-Aktoren verdreht, d.h. wenn ich nach unten fahren möchte fährt er nach oben und umgekehrt. Habe es nun kurzfristig so gelöst, dass ich die Bewegungsrichtung invertiert habe (über motor_reversal Häkchen am Aktor)

MOES MS-108ZR

Log für hochfahren des Rollladens
HOCHFAHREN.txt

Log für runterfahren des Rollladens
RUNTERFAHREN.txt

[asgothian]

Habe das genau das gleiche Problem. Seit Update des Zigbee Adapters im Iobroker sind die Fahrtrichtungen meiner Zigbee Jalousie-Aktoren verdreht, d.h. wenn ich nach unten fahren möchte fährt er nach oben und umgekehrt. Habe es nun kurzfristig so gelöst, dass ich die Bewegungsrichtung invertiert habe (über motor_reversal Häkchen am Aktor)

Log für hochfahren des Rollladens HOCHFAHREN.txt

Log für runterfahren des Rollladens RUNTERFAHREN.txt

Please filter / generate the data as requested (and shown in the posts above). This may sound silly, but parsing separate log files for the data I need adds additional workload to an already full table.

A.

[atifan]

Hallo, ich weiß nicht ob es was zu bedeuten hat, aber ich habe eben mein IoBroker von NPM 22 auf NPM 24 geupdatet. Seit dem ist die Richtung der Rollladen wieder umgekehrt, d.h. ich musste das INVERT Rückgängig machen damit sie wieder richtig rum funktionieren. Bin nicht 100% sicher ob es mit dem NPM Update zusammenhängt, da ich mein IoBroker komplett neu von LXC auf VM umgezogen habe, aber ich vermute dass es damit zusammenhängt. Wollte das nur mitteilen.

[asgothian]

Hallo, ich weiß nicht ob es was zu bedeuten hat, aber ich habe eben mein IoBroker von NPM 22 auf NPM 24 geupdatet. Seit dem ist die Richtung der Rollladen wieder umgekehrt, d.h. ich musste das INVERT Rückgängig machen damit sie wieder richtig rum funktionieren. Bin nicht 100% sicher ob es mit dem NPM Update zusammenhängt, da ich mein IoBroker komplett neu von LXC auf VM umgezogen habe, aber ich vermute dass es damit zusammenhängt. Wollte das nur mitteilen.

I assume that you updated to Node 24 - NPM 24 has not passed version 12 yet.

@PastCoder @Xerxes55 @agross - which node version are you running, and if you update to Node 24, does the behaviour change ?

A.

[atifan]

@asgothian yes sorry, i mean NodeJS24. I Updated from NodeJS22 to NodeJS24.