Categorie archief: VERA Blog

Hier vindt u onze ervaringen met VERA Lite en VERA3.

How to use WallC-S remote controller with UI7

In this section we will try to explain how to configure the ZWave.Me WallC-S Remote Controller (ZME_WALLC-S) with the new interface UI7.

Adding the device

First lets add the device. When the device is not connected to any network initially, the include process is straight forward.

Select “Generic Device” and press next till step 3. Inclusion of the new wall controller can be done with pressing button 1 for 2 seconds. The device will be included automatically and the process will finish.

Configuration

To let the wall controller communicate in scene mode with the Vera, we have to change the default settings. When we have a look at the “Device Options” section, Vera will automically configure the Wall Controller with the following parameters:

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

Before we can have the wall controller working in scene mode, we have to change the parameters 11 to 14. The value we need to set here is 4: Send Scenes.

After changing the settings it should look similar to:

WallC-S Configuration Settings
WallC-S Configuration Settings

Scene Triggering

When all went ok, you are ready to set your scenes. Unfortunately this has to be done with a small trick, as the changing variable is “LastSceneID” and not the “sl_SceneActivated” (which is used by Vera to trigger scenes).

Some experiments learn that even when buttons are pressed the “sl_SceneActivated” variable will stay 0. So it is time to make some trigger for that, and execute the code to start scene’s.

First we need to make a scene for activation of the variable “sl_SceneActivated”. Add a new scene, with a trigger on the Wall Controller. Choose when a scene is actived and select 0 as scene number. In this case everytime the controller sends a scene number, this scene will be executed.

WallC-S Scene Selection
WallC-S Scene Selection
WallC-S Scene Activation
WallC-S Scene Activation

LUUP Code

Now its time for the LUUP code, which need to be applied within this scene also:

luup.call_delay('scene_controller', 1)
function scene_controller()
 local lastSceneID= luup.variable_get("urn:micasaverde-com:serviceId:SceneController1", "LastSceneID",
 135)
if (lastSceneID== "11") then
 luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene",
 { SceneNum="1" },0)
 elseif (lastSceneID== "12") then
 luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene",
 { SceneNum="2" },0)
 elseif (lastSceneID== "21") then
 luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene",
 { SceneNum="7" },0)
 elseif (lastSceneID== "22") then
 luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene",
 { SceneNum="2" },0)
 elseif (lastSceneID== "31") then
 luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene",
 { SceneNum="1" },0)
 elseif (lastSceneID== "32") then
 luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene",
 { SceneNum="2" },0)
 elseif (lastSceneID== "41") then
 luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene", { SceneNum="1" },0)
 elseif (lastSceneID== "42") then
 luup.call_action("urn:micasaverde-com:serviceId:HomeAutomationGateway1","RunScene", { SceneNum="2" },0)
 end
end

There are a few things you need to update for this code, corresponding to your own setup.

  • Device number: change 135 to the device number (id) of the wall controller;
  • Change the LastSceneID values corresponding to your needs; this is only an example of the configuration, but more options are possible;
  • Change the SceneNum values to the id’s (can be found in the main Scenes screen) you would like to run.

Using an RGB(W) Bulb in Vera UI5/6

At this moment, there are 3 different kinds of RGB(W) devices on the market. Some are controllers, other are LED bulbs, with the possibility to change colors.

In this document we try to describe how to setup these controllers to use them with Vera UI5/6. In this case we work with the (new) Aeotec RGBW Bulb.

1. First we need to include the controller / bulb into the Vera. We do this in the normal way, by following the manual and the normal inclusion process.

2. Because every module is included as a dimmer, and there is no default support for it to control the colors, we need to install a seperate plugin.

3. To get the plugin to work, we need to install a JSON decoder, because this isn’t installed by default. You can do this with e.g. WinSCP, and upload the following file to “/usr/lib/lua”. The file can be found here: http://code.mios.com/trac/mios_genericutils/export/20/json.lua

4. After installing the file, you can install the app called “RGB Controller”, just from the Apps section.

RGB Controller App
RGB Controller App

5. If all went ok, you should see a new device on the Devices tab. Click on it, and go to settings for configuration of your device.

6. For e.g. the Aeotec bulb, you choose Device type Aeotect RGBW Buld, in combination with the just added device (can be selected from the dropdown).

RGBW Settings
RGBW Settings

7. Save your settings, close the dialog and save your settings again.

8. Now its time to play and try your color wheel.

RGBW Color Wheel
RGBW Color Wheel

EXTRA OPTIONS:

Using the RGBW controller / bulb into advanced scenes / LUA is also possible:

  • Switch on/off the RGBW device
