How to get my first rule running

I’m trying to get my first rule up and running.

Plan is to get the Fibaro Motion Sensor via Z-Wave to control the light.

Adding the sensor brings this traces:

2018-01-20 22:36:07.390 [hingStatusInfoChangedEvent] - 'zwave:device:597362ca:node2' changed from UNINITIALIZED to INITIALIZING
2018-01-20 22:36:07.397 [hingStatusInfoChangedEvent] - 'zwave:device:597362ca:node2' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2018-01-20 22:36:07.434 [hingStatusInfoChangedEvent] - 'zwave:device:597362ca:node2' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to UNINITIALIZED
2018-01-20 22:36:07.449 [hingStatusInfoChangedEvent] - 'zwave:device:597362ca:node2' changed from UNINITIALIZED to UNINITIALIZED (HANDLER_MISSING_ERROR)
2018-01-20 22:36:07.543 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_597362ca_node2_sensor_binary-zwave:device:597362ca:node2:sensor_binary' has been added.
2018-01-20 22:36:07.577 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_597362ca_node2_sensor_temperature-zwave:device:597362ca:node2:sensor_temperature' has been added.
2018-01-20 22:36:07.610 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_597362ca_node2_sensor_seismicintensity-zwave:device:597362ca:node2:sensor_seismicintensity' has been added.
2018-01-20 22:36:07.641 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_597362ca_node2_sensor_luminance-zwave:device:597362ca:node2:sensor_luminance' has been added.
2018-01-20 22:36:07.672 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_597362ca_node2_alarm_motion-zwave:device:597362ca:node2:alarm_motion' has been added.
2018-01-20 22:36:07.701 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_597362ca_node2_alarm_tamper-zwave:device:597362ca:node2:alarm_tamper' has been added.
2018-01-20 22:36:07.730 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_597362ca_node2_battery_level-zwave:device:597362ca:node2:battery-level' has been added.
2018-01-20 22:36:07.760 [.ItemChannelLinkAddedEvent] - Link 'zwave_device_597362ca_node2_alarm_general-zwave:device:597362ca:node2:alarm_general' has been added.
2018-01-20 22:36:07.801 [hingStatusInfoChangedEvent] - 'zwave:device:597362ca:node2' changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2018-01-20 22:36:07.834 [hingStatusInfoChangedEvent] - 'zwave:device:597362ca:node2' changed from INITIALIZING to OFFLINE (BRIDGE_OFFLINE): Controller is offline
2018-01-20 22:36:07.840 [hingStatusInfoChangedEvent] - 'zwave:device:597362ca:node2' changed from OFFLINE (BRIDGE_OFFLINE): Controller is offline to ONLINE
2018-01-20 22:36:07.886 [me.event.ThingUpdatedEvent] - Thing 'zwave:device:597362ca:node2' has been updated.

I have no idea how to use an item in the rule.
I’ve tried something like this, and I assume I should see a message in the log file, but I can’t see it.

rule "My first rule"
when
    Item zwave_device_597362ca_node2_sensor_binary changed to ON
then
    logInfo("MotionSensor", "Binary")
    ...
end

I am pretty sure than in order to use rules, channels must be defined in an ITEMS file.

You would then use the channels unique ID as defined in the items file.

Hi Mike,

i have the same Motion Sensor from Fibaro and as Light a Fibaro RGBW Controller. I use the channel white.
Items:

