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.

 

Technisat Szenenschalter 1 ( Technisat scene controller 1 with 4 buttons)

 Hi,

for everybody wondering how to include this device or what device handler to use and so on... I am using this device as a small remote for some lights with my Vera Lite. As the device was not readily in the list of a possbile "new device", I just added it as the HKZW-SCN04-V1.0 from Hank.

First, charge the "battery" all the way. Check the manual. Inclusion is via the center button, tripple click. 

It appears that most of the Technisat Z-wave products are just rebranded Hank devices, so using the appropriate settings and handlers like the original Hank device works just fine. As with all device inclusion on Vera Lite, I recommend doing it via the App, not the WebUI. 

In Vera, the buttons are mapped as per below image.

In the device options, there will be a menu where you can assign scenes to the different actions of buttons. Or you can use the remote as "trigger" when creating scenes in the scene editor. Whatever you do, stick with one version. Also, it is best to control devices or lights via scenes. It should be possible to link the remote directly to a device but I can't be bothered to set this up.

If you want to assign the function ON and OFF to let's say one button on the remote, say to "toggle" a light on or off depending if it is on or off already, there is a way to do this. You don'd need two buttons/scenes, one for ON, one for OFF. 

What we need, is to "toggle" the controlled device, which means "change to the other state" and not tell them what exact state to go to. To toggle a device in Vera Lite (or Ezlo ???), create a scene for this (best with manual trigger, if you assign this scene to the button) purpose. Go to the advanced editor and add an action, choose your device/light and there look for something called "toggle". Worked for me.

Fibaro Flood Sensor FGFS-101 Gen5 FW3.4 & Vera Lite

 Hi,

short post regarding the usage of Fibaro Floodsensor FGFS-101 with the Firmware 3.4 as per sticker on the PCB of the sensor. Adding them to an (old) Vera Lite z-wave hub was a pain until I figured out that it needs some manual work. My "old" Vera Lite is now I think over 7 years old, running okay most of the time with no problems or stability issues. I have a few roller shutters and lights. The Firmware of the Vera Lite is stuck at 1.7.1030 as I can't update to 1.7.1040 due to not enough storage. And I don't want to as everything works...

First, let me say that I recommend running these sensors with DC power supply. In battery mode they will die fast and are reported as "disconnected" in Vera. I don#t remember how I got them running the first time (when using battery) but today I tried to reconnect them and decided to use DC power instead of battery. One reason is the location in the cellar is far away from any other Z-Wave device which could relay their meassages and I have the feeling that with DC power they are more reliable. 

Anyway, changing them to DC power required to remove them (exclude) and then add (include) again. As there was no way to get them properly removed I had to delete them manually from Vera and exclude the devices manually as well. Once that was done, I wired them up properly as per manual and cut some small holes in the upper and lower shell to allow the cable to pass. Make them small, so the cable will be snug.

Then to the re-inclusion... Use the Vera App! Don´t use the web UI... Choose to add an "generic" Z-Wave device, connect the power to the FGFS-101, then advance in the wizard for inclusion until it asks for pressing the inclusion button on the "generic device". It is a quick triple click on the small tamper switch lever on the PCB. I did this while standing with the device in front of the Vera Lite, so I can see the inclusion LED stop blinking but nothing happened in the Vera App.... Try to start the inclusion (triple click) as soon as the 60s count down starts... The inclusion nearly takes 60s! Anyway, once triple clicked, don't worry (yet) if nothing happens. Once the countdown timer passed, the inclusion was still successful and the app (I am using iPhone app) asks for a name and a room for the "generic device". 

Back at the computer in the web UI you can see your new device along with a "_Temperature Sensor" which belongs to this FGFS-101. Give it a proper name.

You will see that the device in Vera shows up as Generic Device and not as sensor so it can't be used properly for scenes or alarms. This can be fixed by telling Vera Lite that this is actually a flood sensor. You will need to go into the settings of the "Generic Device", then "Advanced". In the "Params" (parameters) section there, you can make all the necessary changes. I did the following, I swapped the values for the generic device with flood sensor values:

• device_file: D_FloodSensor1.xml
• device_type: urn:schemas-micasaverde-com:device:FloodSensor:1
• manufacturer: Fibaro
• model: FGFS-101 Gen5
• device_json: D_FloodSensorWithTamper1.json
• category_num: 4
• subcategory_num: 2

Thanks for the advise from amdokamal and mdg from this forum thread over at the official forum for the Vera Lite. My flood sensors now show up properly and work as expected.