Configuring the Wevolor device

Wevolor version: 5.4

NOTE: based on 5.3 instructions. 5.4 updates and 5.4.1 are flagged.

The ‘Wevolor’ (referred to hereafter as ‘Wevolor’, or ‘device’) is software running on an ESP32 development board. It takes commands from 'If This Then That' (hereafter IFTTT). IFTTT can be triggered by many events including home automation such as Amazon Echo (hereafter 'Alexa') and Google Home. The Wevolor relays the actions to the Levolor Premium 6-Channel Remote Control (referred to hereafter as ‘remote’). If configured correctly the Wevolor can take (via IFTTT) Google Home or Alexa such as “Alexa, trigger close the blinds”, or timed commands like closing the blinds at sunset and opening them at 6am. Those commands are then relayed to the remote to execute the action.

Before you start:

  1. You should have an IFTTT Account and optionally a home automation hub such as Amazon Echo.

  2. You should have a Levolor 6-channel remote which is paired with one or more blinds so you can successfully open and close the blind(s) using the remote. Make sure the remote has good batteries and is physically close (within 10 feet) of your Wevolor.

Note: The Wevolor requires IFTTT, and the Levolor Premium 6-channel remote. Amazon Echo / Google Home etc. are optional. See IFTTT for home automation and other triggers supported.

Steps to configuring:

  1. Power the device on by connecting a USB power supply to the device micro-USB connector.

  2. Check the bright blue LED on the board is on. Note: some devices have a dim constantly flashing blue LED or a red LED - this shows the board is powered and can be ignored. The bright blue LED signifies the board is in ‘setup mode’. If this is your first time powering your Wevolor and the bright blue LED is not solidly lit, you may need to reset the device using the reset button on the device itself, or by removing and reconnecting power. Note: If you are using a board other than the Lolin32, the blue LED may not light. [5.4] Setup allows for testing and setting (see 'Other Settings' below) other LED pin numbers and the correct polarity.

  3. A WiFi network ('access point') is served by the Wevolor device to allow setup. On a phone or computer, connect to the 'Wevolor' WiFi network. Password is 'setupmode'. Note: It may takes a minute or so for the WiFi network to show up in the available networks list on your phone or computer, if it’s not there, wait a minute.

  4. Once connected to the Wevolor WiFi. Type '192.168.4.1' into the browser.

  5. A 'Configure your Wevolor' page should be presented.

    IMPORTANT: The unique 16-character identifier for your Wevolor should be noted. It is needed when setting up IFTTT and for accessing the myWevolor website.

  6. Configure the following sections:

    1. WiFi - [5.4] select from the dropdown where the WiFi networks available are shown in order of signal strength. Choose a network that is 'Strong' or 'Ok', and is 'Secure'. Networks shown as 'Unsafe' have network security settings that are not recommended. Alternatively, enter the SSID (name) and Password of your home 2.4G WiFi. Note: ESP32 boards do not support 5G WiFi. Both have a maximum length of 31 characters. The password is shown as you type it, but you are the only one who can see it. It's important you get the SSID and password correct, so double check. The performance of your Wevolor is highly dependent on a strong and stable WiFi connection.

    2. Levolor Remote

      1. Name - If you have only one remote you can leave this blank. If you have more than one you can specify which you want the Wevolor to connect to. The name should match exactly the name the remote was given in the Levolor phone App.

      2. Group - Set what blind group or groups you want to open and close. These are the same as the 6 numbered buttons on the remote. Default is Group 1.

    3. [5.4] Additional Security

      1. Send To Server - uncheck this if you want your Wevolor to be on your local WiFi network only. See the 'Local WiFi Network API' section below for details of how your Wevolor can be used when this is unchecked. Note: The following two options are irrelevant if this is unchecked.

      2. Send IP Address - if checked the IP address of your Wevolor is sent to the server so the myWevolor web pages can find it. If unchecked the IP address is not send, and you will need to find it yourself and type it into the myWevolor 'Local Status and Command' page.

      3. Security Phrase - if provided, any set commands (see Steps to connect IFTTT below) will need to include the security phrase. This adds additional security beyond the 16 character unique identifier. The Security Phrase can be anything but is limited to 31 characters.

    4. Other Settings: LED Pin - allows Wevolor users who loaded their own ESP32 board to set and remember the correct LED Pin (the 'Blight Blue LED' mentioned throughout these instructions) and polarity. Only change this if the blight blue LED doesn't light during setup. Enter a number such as 2, -5 or -22 (three common values for the LED pin) and hit the test button. If the correct value, the blue LED will flash slowly and go off. The '-' sign says the LED pin is active low (set it off and the LED comes on). If the LED flashes and stays on, the pin number is correct but the polarity wrong. Add or remove the minus sign and retest.

  7. 'Submit' the form with the green button. A red 'RESTART' button will appear. If you are happy with your settings, hit the RESTART button to apply your configuration.

  8. Close the browser window or tab, as configuration is now complete. The bright blue LED should now be off, and there should no longer be a 'Wevolor' WiFi network available.

  9. You can check whether your Wevolor connected by going to https://wevolor.com/myWevolor and entering your unique 16-character identifier(UID). If status pops up then your Wevolor connected to the server and is configured correctly. At this stage the 'set' and 'acknowledge' will be blank since no commands have yet been sent.

Steps to connect IFTTT:

[5.4.1]Note:do.wevolor.com replaces hghst.net for sending set commands. While hghst.net continues to work its use is deprecated.

  1. Go to the IFTTT web site or Download the IFTTT app on your phone. If you don't already have an account, sign up for free.

  2. IFTTT has 'triggers' (this) and 'actions' (that). Using Alexa as the example, a voice command "Alexa open the blinds" is our trigger and the Wevolor activating the remote is the action.

  3. On the IFTTT web site, click the 'Create' menu item taking you to a 'Create Your Own' page. Click on 'This' and select the Amazon Alexa service or your preferred service such as Google Assistant etc. Follow the steps to configure IFTTT to access your account, and set your specific trigger. For example, with Alexa the trigger can be "Say a specific phrase".

  4. Next click on 'That'. Wevolor uses the 'Webhooks' action service. Click on it and select 'Make a web request'. This is where the unique 16-character identifier you noted earlier comes in. Let's assume it was '00112233AABBCCDD'. The URL field should be set to 'https://do.wevolor.com:9443/set/00112233AABBCCDD/open' to open the blinds. 'https://do.wevolor.com:9443/set/00112233AABBCCDD/close' would be the URL to close the blinds. Make sure you use your Wevolor's unique 16-character identifier and the correct action. Also note that alpha characters in the identifier are always upper case, and the actions lower case.

    Wevolor supports 'open', 'close', 'tiltopen', 'tiltclose', 'stop' and 'favorite'.
    Note: if your blinds/shades operate with the left and right buttons on the remote then use 'tiltopen' and 'tiltclose' rather than open/close

    To override the default group(s) that commands are sent to, simply add '/123' to the command to execute on groups 1,2 and 3. Adding '/123456' would execute the command on all six groups.

    Multiple Wevolors can be 'set' with a single command if required. Add additional 16-character identifiers to 'set' commands separated by a '+'.
    For example 'https://do.wevolor.com:9443/set/00112233AABBCCDD+22446688AACCDDFF/open' would send the open command to two Wevolors.

    As well as the actions listed above, one additional is 'toggle'. Sending toggle will open your blinds if previously closed and vice versa. Note: If toggle is used before an 'open' or 'close' command is set, it will initially open your blinds. Toggle allows a single IFTTT action to be set up which both opens and closes your blinds (handy since IFTTT recently changed to only allowing three applets to be configured without paying for a Pro account).

    Other fields:

  5. Save. IFTTT should show you your new 'Applet' for example 'If you say "Alexa trigger open the blinds", then make a web request'. Note the 'trigger' word in there. If you prefer not to have that you can set a routine in the Alexa app to recognize "Alexa, open the blinds" without the 'trigger' word.

  6. Go ahead and say to Alexa "Alexa, trigger open the blinds" and your blinds should activate.

  7. Repeat for the other actions you wish Alexa to perform (close, tiltopen, etc.).

That's it!

Leave the Wevolor plugged in and physically close (10 feet or so) to the remote, and it should work well.

If there is an issue, see ‘Troubleshooting’ below.

If the bright blue LED is solid-on at any time the device has not been able to connect to the WiFi and has gone back to setup mode. It will cycle between retrying the WiFi and setup. If the bright blue LED is on you can repeat the ‘Steps to Configuring’ above, to make changes to the WiFi or other settings.

If the device is connected to the WiFi and operational you can make changes by navigating to https://wevolor.com/myWevolor and entering the unique ID of your Wevolor. See 'Other Useful Features' below for details.

