Categoriearchief: Vera Blog @en

This page contains our own experiences with Micasaverde Vera Lite and 3.

How to use ZWave.Me Keyfob in scene mode with UI7

In this section I will try to explain how to configure the ZWave.Me Keyfob (ZME_KFOB2) with the new (beta) interface UI7.

Adding the device

First lets add the device. You can add it with the help of Vera. The inclusion procedure is descriped in detail when you choose “Hand Held” -> “Z-Wave.Me Key Fob”.

Follow the guide and add the device by pressing all four buttons at once for 5 seconds. After that directly press button 1. This will trigger the inclusion process and Vera will find the device and configures it.


To let the keyfob communicate in scene mode with the Vera, we have to set some associations before. Go to “Device Options” and add groups 1 to 4. For each group, set the association to the ZWave device, as shown in the following image:

Set Associations for each group (1-4)
Set Associations for each group (1-4)

Association Overview

After you have set all four groups, the association overview should look like this:

All associations set
All associations set

Now its time to save these settings. Go back to tab “Advanced”, scroll down, and press “Configure Node right now”. Wake up the keyfob by pressing all four buttons for 5 seconds, followed by pressing button 2.

Define Scene Mode

There is a small (frustrating) bug when setting the variables needed for scene mode via the UI. A simpler and faster solution is to set the variables via the “VariablesSet” method. You can find this variable when selecting the “Advanced” submenu for the keyfob.

Here you can fill in the following values:

Fill in the variable VariablesSet
Fill in the variable VariablesSet

which in short means:

  • parameters 1 and 2, 1dec, value 0;
  • parameters 11 – 14, 1dec, value 5;

(you can supply your own values here, but to have the simple scene mode to work, choose value 5 for parameters 11 – 14).

Scroll down, press “Configure node right now” and wake up the keyfob again, by pressing button 2. The device will reconfigure itself now and when you have a look again at the “Advanced” tab, it should look like this:

Configuration Settings
Configuration Settings

Scene Triggering

When all went ok, you are ready to set your scenes. This can be done triggering for the numbers 1 to 4, corresponding with the numbers of the keyfob.

Get setpoints working in UI7

Changes won’t display

When playing around with the new interface (UI7), I stumbled across the fact that setpoints of the Horstmann HRT4-ZW (better known as SRT321), can’t be set anymore from the thermostat itself. At least, the values won’t display.

Thermostat is turned OFF

After some searching, it seems that the setpoints are correctly set, but that the thermostat isn’t turned on (as indicated by the button OFF). If this is the case for you – the button OFF is grayed out – you can’t activate it by pressing another button, as the thermostat doesn’t support these commands.

Activate Heating

The solution is pretty straightforward, as we need to activate the device and turn heating on. You can do this by defining the following variable “ModeStatus”.

Go to your device and select “Advanced”. Scroll down to the bottom and fill in the following values:

New variable
New service: urn:upnp-org:serviceId:HVAC_UserOperatingMode1
New variable: ModeStatus
New value: HeatOn


The result should look like the following image. Updates from spinning the wheel should be displayed with a small delay.

Thermostat View

Using the ZWave.Me 5460 Wall Controller with VERA

This guide shows how to add the ZWave.Me 5460 Wall Controller into VERA. This wall controller is very versatile, as it can be used in different setups throughout your Z-Wave network. When included into you network, it can operate in different modes:

  • association mode; direct control of associated devices (On/Off/Dim)
  • scene mode; control of scenes in your controller.


Inclusion of the wall controller is straight-forward and is done with holding the include button for 2s when the Vera is in inclusion mode.

ZWave.Me 5460
ZWave.Me 5460

Parameter Configuration

Before you can use the controller as a scene controller, you need to set parameter 13 and 14 to value 3 (1 dec). You can do this by adding configuration parameters to the wall controller:

Parameter Settings

After setting these values, you need to “wake-up” the controller to finish the configuration. You can do this by doing a triple click on the paddle. Note: before you can actually see the new values, you have to perform a “reload” (top-right in Vera advanced interface).

