Garage door stuck closing or opening
<!-- PLEASE READ BEFORE POSTING A NEW ISSUE
   → If you are giving feedback or requesting a new feature then feel free to ignore this template.
   → If you are experiencing an issue with the plugin then please use this template as well as you can.
   → Things that may seem unimportant to you are often helpful in finding the cause of the issue.
-->

### What issue do you have? Please be as thorough and explicit as possible.
Garage door simulation with Sonoff 3Channel works to open/close from HomeKit but somehow will keep saying “Opening…” or “Closing…” indefinitely. 

I have paired it with a DW2-RF contact sensor and inputted it in the settings, no change. Removing sensor and it still is stuck opening or closing message. Very strange. 

In the past, without the sensor, it would change to Open or Close after the specified seconds in Operation time. Now it just stays indefinitely in the opening/closing. If I press it again it’ll operate the sonoff (go from closing to opening and Vice versa) but the status stays stuck. 

Things Ive tried:
Removing bridge
Delete cache for sonoff 3CH
Delete plugin and config in homebridge 
Remove/re-add bridge to HomeKit 


### Details of your setup.
* Do you use Homebridge (with config-ui?) or HOOBS? 

Homebridge 

* Which version of Homebridge/HOOBS do you have?

1.50


* Which version of this plugin (homebridge-ewelink) do you have? Has the issue started since upgrading from a previous version?

10.0.0. I’m not sure, but it used to work. Not sure if this is due to newer version or not. 

* Which eWeLink devices do you have that are causing issues? Please include product models if applicable.

Sonoff 3CH (HC-3CH-E (3))

* Do you use your main eWeLink credentials or do you use a secondary eWeLink account for Homebridge?

Main credentials 

### Please paste any relevant logs below.
<!-- ABOUT LOGS
   → More thorough logging can be seen by enabling 'Debug Logging' in
     ...the plugin settings.
   → If you are posting an error then it is helpful for me to also see
     ...the previous few lines as this can show the cause of the error.
   → Please enter the logs between the two ``` lines below so that
     ...the logs are formatted in a way which is easier to read.
-->

```

```
