Fibaro motion sensor FGMS001 Gen5 (Zwaveplus)

Seaside · November 4, 2016, 9:49am

Hi!

I’m not getting the fibaro motion sensor to work as I expect.
I have the following items:

Group ZwaveEye1                     "Motion Sensor"                                         (Zwave)
Number ZwaveEye1Lux                 "Motion Sensor [%.2f Lux]"    <sun>                     (ZwaveEye1) { channel="zwave:device:be1078de:node26:sensor_luminance" }
Number ZwaveEye1Battery             "Motion Sensor [%d %%]"      <battery>    (ZwaveEye1)        { channel="zwave:device:be1078de:node26:battery-level" }
Number ZwaveEye1Temp                "Motion Sensor [%.1f C]"     <temperature>    (ZwaveEye1)    { channel="zwave:device:be1078de:node26:sensor_temperature" }
Switch ZwaveEye1Motion              "Motion Sensor Motion [%s]"           (ZwaveEye1)     { channel="zwave:device:be1078de:node26:sensor_binary" }
Contact ZwaveEye1MotionC            "Motion Sensor MotionC [%s]"           (ZwaveEye1)     { channel="zwave:device:be1078de:node26:sensor_binary" }
Switch ZwaveEye1Alarm               "Motion Sensor Alarm [%s]"             <fire>   (ZwaveEye1)      { channel="zwave:device:be1078de:node26:alarm_general" }
Switch ZwaveEye1AlarmBurglar        "Motion Sensor Alarm b [%s]"             <fire>   (ZwaveEye1)      { channel="zwave:device:be1078de:node26:alarm_burglar" }
Number ZwaveEye1Seismic             "Motion Sensor Seismic [%f]"                (ZwaveEye1)      { channel="zwave:device:be1078de:node26:sensor_seismicintensity" }

So the
Number ZwaveEye1Lux,
Number ZwaveEye1Battery,
Number ZwaveEye1Temp and
Number ZwaveEye1Seismic

seems to work fine. My problem is to get the motion detection

out of:
ZwaveEye1Motion
ZwaveEye1MotionC
Switch ZwaveEye1Alarm
Switch ZwaveEye1AlarmBurglar

It is only the burglar alarm that is triggered due to motion, the others are unaffected by motion.
Has anyone gotten it to work in openhab2? Is there any configuration needed to get the others to work?

Regards, S

sihui · November 7, 2016, 4:24pm

Switch FibEye1_Motion_S "Motion Hallway up [%s]" (gAlarmSensors,gInfluxdb) {channel="zwave:device:15839bd6d36:node3:sensor_binary"}

worked for me.

zen · November 7, 2016, 6:13pm

You have duplicated definition here.
What do you mean by motion, is it people moving in front of sensor or moving sensor itself.

Seaside · November 8, 2016, 9:44am

Hi!

Moving in front of the sensor is what I’m doing.
I’m having duplicated definitions just to test if a contact is working better than a switch, removing one of them doesn’t do anything.
Moving the senor itself doesn’t trigger the motion either. I’m thinking I’m missing some basic configuration?

Regards, S

sihui · November 8, 2016, 10:18am

Make sure you have config parameter 8 set to “always active” and 12 to “Basic ON and Basic OFF”

Seaside · November 9, 2016, 11:36am

Hi!

Thanks for the help. The sensor is now working. I had to exlude it, include it, reset it several times.
I think it boiled down to the device not being fully initialized, and then doing a restart of openhab.
If I let it perform a full initialization (20 mins+), it would start working.

Regards, S

chris · November 9, 2016, 4:52pm

Initialisation of battery devices will take some time unless you wake it up manually, which is likely necessary if the device is newly included as the wakeup interval often isn’t set by default, and it if it, it’s normally set to broadcast which doesn’t get routed…

It shouldn’t take 20 minutes of continuous communications to initialise this, or any other device - once it’s awake ;).

nokyyz · December 28, 2016, 1:18pm

