Duwi 05436 Jalousie Funk Einbauschalter also known as ZW ESJ from Duwi or Popp

 So I have those roller shutter blind control modules since ages and they seem to work okay. I bought them as Düwi 05459x or 05436 (last number just represents the style of the cosmetic frame and paddle switch) but they are also known as ZW ESJ by Popp or some other company as interact3 or as DUW_064367. I have even read that they were the very first z-wave devices when the system was called something else.

Anyway, point if this post is to remind us of the z-wave parameters you can program in those as the parameters are nowhere documented properly. The manual will only state how to calibrate up and down with the device in learning mode but not how to calibrate via programming with z-wave parameters. While looking for an answer I came across many forum posts asking how to do it but no answers. Finally I stumbled across jeedom  where the device parameters are finally explained. While I was reading it I remembered this as I have done it many years ago myself. So before forgetting it again and helping others to find this information, I will share it here (again):

You can only work with two parameters here:

• Parameter 0 is configuring the runtime for up and down
• Parameter 1 is configuring the behavior when pressing the opposite button while the moving

Both these things can apparently be set also without parameters as per manual, see screenshot:

As you can see after browsing through many manuals which cover (what I believe is the same device), now let's have a look at the "modern" way on how to do this:

• Parameter 0 is configuring the runtime for up and down
• Parameter 1 is configuring the behavior when pressing the opposite button while the moving

For Parameter 1 it is pretty easy. I was able to modify the behavior of the module. In the default setting, it will stop the movement if you press the opposite direction. For this you need to set the value to 1. If you want to immediately revert the movement, set it to 0. I was successful by using parameter type and size of "1 byte decimal". First time I "monitored" the value it was 255 though, which is decimal for FF (hex code). So not sure if it might be required to use "1 byte hex" instead. Anyway, as pictured below works for me either 1 or 0 in parameter 1 "1 byte dec".

While typing this, I tried it in "1 byte hex" with value FF and it resulted in value 255 as "current value". Seems to work either way. You will see for parameter 0 why hex is important....

 

Now let's check out parameter 0 for the runtime. It seems to code the runtime, in up and down direction with two different values in one string. I try my best to explain. First, if we work with times less than 2minutes we get an accuracy (or possibility) to program in 1s intervals, while anything more will only be in 10s steps, as per user manuals stated above. Usually 2 minutes is enough for shutter operations.

In the following paragraphs, numbers starting with "0x" are hex values. Use an online converter to follow along or make your own "calculations". I will explain how enter your runtimes:

Parameter 0 will include both your up and down time. My Vera shows a current value of 6167 (which is a decimal number), check screenshot earlier. Inside the roller blind actor device the value is stored as hexadecimal number, which is 0x1817. The first part is "18", representing the runtime up and the second part is "17" representing the runtime down. These values are hex! 0x18 is 24s and 0x17 is 23s. So my "up" is 24s and my "down" is 23s.

Once you know what your desired up and down values are, you can "construct" your value for parameter one. As example for me I want to change to 25s up and 23s down. This would mean 0x19 up and 0x17 down. Combine "19"&"17" to get 0x1917 as new hex value for your parameter. We can convert this to 6423 as decimal number. In below picture I sent my new runtimes to the device with data type "2 byte hex" 0x1917 (in the Vera UI you don#t enter the leading 0x) and I get the desired value and behavior (25s up, 23s down).

You can also enter your runtime as a four digit decimal number with data type "2 byte dec" which works as below screenshot shows. In this example I used decimal 6168 which is 0x1818 which is "18" up and "18" down which is 24s up and 24s down.

Just make sure to use the correct "data type/size" for whatever you will decide which route to go. Vera will display the actual setpoint the device uses always as "decimal", so maybe it is better to use the decimal 2 byte variant to make sure the parameter is accepted.