Windows Covering - OPEN & CLOSE incorrectly Reversed !! - Need Solution

I have about 8 blinds recently installed and automated (with AEON Micro Controllers). All working fine except that the OPEN and CLOSE are reversed. This is definitely a BUG due to which the Bind Controller can’t be used in SQ Remote device (unless you train your brain to read open as closed or closed as open !!)

CURRENT BEHAVIOR :
UP/CLOSE Button ==> Moves the Blind Up and changes the status in iPhone SQ Remote to “Closed” - Incorrect
Down/OPEN Button ==> Moves the Blind Down and changes the status in iPhone SQ Remote to “Open” - Incorrect
Pressing the ‘Windows Control’ toggle button in iPhone SQ Remote == > Toggle-to-Open moves the blind Down and Toggle-to-Closed moves the blind Up - Incorrect

This is highly confusing. The desired behavior is reverse of OPEN/CLOSE buttons (no change to Up/Down).

EXPECTED BEHAVIOR :

  • UP/OPEN Button ==> Should Move the Blind Up and change the status in iPhone SQ Remote to “Open”
  • Down/CLOSE Button ==> Should Move the Blind Down and change the status in iPhone SQ Remote to “Closed”
    -Pressing the ‘Windows Control’ toggle button in iPhone SQ Remote == >Toggle-to-Open should moves the blind UP and Toggle-to-Closed should move the blind DOWN

Workaround tried so far

  1. I tried to use the jason file provided by Shady in " http://forum.micasaverde.com/index.php/topic,5974.msg77476.html#msg77476" to reverse the Open/Close but could not achieve the above behavior ( i could only reverse the Up/Down). I have also raised a ticket but response is very slow so far.
  2. Variable to reverse the function. This link “http://wiki.micasaverde.com/index.php/Release_Notes#UI5:_1.5.621_.28and_1.5.622.29_-_March_1.2C_2013_-_private_beta” talks about a varable “ReverseOnOff” . I could not find any more information on the same. Nevertheless, I tried to use the variable “ReverseOnOff” ( set it to 1), but I did not notice any changes.
    3.I have not tried this but one workaround is to reverse the M1 & M2 connections in the micro controller or to re-calibrate this blinds in other directions. Con : Costly or time consuming options. Besides this will reverse the UP and DOWN button.
    4.Create 2 different scenes for Open / Close. Use the scenes in SQ Remote. Con : Can’t view the status in SQ Remote.

Anyone faced this issue and have a solution to the same ? I can change/test/experiment with JASON/XML files if you can help me with what needs to be changed. I have done some tinkering but not getting the desired result (to obtain the expected behavior mentioned above).

I have also raised a ticket with MIOS but response is extremely slow thus far !!

Note : I had also posted this in “http://forum.micasaverde.com/index.php?topic=11599.0”. Please post any replies here.

Can’t you change the directions by changing the wiring ?

Good point Richard

Yes you can, I have these same Aeon Labs controllers and fell into this same trap on one of them.

I reversed the wires and everything was working as it should

:slight_smile:

Yes, that’s no. 3 workaround as mentioned above. But this will require me to get a electrician to open up the wall plate and reverse the directions. The wall plate is bit difficult to reach as it is behind the blind and will also require the blinds to be opened :(. Hence want to avoid this workaround. It will also mean that the Up and Close will get reversed (i.e. Up button will bring the blind down and Down button will bring the blind up).

The bug here is that UP is linked to CLOSE and DOWN s linked to OPEN so whatever you do one set (OPEN/CLOSE or UP/DOWN) will work the reverse way !!

People who are doing new installations, i suggest you calibrate or do the connections based on OPEN/CLOSE not UP/DOWN till this issue is fixed. That way you will see the correct status in SQ Remote.

I am still looking for a solution to SOFT reverse the OPEN/CLOSE (and not via a HARD Reverse i.e. change the wiring ). Anyone ?

The only working solution I found was to reverse the wiring…as you said everything else was a bit of a hack.

Changing the JSON file will allow you change the labels for Vera … but likely have no effect for SQL Remote

Motor controllers belong to the dimmer class.
ON / DIM UP is UP /OPEN
OFF / DIM DOWN is DOWN /CLOSE

The UP and OPEN commands have to be the same, (as well as CLOSE and DOWN) any fix will throw something else out of sync.
MIOS has to fix this.
Keep bugging them

Hi

I have been reading through various posts related to Aeotec Motor Controllers re a similar problem I have but haven’t, as yet, found another similar problem.

I have 6 roller shutters controlled with the Aeotec Motor Controllers.

When controlling them all through the UI or iVera Remote “up is up” and “down is down” on all 6 - no problems

BUT

I have 2 scenes that when run open or close all roller shutters in one go.

This works fine for 4 of them but for 2 the functions / directions are reversed.

In the wiring / configuration of the shutters / motor controllers I have 100=close and 0=open

In the open scene the “SetLoadLevelTarget” is set to “0” to open all 6 shutters but for 2 of them they stay closed. If I set the “SetLoadLevelTarget” to “100” for these 2 shutters they all open when the scene is run as expected.

In the close scene the "SetLoadLevelTarget is set to “100” to close all 6 shutters but again for the same 2 they stay open. If I set the “SetLoadLevelTarget” to “0” for these 2 shutters they all close when the scene is run as expected.

This can’t be a wiring configuration error as the same 2 shutters open and close correctly when controlled directly through the device in the UI.

Anyone have any ideas as to what could be causing this?

Thanks :sunglasses:

Looks like the latest firware update from VERA fixed the UP?DOWN - OPEN?CLOSE reversal, everything looks good now
Maybe you should try to “exclude” and re"include" the 2 that are giving you grief, then check that “0” is close/down and “100” is open/up for all 6 modules

In addition to my comment a couple of posts ago, after investigation, it looks like the UP/DOWN and OPEN/CLOSE commands dont belong to the same command class, one is SWITCH_MULTILEVEL and the other one is BASIC. Can anybody confirm which one is what?