Blinds-type devices do not support the 'stop' command on Alexa

[christianbalz]

Describe the bug When asking Alexa to open and close the curtain, everything works fine. However, when requesting to "stop" the curtain, it is the closing command that is mistakenly executed.

To Reproduce Steps to reproduce the behavior:

1. Add a virtual device node
2. Set the type as blinds
3. Add a debug node
4. "Alexa, open curtain" (works fine)
5. "Alexa, close curtain" (works fine)
6. "Alexa, stop curtain" (executes the closing command)
7. "Alexa, set curtain to 73%" (works fine)

Expected behavior It is expected that the curtain stops when requested through Alexa.

Screenshots

Environment (please complete the following information):

• virtual-smart-home version: 4.0.0
• Node-RED version: 3.1.3

Additional context

1. I have some Sonoff Dual R3 devices, and I can simulate the commands to open, close, and stop with Alexa.

2. I am using a Zigbee + RF curtain switch module Moes MS-108ZR, which is designed to support three states: open, close, and stop.

[csuermann]

Hi @christianbalz,

While the capability to command Alexa to stop would be a welcomed addition, it doesn't seem to possible with the functionality provided by the RangeController interface. This interface is used to control devices such as blinds and curtains. If you possess any insights on how to incorporate a stop feature within a smart home skill, I would greatly appreciate any guidance you can provide.

[jpadie]

@csuermann @christianbalz perhaps adding a powerController interface to the endpoint template would be an idea.
some logic could sit in node-red to cut power to the blinds or send a position adjustment to the then current location of the blind.

[github-actions[bot]]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[christianbalz]

Hello, I'm revisiting the previously reported issue where the "stop" command for the curtains via Alexa was mistakenly interpreted as a closing command. I would like to know if there have been any progress or updates in recent versions that now allow proper support for the "stop" command. Thank you in advance for your attention and for the continued development of this component.

[csuermann]

Hi @christianbalz! Unfortunately no progress was made on this issue. Unless Amazon adds official support to the Alexa API for stopping curtains / blinds etc. I'm not sure how VSH could fix this.

[jpadie]

Hello, I'm revisiting the previously reported issue where the "stop" command for the curtains via Alexa was mistakenly interpreted as a closing command. I would like to know if there have been any progress or updates in recent versions that now allow proper support for the "stop" command. Thank you in advance for your attention and for the continued development of this component.

@christianbalz there are ways to make this work with vsh. The easiest is to add an onoff virtual device and link the off state (in node red) to the stop command of your ZigBee window covering node. The Alexa utterances would reference the name of that onoff device. So it would be open the curtains and then maybe stop the motor.

As an alternative the matter protocol supports stopMotion and I have built synthetic matter window covering devices in node red that function with Alexa and other ecosystems. I have not tried the stopMotion command and as @csuermann says, if Amazon have not augmented their NLP to include this utterance then you're stuck with the UI or a workaround