Collection of working z-wave configs

naturalblaze · August 16, 2015, 10:50pm

I have two of them working in my setup. Here is what I had to configure in Habmin. On Configurgation tab, Binding, z-wave binding, expand to your Aeon multisensor node, expand Configuration Parameters.
3: On Time: 30 (this is just personal preference of 30 second reports, I wanted to see how long the battery would last. so far have 58% left after about a month and a half.)
4: Motion Sensor: Enabled
5: Command to send when movement: Send binary report
101: Which reports to send automatically in timing to group 1: 225
102: group 2: 0
103: group 3: 0
111: Interval to send out reports to group 1: 240 (also personal preference for testing battery life)
112: Interval to send out reports to group 2: 720
113: Interval to send out reports to group 3: 720

Hope this helps get everything working. I found those parameters on someones guide when doing a google search

jon · August 17, 2015, 1:49am

Smoke detector from Monoprice. They identify as Vision Security ZS6101.

> Contact	iSmokeSensorMasterAlarm			"Master Status [%s]"		<fire>		(gSmokeSensorMaster)		{ zwave="8:command=SENSOR_BINARY,respond_to_basic=true" }
> Number	iSmokeSensorMasterBattery		"Master Battery [%s]"		<battery>	(gSmokeSensorMaster)		{ zwave="8:command=BATTERY" }

mikael_trieb · August 17, 2015, 6:42pm

Thanks!
Feels good to finally see those values

naturalblaze · August 18, 2015, 4:36pm

Jim,
That Aeotec Door/Window sensor you have configs for. I just got one and I have had nothing but problems trying to get it configured. I was wondering if you had any advice or things you had to do to get it working? I can’t seem to get it initialized correctly (it will never create my node.xml file), I was able to get the open/close working first but the battery and alarm never reported. I messed with the Habmin config and got the alarm and battery working but now the door open/close is broken and the magnet trigger just sends a battery report, lol. Now I’m wishing I had just left it alone so the door sensor still worked. Any help/suggestions would be great.

xsnrg · August 19, 2015, 2:46am

Well, I can tell you I have parameter 121 set to 256 and I am getting alerts back to the Z stick every time the door opens. Other than that, nothing I can see that is special. The battery life is still 100%. When first setting it up, I had to take a paperclip and push the little center button a few times. Never had to hold it in or anything. Now when I reset OpenHAB (running OH2 and Habmin2), and I want it to register things, I can just poke the button one time, and it creates the xml without issue. The only other thing to mention is it is part of a mesh and has at least 2 neighbors that have line power. It really has been a dependable device to date.

Jim

jkarsten · August 22, 2015, 4:23pm

Hello,

i have the Aeon Z-Stick on my Windows 7 - openHAB NUC.
At the moment i use a
Fibaro RGBW Controller … the Full Item File is:

Group	gWohnzimmer		"Wohnzimmer"			<sofa>	(gAlles)
Group	gwzRGBW			"TV Rücklicht Erweitert"	<sofa>	(gWohnzimmer)

Color 	wzRGBW 		"TV Rücklicht" 		<slider> 	(gwzRGBW)
Dimmer 	wzRGBW_All 	"Helligkeit [%d %%]" 	<switch> 	(gwzRGBW)	{zwave="2"}
Dimmer	wzRGBW_R 	"Rot [%d %%]" 		<switch> 	(gwzRGBW)	{zwave="2:2"}
Dimmer 	wzRGBW_G 	"Grün [%d %%]" 		<switch> 	(gwzRGBW)	{zwave="2:3"}
Dimmer 	wzRGBW_B 	"Blau [%d %%]" 		<switch> 	(gwzRGBW)	{zwave="2:4"}
Dimmer 	wzRGBW_W 	"Weiß [%d %%]" 		<switch> 	(gwzRGBW)	{zwave="2:5"}

Switch  wzRGBW_Switch	"Schalter Alle"		<switch> 	(gwzRGBW)	{ zwave="2:1"}
Switch  wzRGBW_R_Switch	"Schalter Rot"		<switch> 	(gwzRGBW)	{ zwave="2:2"}
Switch  wzRGBW_G_Switch "Schalter Grün"		<switch> 	(gwzRGBW)	{ zwave="2:3"}
Switch  wzRGBW_B_Switch	"Schalter Blau"		<switch> 	(gwzRGBW)	{ zwave="2:4"}
Switch  wzRGBW_W_Switch	"Schalter Weiß"         <switch> 	(gwzRGBW)	{ zwave="2:5"}