Select scenes to control

Now its time to select two (or more), scenes to control. Go to this scene, and select the Tab “triggers”. Here you need to define which action to respond to. See also the following image, where will “catch” all scene Id’s and handle it in Luup code:

A Catch All for scene id's
A Catch All for scene id’s

And the Luup code I used to control scenes 11 and 12:

luup.call_delay(‘scene_controller’, 1)
function scene_controller()
local lastSceneID= luup.variable_get(“urn:micasaverde-com:serviceId:SceneController1”, “LastSceneID”,130)
if (lastSceneID== “1”) the
{ SceneNum=”12″ },0)
elseif (lastSceneID== “2”) then
{ SceneNum=”11″ },0)

As you can see my controller (Zwave.Me 5460 module) is 130 and I only used the Up and Down scene command from the wall controller. The trick here is to look for the variable “lastSceneId”, which will change after a single or double click on the paddle.

Reference List of SceneID’s

  • Scene 1: Single Click on Upper Part of Paddle;
  • Scene 2: Single Click on Lower Part of Paddle;
  • Scene 3: Single Click Dim Up;
  • Scene 4: Single Click Dim Down;
  • Scene 5: Single Click Dim Up Stop
  • Scene 6: Single Click Dim Down Stop
  • Scene 11: Double Click on Upper Part of Paddle;
  • Scene 12: Double Click on Lower Part of Paddle;
  • Scene 13: Double Click Dim Up;
  • Scene 14: Double Click Dim Down;
  • Scene 15: Double Click Dim Up Stop
  • Scene 16: Double Click Dim Down Stop

Light level (LUX) timer based switch

Fibaro Motion Sensor

Recently the new Fibaro Motion Sensor was introduced. This device has the capability of measuring the light level (LUX) within the range from 0 ~ 32757 LUX. This is also the first device which can measure such levels and we would like to use it for putting our screens down when the light level exceeds 10000 LUX for 5 minutes or longer.

When the level drops below 10000 LUX (also for 5 minutes or longer), the screens must go up again. Please find yourself a suitable limit for going up/down.

Brightness Measuring

For this setup to work correctly you need at least UI6, as this is (for now) the only firmware which supports most of the options from the  motion sensor.

There is just one small problem when you want to trigger for a certain brightness level, as the conditions (< and >) don’t work correctly (yet) within this firmware. Please upload the following file to fix this problem:

3.0 KiB

Please go to “Apps” -> “Develop Apps” and select the option “Luup files”. You may upload the file here. Don’t forget to check the box to restart Luup after reload.

Plugin Countdown Timer

For the timer based option – i.e. wait 5 minutes before executing a scene – we will use the plugin “Countdown Timer” (2 instances per motion sensor). As this is a plugin it can be downloaded directly by going to “Apps” -> “Install Apps”.

When done, there will be already 1 instance created. For our purposes we need 2 instances, so create another one:

Countdown Timer
Countdown Timer

When done, you will have two instances of the countdown timer in your dashboard. We are going to use each one for performing actions when a timer is completed :

Two Instances
Two Instances

Don’t forget to configure the duration – in our case 300 seconds, but you can use every value you prefer.

Set duration of the timer
Set duration of the timer

Creating the scenes

We will need 4 scene’s for executing all actions:

4 Scene's
4 Scene’s

Now it’s easy to get the timers going; the scene’s Lux > 10000 and Lux < 10000 will trigger the timers, depending on the Lux value measured by the motion sensor.

This can be done easily using a trigger in both scene’s and use this trigger to activate or stop the corresponding countdown timer:


Brightness Trigger
Brightness Trigger

and in case LUX < 10000:

LUX < 10000
LUX < 10000
Brightness Trigger
Brightness Trigger

When done, you can do this also for the scene’s “Screens Up / Down” :

Screens UP
Screens UP
Screens DOWN
Screens DOWN