// Bewegungsmelder - Z036
Group	gKu_Bewegung			"Küche Bewegunsgmelder"						                <motion>		        (gKueche)
Switch	Ku_Bewegung				"Küche Bewegung" 							                <motion> 		        (gKu_Bewegung, gBewegung)	{ channel="zwave:device:0145ca4e:node55:alarm_motion" }
Switch	Ku_Bewegung_Intrusion	"Küche Intrusion" 							                <Alarm>   	            (gKu_Bewegung) 				{ channel="zwave:device:0145ca4e:node55:alarm_tamper" }
Number	Ku_Beweg_Batterie		"Küche Bewegunsgmelder Batterie [%s]"		                <battery>		        (gKu_Bewegung, gBatterie) 	{ channel="zwave:device:0145ca4e:node55:battery-level" }
Number	Ku_Beweg_Helligkeit		"Küche Bewegunsgmelder Helligkeit [%s]"		                <sun>			        (gKu_Bewegung, gHelligkeit)	{ channel="zwave:device:0145ca4e:node55:sensor_luminance" }
Number	Ku_Beweg_Temperatur		"Küche Bewegunsgmelder Temperatur [%s]"		                <temperature>	        (gKu_Bewegung, gTemperatur)	{ channel="zwave:device:0145ca4e:node55:sensor_temperature" }
Number	Ku_Beweg_seismic		"Küche Bewegunsgmelder Seismischer Wert"	                <movecontrol>    	    (gKu_Bewegung)          	{ channel="zwave:device:0145ca4e:node55:sensor_seismicintensity" }

// Beleuchtung Küchenschrank - Z037
Group	gKu_Schrank					"Küchenschrank Licht"						                <colorlight>        (gKueche)
Dimmer	Ku_Schrank_Helligkeit		"Küchenschrank Helligkeit"					                <light>		        (gKu_Schrank)  	[ "Lighting" ]	{ channel="zwave:device:0145ca4e:node37:switch_dimmer" }
Dimmer 	Ku_Schrank_Weiss 			"Küche Arbeitsplatte"						                <light> 	        (gKu_Schrank) 	[ "Lighting" ] 	{ channel="zwave:device:0145ca4e:node37:switch_dimmer5" }
Dimmer 	Ku_Schrank_Rot 				"Küchenschrank Rot" 						                <light> 	        (gKu_Schrank) 	[ "Lighting" ] 	{ channel="zwave:device:0145ca4e:node37:switch_dimmer2" }
Dimmer 	Ku_Schrank_Gruen 			"Küchenschrank Gruen" 						                <light> 	        (gKu_Schrank) 	[ "Lighting" ] 	{ channel="zwave:device:0145ca4e:node37:switch_dimmer3" }
Dimmer 	Ku_Schrank_Blau 			"Küchenschrank Blau" 						                <light> 	        (gKu_Schrank) 	[ "Lighting" ] 	{ channel="zwave:device:0145ca4e:node37:switch_dimmer4" }
Color	Ku_Schrank_Color			"Küchenschrank Color" 						                <colorlight>        (gKu_Schrank) 					{ channel="zwave:device:0145ca4e:node37:color_color" }
Number 	Ku_Schrank_Power 			"Küchenschrank Stromverbrauch"				                <energy> 		    (gKu_Schrank, gPower) 			{ channel="zwave:device:0145ca4e:node37:sensor_power" }
Number 	Ku_Schrank_Electric_kWh 	"Küchenschrank Gesamtverbrauch [%.1f kWh]"	                <energy> 		    (gKu_Schrank) 					{ channel="zwave:device:0145ca4e:node37:meter_kwh" }
Number 	Ku_Schrank_Electric_watt	"Küchenschrank Stromverbrauch [%.1f W]"		                <energy> 		    (gKu_Schrank) 					{ channel="zwave:device:0145ca4e:node37:meter_watts" }

My rule looks like:

// Bewegungsmelder Küche im Nachtmodos
rule "Kueche Bewegung AN"
when
    Item Ku_Bewegung changed from OFF to ON 
then
   	if(Modus.state == "Nachtmodus") {
		sendCommand(Ku_Schrank_Weiss, 5)
		sendCommand(Ku_Schrank_Weiss, ON)
	}
end

rule "Kueche Bewegung AUS"
when
    Item Ku_Bewegung changed from ON to OFF 
then
   	if(Modus.state == "Nachtmodus") {
		sendCommand(Ku_Schrank_Weiss, OFF)
	}
end

I hope this will help.

Jörg

Not true. One can use Items in Rules no matter how they are defined.

But the Item must be linked to the Channel on the Thing. Based on the OP’s Item name and the link events in the log I’m going to guess they are using Simple Mode which automatically creates Items for each Channel named the same as the Channel ID.

