search

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.15k stars 29.83k forks source link

Tuya - Cover - Status never changes #83670

Open anthosz opened 1 year ago

anthosz commented 1 year ago

The problem

When I close/open a cover, The status never change on Tuya entities but the action is well triggered.

It worked well with the custom tuya integration (via HACS) but it's broken since I replaced it by "official" Tuya integration (via 2022.09 update)

To do it: simply removed the old integration & used the tuya integration via the UI (/config/integrations).

Here is an example: image

All status are static since I added this new integration (always closed (icon) even if I open it for several cover and always open (icon) even if I close it for last covers). Status always set to unknow: image

What version of Home Assistant Core has the issue?

2022.09-2022.11.5

What was the last working version of Home Assistant Core?

NC

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Tuya

Link to integration documentation on our website

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

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

Nothing in logs related to that

Additional information

No response

home-assistant[bot] commented 1 year ago

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

Code owner commands Code owners of `tuya` can trigger bot actions by commenting: - `@home-assistant close` Closes the issue. - `@home-assistant rename Awesome new title` Change the title of the issue. - `@home-assistant reopen` Reopen the issue. - `@home-assistant unassign tuya` Removes the current integration label and assignees on the issue, add the integration domain after the command.

(message by CodeOwnersMention)

tuya documentation tuya source (message by IssueLinks)

anthosz commented 1 year ago

HA upgraded to 2022.12 -> same issue

issue-triage-workflows[bot] commented 1 year 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.

anthosz commented 1 year ago

Issue not fixed

anthosz commented 1 year ago

Same issue with 2023.5.2

issue-triage-workflows[bot] commented 1 year 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.

anthosz commented 1 year ago

Issue not fixed

kfir-bar commented 10 months ago

Still not fixed

issue-triage-workflows[bot] commented 7 months 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.

anthosz commented 7 months ago

Issue not fixed at this time

Mike5357 commented 7 months ago

I'm having a similar issue after updating and reauthenticating Tuya. Everything seemed to have been working flawlessly up until this morning, when my automation alerts all started going off that my garage doors were left open (they were not open).

Restarting the integration made HA see the correct state again, but just before I was heading out for work it happened again! The Smart Life app correctly shows them as closed but HomeAssistant is reporting them as open. The controls work in HomeAssistant to open and close them, but the sensor will seemingly randomly switch from appearing as Closed to Open, and when manually reopening and closing the garage through HA the status wont switch to Closed at all until the integration is manually reloaded.

lukelalo commented 5 months ago

Issue not fixed

Mike5357 commented 3 months ago

Issue still persists.

anthosz commented 3 months ago

@frenck maybe you can unassign the ticket if you don't have time to manage it? Cc @zlinoliver?

frenck commented 3 months ago

There is nothing to do. Anyone can pick up. This is an open source project, all integrations are community maintained. I help review the code changes for this integration.

Benon-user commented 3 months ago

I can confirm the issue still exists. The only way around I found is to set up automation in HA to restart Tuya integration every couple minutes.

erickson-brian57 commented 1 month ago

Still broken (or broken again…) It could be fixed but the decision seems to be to leave it broken … home-assistant/core#121731

Benon-user commented 1 month ago

As I see only Mr. @frenck needs to approve this change https://github.com/home-assistant/core/pull/121731.

erickson-brian57 commented 1 month ago

Yes, but I'm not sure he will. It seems like he believes it's not a homeassistant problem.