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

Impossible to use a Tuya cover (smart life) in a card. #5664

Closed
sidwin9 opened this issue Apr 29, 2020 · 10 comments · Fixed by #5687
Closed

Impossible to use a Tuya cover (smart life) in a card. #5664

sidwin9 opened this issue Apr 29, 2020 · 10 comments · Fixed by #5687
Assignees
Labels
Bug Current Bug in UI - Extra Attention

Comments

@sidwin9
Copy link

sidwin9 commented Apr 29, 2020

The request

My cover Smart Life is no longer usable in a map, the states do not update and the open and close buttons cannot be used since the update to version 0.109.0.
This problem is caused by the fact that when my switch turns off the power a few seconds after an action, the state changes to unknown. Another problem, if I press Stop, I no longer have the 2 possibilities to go up or down, I only have one possibility, up or down.
image

The alternatives

You must reset the functionality as before in version 0.108.x

Additional information

The cover states in the database are correct and update and the use of the cover.open_cover and cover.close_cover services are working properly.

@sidwin9 sidwin9 added the Feature Request Should be a discussion label Apr 29, 2020
@bramkragten
Copy link
Member

Please share the states + a screenshot at the moment you believe the UI is not right.

@sidwin9
Copy link
Author

sidwin9 commented Apr 30, 2020

Hello,

Unknown state after automatic shutdown of the blind power supply after a few seconds. No action possible
image

After pressing stop after partial opening of the blind, only one action possible
image

I didn't have this problem with previous versions of Home Assistant

@sidwin9
Copy link
Author

sidwin9 commented Apr 30, 2020

I got around the problem with a template cover, but that does not solve the problem of a single possibility after a stop

- platform: template
covers:
store_terrasse:
friendly_name: "Store Terrasse"
open_cover:
service: script.1588234357264
close_cover:
service: script.1588234416379
stop_cover:
service: script.1588234488607
value_template: >-
{% if is_state('cover.328214383c71bf312919', 'open') %}open
{% elif is_state('cover.328214383c71bf312919', 'closed') %}closed
{% else %}{{ states('sensor.store_terrasse_state') }}
{% endif %}

@bramkragten
Copy link
Member

Please share the states from /developer-tools/state especially for the stop case.

@bramkragten bramkragten added Bug Current Bug in UI - Extra Attention and removed Feature Request Should be a discussion labels May 1, 2020
@bramkragten bramkragten self-assigned this May 1, 2020
@sidwin9
Copy link
Author

sidwin9 commented May 1, 2020

See the same topic
home-assistant/core#34942

@sidwin9
Copy link
Author

sidwin9 commented May 1, 2020

Hi,

One click on ↓ and one clic stop after 3 seconds
image
image
If back to version 0.108.9 or 0.108.8 there is no longer this problem, we can click on ↓ and ↑

Exactly the same problem for other users. See the same topic
home-assistant/core#34942

@thimic
Copy link

thimic commented May 1, 2020

I’ve got a similar issue with MQTT covers on 0.109. All buttons are greyed out except the stop buttons that do nothing.

Interestingly, I have a few covers grouped and the groups are fine. Once the blinds have been operated via the group, the blinds in that group become available in the card. Similarly, if I operate a cover by calling a service, that blind becomes available. A restart of Home Assistant will deactivate the individual MQTT blinds in the card once more.

Sample from my config:

- platform: mqtt
  name: "Dixon Street Left"
  command_topic: "home/cover/set"
  payload_open: "{\"name\": \"dixon_l\", \"command\": \"up\"}"
  payload_close: "{\"name\": \"dixon_l\", \"command\": \"down\"}"
  payload_stop: "{\"name\": \"dixon_l\", \"command\": \"stop\"}"
- platform: mqtt
  name: "Dixon Street Right"
  command_topic: "home/cover/set"
  payload_open: "{\"name\": \"dixon_r\", \"command\": \"up\"}"
  payload_close: "{\"name\": \"dixon_r\", \"command\": \"down\"}"
  payload_stop: "{\"name\": \"dixon_r\", \"command\": \"stop\"}"

- platform: group
  name: "Dixon Street"
  entities:
    - cover.dixon_street_left
    - cover.dixon_street_right

What the card looks like when it doesn't let me operate certain blinds:
image

State:
image

State for the group which is working:
image

Seems this occurs when the current state of the cover is unknown? Trouble is, my covers are dumb and communication with them is one way. They never report a state.

@sidwin9
Copy link
Author

sidwin9 commented May 1, 2020

Hi,

I don't have this problem with RFLink covers
image

I have in all situations the possibility of activating ↓ or ↑

@bramkragten
Copy link
Member

The problem is that the state is reported as unknown, that is wrong.

@anthosz
Copy link

anthosz commented May 2, 2020

@bramkragten probably related to home-assistant/core#30112

@github-actions github-actions bot locked and limited conversation to collaborators Jul 6, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Bug Current Bug in UI - Extra Attention
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants