My first attempt was controlling a servo which pushed the up and down buttons on the remote. Surprisingly it worked pretty well, but I figured I could do something more sophisticated. After all, if the Levolor app on my phone can drive the remote, I should be able to too, right! It took a while to figure it out, but eventually I worked out how the app communicated to the remote, and hey presto!
My 'version 4' (2 and 3 were a bust) was really the ideal solution, get the Wevolor to pretend it's a WEMO switch which Alexa can talk to locally without having to go outside my home network to the cloud. Worked very well initially, but changes to Alexa software caused it to be unstable - Alexa would loose contact with my 'switch' and it was a real issue getting her to find it again.
That led me to look at what Alexa and other home automation hubs can already talk to. If-this-then-that(IFTTT) is really easy to set up to take commands from Alexa and many other 'triggers'. That seemed the way to go, so version 5 of Wevolor has been all about that. There are too many hops if we're honest: Alexa sends a command to IFTTT which send another to the messaging server which gets polled by the Wevolor, and connects to the 6-channel remote, which finally sends the command to the blinds. Sounds more 'overcomplicated' than 'sophisticated', but it works well enough.
I'm looking at ways next to potentially take IFTTT and the messaging server out of the loop. 'Home Assistant' works well and since the Wevolor exposes an API which is easy to send commands to on your local network, it was very simple to configure Home Assistant to do so. The only issue is there's a monthly subscription charge to allow Alexa to connect (I'm kinda allergic to monthly subscriptions). I'm also looking at 'OpenHab', and that seems promising. If you want more information about setting up Home Assistant or OpenHab to drive the Wevolor, e-mail me.