luup.call_action("urn:upnp-org:serviceId:SwitchPower1", "SetTarget", {newTargetValue = 1}, <idPlugin>)
  • Change the RGB color
luup.call_action("urn:upnp-org:serviceId:RGBController1", "SetColorTarget", {newColorTargetValue = "#FF0000"}, <idPlugin>)
  • Change the RGBW color
luup.call_action("urn:upnp-org:serviceId:RGBController1", "SetColorTarget", {newColorTargetValue = "#FF0000FF"}, <idPlugin>)

Sources: http://forum.micasaverde.com/index.php/topic,32613.0.html

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.

Configuration

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:

1,1d,0,2,1d,0,11,1d,5,12,1d,5,13,1d,5,14,1d,5
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:

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

Result

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

thermostat
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

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
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1″,”RunScene”,
{ SceneNum=”12″ },0)
elseif (lastSceneID== “2”) then
luup.call_action(“urn:micasaverde-com:serviceId:HomeAutomationGateway1″,”RunScene”,
{ SceneNum=”11″ },0)
end
end

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:

D_LightSensor1.json
D_LightSensor1.json
D_LightSensor1.json
3.0 KiB
625 Downloads
Details

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:

"LUX

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!

Installing the RFXCOM to the VERA

If you would like Vera to work with non Z-Wave wireless home automation equipment (such as the LightwaveRF, X10, etc) then take a look at the RFXCOM USB Transciever 433,92Mhz. This module gives you the ability to communicate with a large number of products that operate within in the 433Mhz range.

Hooking up the RFXCOM to the VERA is not that hard:

  1. Plug the USB cable of the RFXCOM Transceiver into the back of your Vera;
  2. Once connected you need to upload all the required device files onto our Vera via Apps / Develop Apps / Luup Files. These files can be found by looking at MiCasaVerde RFXrtx433 Plugin Beta3 Code Page (or download directly here);
  3. You need to upload every file seperately. Due to the number of files that need to be uploaded you will need to do this in a couple of batches. Make sure to restart Luup after eacht batch (just select the box);

    Upload files one by one. Restart Luup after each batch.
    Upload files one by one. Restart Luup after each batch.
  4.  After the files uploaded, you now need to Create the master device using Apps / Develop Apps / Create Device, and enter the D_RFXtrx.xml file name into the Upnp Device Filename field.

    Create a new device
    Create a new device
  5. To setup the serial port, choose Serial Port configuration, where you need to change the speed value to 38400 bauds and also select the device named “RFXtrx controller device” from the field “Used by device”. 

    Change baud rate and device type
    Change baud rate and device type
  6. That should be it. Do a “Reload” to make sure everything is reloaded. There should be no error messages and when you go back to your device tab, you will see something like this:There are already found some RFX devices. They will be automatically be shown in the interface when found by the RFXCOM.
    There are already found some RFX devices.

Installing the RFXCOM to the VERA

If you would like Vera to work with non Z-Wave wireless home automation equipment (such as the LightwaveRF, X10, etc) then take a look at the RFXCOM USB Transciever 433,92Mhz. This module gives you the ability to communicate with a large number of products that operate within in the 433Mhz range.

Hooking up the RFXCOM to the VERA is not that hard:

  1. Plug the USB cable of the RFXCOM Transceiver into the back of your Vera;
  2. Once connected you need to upload all the required device files onto our Vera via Apps / Develop Apps / Luup Files. These files can be found by looking at MiCasaVerde RFXrtx433 Plugin Beta3 Code Page (or download directly here);
  3. You need to upload every file seperately. Due to the number of files that need to be uploaded you will need to do this in a couple of batches. Make sure to restart Luup after eacht batch (just select the box);

    Upload files one by one. Restart Luup after each batch.
    Upload files one by one. Restart Luup after each batch.
  4.  After the files uploaded, you now need to Create the master device using Apps / Develop Apps / Create Device, and enter the D_RFXtrx.xml file name into the Upnp Device Filename field.

    Create a new device
    Create a new device
  5. To setup the serial port, choose Serial Port configuration, where you need to change the speed value to 38400 bauds and also select the device named “RFXtrx controller device” from the field “Used by device”. 

    Change baud rate and device type
    Change baud rate and device type
  6. That should be it. Do a “Reload” to make sure everything is reloaded. There should be no error messages and when you go back to your device tab, you will see something like this:There are already found some RFX devices. They will be automatically be shown in the interface when found by the RFXCOM.
    There are already found some RFX devices.

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
zme_kfob_in_en.pdf
131.6 KiB
666 Downloads
Details

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:

Zwave.me Keyfob Parameters
Zwave.me 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!