PergolaHorizontalAwning (io:PergolaRailGuidedAwningIOComponent) doesn't provide current_position

[xefil]

The problem

Hello to all, As descrived here https://github.com/iMicknl/ha-tahoma/issues/786 , after moving from HACS integration to che CORE I'm having some problems. So I have disabled the HACS component and installed the integration from HA. What I'm missing now is the position of the current_position attribute. So if I open the device, I have the position bar, and if I slide it to, i.e. 50%, it goes at 50%, but then the position is not reported to HA, so if I reopen the device again, the position is at 100%, because the current_position is missing. The cover / awning remains correctly at 50%. Under the Developer Tools the position of the device is completely missing.

Then opening the device again, the slidebar is again at 0% even if it was moved to 50%.

Ideas?

Thanks,

Simon

What version of Home Assistant Core has the issue?

core-2022.3.0

What was the last working version of Home Assistant Core?

N/A

What type of installation are you running?

Home Assistant Container

Integration causing the issue

overkiz

Link to integration documentation on our website

https://www.home-assistant.io/integrations/overkiz

Diagnostics information

config_entry-overkiz-213f2759e1c37e33e70d8dbce6964c7a.json.txt

Example YAML snippet

---

Anything in the logs that might be useful for us?

---

Additional information

---

[probot-home-assistant[bot]]

overkiz documentation overkiz source _{^{(message by IssueLinks)}}

[probot-home-assistant[bot]]

Hey there @imicknl, @vlebourl, @tetienne, mind taking a look at this issue as it has been labeled with an integration (overkiz) you are listed as a code owner for? Thanks! _{^{(message by CodeOwnersMention)}}

[xefil]

debug.txt

Here an example where I've moved the cover to 50%.

[xefil]

Hello @iMicknl @tetienne any suggestion?

[iMicknl]

@xefil I am currently looking into your issue, but I cannot pin point the issue yet. Which device has the issue? Is this your Awning or PergolaHorizontalAwning?

If it happens only to your PergolaHorizontalAwning, than the issue is that we don't check for the core:DeploymentState.

[xefil]

Hello @iMicknl I've noticed it happens only on the PergolaHorizontalAwning (io:PergolaRailGuidedAwningIOComponent) but it works on PositionableHorizontalAwning (io:HorizontalAwningIOComponent). Is so that expected? Isn't the position information on the PergolaHorizontalAwning component? Thanks, Simon

[iMicknl]

Thanks, this should be a relatively small fix. We will have a look.

Can you perhaps rename your issue title to "PergolaHorizontalAwning (io:PergolaRailGuidedAwningIOComponent) doesn't provide current_position".

[xefil]

Hello @iMicknl , renamed! Let me know if I can help in some tests just in case. Thanks, Simon

[iMicknl]

@xefil can you fully open the cover and fully close the cover, and export the diagnostics file for both? It would be good to understand if it needs to be inverted or not. And since open / closed can be quite ambiguous, would be good to also describe how it looks in real-life :D.

[xefil]

Hi @iMicknl , sorry, let me understand better what I need to do. First of all, my setup: I have a Pergola with 3 motors, controlled by Tahoma V2. The roof is io:PergolaRailGuidedAwningIOComponent (PergolaHorizontalAwning) having entity name in HA cover.tetto_pergola_2. The _2 because moving from HACS to CORE component, has created new entities..... Here I'm having 2 problems: First I cannot set the percent for open and close and the percent is not tracked. Second, in addiction, in this right moment the roof is closed (so no rain/sun enters), but from the device point of view the cover is open. I think because it's streched / unrolled. It's not easy to tell Home Assistant to close the roof pressing an OPEN command. Hope you've understood. To solve this, I've applied an automation reported at the end of my post. The other two components are two window curtains / vertical awning io:HorizontalAwningIOComponent (PositionableHorizontalAwning) having entity name in HA: cover.tenda_piccola_pergol_2 and cover.tenda_grande_pergola_2. Those are recognizing the correct position in percent, but have the same issue related to the OPEN/CLOSE status. If I want to close the vertical awning, I need to press the OPEN button. So, to bypass the inverted status, I've written this scrips:

- platform: template
  covers:
    pergola_tenda_piccola:
      friendly_name: Pergola Tenda Piccola
      position_template: "{{ 100 - (state_attr('cover.tenda_piccola_pergol_2', 'current_position') | int) }}"
      open_cover:
        service: cover.close_cover
        data:
          entity_id: cover.tenda_piccola_pergol_2
      close_cover:
        service: cover.open_cover
        data:
          entity_id: cover.tenda_piccola_pergol_2
      stop_cover:
        service: cover.stop_cover
        data:
          entity_id: cover.tenda_piccola_pergol_2
      set_cover_position:
        service: cover.set_cover_position
        data:
          entity_id: cover.tenda_piccola_pergol_2
          position: "{{ 100 - (position) }}"
    pergola_tenda_grande:
      friendly_name: Pergola Tenda Grande
      position_template: "{{ 100 - (state_attr('cover.tenda_grande_pergola_2', 'current_position') | int) }}"
      open_cover:
        service: cover.close_cover
        data:
          entity_id: cover.tenda_grande_pergola_2
      close_cover:
        service: cover.open_cover
        data:
          entity_id: cover.tenda_grande_pergola_2
      stop_cover:
        service: cover.stop_cover
        data:
          entity_id: cover.tenda_grande_pergola_2
      set_cover_position:
        service: cover.set_cover_position
        data:
          entity_id: cover.tenda_grande_pergola_2
          position: "{{ 100 - (position) }}"
    pergola_tetto:
      friendly_name: Pergola Tetto
      position_template: "{{ 100 - (state_attr('cover.tetto_pergola_2', 'current_position') | int) }}"
      open_cover:
        service: cover.close_cover
        data:
          entity_id: cover.tetto_pergola_2
      close_cover:
        service: cover.open_cover
        data:
          entity_id: cover.tetto_pergola_2
      stop_cover:
        service: cover.stop_cover
        data:
          entity_id: cover.tetto_pergola_2
      set_cover_position:
        service: cover.set_cover_position
        data:
          entity_id: cover.tetto_pergola_2
          position: "{{ 100 - (position) }}"

Great would be if I can set the device type or expected behaviour to avoid havig the above script, but this is only a part of the problem.

So, exactly what should I try? If I press on one of the core components, I know there is the DOWNLOAD DIAGNOSTICS data, but please let me know better what to try.

....and thanks for the component anyway!!! Great job.

Thanks, Simon

[lindemar]

I also recently changed from the HACS to the Overkiz core integration (Home Assistant 2022.12.8). In my case the current_position from the device type PositionableHorizontalAwningUno is permanently reported as 124. Forcing the awning to a specific position (with Node-RED) works as expected. Any advice?

[iMicknl]

@lindemar this is a separate problem, so please create a separate issue.

[iMicknl]

Not stale. Still waiting on rewrite of the cover entity.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.