Aeotec Multisensor 6 ZW100-C

Hi all,

I just got 3 new Aeotech multisensor 6, model no ZW100-C. I able to setup the device with Z-Stick Gen 5 Z-Wave. Then I choose Binary Sensor & Alarm from Things section. I moved to Control section inside paper UI but it seems no alarm or motion is detected by openhab2. Please help me to figure it out where I am doing wrong?When I shake the sensor it seems openhab2 identify alarm inside log. Log is below for reference

2016-08-17 23:39:20.001 [INFO ] [smarthome.event.ItemStateEvent:43   ] - Wifi_Level updated to 0
2016-08-17 23:39:20.002 [INFO ] [s.event.ItemStateChangedEvent :43   ] - Wifi_Level changed from 2 to 0
2016-08-17 23:39:23.036 [DEBUG] [rialHandler$ZWaveReceiveThread:244  ] - Receive Message = 01 10 00 04 00 08 0A 71 05 00 00 00 FF 07 03 00 00 66 
2016-08-17 23:39:23.036 [INFO ] [smarthome.event.ItemStateEvent:43   ] - zwave_serial_zstick_d4681df1_serial_sof updated to 263
2016-08-17 23:39:23.036 [DEBUG] [b.z.i.protocol.ZWaveController:1284 ] - Receive queue TAKE: Length=0
2016-08-17 23:39:23.036 [DEBUG] [o.b.z.i.protocol.SerialMessage:255  ] - Assembled message buffer = 01 10 00 04 00 08 0A 71 05 00 00 00 FF 07 03 00 00 66 
2016-08-17 23:39:23.036 [INFO ] [s.event.ItemStateChangedEvent :43   ] - zwave_serial_zstick_d4681df1_serial_sof changed from 262 to 263
2016-08-17 23:39:23.036 [DEBUG] [b.z.i.protocol.ZWaveController:1285 ] - Process Message = 01 10 00 04 00 08 0A 71 05 00 00 00 FF 07 03 00 00 66 
2016-08-17 23:39:23.036 [DEBUG] [b.z.i.protocol.ZWaveController:203  ] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 08 0A 71 05 00 00 00 FF 07 03 00 00 
2016-08-17 23:39:23.036 [DEBUG] [ApplicationCommandMessageClass:42   ] - NODE 8: Application Command Request (ALIVE:GET_CONFIGURATION)
2016-08-17 23:39:23.036 [DEBUG] [ApplicationCommandMessageClass:152  ] - NODE 8: Incoming command class ALARM
2016-08-17 23:39:23.037 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:99   ] - NODE 8: Received Alarm Request V3
2016-08-17 23:39:23.037 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:103  ] - NODE 8: Process Alarm Report, V3, length 13
2016-08-17 23:39:23.037 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:125  ] - NODE 8: Alarm report - 7 = 0, sensor=0, event=3, status=255
2016-08-17 23:39:23.037 [DEBUG] [z.i.p.c.ZWaveAlarmCommandClass:145  ] - NODE 8: Alarm Type = Burglar (7)
2016-08-17 23:39:23.038 [DEBUG] [b.z.i.protocol.ZWaveController:538  ] - Notifying event listeners: ZWaveAlarmValueEvent
2016-08-17 23:39:23.038 [DEBUG] [.b.z.handler.ZWaveThingHandler:896  ] - NODE 8: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-08-17 23:39:23.038 [DEBUG] [.b.z.handler.ZWaveThingHandler:905  ] - NODE 8: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2016-08-17 23:39:23.038 [DEBUG] [.b.z.handler.ZWaveThingHandler:1066 ] - NODE 8: Updating channel state zwave:device:d4681df1:node8:alarm_general to OFF [OnOffType]
2016-08-17 23:39:23.038 [DEBUG] [ApplicationCommandMessageClass:126  ] - NODE 255: Transaction not completed: node address inconsistent.  lastSent=255, incoming=255
2016-08-17 23:39:23.038 [INFO ] [smarthome.event.ItemStateEvent:43   ] - zwave_device_d4681df1_node8_alarm_general updated to OFF

Did you ever figure this out? What was the solution? I’m experiencing something similar.

Hmm. I think I have similar issues (a ZW100 isn’t showing motion in PaperUI), but what’s weird is I have two of these devices and the other one works fine (though it is powered by USB).

The problematic one is defined as:
Switch GF_Living_Motion "Ground floor - Motion: " <present> (gGroundFloor, gInternalMotionSensors) { channel="zwave:device:157b8d41438:node30:sensor_binary" }

The one which works is identical:
Switch FF_Hallway_Motion "Hallway Motion: [%s]" <present> (gFirstFloor, gInternalMotionSensors) { channel="zwave:device:157b8d41438:node39:sensor_binary" }

So I’m pretty sure it’s not that. The node.xml files look quite different, but I’m not sure how significant that is (given that one is battery powered and one is on USB).

If I try in the console, it appears to know the item:
openhab> smarthome:status GF_Living_Motion OFF

And I can trigger it:
openhab> smarthome:send GF_Living_Motion ON Command has been sent successfully.

So it’s all a bit confusing. I might try deleting the node.xml file, but I don’t have easy access to the house to fix it if/when it doesn’t work and the device needs waking. So I’m a bit nervous (given that temp etc seem to work fine).

I made a separate thread about this, check my history. Someone posted about how to set the parameters to make it work. For example you need to be in binary report mode.

1 Like