Hi all,

I have a similar problem with my Fibaro FGMS001 Gen5 sensor.
My item configuration is:

Group groupDetecteur1Terrasse "Detecteur 1 Terrasse" (groupExterieur)
Switch  Detector38_Movement         "Mouvement [%s]"          <present>  (groupDetecteur1Terrasse, groupPresence)    { channel = "zwave:device:e663edc3:node38:sensor_binary" }
Number  Detector38_Alarm            "Alarm [%s]"             <fire>     (groupDetecteur1Terrasse)    { channel = "zwave:device:e663edc3:node38:alarm_general" }
Switch  Detector38_Tamper         "Tamper [%s]"          <present>  (groupDetecteur1Terrasse)    { channel = "zwave:device:e663edc3:node38:alarm_burglar" }
Number  Detector38_Vibration         "Vibration [%f]"          <present>  (groupDetecteur1Terrasse)    { channel = "zwave:device:e663edc3:node38:sensor_seismicintensity" }
Number  Detector38_Lux              "Luminosite [%.2f Lux]"         <sun>     (groupDetecteur1Terrasse)     { channel = "zwave:device:e663edc3:node38:sensor_luminance" }
Number  Detector38_Temp             "Temperature [%.1f °C]"  <temperature>  (groupDetecteur1Terrasse, groupTemperature)  { channel = "zwave:device:e663edc3:node38:sensor_temperature" }
Number  Detector38_Battery              "Batterie [%d %%]"        <energy>    (groupDetecteur1Terrasse, groupIntrusionBattery)   { channel = "zwave:device:e663edc3:node38:battery-level" }

The sensor_luminance, sensor_temperature, battery-level channels are Ok.
But:

The sensor_seismicintensity channel is never updated when I shake the sensor (no logs in zwave log file)
On motion detection, the sensor_binary or alarm_general channels are not updated but the alarm_burglar channel is updated . My zwave logs:

2016-12-28 12:10:06.726 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 0F 00 04 00 26 09 71 05 00 00 00 FF 07 08 00 5F 
2016-12-28 12:10:06.726 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-12-28 12:10:06.726 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0F 00 04 00 26 09 71 05 00 00 00 FF 07 08 00 5F 
2016-12-28 12:10:06.726 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 0F 00 04 00 26 09 71 05 00 00 00 FF 07 08 00 5F 
2016-12-28 12:10:06.727 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 26 09 71 05 00 00 00 FF 07 08 00 
2016-12-28 12:10:06.727 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 12:10:06.727 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 12:10:06.727 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@4c31b46e already registered
2016-12-28 12:10:06.727 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class ALARM
2016-12-28 12:10:06.727 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Received ALARM command V5
2016-12-28 12:10:06.727 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Process NOTIFICATION_REPORT V5
2016-12-28 12:10:06.727 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: NOTIFICATION report - 0 = 0, event=8, status=255
2016-12-28 12:10:06.727 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Alarm Type = BURGLAR (0)
2016-12-28 12:10:06.727 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2016-12-28 12:10:06.727 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-12-28 12:10:06.727 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2016-12-28 12:10:06.728 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter processing NOTIFICATION
2016-12-28 12:10:06.728 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - Alarm converter NOTIFICATION event is 8, type OnOffType
2016-12-28 12:10:06.728 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:alarm_burglar to ON [OnOffType]

On @sihui advices, I check my sensor configuration. My config paramater 8 is well set to “always active” and 12 to “Basic ON and Basic OFF”.

My zwave binding is org.openhab.binding.zwave-2.0.0-20161216.231458-318.jar

What is the problem ?

Thks

TeeVee · December 28, 2016, 2:48pm

Hi Nokyyz,

I have the same sensor. I really love these fibaro “eyes” and also have some of the Gen 1 versions but this very Gen 2 type has a weird behaviour. In my case it always triggered motion (without any motion) and soon after cancellation time triggered again etc.
After searching all available forums I found a “work around” with setting parameter 1 to 32 and paramter 2 to 15.
Now it bahaves as expected. Don’t ask me the reason for this, Maybe has to do with binary representation of 15 (= 1111) and 32 (=10 0000) but that’s really a guess.

