Curtain Status stuck on opening or closing #143

edmarts · 2020-12-23T17:52:10Z

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 · 2020-12-23T17:53:39Z

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 · 2020-12-24T10:10:56Z

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 · 2020-12-26T06:46:54Z

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

thanks.

milo526 · 2021-01-04T21:57:00Z

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 · 2021-01-05T10:36:55Z

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 · 2021-01-05T10:56:51Z

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 · 2021-01-05T11:00:25Z

@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 · 2021-01-06T04:00:28Z

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 · 2021-01-06T07:56:24Z

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 · 2021-01-06T10:43:29Z

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 · 2021-01-07T00:49:28Z

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 · 2021-01-07T00:56:36Z

Me too 😔

rulez86 · 2021-01-07T07:43:02Z

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:

Upgrade to 0.8.0.0
Try closing / opening curtain by tuya app, works fine State: closed
switch to homebridge plugin and try to adapt status to closed, because there it was open for some reason
So, both, tuya app and homebridge plugin has status closed
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 · 2021-01-09T11:30:45Z

@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 · 2021-01-10T13:01:16Z

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 · 2021-01-10T15:08:03Z

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

milo526 · 2021-01-10T16:20:07Z

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 · 2021-01-17T17:57:13Z

Hey

Same problem :-(

rulez86 · 2021-01-17T18:49:18Z

Hey

Same problem :-(

@alanit0
Which model of device do you have?

AnonymousPea · 2021-01-21T01:07:40Z

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 · 2021-01-21T14:13:29Z

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 · 2021-01-24T20:54:33Z

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 · 2021-01-25T16:04:19Z

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 · 2021-01-27T20:50:14Z

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.

bkarlson · 2021-10-11T05:24:56Z

@milo526 ,
Any plans to merge changes from https://github.com/bsr43/homebridge-tuya-web into this repo? Relevant commit:
bSr43@91ef52e

milo526 · 2021-10-11T07:10:33Z

Sadly not, I have not yet received a request from bsr43 to merge this.
While I could legally use their code, it is not a nice thing to do without their consent.
If they'd like to get their code in this codebase they can submit a pull request and we can discuss the code.

bSr43 · 2021-10-12T12:41:06Z

Hello,

Sorry for delay, I was not looking at the repo and all notifications are disabled on my side 😅
I'm not using these kind devices anymore, and this is why I was not looking at the improvements anymore.
Anyway, of course, feel free to use the code of my fork!

Tomcraft1980 · 2021-10-13T11:08:32Z

Would be great to see the fix from bSr43/homebridge-tuya-web@91ef52e in the next version as I'm struggling with the same issue.

movy · 2021-10-14T08:48:36Z

Also, related to #148, I can see that bSr43@91ef52e includes percentage values in theory allowing curtains to stay ajar (half-open), however even with bSr43's fork I cannot get curtain to 50% open.

Wondering whose fault is it, homekit or tuya or..? And whether it's fixable at all.

bkarlson · 2021-10-20T14:10:27Z

Any progress on this one? Should I create a PR from @bSr43's fork?

I just encountered #161 while on that fork, not sure it's Tuya's problem or the fork's... want to switch to @milo526's one, but w/o bSr43@91ef52e this will render my curtains non-functional.

milo526 · 2021-10-20T14:17:16Z

I have very little time to develop this library further until the end of this year, please do not expect any release until that time.

Hoobs-User · 2022-04-13T10:34:38Z

I have the same problem with the Wifi curtain motor model BCM700D WiFi
https://www.amazon.de/gp/product/B09HCGB1M7/ref=ppx_yo_dt_b_asin_title_o07_s00?ie=UTF8&psc=1

joaco1728 · 2023-06-06T14:19:25Z

hi I have the latest version, I used the IOT Tuya platform, loading the Secret Key and everything with the tuya plugin on home bridge. There, everything worked well. The thing is that Tuya IoT platform is payed (pretty expensive for home use) and the 1 month free trial has ended. Now Using @milo526 plugin, it exposes the curtains pretty well, but mainly two issues. The curtains have a lag on the status (closing or opening, when already reached the closing/open point) and also there is no way to make the curtains half open or on a partial closing/opening point. As I said, I am running latest plugin version. Thank @milo526 for the plugin.

leo150 · 2023-07-07T07:22:52Z

Fix for a similar issue for official tuya plugin: tuya/tuya-homebridge#363

zico202020 · 2023-07-22T05:27:36Z

Hi @milo526 ! How are you?
I checked with a user and got the solution to solve the curtain problem, can you update the plugin to fix this problem? We in the community would be very grateful for your help!
best regards

Zobbi69 · 2023-12-04T11:00:12Z

Hey @zico202020, would you be able to share how you’ve got this working?

beber666 · 2023-12-15T14:07:21Z

Got the exact same issue since i'm using home bridge. In home bridge, the curtain seems to be at 50% everytime.

adityag78 · 2024-05-16T19:11:12Z

Have an issue with the curtain. @milo526 It’s showing on the home app. But it can only open. Can’t close. Please help.
@milo526_homebridge-tuya-web.log.txt

JanMostert · 2024-05-17T07:02:47Z

Have an issue with the curtain. @milo526 It’s showing on the home app. But it can only open. Can’t close. Please help. @milo526_homebridge-tuya-web.log.txt

I think this project is sort of dead. You better try another plugin.

Tomcraft1980 · 2024-05-17T11:33:03Z

What plugin can you recommend?
The problem with 0x5e/homebridge-tuya-platform is, that you only have 50 devices with only 10 of them controllable via the Tuya IoT API.

JanMostert · 2024-05-17T15:47:01Z

I use the plugin homebridge-tuya-web (https://github.com/bsr43/homebridge-tuya-web#readme). You need an account for it, but it works good.

Tomcraft1980 · 2024-05-17T17:57:26Z

Ok, but then I do not get the point:

What plugin can you recommend? The problem with 0x5e/homebridge-tuya-platform is, that you only have 50 devices with only 10 of them controllable via the Tuya IoT API.

Last commit there is 4 years ago and the plugin was forked from milo526/homebridge-tuya-web

adityag78 · 2024-05-20T08:23:04Z

@bSr43 can u pls help. Loaded but curtain not working. It’s showing as icon in HomeKit.
Uploading @bsr43_homebridge-tuya-web.log.txt…

bSr43 · 2024-05-21T15:14:35Z

@bSr43 can u pls help. Loaded but curtain not working. It’s showing as icon in HomeKit. Uploading @bsr43_homebridge-tuya-web.log.txt…

I'm sorry, but like I previously said here a few years ago, I'm not using these devices anymore. I switched to Meross which worked perfectly fine for the last two years. Sorry for not being able to help.

Tomcraft1980 · 2024-05-22T07:37:42Z

Is there a way to fund you to speed things up regarding the fix from bSr43@91ef52e ?

milo526 · 2024-05-22T08:00:15Z

Is there a way to fund you to speed things up regarding the fix from bSr43@91ef52e ?

I'd rather see someone making a PR and working with me to fix this.
I don't have the necessary hardware to test this; or time to develop this.
If someone has those two things; I will review and merge & deploy when ready.

Tomcraft1980 · 2024-05-22T08:03:12Z

@bSr43 Could you please send a PR for bSr43/homebridge-tuya-web@91ef52e ?
I guess this will speed things up, although he already gave permission to use his code:

[...] Anyway, of course, feel free to use the code of my fork!

I think there are more then enough people here willing to test this. ;-)

adityag78 · 2024-05-22T08:16:59Z

@bSr43 Could you please send a PR for bSr43/homebridge-tuya-web@91ef52e ?

I guess this will speed things up, although he already gave permission to use his code:

[...] Anyway, of course, feel free to use the code of my fork!

I think there are more then enough people here willing to test this. ;-)
YES I AGREE

COLAXDad · 2024-06-14T16:36:27Z

Hi - Just jumping into this home bridge-tuya thing. My curtains are exhibiting what's been discussed here.

with my curtains wide open, Homebridge shows 50%. tuya smart app reports 0% (Fully open). Apple home is stuck in an "Opening" Status. Position State on the accessory always stays at "2". whether they are opened or closed. The curtains seem controllable in apple home and home bridge. For instance when I click the curtain (shown in home bridge at 50%) it closes (tile goes dark but still reports 50%). Apple home reports "closing". but never closed.

Then when I click the home bridge icon to open, It opens Goes light again and apple home reports opening. but never sets the state as "opened".

But would love to know if there is a fix for this.

vedmant · 2024-06-26T14:34:31Z

Having the same exact issue as described above, I have this type of Wifi motors for curtains https://cnwstele.en.made-in-china.com/product/BOWavTiFrgVP/China-Tuya-Smart-Curtain-Motor-Bt-Voice-Control-Electric-Curtain-Robot.html

In the Tuya Developer Platform I can see this in device debug:

Code	Type	Values
control	Enum	{ "range": [ "open", "stop", "close", "continue" ] }
percent_control	Integer	{ "unit": "%", "min": 0, "max": 100, "scale": 0, "step": 1 }

Code	Type	Values
control	Enum	{ "range": [ "open", "stop", "close", "continue" ] }
percent_control	Integer	{ "unit": "%", "min": 0, "max": 100, "scale": 0, "step": 1 }
percent_state	Integer	{ "unit": "%", "min": 0, "max": 100, "scale": 0, "step": 1 }
fault	Bitmap	{ "label": [ "motor_fault" ] }
battery_percentage	Integer	{ "unit": "%", "min": 0, "max": 100, "scale": 0, "step": 1 }

Maybe this will be helpful

PencilDH · 2024-09-16T16:52:16Z

Did anyone managed to get a PR in place with a fix for this? Would be great to get this resolved as it has been open issue since 2020

milo526 · 2024-09-16T17:00:02Z

Did anyone managed to get a PR in place with a fix for this? Would be great to get this resolved as it has been open issue since 2020

I have not seen any such PR.

Tomcraft1980 · 2024-09-16T18:17:59Z

You should have received a PR now. #618

tommylux · 2024-11-17T01:58:30Z

I've seen this also on my smart blinds

edmarts added the bug Something isn't working label Dec 23, 2020

milo526 changed the title ~~Curtain Status~~ Curtain Status stuck on opening or closing Dec 28, 2020

milo526 added the active Should stay opened label Dec 28, 2020

milo526 mentioned this issue Dec 30, 2020

[Accessory Request] Cover accessory #18

Open

milo526 mentioned this issue Jan 5, 2021

Open / Closed the wrong way #160

Closed

milo526 mentioned this issue Jan 15, 2021

Window cover that doesn't work well #171

Closed

Curtain Status stuck on opening or closing #143

Curtain Status stuck on opening or closing #143

Comments

edmarts commented Dec 23, 2020

milo526 commented Dec 23, 2020

adspen commented Dec 24, 2020

siim911 commented Dec 26, 2020

milo526 commented Jan 4, 2021

adspen commented Jan 5, 2021

edmarts commented Jan 5, 2021

milo526 commented Jan 5, 2021

mattlukc commented Jan 6, 2021

milo526 commented Jan 6, 2021

adspen commented Jan 6, 2021

mattlukc commented Jan 7, 2021

taaa22 commented Jan 7, 2021

rulez86 commented Jan 7, 2021 • edited Loading

edmarts commented Jan 9, 2021

milo526 commented Jan 10, 2021

rulez86 commented Jan 10, 2021

milo526 commented Jan 10, 2021

alanit0 commented Jan 17, 2021

rulez86 commented Jan 17, 2021

AnonymousPea commented Jan 21, 2021 • edited Loading

serial8killer commented Jan 21, 2021 • edited Loading

Garywoo commented Jan 24, 2021

serial8killer commented Jan 25, 2021

jerem15fr commented Jan 27, 2021 • edited Loading

bkarlson commented Oct 11, 2021

milo526 commented Oct 11, 2021

bSr43 commented Oct 12, 2021

Tomcraft1980 commented Oct 13, 2021

movy commented Oct 14, 2021

bkarlson commented Oct 20, 2021

milo526 commented Oct 20, 2021

Hoobs-User commented Apr 13, 2022

joaco1728 commented Jun 6, 2023

leo150 commented Jul 7, 2023 • edited Loading

zico202020 commented Jul 22, 2023

Zobbi69 commented Dec 4, 2023

beber666 commented Dec 15, 2023

adityag78 commented May 16, 2024 • edited Loading

JanMostert commented May 17, 2024

Tomcraft1980 commented May 17, 2024

JanMostert commented May 17, 2024

Tomcraft1980 commented May 17, 2024

adityag78 commented May 20, 2024

bSr43 commented May 21, 2024

Tomcraft1980 commented May 22, 2024 • edited Loading

milo526 commented May 22, 2024

Tomcraft1980 commented May 22, 2024 • edited Loading

adityag78 commented May 22, 2024

COLAXDad commented Jun 14, 2024 • edited Loading

vedmant commented Jun 26, 2024

PencilDH commented Sep 16, 2024

milo526 commented Sep 16, 2024

Tomcraft1980 commented Sep 16, 2024 • edited Loading

tommylux commented Nov 17, 2024

rulez86 commented Jan 7, 2021 •

edited

Loading

AnonymousPea commented Jan 21, 2021 •

edited

Loading

serial8killer commented Jan 21, 2021 •

edited

Loading

jerem15fr commented Jan 27, 2021 •

edited

Loading

leo150 commented Jul 7, 2023 •

edited

Loading

adityag78 commented May 16, 2024 •

edited

Loading

Tomcraft1980 commented May 22, 2024 •

edited

Loading

Tomcraft1980 commented May 22, 2024 •

edited

Loading

COLAXDad commented Jun 14, 2024 •

edited

Loading

Tomcraft1980 commented Sep 16, 2024 •

edited

Loading