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

ewand cover not reporting open/close state correctly through ZHA #93836

Closed
shanelord01 opened this issue May 31, 2023 · 10 comments
Closed

ewand cover not reporting open/close state correctly through ZHA #93836

shanelord01 opened this issue May 31, 2023 · 10 comments

Comments

@shanelord01
Copy link

The problem

I've moved to ZHA from Z2M, and a similar issue was on Z2M but has been resolved as per this thread:

zigbee2mqtt/hassio-zigbee2mqtt#359

Currently the ON/OFF switch is working to open and close these, but the "Cover" state is not updated, and if the Cover open or close controls are used it just states "Opening" or "Closing" and never changes to "Open" or "Closed"

What version of Home Assistant Core has the issue?

core-2023.5.4

What was the last working version of Home Assistant Core?

No response

What type of installation are you running?

Home Assistant OS

Integration causing the issue

ZHA

Link to integration documentation on our website

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

Diagnostics information

config_entry-zha-7b7d9b63988404ad9641a5bae915657a.json.txt

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

@home-assistant
Copy link

Hey there @dmulcahey, @Adminiuga, @puddly, mind taking a look at this issue as it has been labeled with an integration (zha) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of zha 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 zha Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)


zha documentation
zha source
(message by IssueLinks)

@deam0n
Copy link

deam0n commented Jun 13, 2023

Same issue with Ikea Fyrtur... state never goes do open or close until cover.stop service is called.

@oscar-b
Copy link

oscar-b commented Jul 3, 2023

@puddly I'm seeing the same thing for IKEA Tredansen, weirdly enough it seems like it worked before the firmware update that also made the quirk obsolete:

zigpy/zha-device-handlers#2418

Firmware: 0x24040011

{
  "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.EndDevice: 2>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress: 128>, manufacturer_code=4476, maximum_buffer_size=82, maximum_incoming_transfer_size=82, server_mask=11264, maximum_outgoing_transfer_size=82, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=True, *is_full_function_device=False, *is_mains_powered=False, *is_receiver_on_when_idle=False, *is_router=False, *is_security_capable=False)",
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0202",
      "input_clusters": [
        "0x0000",
        "0x0001",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0020",
        "0x0102",
        "0x1000",
        "0xfc7c"
      ],
      "output_clusters": [
        "0x0003",
        "0x0019",
        "0x1000"
      ]
    }
  },
  "manufacturer": "IKEA of Sweden",
  "model": "TREDANSEN block-out cellul blind",
  "class": "zigpy.device.Device"
}

I bought it yesterday, so I'm not entirely sure, but I think it worked properly then on the older firmware. During the night, it updated, and I noticed because the battery % was incorrect and found the bug report above and saw that the only thing (?) the quirk did was double the reported battery.

But, now when moving it with cover.set_cover_position it never stops moving according to HA.

@ktreu01
Copy link

ktreu01 commented Jul 19, 2023

I have the same issue with: FYRTUR block-out roller blind
by IKEA of Sweden. I can operate the blind but when I do open or close, HA always says opening or closing. The position always reports 100.

@shanelord01
Copy link
Author

shanelord01 commented Aug 13, 2023

This issue still remains. Note - there was previously a similar issue in Z2M that was resolved here: zigbee2mqtt/hassio-zigbee2mqtt#359

@fender4645
Copy link
Contributor

Same issue. To narrow it down a bit, if you set the position to either 0% or 100%, the state updates correctly. Anything in between (e.g. 90% open), the state will stay in "Opening" until you put it at either 0% or 100%. A few more details in this community thread: https://community.home-assistant.io/t/opening-closing-state-of-ikea-fyrtur-blind-with-zha-does-not-get-updated/513653

@oscar-b
Copy link

oscar-b commented Aug 13, 2023

More info here as well. There’s just no code for handling it currently, I guess in part that there’s no “desired state” being persisted so that it can be compared against. The only updates the blinds provide is the current position, it’s up to ZHA to decide the state, and it currently has nothing to compare to.

zigpy/zha-device-handlers#2418

@shanelord01
Copy link
Author

Well when the switch for this is set to On, it should reflect as Cover Open state. When the switch is Off it should reflect as Cover Closed state.

@oscar-b
Copy link

oscar-b commented Aug 17, 2023

I don’t know anything about this cover, I use IKEA, but I’d assume it works the same. It sets open/closed when the cover reports the position to either 0 or 100.

@issue-triage-workflows
Copy link

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 issue-triage-workflows bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 22, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Dec 22, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

8 participants