Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Feature request]: ZM25EL update cover state from device after movement #23593

Closed
alexeiw123 opened this issue Aug 12, 2024 · 3 comments
Closed
Labels
feature request Feature request

Comments

@alexeiw123
Copy link

Is your feature request related to a problem? Please describe

When I use the RF remote to move my ZM25EL blinds ( _TZE200_pw7mji0l ), Z2MQTT state for the blind does not update.
When moved from Z2M or HA, the state change initiates the movement, so this issue isn't noticed.

The "position" expose does update, just the state doesn't reflect that.

In this screenshot, both blinds have been opened completely (100% position) from a previous closed position.
Blind 1 was opened from HA. Blind 2 was opened from the physical remote.

image

Describe the solution you'd like

The state of the blind should update to reflect the position after the position has changed.
At present, pressing 'stop' in the UI will cause the state to be correctly reflected in home assistant. I haven't found a way to automate this across all blinds elegantly after the blind is moved externally.

Describe alternatives you've considered

  • workaround in automation - unsuccessful so far
  • external converter - beyond my skill level to incorporate all features
  • PR to existing converter - given number of tuya covers, I'm more likely to break other devices (low skill level)

Additional context

relevant location in code appears to be here: https://github.com/Koenkk/zigbee-herdsman-converters/blob/d28d1994b84aad59c044e3445215fd2d2c77b680/src/devices/tuya.ts#L4285

@alexeiw123 alexeiw123 added the feature request Feature request label Aug 12, 2024
@alexeiw123
Copy link
Author

this feature request is closely related to this issue: #19665

@alexeiw123
Copy link
Author

temporary workaround here: #19665 (comment)

@alexeiw123
Copy link
Author

Fixed in #19665

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request Feature request
Projects
None yet
Development

No branches or pull requests

1 participant