I’m still not getting it to work.

Here is my default.items

// Bewegungsmelder - Z036
Group	gBad_Bewegung			"Bad Bewegunsgmelder"						<motion>		        (gBad)
Switch	Bad_Bewegung			"Bad Bewegung" 							    <motion> 		        (gBad_Bewegung, gBewegung)		{ channel="zwave:device:597362ca:node2:alarm_motion" }
Switch	Bad_Bewegung_Intrusion	"Bad Intrusion" 							<Alarm>   	            (gBad_Bewegung) 				{ channel="zwave:device:597362ca:node2:alarm_tamper" }
Number	Bad_Beweg_Batterie		"Bad Bewegunsgmelder Batterie [%s]"		    <battery>		        (gBad_Bewegung, gBatterie) 		{ channel="zwave:device:597362ca:node2:battery-level" }
Number	Bad_Beweg_Helligkeit	"Bad Bewegunsgmelder Helligkeit [%s]"		<sun>			        (gBad_Bewegung, gHelligkeit)	{ channel="zwave:device:597362ca:node2:sensor_luminance" }
Number	Bad_Beweg_Temperatur	"Bad Bewegunsgmelder Temperatur [%s]"		<temperature>	        (gBad_Bewegung, gTemperatur)	{ channel="zwave:device:597362ca:node2:sensor_temperature" }
Number	Bad_Beweg_seismic		"Bad Bewegunsgmelder Seismischer Wert"	    <movecontrol>    	    (gBad_Bewegung)          		{ channel="zwave:device:597362ca:node2:sensor_seismicintensity" }

// Beleuchtung Badnschrank - Z037
Group	gBad_Schrank				"Bad Licht"				<colorlight>        (gKueche)
Dimmer	Bad_Schrank_Helligkeit		"Bad Helligkeit"		<light>		        (gBad_Schrank)  	[ "Lighting" ]	{ channel="milight:rgbwwLed:eae08b75:0:ledbrightness" }
Dimmer 	Bad_Schrank_Farbtemperatur	"Bad Farbtemperatur"	<light> 	        (gBad_Schrank) 		[ "Lighting" ] 	{ channel="milight:rgbwwLed:eae08b75:0:ledtemperature" }
Color	Bad_Schrank_Color			"Bad Color" 			<colorlight>        (gBad_Schrank) 						{ channel="milight:rgbwwLed:eae08b75:0:ledcolor" }

and the default.rules

// Bewegungsmelder Küche im Nachtmodos
rule "Bad Bewegung AN"
when
    Item Bad_Bewegung changed from OFF to ON 
then
   	logInfo("MotionSensor", "Bad_Bewegung OFF -> ON")
	sendCommand(Bad_Schrank_Helligkeit, 100)
end

rule "Bad Bewegung AUS"
when
    Item Bad_Bewegung changed from ON to OFF 
then
   	logInfo("MotionSensor", "Bad_Bewegung ON -> OFF")
	sendCommand(Bad_Schrank_Helligkeit, 0)
end

and the default.sitemap

sitemap default label="My first sitemap"
{
    Switch item=Bad_Bewegung 			label="Fibaro Bewegung"
    Switch item=Bad_Bewegung_Intrusion 	label="Fibaro Alarm"
    Switch item=Bad_Schrank_Helligkeit 	label="MiLight Helligkeit"
}

It does not work when triggering the motion sensor. The led at the fibaro flashes shortly, so motion is being detected.
I can’t see any thing in the log and light isn’t switch either.

Manually switching the “Fibaro Bewegung” in the sitemap triggers the rule. Meaning the light is being switched and an entry is written to the log.

What am I’m doing wrong.

can anybody give me a good hint?

I’m struck.
How can I debug such an issue?

Can you set the log level of the zwave binding to DEBUG in Karaf?

http://www.cd-jackson.com/index.php/openhab/5-zwave-debugging-openhab

You then should see something like this (taken from a fibaro door contact) when the sensor is triggered.

