Aeotec MultiSensor 6 - many problems

Add-ons Bindings
,
1

Hi,

I’m trying to make sensor working, and I succeeded to some extent. I have all sensors working except for alarm and motion.
I can see alarm triggering in logs, but not changing state of item. My conf is:
Switch Hr_Kitchen_AMS_Alarm “Alarm [%s]” (gH_Kitchen) {channel=“zwave:device:c76af4c3:node5:alarm_general”}

I tried contact, switch and even string items. No luck

Another problem is with motion sensing, it’s not triggering. I thought that sensor may be faulty, but after connecting to Aeon firmware update tool, I’m getting motion triggered. I tried on USB power as well as battery.

I also have another problem, that I cannot change any configuration. I’m waking the device, but configuration changes are not preserved

2

first thing.
please note that you should use the device with the power source you included it

so… if you included it USB powererd you should use it by USB … same for battery.
otherwise the device may not work correct. reinclude if you want to switch power source is recommended.

3

motion is detected by this channel for me:

Switch node20_Motion “Bewegung” {channel=“zwave:device:15348538564:node20:sensor_binary”} label=“Motion [MAP(motion.map):%s]”

cant remember if I altered config parameter 5 for this … but likely
5: Motion Sensor Triggered Command

4

Sure I did. I added and removed node many times, on USb and battery power

5

I have “Send Basic Set CC” in option 5, cannot currently change it to other options from OH2, I will try ozwcp. My conf is exactly the same:
Switch Hr_Kitchen_AMS_Motion “Motion [%s]” (Motion, gH_Kitchen, gH_Motion) {channel=“zwave:device:c76af4c3:node5:sensor_binary”}

6

Looks like “Send Sensor Binary Report CC” solved motion problem, but I was not able to change it through OH2, I used OWZ panel for that.

Still fighting with burglar alarm.

7

why? its probably also motion. just triggered with different comfig params

8

I’m getting this in logs:

2016-10-24 19:49:15.308 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 11 00 04 04 07 0B 71 05 00 00 00 FF 07 03 00 00 00 6D
2016-10-24 19:49:15.313 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-10-24 19:49:15.315 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 11 00 04 04 07 0B 71 05 00 00 00 FF 07 03 00 00 00 6D
2016-10-24 19:49:15.316 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 11 00 04 04 07 0B 71 05 00 00 00 FF 07 03 00 00 00 6D
2016-10-24 19:49:15.320 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=04 07 0B 71 05 00 00 00 FF 07 03 00 00 00
2016-10-24 19:49:15.323 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 7: Application Command Request (ALIVE:DYNAMIC_VALUES)
2016-10-24 19:49:15.324 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 7: Incoming command class ALARM
2016-10-24 19:49:15.324 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 7: Received Alarm Request V3
2016-10-24 19:49:15.326 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 7: Process Alarm Report, V3, length 14
2016-10-24 19:49:15.326 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 7: Alarm report - 7 = 0, sensor=0, event=3, status=255
2016-10-24 19:49:15.327 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 7: Alarm Type = Burglar (7)
2016-10-24 19:49:15.328 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveAlarmValueEvent
2016-10-24 19:49:15.329 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got an event from Z-Wave network: ZWaveAlarmValueEvent
2016-10-24 19:49:15.329 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Got a value event from Z-Wave network, endpoint = 0, command class = ALARM, value = 0
2016-10-24 19:49:15.330 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Updating channel state zwave:device:c76af4c3:node7:alarm_general to OFF [OnOffType]
2016-10-24 19:49:15.332 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Message has Ack Pending: Message: class=SendData[0x13], type=Request[0x00], priority=Get, dest=7, callback=82, payload=07 02 73 02

My item is like this:

Contact Hr_Kitchen_AMS_Alarm			"Alarm [%s]"						<alarm>		(gH_Kitchen)			{channel="zwave:device:c76af4c3:node7:alarm_general"}

But most interesting part is:

2016-10-24 19:49:15.330 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 7: Updating channel state zwave:device:c76af4c3:node7:alarm_general to OFF [OnOffType]

So, alarm is triggered, but channel is set to OFF. Why is that? It should be the other way around

Also, after removing sensor from network, removing it from OH2, including on battery I was able to change configurations, but motion sensor stooped working. I will report any progress I made.

9

Not necessarily. When you have a look at http://www.cd-jackson.com/index.php/zwave/zwave-device-database/openhab-2-channel-types, you will find the command class alarm_general. First point: It’s defined as a SWITCH. So from my understanding, you have to define your item accordingly (not CONTACT). Second: When the list is reliable, OFF means alarm. Reliable because I had a similar case where the list said OFF=alarm, but chris posted something directly out of the binding code and there it was (as it is more logical) ON=alarm.

10

So, I implemented it now as:

Switch Hr_Kitchen_AMS_Alarm			"Alarm [MAP(alarm.map):%s]"						<alarm>		(gH_Kitchen)			{channel="zwave:device:c76af4c3:node7:alarm_general"}

with alarm.map like:

OFF=Alarm
ON=OK
-=N/A

And it is always on, despite the fact that I didn’t touch it for couple of hoursl

11

Can you trigger the alarm and see if it switches to another state?

12

I did it hundred of times, is sometimes works and sometimes not. I’m really pissed off, not sure if with sensor or OH2 :wink: