Curtain Status stuck on opening or closing

[edmarts]

I have a problem with the curtains (Zemismart).

In the homebridge they always appear as if they have 50%, even though they are already open. When I click, it appears as 100% open. (image 1)

In the homekit it appears as closed and with the spin thinking. I have to click on it to appear as open, but it is already open. (image 2)

[milo526]

Good catch, thanks for the report!

Could you add the api output as requested in the issue template? Then I'll look into it after the holidays

[adspen]

Hello - the curtain device is VERY welcome - thank you!

However, I think I have the same (similar?) issue. When the curtains are open, the switch in HomeKit shows 'Open' but when they are closed, the switch endlessly shows as 'Closing'.

Thanks.

[siim911]

same here, if also include percentage control it will be much welcomed Now only open and close

thanks.

[milo526]

Hello, could you please trying installing the latest pre-release version and see if that fixes the problem for you.

How to install a pre-release version. Logically do this for the @milo526/homebridge-tuya-web or TuyaWebPlatform plugin. You should be able to install version v0.8.0-0. Please let me know how that works for you!

[adspen]

Hi Milo

I've installed the pre-release version and can confirm that this now appears to be fixed, for me at least. Many thanks!

[edmarts]

I upgraded to version v0.7.1 and it always appears to me that the curtain is open now. I click the button to close, but after a while the button appears as open.

[milo526]

@edmarts cool, but how about the pre-release? 😛 you will need to install version v0.8.0-0 to test the latest changes. See instructions above on how to install these.

[mattlukc]

After installing the pre-release v0.8.0-0, in Homekit my 3 roller shade covers are showing either (Closing...) when the shades are already closed, or (Opening...) when the shades are already open.

If the Shades are closed and I close out of and reopen Homekit, the (Closing...) status automatically changes to (Opening...). Below is the log right after restarting Homekit. Maybe it will help?

[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 3] - Creating new debounced promise
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 3] - Triggering debouncedDeviceStateRequest
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 3] - Requesting device state
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 3] - Triggering debouncedDeviceStateRequest
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 2] - Requesting device state
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 2] - Creating new debounced promise
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 2] - Triggering debouncedDeviceStateRequest
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 2] - Requesting device state
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 2] - Triggering debouncedDeviceStateRequest
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 1] - Requesting device state
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 1] - Creating new debounced promise
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 1] - Triggering debouncedDeviceStateRequest
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 1] - Requesting device state
[1/5/2021, 8:46:25 PM] [TuyaWebPlatform] [Shade 1] - Triggering debouncedDeviceStateRequest
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 3] - Unsetting debouncedDeviceStateRequestPromise
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 3] - Resolving resolveDeviceStateRequest from cache
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 3] Characteristic.CurrentPosition - [GET] 1
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 3] Characteristic.CurrentPosition - Updating value { support_stop: true, online: true, state: 1, target_cover_state: 2 }
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 3] Characteristic.TargetPosition - [GET] 1
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 2] - Unsetting debouncedDeviceStateRequestPromise
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 2] - Resolving resolveDeviceStateRequest from cache
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 2] Characteristic.TargetPosition - [GET] 1
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 2] Characteristic.CurrentPosition - [GET] 1
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 2] Characteristic.CurrentPosition - Updating value { support_stop: true, online: true, state: 1, target_cover_state: 2 }
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 1] - Unsetting debouncedDeviceStateRequestPromise
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 1] - Resolving resolveDeviceStateRequest from cache
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 1] Characteristic.TargetPosition - [GET] 2
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 1] Characteristic.CurrentPosition - [GET] 2
[1/5/2021, 8:46:26 PM] [TuyaWebPlatform] [Shade 1] Characteristic.CurrentPosition - Updating value { support_stop: true, online: true, state: 2, target_cover_state: 2 } 

Also in homebridge it shows the shade accessory at 50% open.

[milo526]

If you open the Home app 15 minutes after you closed the roller shades, do they still show as closing? Or are they then properly shown as closed?

[adspen]

Hi, I think I might have spoken too soon on my previous message. As far as I can tell, the button now performs correctly when I press it manually in the HomeKit app (which it didn't previously), however if the curtains are closed by a HomeKit automation (as happens for me every evening) it still seems to stick at 'Closing...' indefinately (though the curtains do physically close properly).

I will keep an eye on it again and report if this was just a blip for some reason the last time the automation ran.

[mattlukc]

If you open the Home app 15 minutes after you closed the roller shades, do they still show as closing? Or are they then properly shown as closed?

It is never ending for me.

[taaa22]

Me too 😔

[rulez86]

Using this device: https://www.ebay.de/itm/Wifi-Vorhang-Rolll%C3%A4den-Shutter-Switch-Modul-Sprachsteuerung-F%C3%BCr-Alexa-Google/333591455203?ssPageName=STRK%3AMEBIDX%3AIT&_trksid=p2057872.m2749.l2649

Hello, unfortunetelly, i have same issue. What i did is:

1. Upgrade to 0.8.0.0
2. Try closing / opening curtain by tuya app, works fine State: closed
3. switch to homebridge plugin and try to adapt status to closed, because there it was open for some reason
4. So, both, tuya app and homebridge plugin has status closed
5. Try to open curtain with homebridge plugin, unfortunately no reaction, just "opening..." for a few minutes, then switch back to status "closed"

Means, i can not control the curtain. For some reason when i press the button in homekit multiple times, the curtain will open. But this is more or less coincidence.

Any idea about that? Here is some output of my protocol:

[7.1.2021, 08:33:04] [TuyaWebPlatform] [Vorhangschalter] - Unsetting debouncedDeviceStateRequestPromise [7.1.2021, 08:33:04] [TuyaWebPlatform] [Vorhangschalter] - Resolving resolveDeviceStateRequest from cache [7.1.2021, 08:33:04] [TuyaWebPlatform] [Vorhangschalter] Characteristic.CurrentPosition - [GET] 1 [7.1.2021, 08:33:04] [TuyaWebPlatform] [Vorhangschalter] Characteristic.CurrentPosition - Updating value { online: true, state: 1, target_cover_state: 1 } [7.1.2021, 08:33:04] [TuyaWebPlatform] [Vorhangschalter] Characteristic.TargetPosition - [GET] 1 [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] - Requesting device state [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] - Creating new debounced promise [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] - Triggering debouncedDeviceStateRequest [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] - Requesting device state [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] - Triggering debouncedDeviceStateRequest [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] Characteristic.PositionState - Setting position state to stopped [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] - Unsetting debouncedDeviceStateRequestPromise [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] - Resolving resolveDeviceStateRequest from cache [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] Characteristic.CurrentPosition - [GET] 1 [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] Characteristic.CurrentPosition - Updating value { online: true, state: 1, target_cover_state: 1 } [7.1.2021, 08:33:06] [TuyaWebPlatform] [Vorhangschalter] Characteristic.TargetPosition - [GET] 1 [7.1.2021, 08:33:09] [TuyaWebPlatform] [Vorhangschalter] - Requesting device state [7.1.2021, 08:33:09] [TuyaWebPlatform] [Vorhangschalter] - Creating new debounced promise [7.1.2021, 08:33:09] [TuyaWebPlatform] [Vorhangschalter] - Triggering debouncedDeviceStateRequest [7.1.2021, 08:33:09] [TuyaWebPlatform] [Vorhangschalter] - Requesting device state [7.1.2021, 08:33:09] [TuyaWebPlatform] [Vorhangschalter] - Triggering debouncedDeviceStateRequest [7.1.2021, 08:33:09] [TuyaWebPlatform] [Vorhangschalter] Characteristic.PositionState - Setting position state to stopped [7.1.2021, 08:33:10] [TuyaWebPlatform] [Vorhangschalter] - Unsetting debouncedDeviceStateRequestPromise [7.1.2021, 08:33:10] [TuyaWebPlatform] [Vorhangschalter] - Resolving resolveDeviceStateRequest from cache [7.1.2021, 08:33:10] [TuyaWebPlatform] [Vorhangschalter] Characteristic.CurrentPosition - [GET] 1 [7.1.2021, 08:33:10] [TuyaWebPlatform] [Vorhangschalter] Characteristic.CurrentPosition - Updating value { online: true, state: 1, target_cover_state: 1 } [7.1.2021, 08:33:10] [TuyaWebPlatform] [Vorhangschalter] Characteristic.TargetPosition - [GET] 1 [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] - Requesting device state [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] - Creating new debounced promise [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] - Triggering debouncedDeviceStateRequest [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] - Requesting device state [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] - Triggering debouncedDeviceStateRequest [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] - Unsetting debouncedDeviceStateRequestPromise [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] - Resolving resolveDeviceStateRequest from remote [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] - Set device state request cache [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] Characteristic.CurrentPosition - [GET] false [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] Characteristic.CurrentPosition - Updating value { online: true, state: false } [7.1.2021, 08:34:46] [TuyaWebPlatform] [Vorhangschalter] Characteristic.TargetPosition - [GET] false

[edmarts]

@edmarts cool, but how about the pre-release? 😛 you will need to install version v0.8.0-0 to test the latest changes. See instructions above on how to install these.

I installed the version v0.8.0-0 but the issue still.

In version v0.7.1, one of the curtains always appears as open and the other always appears as closed, but in version v0.8.0-0 the curtains still showing the message "opening" or "closing" or if they are open show "50% opened" ... the v0.7.1 is more stable

[milo526]

So I don't know what is wrong here, since I don't yet own a Tuya cover device, it is hard for me to debug this.

I will put this issue "on-hold" until I acquire such a device or somebody is able to fix this through a pull-request.

[rulez86]

Would it be possible to provide such a device so that you can implement this?

[milo526]

That is always an option (and a very welcome one), however in this case it is an option that is already put in motion. Somebody else told me that the sent a cover device my way, however I do not have any tracking codes so I don't know when it will arrive.

If this plugin helps you and you want to ensure its continued development you are very welcome to donate, see the donation options on the homepage. The donations help me get some time in which I can work on the plugin and help me buy new devices to implement.

[alanit0]

Hey

Same problem :-(

[rulez86]

Hey

Same problem :-(

@alanit0 Which model of device do you have?

[AnonymousPea]

UPDATE: Never mind about 10 minutes later they are back to saying closing. So I was having the same issue. Where it would constantly be loading as closing when I hit close, even though the blinds were closed. I updated to the newer vision and had the issue others where having where it was always "closing" or "opening" and never just opened on closed. So I went back to v0.7. Although today, it seems to have solved it's self. All I have changed was adding another one of the blind controllers to my set-up I have even tested this via an automation, and all working well. This is on v0.7

[serial8killer]

Hey guys. So just trying to help, I have at the moment 4 Loratap curtain controllers (link bellow), they work great has they have a remote controller has a backup, and with homebridge and your plug in, they work great, they open and close has requested by HomeKit, although their status is always as closed, even if they are open. https://www.aliexpress.com/item/4000291503955.html

What is “funny” is that if they are actually closed, I issue the “open” command in HomeKit and they open right away, but if they are actually open with a status of closed, I touch the button to order then to open (since the status in HomeKit is closed but the shutters are open, I mind you) homekit changes status to “opening “ for a dozen seconds and then status change to “open” for 30 seconds or so, then HomeKit changes status to close again. If I touch the HomeKit button 2 times, the shutters close as supposed to.

The strange thing is that this only started to happen after I installed more than 1 controller, when I only had 1 single controller in the house, the controller status would be accurate, status as opened when open and closed when closed. Other than that, they work great, even with automations. They open on sunrise and close on sundown perfectly, regardless of the HomeKit status.

btw, I’m on 0.7

[Garywoo]

I'm seeing the same behaviour as @edmarts in v0.8.0-0

In version v0.8.0-0 the curtains still showing the message "opening" or "closing" or if they are open show "50% opened" ... the v0.7.1 is more stable

I did test the hold position switch in v0.8.0-0 and this worked correctly, stopping the motion of my device when activated.

I'm using one of these blind chain motors.

[serial8killer]

Just to note that I've tried version 0.8.0-0 and for some reason the behaviour of my controllers is even worst, now when I send an order it still closes and opens but the status is always on "opening" and then eventually gets "not responding". I've returned to 0.7.1 and it's better. At least it's no longer stuck on "opening" or closing, and it changes states when the shutter has stopped opening and closing., although the open state returns to closed after a few seconds or a few minutes.

[jerem15fr]

Hi,

I have 7 controllers and in 0.7 and 0.7.1 I have the same issue like serial8kille : Open and closing is working in automation or with Siri. But in HomeKit the statut stay close, so I have to do a double tap to close where the blind are opened. With version 0.8, it's on the good way : a thing is interesting : in home bridge interface the state is good, and it stay good after few minutes. But in HomeKit, it's the same problem that in 0.7 and 0.7.1 : after 1 or 2 min the state is close. If I kill HomeKit and relaunch the app, state is open like in home bridge but after 1 or 2 min, it's again close. In this time the state in home bridge stay good at open...

Edit : it seems if I open HomeKit after few minutes, I have the good state in open. I'll keep you in touch in 1 or 2 days to confirm this point.

[JanMostert]

Have same issue. Blinds are closed, but status is “Closing ...”. One blind is open and status is “ Opening ...”. Looks like no confirmation is received that blind is completely closed/opened. I have version 1.0.1

[avbaga]

Same issue. it homebridge blinds always 50% opened. In homekit they stuck in closing or opening state.

[notorioustubze]

Hi I have the same issue as the ones mentioned above. Unsure if it's any help but I've been using another plugin by @bsr43/homebridge-tuya-web v0.7.1 and this doesn't happen any chance you could compare the code and see if anything stands out as to why this one isn't working? Thanks in advance!

[patrickl96]

Same issue here. Using zemismart blind motor (this same one as @Garywoo: https://www.aliexpress.com/item/1005001876951084.html)

Homekit always shows "opening..." or "closing..." and in the homebridge accessories tab it's showing the blinds at 50%

[idostern]

Same here, any workaround that we can test?

[milo526]

Same here, any workaround that we can test?

none known to me