2018-01-26 22:25:42.473 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 8: Incoming command class MULTI_INSTANCE
2018-01-26 22:25:42.477 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 8: Received MULTI_INSTANCE command V0
2018-01-26 22:25:42.481 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 8: Requested Command Class = ALARM (0x71)
2018-01-26 22:25:42.485 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 8: Originating Command Class ALARM (0x71) was on the root node.
2018-01-26 22:25:42.489 [DEBUG] [class.ZWaveMultiInstanceCommandClass] - NODE 8: Endpoint = 0, calling handleApplicationCommandRequest.
2018-01-26 22:25:42.493 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: Received ALARM command V5
2018-01-26 22:25:42.497 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: Process NOTIFICATION_REPORT V5
2018-01-26 22:25:42.500 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: NOTIFICATION report - 0 = 0, event=23, status=255
2018-01-26 22:25:42.505 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 8: Alarm Type = ACCESS_CONTROL (0)
2018-01-26 22:25:42.507 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2018-01-26 22:25:42.510 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2018-01-26 22:25:42.512 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2018-01-26 22:25:42.516 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2018-01-26 22:25:42.518 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 23, type OpenClosedType
2018-01-26 22:25:42.521 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION 3
2018-01-26 22:25:42.523 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 8: Updating channel state zwave:device:86910632:node8:sensor_door to CLOSED [OpenClosedType]
2018-01-26 22:25:42.527 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION

==> /var/log/openhab2/events.log <==

2018-01-26 22:25:42.532 [vent.ItemStateChangedEvent] - Door_Terrace_GroundFloor changed from OPEN to CLOSED

If not, you should try re-include the sensor again. Battery devices sometimes are a bit “bitchy” during inclusion.
Are the other items from this sensor working?

I can see some traces after readding the sensor, but they just seem to be caused by readding.

