Virtual Shade Behaviour

I just tried out the virtual shade device in order to control some DIY MQTT blinds via Maker API and node red and found that the actual open/close/set position commands don't get sent until 10s after the virtual device is activated. At this point the status of the virtual device simultaneously updates.

So nothing happens for 10s and then my blinds start moving and the device tile shows it at being open at whatever setting was selected. Shouldn't the open/close/position command get sent immediately? I can live with the arbitrary 10s status message delay (but being adjustable would be nice),

Tagging @mike.maxwell (sorry if I'm tagging the wrong person on this!)

I guess you could look at this a number of ways, in this case we have chosen to have the device report it's position when it is done traversing. The travel time is set to 10 seconds, I'll see about adding some transition time options which would make this device more usefull...

Thanks for considering this Mike!

Not sure if I was 100% clear though - my main problem is that within node-red I can see that the message payload from the HE virtual shade device (which contains the command parameters like setting the blind position etc and which gets relayed to my blind controller) only gets sent at the same time as the report message (ie after the preset 10s) so my blinds can only start moving after 10s. I guess I kind of have 2 issues:

(1) send the open/close/position command immediately so it can be passed via maker API to the blind controller to start opening/closing without delay; and then
(2) have the virtual shade report the desired position has been reached after a period of time (which would be proportional to a set-able delay from fully closed to open). This is nice to have but not absolutely critical.

Hi Mike, any progress on this? Not sure if you saw my post above regarding when the close/open command actually gets sent.

A transition time of 0 was added in platform 2.2.1

Thanks, I'll check it out!