Cover not as expected

[tbloth]

Hey team,

based on motion detection I trigger a scene (lights on, cover down). The three covers I have in that scene move - but one of them into a different direction as expected :-) From the log I find:

2020-05-10 21:06:10 INFO (MainThread) [custom_components.freeathome.pfreeathome] set_datapoint ABB7F59324BE/ch0003 idp0002 100
2020-05-10 21:06:10 INFO (MainThread) [custom_components.freeathome.pfreeathome] set_datapoint ABB7F59323C8/ch0003 idp0002 80
2020-05-10 21:06:10 INFO (MainThread) [custom_components.freeathome.pfreeathome] set_datapoint ABB7F593249C/ch0003 idp0002 70
2020-05-10 21:06:10 INFO (MainThread) [custom_components.freeathome.pfreeathome] method response: True
2020-05-10 21:06:10 INFO (MainThread) [custom_components.freeathome.pfreeathome] method response: True
2020-05-10 21:06:10 INFO (MainThread) [custom_components.freeathome.pfreeathome] method response: True
2020-05-10 21:06:11 INFO (MainThread) [custom_components.freeathome.pfreeathome] device Rollladen Essbereich (ABB7F59324BE/ch0003) is 3
2020-05-10 21:06:11 INFO (MainThread) [custom_components.freeathome.pfreeathome] device Rollladen WZ links (ABB7F59323C8/ch0003) is 2
2020-05-10 21:06:11 INFO (MainThread) [custom_components.freeathome.pfreeathome] device Rollladen WZ rechts (ABB7F593249C/ch0003) is 3

What differs is the second last entry. Device is 2? What does it mean? 3 is down, 2 is up?

The Scene is pretty straight forward:

- id: 'rollos_eg_80'
  name: Rollos EG 80%
  entities:
    cover.rollladen_essbereich:
      current_position: 0
      friendly_name: Essen
      state: open
    cover.rollladen_wz_links:
      current_position: 20
      friendly_name: Rollo WZ links
      state: open
    cover.rollladen_wz_rechts:
      current_position: 30
      friendly_name: Rollo WZ rechts
      state: open

Thanks!

[jheling]

That is a bit strange. Is the a difference in the configuration of these covers? The value 3 indicates the device is closing. And the value 2 indicates the device is opening.

[dvorpahl]

Hey team,

based on motion detection I trigger a scene (lights on, cover down). The three covers I have in that scene move - but one of them into a different direction as expected :-)

hi,

i can confirm some issues with covercontrol depending on scenes. this is definitely no ha/fah issue. example: i am using scene to close my "esszimmer links"-cover at 20pm. i've got a switch to trigger "esszimmer dunkel" scene, this should close both covers (left and right) at once.. but if scene "esszimmer links" is already active, it will always move one of the desired covers in wrong direction .. up/down .. seems to be triggered randomly. i don't know why this foible apear, but it is some malfunction of the SystemAccess Point (in my case sysap2.0). this issue was already there before i connected homeassistant to my system. it is one task for me to find out..