Number wzRGBW_Power     "Stromverbrauch [%.1f W]"   	<energy> 	(gwzRGBW)	{ zwave="2:command=sensor_multilevel"}
Number wzRGBW_Energy    "Gesamtverbrauch [%.2f KWh]"   	<energy> 	(gwzRGBW)	{ zwave="2:command=meter", refresh_interval=60}

I have only the Colorpicker in the Sitemap
And the rule for the Colorpicker is:

import org.openhab.core.library.types.*

var HSBType hsbValue
var String redValue
var String blueValue
var String greenValue

rule "Set wzRGBW Value"
when
	Item wzRGBW changed
then
	hsbValue = wzRGBW.state as HSBType
        redValue = hsbValue.red.intValue.toString
        greenValue = hsbValue.green.intValue.toString
        blueValue = hsbValue.blue.intValue.toString

        sendCommand(wzRGBW_R,redValue)
        sendCommand(wzRGBW_G,greenValue)
        sendCommand(wzRGBW_B,blueValue)
end

i have sometimes a Warning Message … i dont know why ???

2015-08-22 18:12:21.124 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: Generating message failed for command class = SWITCH_MULTILEVEL
2015-08-22 18:12:21.172 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: Generating message failed for command class = SWITCH_MULTILEVEL
2015-08-22 18:12:21.174 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: Generating message failed for command class = SWITCH_MULTILEVEL
2015-08-22 18:12:21.177 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: Generating message failed for command class = SWITCH_MULTILEVEL
2015-08-22 18:12:21.181 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: Generating message failed for command class = SWITCH_MULTILEVEL
2015-08-22 18:12:21.186 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: Generating message failed for command class = SWITCH_MULTILEVEL
2015-08-22 18:12:21.189 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: Generating message failed for command class = SWITCH_MULTILEVEL
2015-08-22 18:12:21.194 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: Generating message failed for command class = SWITCH_MULTILEVEL
2015-08-22 18:12:21.198 [WARN ] [.b.z.i.c.ZWaveConverterHandler] - NODE 2: Generating message failed for command class = SWITCH_MULTILEVEL

The second Device is a Fibaro Rollershutter FGRM-222

Group	gKind			"Kinderzimmer"				<boy3>		(gAlles)
Group	gkdSHUTTER		"Kinderzimmer Außenrollo Erweitert"	<rollershutter>	(gKind)

Rollershutter kdSHUTTER		"Außenrollo [%d %%]" 				(gkdSHUTTER)	{zwave="3:command=switch_multilevel,invert_state=false,invert_percent=true"}

Number kdSHUTTER_Power		"Stromverbrauch [%.1f W]"	<energy> 	(gkdSHUTTER)	{ zwave="3:command=sensor_multilevel"}
Number kdSHUTTER_Energy		"Gesamtverbrauch [%.2f KWh]"	<energy> 	(gkdSHUTTER)	{ zwave="3:command=meter" }

wolf_from_the_north · August 27, 2015, 12:58pm

Fibaro Smoke detector

Contact Z_Kitchen_Smoke “Smokedetector_K is[%s]” (Smoke_Alarm) {zwave=“6:command=sensor_alarm,alarm_type=1” }

Contact Z_Kitchen_Tamper “Smoke_sensor_K Tamper is[MAP(en.map):%s]” (Tamper_Alarm) { zwave=“6:command=sensor_alarm,alarm_type=0” }

Number Z_Kitchen_Battery “Smoke_sensor_batt [%d %%]” (Battery_Levels) {zwave=“6:command=battery” }

Number Z_Kitchen_Temp “Kitchen_temperature [%.1f°C]” (Temperatures) {zwave=“6:command=sensor_multilevel,sensor_type=1” }

wolf_from_the_north · August 27, 2015, 12:58pm

Fibaro RGBW Controller + white value

