Alle berichten van Gertjan

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.

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.

Using the Aeon Labs keyfob in Scene Modus on Home Center 2

HC2 Firmware: 4.017 beta

When adding the Aeon Labs Keyfob to the current (beta) firmware can be a bit of a challange. First of all it is difficult to setup the device correctly, and some times, the device won’t function in scene modus.

Inclusion of the device

First let us include the device:

  1. Make sure the keyfob is in management modus (you can easilty check this by pressing button 3. In management modus, it won’t react and no LED will light).
  2. Choose add device on  HC2 to add a new Z-Wave device;
  3. Press button 4 (Learn) just once;
  4. If the HC2 seems to “hang” (no reaction after one minute) stop the proces and try adding it again with one press of the Learn button on the back.

Now switch the mode from management to scene by pressing the mode button once (also located at the back). The switch will be confirmed by a green LED for 2 seconds.

Scene mode

If everything went ok, your device should now be working in scene mode. You can check this also visually by pressing one of the buttons on top. If a green LED will light up, you’re ok and can skip the next step.

If a red LED lights up, you have to set a variable to let the keyfob function in scene mode:

  • Parameter 250 with value 1. This enables scene mode.
  • Wakeup the device by pressing the Learn button on the back for 2 seconds.
setvariable
Set Parameter 250 to value 1

 Keyfob Lua Scene

Now its time to define a scene to “catch” the scene ID’s sent by the remote controller.

Create a LUA based scene by selecting “Add scene in LUA”.  Copy the following lines of code and adjust where needed (put the ID from your keyfob here).

You can test the scene by selecting Start and pressing one of the buttons on the keyfob.

--[[ 
%% properties 
18 sceneActivation 
%% globals 
--]] 

local ButtonPressed = fibaro:getValue(18, "sceneActivation") 

if ( tonumber(ButtonPressed) == 1) then 
  fibaro:debug("Keyfob button 1 pressed") 
elseif ( tonumber(ButtonPressed) == 2) then 
  fibaro:debug("Keyfob button 2 pressed") 
elseif ( tonumber(ButtonPressed) == 3) then 
  fibaro:debug("Keyfob button 3 pressed") 
elseif ( tonumber(ButtonPressed) == 4) then 
  fibaro:debug("Keyfob button 4 pressed") 
elseif ( tonumber(ButtonPressed) == 5) then 
  fibaro:debug("Keyfob button 5 pressed") 
elseif ( tonumber(ButtonPressed) == 6) then 
  fibaro:debug("Keyfob button 6 pressed") 
elseif ( tonumber(ButtonPressed) == 7) then 
  fibaro:debug("Keyfob button 7 pressed") 
elseif ( tonumber(ButtonPressed) == 8) then 
  fibaro:debug("Keyfob button 8 pressed") 
else
  fibaro:debug("No response") 
end

Using the Aeon Labs keyfob in Scene Modus on Home Center 2

HC2 Firmware: 4.017 beta

When adding the Aeon Labs Keyfob to the current (beta) firmware can be a bit of a challange. First of all it is difficult to setup the device correctly, and some times, the device won’t function in scene modus.

Inclusion of the device

First let us include the device:

  1. Make sure the keyfob is in management modus (you can easilty check this by pressing button 3. In management modus, it won’t react and no LED will light).
  2. Choose add device on  HC2 to add a new Z-Wave device;
  3. Press button 4 (Learn) just once;
  4. If the HC2 seems to “hang” (no reaction after one minute) stop the proces and try adding it again with one press of the Learn button on the back.

Now switch the mode from management to scene by pressing the mode button once (also located at the back). The switch will be confirmed by a green LED for 2 seconds.

Scene mode

If everything went ok, your device should now be working in scene mode. You can check this also visually by pressing one of the buttons on top. If a green LED will light up, you’re ok and can skip the next step.

If a red LED lights up, you have to set a variable to let the keyfob function in scene mode:

  • Parameter 250 with value 1. This enables scene mode.
  • Wakeup the device by pressing the Learn button on the back for 2 seconds.
setvariable
Set Parameter 250 to value 1

 Keyfob Lua Scene

Now its time to define a scene to “catch” the scene ID’s sent by the remote controller.

Create a LUA based scene by selecting “Add scene in LUA”.  Copy the following lines of code and adjust where needed (put the ID from your keyfob here).

You can test the scene by selecting Start and pressing one of the buttons on the keyfob.

--[[ 
%% properties 
18 sceneActivation 
%% globals 
--]] 

local ButtonPressed = fibaro:getValue(18, "sceneActivation") 

if ( tonumber(ButtonPressed) == 1) then 
  fibaro:debug("Keyfob button 1 pressed") 
elseif ( tonumber(ButtonPressed) == 2) then 
  fibaro:debug("Keyfob button 2 pressed") 
elseif ( tonumber(ButtonPressed) == 3) then 
  fibaro:debug("Keyfob button 3 pressed") 
elseif ( tonumber(ButtonPressed) == 4) then 
  fibaro:debug("Keyfob button 4 pressed") 
elseif ( tonumber(ButtonPressed) == 5) then 
  fibaro:debug("Keyfob button 5 pressed") 
elseif ( tonumber(ButtonPressed) == 6) then 
  fibaro:debug("Keyfob button 6 pressed") 
elseif ( tonumber(ButtonPressed) == 7) then 
  fibaro:debug("Keyfob button 7 pressed") 
elseif ( tonumber(ButtonPressed) == 8) then 
  fibaro:debug("Keyfob button 8 pressed") 
else
  fibaro:debug("No response") 
end

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

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