When you have configured everything properly, you can activate the timers manually by holding your hand on the “eye”. The LUX level will drop and the timer (LUX < 10000) will be activated. After the pre-configured time period, an event will occur (Screens UP).

If in any event – the LUX level will rise again above 10000, the other timer will be activated and the current timer will be canceled. When this timer ends, the scene Screens DOWN will occur.

Thats all! Suggestions are very welcome!

Activating scenes using the input (IN) of the Fibaro Door/Window Sensor in Vera

We recently received a question on how to configure the door/window sensor from Fibaro (product FGK-101 / 107)  using the potential free input. This manual tries to explain how we have setup a configuration using  two scenes.

For a reference here you can find the Fibaro manual: 

FGK-101-107-Door-Window-Sensor-en-2.1 (1.5 MiB, 1033 downloads)

Initial Setup

For this setup we use two plugins (PLEG):

  1. Program Logic Core (v. 5.93)
  2. Program Logic Event Generator (v. 5.93)

So make sure that you have these apps  installed before continue reading.

Including the D/W Sensor itself is straight forward. You can use the TMP switch on the back (or inside) to include the module into your Z-Wave network.

After installing the apps and including the module, your ui should look something like this:

Fibaro D/W Sensor & PLEG plugin
Fibaro D/W Sensor & PLEG plugin

Parameter Settings

To activate the scene functionality within the D/W Sensor, it is necessary to set parameter 14 to value 1 (default 0). In our case we also used a monostable switch for starting the different scenes (parameter 3, value 2).

Configure the parameters correctly (both 1 hex/dec):


Fibaro D/W Sensor Parameters
Fibaro D/W Sensor Parameters

When done, you need to save and refresh your browser (or perform a reload) to set all values correctly. You also need to reconfigure the device.

PLEG Configuration

The following pictures define which actions needs to be performed when a double click/triple click is detected. This is just an example to show how you can setup two scenes.

Under Inputs -> Device Properties, you need to define the properties which you want to use for your conditions. So we setup the following:

PLEG Device Properties
PLEG Device Properties

After that, you need to define the conditions when the scenes need to be activated:

PLEG Conditions
PLEG Conditions

As you can see above, we defined some scene numbers. These numbers correspond to the actions as explained in the manual (parameter 14):

  • Double Click ID = 14
  • Triple Click ID = 15

Last thing to do is to define the scenes itself. This can be done by configuring actions. In our case we attached two scenes, one for ToggleLamp and one for our Goodnight actions (e.g. switch all devices off).

Please note: your scenes will not become visible under the tab “Automation”. They can only be changed from within the PLEG plugin instance.

PLEG Actions

PLEG Actions

Last thing to do is to rename the PLEG instance to a name corresponding to your D/W Sensor (so you can easily find your way back after a while).

Rename PLEG to a simple name
Rename PLEG to a simple name


And now it’s time to test your setup!

When you do a double click, e.g. ToggleLamp, the corresponding scene will be executed. Doing a triple click, will perform the Goodnight action (e.g. switching all devices off).



How to make Vera the secondary controller in your network?

When you have multiple controllers in your (Z-Wave) network, there can only be just one be the primary controller. Some cases, your Vera controller should become a secondary controller and be able to communicate with the same devices but has it’s own scenes. 

We have tried to achieve this with the following setup: 

  • Primary Controller: Fibaro Home Center 2, firmware: 3.582
  • Vera 3 and Vera Lite: firmware both on 1.5.622

Z-Wave Version

First you need to check which version the Primary controller is on. If it is 2.78 you need to change this on the Vera (not in our test-case):

  1. Setup -> Z-Wave Settings -> Options -> uncheck the option ‘Use Z-Wave version 3.20 instead of 2.78’ and Save;
  2. After you check that the version is 2.78 and not 3.20, you will need to change the Vera unit to be secondary.

Connecting your primary controller