hope taht helps

nokyyz · December 28, 2016, 11:02pm

Hi @TeeVee,

I tried your work around. Thanks to Habmin 2, I have set parameter 1 to 32 (parameter 2 was already set to 15). After a forced wake up (triple button), the sensor_binary and general_alarm channels have been updated to ON, but they keep always ON (see my zwave logs).

2016-12-28 23:24:59.218 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Processing config_25_1 len=3
2016-12-28 23:24:59.218 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Processing config_25_1 - id = '25'
2016-12-28 23:24:59.218 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@155eb1a2
2016-12-28 23:24:59.218 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Processing group_org.openhab.binding.zwave.internal.protocol.ZWaveAssociationGroup@1120d08d
2016-12-28 23:24:59.219 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:24:59.219 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 55ms/4870ms.
2016-12-28 23:24:59.219 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 38: Sending REQUEST Message = 01 09 00 13 26 02 30 02 25 28 FE 
2016-12-28 23:24:59.228 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: Sent Data successfully placed on stack.
2016-12-28 23:24:59.249 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: SendData Request. CallBack ID = 40, Status = Transmission complete and ACK received(0)
2016-12-28 23:24:59.249 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.262 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:24:59.263 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.263 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class SENSOR_BINARY
2016-12-28 23:24:59.263 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 38: Received SENSOR_BINARY command V1
2016-12-28 23:24:59.263 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 38: Sensor Binary report, type=Unknown, value=255
2016-12-28 23:24:59.263 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveBinarySensorValueEvent
2016-12-28 23:24:59.263 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_BINARY, value = 255
2016-12-28 23:24:59.263 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:sensor_binary to ON [OnOffType]
2016-12-28 23:24:59.265 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:24:59.265 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 45ms/4870ms.
2016-12-28 23:24:59.266 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 38: Sending REQUEST Message = 01 0B 00 13 26 04 31 04 01 00 25 29 FD 
2016-12-28 23:24:59.275 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: Sent Data successfully placed on stack.
2016-12-28 23:24:59.296 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: SendData Request. CallBack ID = 41, Status = Transmission complete and ACK received(0)
2016-12-28 23:24:59.296 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.310 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:24:59.310 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.310 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class SENSOR_MULTILEVEL
2016-12-28 23:24:59.311 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
2016-12-28 23:24:59.311 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Multi Level REPORT received
2016-12-28 23:24:59.311 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Type = Temperature(1), Scale = 0
2016-12-28 23:24:59.311 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Value = 21.2
2016-12-28 23:24:59.311 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-12-28 23:24:59.311 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 21.2
2016-12-28 23:24:59.311 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 38: Sensor is reporting scale 0, requiring conversion to 0. Value is now 21.2.
2016-12-28 23:24:59.311 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:sensor_temperature to 21.2 [DecimalType]
2016-12-28 23:24:59.313 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:24:59.313 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 45ms/4870ms.
2016-12-28 23:24:59.313 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 38: Sending REQUEST Message = 01 0B 00 13 26 04 31 04 19 00 25 2A E6 
2016-12-28 23:24:59.322 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: Sent Data successfully placed on stack.
2016-12-28 23:24:59.343 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: SendData Request. CallBack ID = 42, Status = Transmission complete and ACK received(0)
2016-12-28 23:24:59.344 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.358 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:24:59.358 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.358 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class SENSOR_MULTILEVEL
2016-12-28 23:24:59.358 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
2016-12-28 23:24:59.358 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Multi Level REPORT received
2016-12-28 23:24:59.358 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Type = SeismicIntensity(25), Scale = 0
2016-12-28 23:24:59.358 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Value = 0E+1
2016-12-28 23:24:59.358 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-12-28 23:24:59.358 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 0E+1
2016-12-28 23:24:59.359 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:sensor_seismicintensity to 0 [DecimalType]
2016-12-28 23:24:59.361 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:24:59.361 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 47ms/4870ms.
2016-12-28 23:24:59.361 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 38: Sending REQUEST Message = 01 0B 00 13 26 04 31 04 03 00 25 2B FD 
2016-12-28 23:24:59.370 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: Sent Data successfully placed on stack.
2016-12-28 23:24:59.391 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: SendData Request. CallBack ID = 43, Status = Transmission complete and ACK received(0)
2016-12-28 23:24:59.391 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.405 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:24:59.405 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.406 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class SENSOR_MULTILEVEL
2016-12-28 23:24:59.406 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
2016-12-28 23:24:59.406 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Multi Level REPORT received
2016-12-28 23:24:59.406 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Type = Luminance(3), Scale = 1
2016-12-28 23:24:59.406 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Value = 24
2016-12-28 23:24:59.406 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-12-28 23:24:59.406 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 24
2016-12-28 23:24:59.406 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:sensor_luminance to 24 [DecimalType]
2016-12-28 23:24:59.408 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:24:59.408 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 47ms/4870ms.
2016-12-28 23:24:59.408 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 38: Sending REQUEST Message = 01 0A 00 13 26 03 71 04 07 25 2C B8 
2016-12-28 23:24:59.425 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: Sent Data successfully placed on stack.
2016-12-28 23:24:59.438 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: SendData Request. CallBack ID = 44, Status = Transmission complete and ACK received(0)
2016-12-28 23:24:59.438 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.452 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:24:59.452 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.452 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class ALARM
2016-12-28 23:24:59.452 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Received ALARM command V5
2016-12-28 23:24:59.452 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Process NOTIFICATION_REPORT V5
2016-12-28 23:24:59.452 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: ALARM report - 0 = 0
2016-12-28 23:24:59.452 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Alarm Type = GENERAL (0)
2016-12-28 23:24:59.452 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-12-28 23:24:59.452 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2016-12-28 23:24:59.453 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:24:59.453 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 45ms/4870ms.
2016-12-28 23:24:59.454 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 38: Sending REQUEST Message = 01 09 00 13 26 02 80 02 25 2D 4B 
2016-12-28 23:24:59.463 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: Sent Data successfully placed on stack.
2016-12-28 23:24:59.484 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: SendData Request. CallBack ID = 45, Status = Transmission complete and ACK received(0)
2016-12-28 23:24:59.484 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.497 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:24:59.498 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.498 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class BATTERY
2016-12-28 23:24:59.498 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 38: Received Battery Request
2016-12-28 23:24:59.498 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 38: Battery report value = 100
2016-12-28 23:24:59.498 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2016-12-28 23:24:59.498 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = BATTERY, value = 100
2016-12-28 23:24:59.498 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:battery-level to 100 [DecimalType]
2016-12-28 23:24:59.499 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:24:59.500 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 46ms/4870ms.
2016-12-28 23:24:59.500 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 38: Sending REQUEST Message = 01 0A 00 13 26 03 9C 01 00 25 2E 55 
2016-12-28 23:24:59.509 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: Sent Data successfully placed on stack.
2016-12-28 23:24:59.530 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: SendData Request. CallBack ID = 46, Status = Transmission complete and ACK received(0)
2016-12-28 23:24:59.530 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.545 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:24:59.545 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:24:59.545 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class SENSOR_ALARM
2016-12-28 23:24:59.545 [DEBUG] [ndclass.ZWaveAlarmSensorCommandClass] - NODE 38: Received SENSOR_ALARM command V1
2016-12-28 23:24:59.545 [DEBUG] [ndclass.ZWaveAlarmSensorCommandClass] - NODE 38: Alarm Report: Source=38, Type=General(0), Value=255
2016-12-28 23:24:59.545 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveAlarmSensorValueEvent
2016-12-28 23:24:59.545 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_ALARM, value = 255
2016-12-28 23:24:59.546 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:alarm_general to ON [OnOffType]
2016-12-28 23:24:59.547 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:24:59.547 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 47ms/4870ms.
2016-12-28 23:25:00.547 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: No more messages, go back to sleep
2016-12-28 23:25:00.547 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2016-12-28 23:25:00.548 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 38: Sending REQUEST Message = 01 09 00 13 26 02 84 08 25 2F 47 
2016-12-28 23:25:00.557 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: Sent Data successfully placed on stack.
2016-12-28 23:25:00.585 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: SendData Request. CallBack ID = 47, Status = Transmission complete and ACK received(0)
2016-12-28 23:25:00.585 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:25:00.586 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Went to sleep
2016-12-28 23:25:00.586 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Is sleeping
2016-12-28 23:25:00.586 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:25:00.586 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 38ms/4870ms.
2016-12-28 23:25:02.290 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:25:02.290 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:25:02.290 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class WAKE_UP
2016-12-28 23:25:02.290 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Received Wake Up Request
2016-12-28 23:25:02.290 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Received WAKE_UP_NOTIFICATION
2016-12-28 23:25:02.291 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Is awake with 0 messages in the wake-up queue.
2016-12-28 23:25:02.291 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveWakeUpEvent
2016-12-28 23:25:02.349 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Transaction not completed: node address inconsistent.  lastSent=38, incoming=255
2016-12-28 23:25:03.291 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: No more messages, go back to sleep
2016-12-28 23:25:03.291 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Creating new message for application command WAKE_UP_NO_MORE_INFORMATION
2016-12-28 23:25:03.292 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 38: Sending REQUEST Message = 01 09 00 13 26 02 84 08 25 30 58 
2016-12-28 23:25:03.300 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: Sent Data successfully placed on stack.
2016-12-28 23:25:03.321 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 38: SendData Request. CallBack ID = 48, Status = Transmission complete and ACK received(0)
2016-12-28 23:25:03.321 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:25:03.321 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Went to sleep
2016-12-28 23:25:03.321 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Is sleeping
2016-12-28 23:25:03.322 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-12-28 23:25:03.322 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 38: Response processed after 30ms/4870ms.
2016-12-28 23:25:04.380 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:25:04.381 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:25:04.381 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class SENSOR_MULTILEVEL
2016-12-28 23:25:04.381 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
2016-12-28 23:25:04.381 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Multi Level REPORT received
2016-12-28 23:25:04.381 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Type = Luminance(3), Scale = 1
2016-12-28 23:25:04.381 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Value = 24
2016-12-28 23:25:04.381 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-12-28 23:25:04.381 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 24
2016-12-28 23:25:04.381 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:sensor_luminance to 24 [DecimalType]
2016-12-28 23:25:04.541 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:25:04.541 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:25:04.541 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class SENSOR_MULTILEVEL
2016-12-28 23:25:04.541 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Received COMMAND_CLASS_SENSOR_MULTILEVEL command V8
2016-12-28 23:25:04.541 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Multi Level REPORT received
2016-12-28 23:25:04.541 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Type = Temperature(1), Scale = 0
2016-12-28 23:25:04.541 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Sensor Value = 21.2
2016-12-28 23:25:04.542 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveMultiLevelSensorValueEvent
2016-12-28 23:25:04.542 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = SENSOR_MULTILEVEL, value = 21.2
2016-12-28 23:25:04.542 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 38: Sensor is reporting scale 0, requiring conversion to 0. Value is now 21.2.
2016-12-28 23:25:04.542 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:sensor_temperature to 21.2 [DecimalType]
2016-12-28 23:25:32.234 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:25:32.234 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:25:32.234 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class ALARM
2016-12-28 23:25:32.234 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Received ALARM command V5
2016-12-28 23:25:32.234 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Process NOTIFICATION_REPORT V5
2016-12-28 23:25:32.235 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: NOTIFICATION report - 0 = 0, event=0, status=255
2016-12-28 23:25:32.235 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Alarm Type = BURGLAR (0)
2016-12-28 23:25:32.235 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-12-28 23:25:32.235 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2016-12-28 23:25:32.235 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:alarm_burglar to OFF [OnOffType]
2016-12-28 23:26:16.574 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:26:16.574 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE
2016-12-28 23:26:16.574 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Incoming command class ALARM
2016-12-28 23:26:16.574 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Received ALARM command V5
2016-12-28 23:26:16.575 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Process NOTIFICATION_REPORT V5
2016-12-28 23:26:16.575 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: NOTIFICATION report - 0 = 0, event=0, status=255
2016-12-28 23:26:16.576 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Alarm Type = BURGLAR (0)
2016-12-28 23:26:16.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-12-28 23:26:16.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 255
2016-12-28 23:26:16.576 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Updating channel state zwave:device:e663edc3:node38:alarm_burglar to OFF [OnOffType]
2016-12-28 23:26:41.475 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Polling...
2016-12-28 23:26:41.475 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Polling zwave:device:e663edc3:node38:sensor_binary
2016-12-28 23:26:41.475 [DEBUG] [converter.ZWaveBinarySensorConverter] - NODE 38: Generating poll message for SENSOR_BINARY, endpoint 0
2016-12-28 23:26:41.476 [DEBUG] [dclass.ZWaveBinarySensorCommandClass] - NODE 38: Creating new message for application command SENSOR_BINARY_GET
2016-12-28 23:26:41.476 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Polling zwave:device:e663edc3:node38:sensor_temperature
2016-12-28 23:26:41.476 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 38: Generating poll message for SENSOR_MULTILEVEL, endpoint 0
2016-12-28 23:26:41.476 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Creating new message for command SENSOR_MULTI_LEVEL_GET
2016-12-28 23:26:41.476 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Polling zwave:device:e663edc3:node38:sensor_seismicintensity
2016-12-28 23:26:41.476 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 38: Generating poll message for SENSOR_MULTILEVEL, endpoint 0
2016-12-28 23:26:41.476 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Creating new message for command SENSOR_MULTI_LEVEL_GET
2016-12-28 23:26:41.476 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Polling zwave:device:e663edc3:node38:sensor_luminance
2016-12-28 23:26:41.476 [DEBUG] [erter.ZWaveMultiLevelSensorConverter] - NODE 38: Generating poll message for SENSOR_MULTILEVEL, endpoint 0
2016-12-28 23:26:41.476 [DEBUG] [ss.ZWaveMultiLevelSensorCommandClass] - NODE 38: Creating new message for command SENSOR_MULTI_LEVEL_GET
2016-12-28 23:26:41.476 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Polling zwave:device:e663edc3:node38:alarm_burglar
2016-12-28 23:26:41.477 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 38: Generating poll message for ALARM, endpoint 0, alarm BURGLAR
2016-12-28 23:26:41.477 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 38: Creating new message for application command NOTIFICATION_GET V5
2016-12-28 23:26:41.477 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Polling zwave:device:e663edc3:node38:battery-level
2016-12-28 23:26:41.477 [DEBUG] [rnal.converter.ZWaveBatteryConverter] - NODE 38: Generating poll message for BATTERY endpoint 0
2016-12-28 23:26:41.477 [DEBUG] [ommandclass.ZWaveBatteryCommandClass] - NODE 38: Creating new message for application command BATTERY_GET
2016-12-28 23:26:41.477 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 38: Polling zwave:device:e663edc3:node38:alarm_general
2016-12-28 23:26:41.477 [DEBUG] [.converter.ZWaveAlarmSensorConverter] - NODE 38: Generating poll message for SENSOR_ALARM, endpoint 0, alarm null
2016-12-28 23:26:41.477 [DEBUG] [ndclass.ZWaveAlarmSensorCommandClass] - NODE 38: Creating new message for command SENSOR_ALARM_GET, type General
2016-12-28 23:26:41.477 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Putting message SendData in wakeup queue.
2016-12-28 23:26:41.477 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Putting message SendData in wakeup queue.
2016-12-28 23:26:41.477 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Putting message SendData in wakeup queue.
2016-12-28 23:26:41.477 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Putting message SendData in wakeup queue.
2016-12-28 23:26:41.477 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Putting message SendData in wakeup queue.
2016-12-28 23:26:41.478 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Putting message SendData in wakeup queue.
2016-12-28 23:26:41.478 [DEBUG] [commandclass.ZWaveWakeUpCommandClass] - NODE 38: Putting message SendData in wakeup queue.
2016-12-28 23:27:52.413 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 38: Application Command Request (ALIVE:DONE)
2016-12-28 23:27:52.413 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 38: Starting initialisation from DONE