==> /var/log/openhab2/openhab.log <==
2018-01-26 22:41:27.819 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising Thing Node...
2018-01-26 22:41:27.822 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising channel zwave:device:597362ca:node2:sensor_binary
2018-01-26 22:41:27.824 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:597362ca:node2:sensor_binary
==> /var/log/openhab2/events.log <==
2018-01-26 22:41:27.824 [vent.ConfigStatusInfoEvent] - ConfigStatusInfo [configStatusMessages=[]]
==> /var/log/openhab2/openhab.log <==
2018-01-26 22:41:27.825 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising poll channel zwave:device:597362ca:node2:sensor_binary
2018-01-26 22:41:27.827 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:597362ca:node2:sensor_binary
2018-01-26 22:41:27.829 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:597362ca:node2:sensor_binary
2018-01-26 22:41:27.830 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising channel zwave:device:597362ca:node2:sensor_temperature
2018-01-26 22:41:27.833 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:597362ca:node2:sensor_temperature
2018-01-26 22:41:27.834 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising poll channel zwave:device:597362ca:node2:sensor_temperature
2018-01-26 22:41:27.835 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:597362ca:node2:sensor_temperature
2018-01-26 22:41:27.837 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising channel zwave:device:597362ca:node2:sensor_seismicintensity
2018-01-26 22:41:27.839 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:597362ca:node2:sensor_seismicintensity
2018-01-26 22:41:27.840 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising poll channel zwave:device:597362ca:node2:sensor_seismicintensity
2018-01-26 22:41:27.842 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:597362ca:node2:sensor_seismicintensity
2018-01-26 22:41:27.843 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising channel zwave:device:597362ca:node2:sensor_luminance
2018-01-26 22:41:27.845 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:597362ca:node2:sensor_luminance
2018-01-26 22:41:27.847 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising poll channel zwave:device:597362ca:node2:sensor_luminance
2018-01-26 22:41:27.848 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:597362ca:node2:sensor_luminance
2018-01-26 22:41:27.850 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising channel zwave:device:597362ca:node2:alarm_motion
2018-01-26 22:41:27.852 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:597362ca:node2:alarm_motion
2018-01-26 22:41:27.853 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising poll channel zwave:device:597362ca:node2:alarm_motion
2018-01-26 22:41:27.854 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:597362ca:node2:alarm_motion
2018-01-26 22:41:27.856 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising channel zwave:device:597362ca:node2:alarm_tamper
2018-01-26 22:41:27.858 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:597362ca:node2:alarm_tamper
2018-01-26 22:41:27.859 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising poll channel zwave:device:597362ca:node2:alarm_tamper
2018-01-26 22:41:27.861 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:597362ca:node2:alarm_tamper
2018-01-26 22:41:27.862 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising channel zwave:device:597362ca:node2:battery-level
2018-01-26 22:41:27.864 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:597362ca:node2:battery-level
2018-01-26 22:41:27.866 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising poll channel zwave:device:597362ca:node2:battery-level
2018-01-26 22:41:27.867 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:597362ca:node2:battery-level
2018-01-26 22:41:27.869 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising channel zwave:device:597362ca:node2:alarm_general
2018-01-26 22:41:27.871 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising cmd channel zwave:device:597362ca:node2:alarm_general
2018-01-26 22:41:27.872 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising poll channel zwave:device:597362ca:node2:alarm_general
2018-01-26 22:41:27.874 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Initialising state channel zwave:device:597362ca:node2:alarm_general
2018-01-26 22:41:27.875 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling intialised at 1800 seconds - start in 1800000 milliseconds.
2018-01-26 22:41:27.981 [DEBUG] [ve.internal.protocol.ZWaveController] - Stopping inclusion timer.
2018-01-26 22:41:27.985 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Ending INCLUSION mode.
2018-01-26 22:41:27.987 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2018-01-26 22:41:27.989 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 05 00 4A 05 01 B4 
2018-01-26 22:41:27.990 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 0. Queue={}
2018-01-26 22:41:27.991 [DEBUG] [ve.internal.protocol.ZWaveController] - ZWave controller end inclusion
2018-01-26 22:41:27.991 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 255: Sending REQUEST Message = 01 05 00 4A 05 01 B4 
==> /var/log/openhab2/events.log <==
2018-01-26 22:41:28.000 [thome.event.ItemStateEvent] - zwave_serial_zstick_597362ca_serial_ack updated to 35
2018-01-26 22:41:28.004 [vent.ItemStateChangedEvent] - zwave_serial_zstick_597362ca_serial_ack changed from 34 to 35
2018-01-26 22:41:28.149 [thome.event.ItemStateEvent] - zwave_serial_zstick_597362ca_serial_sof updated to 60
==> /var/log/openhab2/openhab.log <==
2018-01-26 22:41:28.148 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 4A 01 06 00 00 B5 
2018-01-26 22:41:28.155 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2018-01-26 22:41:28.157 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 07 00 4A 01 06 00 00 B5 
2018-01-26 22:41:28.159 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 07 00 4A 01 06 00 00 B5 
2018-01-26 22:41:28.160 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 06 00 00 
==> /var/log/openhab2/events.log <==
2018-01-26 22:41:28.157 [vent.ItemStateChangedEvent] - zwave_serial_zstick_597362ca_serial_sof changed from 59 to 60
==> /var/log/openhab2/openhab.log <==
2018-01-26 22:41:28.161 [DEBUG] [ol.serialmessage.AddNodeMessageClass] - Add Node: Done.
2018-01-26 22:41:28.163 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveInclusionEvent
2018-01-26 22:41:28.166 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=05 01 
==> /var/log/openhab2/events.log <==
2018-01-26 22:41:28.167 [arthome.event.BindingEvent] - org.openhab.binding.zwave.event.BindingEvent@1da62a7
==> /var/log/openhab2/openhab.log <==
2018-01-26 22:41:28.168 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=AddNodeToNetwork[0x4A], type=Request[0x00], priority=High, dest=255, callback=0, payload=01 06 00 00 
2018-01-26 22:41:28.169 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=AddNodeToNetwork, callback id=0, expected=AddNodeToNetwork, cancelled=false        transaction complete!
2018-01-26 22:41:28.171 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2018-01-26 22:41:28.172 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 255: Response processed after 179ms/705ms.
==> /var/log/openhab2/events.log <==
2018-01-26 22:41:28.397 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV6:eae08b75' has been updated.
==> /var/log/openhab2/openhab.log <==
2018-01-26 22:41:29.253 [INFO ] [org.quartz.core.QuartzScheduler     ] - Scheduler openHAB-job-scheduler_$_NON_CLUSTERED started.
==> /var/log/openhab2/events.log <==
2018-01-26 22:41:33.403 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV6:eae08b75' has been updated.
2018-01-26 22:41:38.409 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV6:eae08b75' has been updated.
2018-01-26 22:41:43.414 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV6:eae08b75' has been updated.
2018-01-26 22:41:48.417 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV6:eae08b75' has been updated.
2018-01-26 22:41:53.424 [me.event.ThingUpdatedEvent] - Thing 'milight:bridgeV6:eae08b75' has been updated