Bring up your primary controller near the Vera unit (or maybe better, your Vera to the primary controller),  and go to:
  1. Setup -> Z-Wave Settings -> Options -> uncheck the options ‘By default Vera should automatically configure devices’ and ‘Use Vera routing instead of Z-Wave (requires 4.5)’.
  2. Setup -> Z-Wave Settings -> Advanced -> click Go next to ‘Copy Z-Wave network from a master controller’
  3. Then, on the remote controller you should wake it up to receive the primary data;

That should be it and if your primary controller has already some devices it should show up in the interface of the Vera.

Using and controlling the Zwave.Me keyfob with Vera

Adding the Zwave.Me Keyfob (2) to the Vera is not that easy. For a reference I added this as a post, so when you follow the steps below,  it is possible to add and activate scenes with the keyfob.

Here is the official manual: 

Zme Kfob In En
Zme Kfob In En
131.6 KiB

Let’s start with including the device into Vera itself:

  1. Press and hold down all 4 buttons together for at least 5 seconds; the green light should be blinking;
  2. Put your Vera in association / learning mode (via normal addition or advanced Z-wave devices, add handheld remote );
  3. Press button 1 onetime for inclusion / exclusion of the keyfob;
  4. When Vera asks for you to wake up the device, repeat steps 1 and 2, but press button 2 this time (this will wake up the device which is the Vera  watiing for).

That should do it! Now it’s time to define some parameters for the keyfob to function correctly. You should do this yourself. Go to your newly added device and click on the wrench tab. The configuration for scene activation looks like this: Keyfob Parameters Keyfob Parameters

Click save and do the wakeup procedure again for the parameters to be set directly (or do you wanna wait? :)). In Vera you need to do an extra Reload for the configured values to be displayed properly.

Scene Activation

For everything to work you should create a new scene. Set your scene with the keyfob as a trigger and the scene actived as an event by the following numbers:

  • Key 1: number 1
  • Key 2: number 3
  • Key 3: number 2
  • Key 4: number 4
Setting up trigger for button 1
Setting up trigger for button 1

Create one or more scenes and attach them to the keyfob. Now its time to test!

Associate the thermostat SRT321 to the actuator SSR303

  1. Switch DIP switcher # 1 SRT321 thermostat to position ON.
  2. Turn the thermostat to the letter “A”, press and the “A” starts flashing.
  3. The actuator must be red LED off. Press the lower button >||< and the thermostat will display “AP”, this is a sign that the actuator and thermostat are associated. In this way we are able to activate manualy the actuator from the thermostat even with the Vera litle gateway not working
  4. Replace the DIP switch # 1 of SRT321 thermostat in normal mode (OFF).

Connect the actuator SSR303

Secure Actuator SSR303
Secure Actuator SSR303
  1.  In VERA go in the “Devices”, then “Add Devices” and click “Add” to start the search for a new device (the orange LED flashes slowly in the Z-Wave Gatewa controller VERA).
  2. The actuator when is it not inserted in any Z-Wave network has two red lights are flashing. Press and hold the bottom button > | | <until you see a green light indicates a proper connection to the VERA.
  3. On the Vera Web Devices tab  you will see the thermostat and actuator.


Set the type of boiler

Thermostats with TPI (Time Proportional Integral) have control algorithms in order to reduce thermal shock that occurs normally when using traditional thermostats with two histeresys points.

As a result, a regulatory TPI thermostat maintains comfort level in a much more efficient way than traditional thermostats.

When used with a boiler, the TPI thermostat will help save energy and the control algorithm to manage the boiler to operate in a more consistent way whte compared to older types of thermostats.

The DIP switchers with numbers 7 and 8 must conform  as shown in the diagram:

  • For gas boilers TPI adjustment to 6 cycles per hour (default). TPI 6
  • For oil boilers TPI set to 3 cycles per hour. TPI 3
  • Electric heating TPI adjusted to 12 cycles per hour. TPI 12
TPI Thermostat Settings
TPI Thermostat Settings


Credits to domotica4all for most of the info!