search

eclipse-archived / smarthome

Eclipse SmartHome™ project
https://www.eclipse.org/smarthome/
Eclipse Public License 2.0
862 stars 787 forks source link

[Homematic] rollershutter position glitch #6867

Closed s0170071 closed 5 years ago

s0170071 commented 5 years ago

I move a rollershutter through Openhab (basicui, rules) from position 15 to 0. There is a glitch in the position / level item. When the shutter starts moving, the position changes from current(15) to destination(0) and back to 15 instantly. When it finishes moving, it correctly shows position 0.

Current Behavior

The log reads: 

2018-09-11 13:58:09.944 [INFO ] [eclipse.smarthome.model.script.myLog] - Fahre Rollo EG_Kueche_Rollo von 15 nach 0
2018-09-11 13:58:09.951 [ome.event.ItemCommandEvent] - Item 'EG_Kueche_Rollo' received command 0
2018-09-11 13:58:09.986 [vent.ItemStateChangedEvent] - EG_Kueche_Rollo changed from 15 to 0
2018-09-11 13:58:10.153 [vent.ItemStateChangedEvent] - EG_Kueche_Rollo changed from 0 to 15
2018-09-11 13:58:10.162 [vent.ItemStateChangedEvent] - EG_Kueche_Rollo_WORKING changed from 0 to 100
2018-09-11 13:58:17.409 [vent.ItemStateChangedEvent] - EG_Kueche_Rollo changed from 15 to 0
2018-09-11 13:58:17.427 [vent.ItemStateChangedEvent] - EG_Kueche_Rollo_WORKING changed from 100 to 0

The same behaviour is observed when using paperui.

Expected Behavior

2018-09-11 13:58:09.944 [INFO ] [eclipse.smarthome.model.script.myLog] - Fahre Rollo EG_Kueche_Rollo von 15 nach 0
2018-09-11 13:58:09.951 [ome.event.ItemCommandEvent] - Item 'EG_Kueche_Rollo' received command 0
2018-09-11 13:58:10.162 [vent.ItemStateChangedEvent] - EG_Kueche_Rollo_WORKING changed from 0 to 100
2018-09-11 13:58:17.409 [vent.ItemStateChangedEvent] - EG_Kueche_Rollo changed from 15 to 0
2018-09-11 13:58:17.427 [vent.ItemStateChangedEvent] - EG_Kueche_Rollo_WORKING changed from 100 to 0

Your Environment

OH 2.3 on RPI 3B using Openhabian.

Probably related: If I move an offline rollershutter the position jumps instantly to the destination value without the shutter moving. It stays there even if it comes back online. A stop command then finally triggers an update of the position value.

s0170071 commented 5 years ago

SOLVED:

an autoupdate="false" after the channel definition fixes this. So this seems to be by design. A working item definition then is:

Rollershutter MyShutter "SomeName" (gGroup) {channel="homematic:HM-LC-Bl1PBU-FM:pivccu:MEQ1606628:1#LEVEL" , autoupdate="false"}