after that I only can see milight traces.

Do you also see any traces when the sensor triggers?

Not a Single one

@chris do you have any experience with this? Inclusion seems to be complete but sensor events are not transmitted to the controller.

@thowa Can you post a screenshot of the configuration page of the thing? Maybe the association to the zwave controller is missing

I’m not quite sure what exacly you mean by configuration page.
Here are 2 screenshots that might be what you are looking for.

on cd-jackson.com I saw that only firmware version up to 2.8 ist supported.
cd-jackson

I assume the firmware version of my sensor is 3.2.

Also type ID is not listed on cd-jackson either.

Perhaphs that is the reason

The database shows both of them:

So I do not think that is the issue. The result of my fibaro door sensor (FGK101) also shows the same result in the database.

Just to make sure that the items file doesn’t have an issue:
Can you also create an item via PaperUI and check if PaperUI is displaying something when the sensor triggers?

I‘ve already created the item via Papier Ui

Does that mean that you have your item created in PaperUI and in addition in your default.items file at the same time?
Especially if they have the same names (Bad_Bewegung) in PaperUI and items file that “could” be a problem.

Does PaperUI show two items being linked to the channel Motion Alarm?

If not (and you still have your item defined in PaperUI and default.items), make sure that you define your item only at one place
If yes, try to delete the item that PaperUI created and only use or default.items (or the other way round).

Once you cleared your items, make sure to delete the cache of OpenHab:
There is a nice description here: Clear the Cache

Sorry for the late reply, I was offline for a couple off days.

As often, it seems, that the error was sitting in front of the machine :wink:
Obviously I have not properly paired the Fibaro Motion Sensor.
Reading the manual, I was aware that I have had to push the button on the sensor 3 times.

Special thanks to @Sascha_Billian, @rlkoshak and @jkarsten

I am running into same issues. Can´t find the missing thing. I use a Fibaro Motion Sensor and a Switch and the Sensor does not trigger any motion. I have tried everything to get it work, but still not. Please can somebody take a look? The Things i have imported via Paper UI (NO Simple Mode).

Thanks!

**My items:**
// Bewegungsmelder

Group gEG_Garderobe "Garderobe Bewegunsgmelder"

Switch Ga_Bewegung "Garderobe Bewegung" <motion> (gEG_Garderobe) {channel="zwave:device:ffac095e:node2:alarm_motion"}

// Lichter

Group gEG_Wohnzimmer "Garderobe Bewegunsgmelder"

Switch Wz_kl_Licht "Wohnzimmer Licht" <light> (gEG_Wohnzimmer) [ "Lighting" ] {channel="zwave:device:ffac095e:node4:switch_binary"}

**sitemap:**

sitemap meinHeim label="Casa Boro" {

Frame label="Wohnzimmer" {

Group item=gEG_Wohnzimmer label="Erdgeschoss" icon="groundfloor"

Switch item=Wz_kl_Licht

}

Frame label="Garderobe" {

Group item=gEG_Garderobe label="Erdgeschoss" icon="groundfloor"

Switch item=Ga_Bewegung

}

}

**rules:**

// Bewegungsmelder Garderobe
rule "Kueche Bewegung AN"
when
Item Ga_Bewegung changed from OFF to ON 
then
sendCommand(Wz_kl_Licht, ON)
end