Other Useful Features:

  1. To access your Wevolor during normal operation, go to https://wevolor.com/myWevolor and enter the 16 character unique ID of your Wevolor. [5.4] If set you will also be prompted for the Security phrase. Once the correct Unique ID is entered, status of your Wevolor will be shown (this is accessible anywhere):

  2. The second panel has a link that allows you to connect to your Wevolor directly (only works if you are on the same WiFi network):

  3. Wevolor Local Status and Commands gives additional information about the state of your Wevolor and a way to send commands directly to it. This is good when you want quick response time - like when issuing a 'STOP' command - however commands sent this way will not be shown in the 'myWevolor' status.

    [5.4] Note: If the IP Address was not send to the server (setup option) you will need to find the IP Address of your Wevolor on your local WiFi network and enter it.

  4. The top panel gives a way to access the Setup page of your Wevolor to reset configuration details. It also shows any available software updates. In general if there are software updates available, it's recommended to install the latest.

[5.4] Local WiFi network API

The Wevolor publishes a simple application programming interface(API) on your local WiFi network. It is only accessible to other computers and devices connected to the same WiFi network. The API allows:

  1. Getting status of your Wevolor - http://{local-IP-Addr}/_status will return a JSON string with status. Optionally add '?log=1' to the end to also return the latest log information.
  2. Sending commands to the remote - http://{local-IP-Addr}/_command?action=close&groups=1 will send a close command to the group 1 blinds. Valid actions are documented above. If 'groups' is omitted the default groups from setup will be used. Note: unlike how groups are defined in the IFTTT section above, this is a bit field value between 1 and 63 (6 bits) for the 6 groups. For example '&groups=3' would apply the action to group 1 and group 2 blinds.
  3. Update the code on the Wevolor - http://{local-IP-Addr}/_update?file=Wevolor/blinds_BLE_5_4.ino.lolin32.bin will load the 5.4 latest stable code to your Wevolor. This takes 30 seconds to a minute, so wait until a success or failure response comes back. _status above shows the code version and modification (fix) level.

Troubleshooting:

There is no 'factory reset' prior to version 5.4.1. The 'reset', 'rst' on 'EN' (Enable) button on the various board types will restart the board similar to removing power and reconnecting. On boards with a 'BOOT' button, this is used during programming and does nothing during operation. If the board is continually unable to connect to WiFi it will automatically restart in setup mode.

[5.4.1] allows factory reset via the 'BOOT' button which when held will flash the blue LED and after 20 seconds will factory reset the device - blue light solid-on showing returned to setup mode. For devices with no 'BOOT' hold finger down on the D04 (marked '4' on some boards) and that will have the same effect.

If you believe the device is properly configured, yet is not performing as expected, try restarting the device with the ‘reset’('rst', 'EN') button.

If you still believe the device is not performing properly, please take a look at the 'Wevolor Status' panel at https://wevolor.com/myWevolor (if not previously entered, you'll need to enter the 16 character unique ID). On the lower panel, click one of the links. If setup is not shown, or the command interface panels remain grayed-out, make sure you are on the same local network as your Wevolor.

If you are on the same network, but your Wevolor is not being found, check whether the bright blue LED is solid-on (remove the lid of the box if it's in a box). If it is, then the device has reentered setup mode. Retry the ‘Steps to configuring’ being especially careful about the spelling and capitalization of the WiFi settings.

If the Command Interface page connects to the local Wevolor, the Status Panel display the 'BLE State'. The ‘BLE State’ should be one of the following:

Any other problems, please contact me via e-mail at support@wevolor.com. Please send as much background information as you can, and a description of the error. Suggestions for features and changes are also welcomed.

Special Note:

The https://do.wevolor.com:9443 website mentioned above sits between IFTTT and your Wevolor. Your Wevolor polls that site to see if new commands are available to execute. The advantage of this method is your Wevolor stays safely on your local WiFi network with no special ports needing to be opened which otherwise might be a security risk. If for whatever reason the do.wevolor.com site is down, your Wevolor will not operate correctly. While every effort will be made to keep the website operational, occasional outages can't be ruled out. Also, your Wevolor sends information to the website for purposes of recording status, and developing/improving the Wevolor code. That information is limited to the last boot time of the Wevolor (to understand how stable it is). No confidential information (such as WiFi credentials) are ever sent or visible in any way to the developer. An encoded version of your Wevolor's local IP address is send (so the wevolor.com/myWevolor page knows where to find your Wevolor) but that is only readable by the Wevolor code and is secure. If you are interested to view the information sent, go to https://do.wevolor.com:9443/status/your-unique-16-character-Wevolor-id. If you want to know what the time numbers mean http://hghst.net can help with that.

There's no membership or cost to running your Wevolor but if you feel inclined to help me pay for the website hosting etc. you can Buy me a coffeeBuy me a coffee

Thanks, Roger.

(©) Copyright 2020-2021, Roger Hoggarth.