On motion detection, the alarm_burglar channel is always updated (no update for sensor_binary or alarm_general channels).
Your work around does not seem to work for me . No luck…

chris · December 28, 2016, 11:21pm

The issue here is we likely need to update the channels in the database to use the notification class. I will take a look at this over the next few days.

nokyyz · December 28, 2016, 11:33pm

Thanks for your help @chris @TeeVee !
I have attached the corresponding zwave node file: node38.xml (21.1 KB)

psixilambda · January 2, 2017, 2:08pm

Hello Chris,

having included this sensor in my alternative home-assitant configuration the event information given 8(motion),3(tamper),0(no alarm) determines if motion or tamper alarm is given. Looking at the first log from nokyyz above I can find the event=8. This should probably match to a channel for motion, event=3 to a channel for tamper.
I haven’t included the Firbaro Gen5 (firmware 3.2) on my openhab setup so I can not provide logs to prove that when tampering above log will change with event=3 but I see a high probability.

Best regards

Alex

"
The entites temperature and luminance seem to work.
But I noticed that only the entity “sensor.fibaro_system_fgms001_motion_sensor_burglar_31” changes its value if the sensor detectes motion:
Value 8 - for motion
Value 3 - seems to be the value for tampering "

from here: https://community.home-assistant.io/t/has-anbody-a-working-setup-of-the-fibaro-motion-sensor-fgms001/3135