Group gRGBW “Living RGBW Licht”
Dimmer RGBWControllerAll “RGBW Licht dimmer [%d %%]” (gRGBW,Lights) { zwave=“7:1” }
Dimmer RGBWControllerALL_Status “RGBW Licht dimmer [%d %%]” (gRGBW,Lights) { zwave=“7:0” }
Color RGBW “RGBW Licht kleur” (gRGBW)
Dimmer RGBWControllerR “RGBW Light Red [%d %%]” { zwave=“7:2” }
Dimmer RGBWControllerG “RGBW Light Green [%d %%]” { zwave=“7:3” }
Dimmer RGBWControllerB “RGBW Light Blue [%d %%]” { zwave=“7:4” }
white RGBW “RGBW Licht Warm Wit” (gRGBW,Lights)
Dimmer RGBWControllerW “RGBW Light White [%d %%]” { zwave=“7:5” }
Number RGBW_Power “RGBW_Power [%.1f W]” {zwave=“7:0:command=sensor_multilevel” }
Number RGBW_Verbruik “RGBW_Verbruik [%.2f kWh]” { zwave=“7:0:command=meter” }

wolf_from_the_north · August 27, 2015, 1:00pm

Fibaro Universal Sensor

Contact Z_deurbel0 “Z_deurbel_sensor” { zwave=“8:0:command=SENSOR_BINARY,respond_to_basic=TRUE” }
Contact Z_deurbel1 “Z_deurbel_input1” { zwave=“8:1:command=SENSOR_BINARY,respond_to_basic=TRUE” }
Contact Z_deurbel2 “deurbel” { zwave=“8:2:command=SENSOR_BINARY,respond_to_basic=TRUE” }

sihui · September 2, 2015, 8:00am

I had a hard time of setting up the Zwave.me Double paddle wall switch WCD1 (this also works with the newer model WCD2), so I would like to share the inputs I got from different forums:

Include the device (send additional NIF according to the manual if it does not show up right away)
Go to habmin and change the configuration parameters to:
11: Send scenes 12: Send scenes 13: Send scenes 14: Send scenes
Set all four Association Groups to a member for your controller (for example Group 1 … Node 1 … Member and so on)
Again, send some NIF to transfer the new values to the device
Start openhab in debug mode, push all buttons at least once and find out the scene numbers in openhab.log, you will need those for your items:
Set up your items:

Switch WCD1_1_BUT1 “Test BUT 1” { zwave=“7:command=SCENE_ACTIVATION,scene=11,state=1” }
Switch WCD1_1_BUT3 “Test BUT 3” { zwave=“7:command=SCENE_ACTIVATION,scene=12,state=0” }
Switch WCD1_1_BUT2 “Test BUT 2” { zwave=“7:command=SCENE_ACTIVATION,scene=21,state=1” }
Switch WCD1_1_BUT4 “Test BUT 4” { zwave=“7:command=SCENE_ACTIVATION,scene=22,state=0” }
Switch WCD1_1_SW1 “Test WCD SW 1” (gTest)
Switch WCD1_1_SW2 “Test WCD SW 2” (gTest)

6.Set up your rules:

    rule "WCD1 Switch 1 ON"
    when
    Item WCD1_1_BUT1 received update ON
    then
    sendCommand(WCD1_1_SW1, ON)
    end

    rule "WCD1 Switch 1 OFF"
    when
    Item WCD1_1_BUT3 received update ON
    then
    sendCommand(WCD1_1_SW1, OFF)
    end

    rule "WCD1 Switch 2 ON"
    when
    Item WCD1_1_BUT2 received update ON
    then
    sendCommand(WCD1_1_SW2, ON)
    end

    rule "WCD1 Switch 2 OFF"
    when
    Item WCD1_1_BUT4 received update ON
    then
    sendCommand(WCD1_1_SW2, OFF)
    end

Now you are able to switch WCD1_1_SW1 with a push of buttons 1 and 3 to ON and OFF and WCD1_1_SW2 with buttons 2 and 4.

Have fun.

neil_renaud · September 2, 2015, 1:16pm

Heat-it Thermostat

Number Temperature { zwave=“4:0:command=SENSOR_MULTILEVEL,sensor_type=1” }
Number Set_Temp { zwave=“4:command=THERMOSTAT_SETPOINT,setpoint_type=1,setpoint_scale=0” }
Number Mode {zwave=“4:0:command=THERMOSTAT_MODE” }
DateTime LastUpdated { zwave=“4:command=info,item=LAST_UPDATE”}

Everspring Wireless Dimmer ADA131

Dimmer Light { zwave=“6:command=SWITCH_MULTILEVEL,respond_to_basic=true” }

