ZHA tuya_moving_state (id: 0xf000) doesn't seem to be used in TS130F rolling shutter module

[darmach]

The problem

When I use GUI arrows to traverse shutter completely to open/closed position, after shutter run completes, HA is aware that the shutter stopped rolling. However, if I traverse shutter to certain position by clicking on position slider, the shutter is stuck in for ex. "opening" state (If the position chosen was higher than starting position). As a result, even if it stopped moving I can't issue another "open / up arrow" command (to let's say open it completely) until I click STOP button on HA gui.

Steps to replicate:

1. Any start position
2. Set target shutter position to any value between 0-100%

• entity state - opening/closing
• tuya_moving_state (id: 0xf000) - value 0 / 2
• shutter traverses, reaches position and stops

4. Arrow is greyed out:

• HA still thinks shutter is moving
• Entity state is still either opening or closing.
• tuya_moving_state (id: 0xf000) value is correct - 1 (stopped)

5. Have to press STOP button to issue another command

I checked tuya_moving_state (id: 0xf000) in cluster management and it seems that this attribute in the module has correct values - 0, 1, 2 for up/stopped/down movement. Is that attribute actually used?

What version of Home Assistant Core has the issue?

core-2022.7.7

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

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

No response

Additional information

No response

[probot-home-assistant]

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!
_{^{(message by CodeOwnersMention)}}

---

zha documentation
zha source
_{^{(message by IssueLinks)}}

[galambert75]

I'm experiencing the same behavior. Running:

• Home Assistant 2022.9.0
• Supervisor 2022.08.6
• Operating System 8.5
• Frontend 20220907.0 - latest

[hugosoares]

Same issue with my device "TS130F by _TZ3000_zirycpws"

don't know if it helps but I found similar issues on zigbee2mqtt support forum:
Koenkk/zigbee2mqtt#11539

This is my device:
https://zigbee.blakadder.com/Tuya_QS-Zigbee-CP03.html

Device signature:
{ "node_descriptor": "NodeDescriptor(logical_type=<LogicalType.Router: 1>, complex_descriptor_available=0, user_descriptor_available=0, reserved=0, aps_flags=0, frequency_band=<FrequencyBand.Freq2400MHz: 8>, mac_capability_flags=<MACCapabilityFlags.AllocateAddress|RxOnWhenIdle|MainsPowered|FullFunctionDevice: 142>, manufacturer_code=4417, maximum_buffer_size=66, maximum_incoming_transfer_size=66, server_mask=10752, maximum_outgoing_transfer_size=66, descriptor_capability_field=<DescriptorCapability.NONE: 0>, *allocate_address=True, *is_alternate_pan_coordinator=False, *is_coordinator=False, *is_end_device=False, *is_full_function_device=True, *is_mains_powered=True, *is_receiver_on_when_idle=True, *is_router=True, *is_security_capable=False)", "endpoints": { "1": { "profile_id": 260, "device_type": "0x0202", "in_clusters": [ "0x0000", "0x0004", "0x0005", "0x0006", "0x0102" ], "out_clusters": [ "0x000a", "0x0019" ] }, "242": { "profile_id": 41440, "device_type": "0x0061", "in_clusters": [], "out_clusters": [ "0x0021" ] } }, "manufacturer": "_TZ3000_zirycpws", "model": "TS130F", "class": "zhaquirks.tuya.ts130f.TuyaTS130GP" }

Diagnostics file:
zha-01ac3cfafbeee245da2520e6edca1b6d-_TZ3000_zirycpws TS130F-d6ef290649adaeda5328636cefcae130.json (1).txt

[github-actions]

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.

[darmach]

Oh, how I hate those bots... This issue still persist

[jasimancas]

I have the same error, in fact it happens to me when I use Google Home, I tell it to open a % and it keeps opening "eternally" although it really marks the percentage, but I have to press STOP to act on the device again.

[issue-triage-workflows]

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.

[darmach]

Looks like the issue still persists, bump.

[issue-triage-workflows]

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.

[darmach]

Bump, newest HA, issue still persist.

[issue-triage-workflows]

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.

[BenPru]

Bump, newest HA, issue still persist.

[issue-triage-workflows]

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.

[darmach]

Bump, newest HA, issue still persist

[issue-triage-workflows]

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.

[darmach]

Bump

[SassoGrieco]

Problema di apertura e chiusura, ogni qual volta si effettua un'azione la stessa non viene mai completata allo stesso modo. A volte si onterrompe prima a volte si interrompere dopo.