chris · January 2, 2017, 2:11pm

Yes - I think you are probably right - it’s not difficult, but I need to find some time. Possibly I’ll look at this tonight or else tomorrow.

Edward_Moyse · January 4, 2017, 12:12pm

Ah interesting … I had noticed that tamper seems to trip with motion:
2017-01-04 12:03:41.481 [ItemStateChangedEvent ] - Garage_Motion changed from OFF to ON 2017-01-04 12:03:41.909 [ItemStateChangedEvent ] - Garage_Tamper changed from 0 to 1 2017-01-04 12:03:47.166 [ItemStateChangedEvent ] - Garage_Motion changed from ON to OFF 2017-01-04 12:03:47.505 [ItemStateChangedEvent ] - Garage_Tamper changed from 1 to 0

Presumably this is the same thing? I would assume that I have a gen1, but honestly I’m not sure. It’s firmware version 2.6 according to habmin, and type/id 0800:1001.

chris · January 4, 2017, 12:14pm

Please ensure you are using the latest version of the binding, and delete and re-add in your things so that it picks up the latest definition.

Edward_Moyse · January 4, 2017, 1:29pm

Hi @chris, I did this - I now have binding version 2.0.0.201701032212, and I deleted and re-added the thing. It seems to be still doing it though (I didn’t have to delete the xml file or anything did I?)

chris · January 4, 2017, 1:45pm

Ok - maybe your version is different - I forget what version numbers the things change at. I’ll take a look tonight…

Edward_Moyse · January 4, 2017, 1:58pm

ok thanks!

chris · January 4, 2017, 4:38pm

@Edward_Moyse can you post the XML for your device please (in the userdata/zwave folder).