the.neon · September 2, 2015, 6:45pm

Z-Weather Weather Station

Number  Windspeed       "Wind [%.2f m/s]"       <wind>  (weather_station)               { zwave="5:command=sensor_multilevel,sensor_type=6,refresh_interval=300" }
Number  Luminance       "Luminance [%.1f %%]"   (weather_station)               { zwave="5:command=sensor_multilevel,sensor_type=3,refresh_interval=300" }
Number  RelativeHumidity        "Humidity [%.1f %%]"    (weather_station)               { zwave="5:command=sensor_multilevel,sensor_type=5,refresh_interval=300" }
Number  DewPoint        "Dew Point [%.1f °C]"   (weather_station)               { zwave="5:command=sensor_multilevel,sensor_type=11,refresh_interval=300" }
Number  BarometricPressure      "Barometric Pressure [%.1f kPa]"        (weather_station)               { zwave="5:command=sensor_multilevel,sensor_type=9,refresh_interval=300" }
Number  TempWeatherStation      "Temp Weatherstation [%.1f °C]" <temperature>   (weather_station)               { zwave="5:command=sensor_multilevel,sensor_type=1,refresh_interval=300" }
Number  BatteryWeatherStation   "Battery Weatherstation [%.2f %%]"      { zwave="5:command=battery,refresh_interval=600" }

smar · September 3, 2015, 7:48pm

Here’s the temperature item for the Fibaro FGK-101 door sensor (requires DS18B20 to be added):

Number  Temp_UtilityRoom "Utility room temperature [%.1f °C]" { zwave="7:2:command=SENSOR_MULTILEVEL" }

dan12345 · September 7, 2015, 10:35am

Fibaro FGS221 Relay Switch 2x1.5kW:

Switch	FibaroSwitch1	"Relay 1"	{ zwave="12:1:command=switch_binary" }
Switch	FibaroSwitch2	"Relay 2"	{ zwave="12:2:command=switch_binary" }

(I don’t use the switch inputs on the device)

KjetilA · September 7, 2015, 12:37pm

Lot’s of useful information in this thread!

It would be great if this kind of information was available on the Wiki in as browsable/searchable way, e.g. structured by manufacturer (Fibaro, Vision, etc.) and model (e.g. FGK-101, FGMS-001, etc.)

What do you think?

smar · September 7, 2015, 3:54pm

Here’s another one that took me a while to get working - motion sensor on the Aeon Multisensor 6:

Contact	Sensor_Livingroom_PIR	"Living room PIR"	<pir>	(Sensors)		{ zwave="14:0:command=SENSOR_BINARY,sensor_type=12,respond_to_basic=TRUE" }

The rest of the items for the Multi Sensor 6 can be set up using the same commands as for the Multi Sensor 4 given earlier on by @xsnrg.

sihui · September 7, 2015, 4:55pm

Regarding the endpoint “0” you (all) should read:

Continuing the discussion from Association doesn't update the associated item status:

Association doesn't update the associated item status

Association doesn't update the associated item status

In any case, I’d suggest specifying “5:0” in your binding.

No - this is not valid and shouldn’t be used. While it MAY work, it also may cause problems, and you shouldn’t use ‘0’ (as per the wiki - see below).

However, you may be right in that the endpoint might be wrong. Can you provide the item definition, and also the XML (from /etc/zwave/node5.xml).

From the wiki -:

The endpoint ID is only required/allowed when using the multi_instance command class. In case a node consists of multiple instances or endpoints, the instance number can be specified using this value. The default value is not to use the multi_instance command class - the number must be positive and must not be 0.

rm65453 · September 29, 2015, 12:01am

here is what i have for ecolink tiltzwave1 sensor for garage door.

Group DoorsWindows “Doors and Windows”
Contact GarageDoor “Garage Door is [MAP(en.map):%s]” (DoorsWindows){zwave=“3:command=SENSOR_BINARY”}

bob_dickenson · September 29, 2015, 12:51am

Personally, I always put groups BEFORE the zwave config. Perhaps superstitious behavior, but…

e.g.

Contact GarageDoor "Garage Door is [MAP(en.map):%s]" (DoorsWindows) {zwave="3:command=SENSOR_BINARY"}

rm65453 · September 29, 2015, 12:52am

Fixed. thanks bob.