Tuya AM43 Blind Drive Bluetooth (via gateway) remains unavailable

[andreabafile]

The problem

I'm trying to interface a AM43 Tuya Blind Drive Bluetooth which is connected via a Tuya+Zigbee wifi&Bluetooth gateway. Everything is working fine through the Tuya App. In Home Assistant the "cover" entity gets created but remain unavailable. I presume I've done correctly the set-up via Tuya Cloud Development platform, because if I connect other sensors (i.e. vibration sensors) to the hub, I get them working in HA straight away.

Any advice on how to get it work?

Thanks in advance.

What version of Home Assistant Core has the issue?

2024.8.2

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

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?

No response

Additional information

[home-assistant[bot]]

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` Renames 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. - `@home-assistant add-label needs-more-information` Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue. - `@home-assistant remove-label needs-more-information` Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

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

[sunkentreasure]

I have the same issue, and have had it for a long time. (several major versions of HA) i.e. blind present but everything unavailable

I don't know if it's because the blind is BLE controlled? The only way to control it at present is using the Tuya Smart Life app, where it connects directly to the blind via Bluetooth. If the app is used outside the home (over the internet) it doesn't work, it can only be used when in range of the blind itself.

[mcastrigno]

@sunkentreasure Do you have a tuya bluetooth gateway? The only way to get this to work is with a tuya bluetooth gateway. I have tuya Bluetooth "curtains" The title of this issue says (via gateway) but what you describe is connecting with your phone via Bluetooth.

[sunkentreasure]

@mcastrigno Since I posted this, I did purchase a tuya bluetooth gateway (this one: https://www.aliexpress.com/item/1005006437139012.html?spm=a2g0o.order_detail.order_detail_item.3.1ab5f19cvE2nW7) This works, but there are issues with reporting the blind status. It seems to "time out" after a while, when it then stops responding to button presses and responding open % properly . Or it thinks it's open when it's completely closed. However if you use the Developer Mode in HA to call the service, it responds immediately, performs the action, then the blind position is correctly reported.

[mcastrigno]

@sunkentreasure That is very interesting information. Yes, I find the status information unreliable as well. This breaks my automations as they act on status, or more precisely the state attribute, position of the shutter (blind). Have you posted about this in the HA community? If I could find out what the developer mode is doing differently and then emulate it is a script then maybe I could have reliable automations.

[sunkentreasure]

@mcastrigno No i haven't posted about it yet. Yes that sounds like it could work.

[sunkentreasure]

Another point, sometimes when the state is wrong, pressing the "stop" button (which is never greyed out) can revive the correct state, but even then that might take 10 seconds or more to update.