home-assistant / core

:house_with_garden: Open source home automation that puts local control and privacy first.
https://www.home-assistant.io
Apache License 2.0
71.25k stars 29.86k forks source link

Hunter Dougles powerview Vanes - Close function doens't close tilt. #118330

Open Symbiot78 opened 3 months ago

Symbiot78 commented 3 months ago

The problem

As title. When I click to close the blinds it closes the blinds but is seems to tilt the curtains to the open position.

if the blinds are tilted to open and I click close it will close tilt, then close the blinds then open them to tilted again.

my curtains are vertical, left stack & vertical, right stack..as far as I know anyway.

If I call one of the powerview scenes I created in the powerview app to close one of the curtains then it'll close as expected.

If I open the tilt control I can close the tilt manually.

I see nothing to indicate anything in the logs.

What version of Home Assistant Core has the issue?

core-2024.5.5

What was the last working version of Home Assistant Core?

core-2024.3 or 4

What type of installation are you running?

Home Assistant OS

Integration causing the issue

Hunter Douglas Powerview

Link to integration documentation on our website

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

Diagnostics information

not an error as such.

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

home-assistant[bot] commented 3 months ago

Hey there @bdraco, @kingy444, @trullock, mind taking a look at this issue as it has been labeled with an integration (hunterdouglas_powerview) you are listed as a code owner for? Thanks!

Code owner commands Code owners of `hunterdouglas_powerview` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Renames the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign hunterdouglas_powerview` Removes the current integration label and assignees on the issue, add the integration domain after the command. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

(message by CodeOwnersMention)


hunterdouglas_powerview documentation hunterdouglas_powerview source (message by IssueLinks)

Symbiot78 commented 3 months ago

tried calling the service directly from dev tools. it reacts in the same way. I tried running the service again and it tilts the blinds closed.. then opens it again.

these are the logs:

2024-05-28 22:49:42.443 INFO (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Running websocket_api script 2024-05-28 22:49:42.443 INFO (MainThread) [homeassistant.helpers.script.websocket_api_script] websocket_api script: Executing step call service 2024-05-28 22:49:42.443 DEBUG (MainThread) [homeassistant.components.hunterdouglas_powerview.cover] Estimated time to complete transition of 50 steps for None: 21 2024-05-28 22:49:42.443 DEBUG (MainThread) [homeassistant.components.hunterdouglas_powerview.cover] Move request None: ShadePosition(primary=0, secondary=None, tilt=50, velocity=None) 2024-05-28 22:49:42.443 DEBUG (MainThread) [aiopvapi.resources.shade] Shade KA Alkove move to: ShadePosition(primary=0, secondary=None, tilt=50, velocity=None) 2024-05-28 22:49:42.443 DEBUG (MainThread) [aiopvapi.resources.shade] Structured Data KA Alkove: ShadePosition(primary=0, secondary=None, tilt=50, velocity=None) 2024-05-28 22:49:42.443 DEBUG (MainThread) [aiopvapi.resources.shade] Raw Conversion KA Alkove: {'shade': {'id': 40999, 'positions': {'posKind1': 1, 'position1': 0, 'posKind2': 3, 'position2': 32767}}} 2024-05-28 22:49:42.443 DEBUG (MainThread) [aiopvapi.helpers.aiorequest] Sending PUT request to: http://10.20.10.17/api/shades/40999 params: {} data: {'shade': {'id': 40999, 'positions': {'posKind1': 1, 'position1': 0, 'posKind2': 3, 'position2': 32767}}} timeout: 15 kwargs: {} 2024-05-28 22:49:44.125 DEBUG (MainThread) [aiopvapi.resources.shade] Raw Data KA Alkove: {'id': 40999, 'type': 54, 'capabilities': 4, 'batteryKind': 1, 'smartPowerSupply': {'status': 0, 'id': 0, 'port': 0}, 'batteryStatus': 0, 'batteryStrength': 0, 'roomId': 36806, 'firmware': {'revision': 1, 'subRevision': 8, 'build': 1944}, 'name': 'S0EgQWxrb3Zl', 'signalStrength': 0, 'groupId': 6735, 'motor': {'revision': 50, 'subRevision': 48, 'build': 11826}, 'positions': {'posKind1': 1, 'position1': 0, 'posKind2': 3, 'position2': 32767}, 'timedOut': False} 2024-05-28 22:49:44.125 DEBUG (MainThread) [aiopvapi.resources.shade] Structured Conversion KA Alkove: ShadePosition(primary=0, secondary=None, tilt=50, velocity=None) 2024-05-28 22:49:44.125 DEBUG (MainThread) [homeassistant.components.hunterdouglas_powerview.cover] Move response None: ShadePosition(primary=0, secondary=None, tilt=50, velocity=None)

I also see from the type that mine are registered as Vertical Slats, Left Stack (54) and Vertical Slats, Right Stack (55)

I see the move response showing tilt=50. that might be the issue ? It's not something I see that I can set with the service call?

Symbiot78 commented 3 months ago

If I call the "Cover: Close tilt" service it will close the tilt. but I cannot call the service from the integration directly. It only has a manual tilt function.

kingy444 commented 3 months ago

The close position is defined in the upstream so I'll need to fix it there. I've checked the code and see the issue.

kingy444 commented 3 months ago

@home-assistant add-label "problem in dependency"

issue-triage-workflows[bot] commented 2 weeks ago

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.

kingy444 commented 1 week ago

@home-assistant reopen