Trouble with 'Aeon ZW080-A17 Gen 5 siren'

Hi,

I tried several things and I’m not being able to turn on the siren. Let me start by describing how I included the siren and configured the controller and then include some logs. Anything else that is not using ZWave Plus is connecting just fine. I have a lot of switches, door/window sensors, motion sensors, etc. and they are working fine.

When I included the ZWave controller I configured it (to be master of course), I tried Secure Inclusion mode “All devices” and also “Entry Control Devices”. For regular Inclusion Mode I have it configured to ‘Network Wide Inclusion’. I also set a Network Security Key like “07 08 08 02 05 06 07 08 06 0A 0D 0C 0A 0E 0F 10”.

The Siren was not paired to anything else before this test. I tried using Paper UI -> Inbox -> Scan For Things and the Siren got paired. OH2 recognized the type of device and it properly showed “ZW080 Siren Gen5”. In the list of Things page, everything appears as ONLINE including the Siren.

When I go to the Control page where I can switch things, I can turn on/off other electrical switches but when I tried with the Siren nothing happens. The switch goes to on but no siren sound. :frowning:

Here you can see some logs of this interaction:

2016-06-02 18:47:27.307 [INFO ] [g.discovery.internal.PersistentInbox] - Added new thing ‘zwave:device:f5630ea3:node20’ to inbox.
2016-06-02 18:47:27.311 [INFO ] [smarthome.event.InboxAddedEvent ] - Discovery Result with UID ‘zwave:device:f5630ea3:node20’ has been added.
2016-06-02 18:47:44.503 [INFO ] [smarthome.event.InboxRemovedEvent ] - Discovery Result with UID ‘zwave:device:f5630ea3:node20’ has been removed.
2016-06-02 18:47:44.511 [INFO ] [smarthome.event.ThingAddedEvent ] - Thing ‘zwave:device:f5630ea3:node20’ has been added.
2016-06-02 18:47:44.533 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:device:f5630ea3:node20’ changed from UNINITIALIZED to INITIALIZING
2016-06-02 18:47:44.581 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:device:f5630ea3:node20’ changed from INITIALIZING to OFFLINE
2016-06-02 18:47:44.600 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising Thing Node…
2016-06-02 18:47:44.600 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:device:f5630ea3:node20’ changed from OFFLINE to ONLINE
2016-06-02 18:47:44.690 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:device:f5630ea3:node20’ changed from ONLINE to UNINITIALIZED (HANDLER_MISSING_ERROR)
2016-06-02 18:47:44.905 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:device:f5630ea3:node20’ changed from UNINITIALIZED (HANDLER_MISSING_ERROR) to INITIALIZING
2016-06-02 18:47:44.928 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:device:f5630ea3:node20’ changed from INITIALIZING to OFFLINE
2016-06-02 18:47:44.931 [WARN ] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Initialising Thing Node…
2016-06-02 18:47:44.942 [INFO ] [me.event.ThingStatusInfoChangedEvent] - ‘zwave:device:f5630ea3:node20’ changed from OFFLINE to ONLINE
2016-06-02 18:47:44.972 [INFO ] [smarthome.event.ThingUpdatedEvent ] - Thing ‘zwave:device:f5630ea3:node20’ has been updated.
2016-06-02 18:47:45.095 [INFO ] [smarthome.event.ItemAddedEvent ] - Item ‘zwave_device_f5630ea3_node20_switch_binary’ has been added.
2016-06-02 18:47:45.102 [INFO ] [home.event.ItemChannelLinkAddedEvent] - Link ‘zwave_device_f5630ea3_node20_switch_binary-zwave:device:f5630ea3:node20:switch_binary’ has been added.

2016-06-02 18:48:03.692 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘zwave_device_f5630ea3_node20_switch_binary’ received command ON
2016-06-02 18:48:03.703 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_f5630ea3_node20_switch_binary changed from NULL to ON
2016-06-02 18:48:17.829 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘zwave_device_f5630ea3_node20_switch_binary’ received command OFF
2016-06-02 18:48:17.851 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_f5630ea3_node20_switch_binary changed from ON to OFF

2016-06-02 18:49:07.224 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘zwave_device_f5630ea3_node20_switch_binary’ received command ON
2016-06-02 18:49:07.235 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_f5630ea3_node20_switch_binary changed from OFF to ON
2016-06-02 18:49:43.027 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘zwave_device_f5630ea3_node20_switch_binary’ received command OFF
2016-06-02 18:49:43.034 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_f5630ea3_node20_switch_binary changed from ON to OFF

2016-06-02 18:52:27.686 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘zwave_device_f5630ea3_node20_switch_binary’ received command ON
2016-06-02 18:52:27.693 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_f5630ea3_node20_switch_binary changed from OFF to ON
2016-06-02 18:53:42.561 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_f5630ea3_node20_switch_binary changed from ON to OFF
2016-06-02 18:53:42.562 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘zwave_device_f5630ea3_node20_switch_binary’ received command OFF

I then enabled more debug logging and saw this when trying to turn on the Siren:

2016-06-02 19:12:20.929 [INFO ] [smarthome.event.ItemCommandEvent ] - Item ‘zwave_device_f5630ea3_node20_switch_binary’ received command ON
2016-06-02 19:12:20.939 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Command received zwave:device:f5630ea3:node20:switch_binary --> ON
2016-06-02 19:12:20.931 [INFO ] [marthome.event.ItemStateChangedEvent] - zwave_device_f5630ea3_node20_switch_binary changed from OFF to ON
2016-06-02 19:12:20.948 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 20: Creating new message for application command SWITCH_BINARY_SET
2016-06-02 19:12:20.950 [DEBUG] [ve.internal.protocol.ZWaveController] - Message queued. Queue length = 1. Queue={}
2016-06-02 19:12:20.951 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - Took message from queue for sending. Queue length = 0
2016-06-02 19:12:20.955 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 0A 00 13 14 03 25 01 FF 25 56 59
2016-06-02 19:12:20.957 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 20: Sending REQUEST Message = 01 0A 00 13 14 03 25 01 FF 25 56 59
2016-06-02 19:12:20.968 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 04 01 13 01 E8
2016-06-02 19:12:20.971 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-06-02 19:12:20.973 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 04 01 13 01 E8
2016-06-02 19:12:20.975 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 04 01 13 01 E8
2016-06-02 19:12:20.977 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Response[0x01], priority=High, dest=255, callback=0, payload=01
2016-06-02 19:12:20.978 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 20: Sent Data successfully placed on stack.
2016-06-02 19:12:20.986 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 07 00 13 56 00 00 02 BF
2016-06-02 19:12:20.989 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-06-02 19:12:20.992 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 09 00 13 56 00 00 02 00 00 B1
2016-06-02 19:12:20.994 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 09 00 13 56 00 00 02 00 00 B1
2016-06-02 19:12:20.996 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=56 00 00 02
2016-06-02 19:12:21.001 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 20: SendData Request. CallBack ID = 86, Status = Transmission complete and ACK received(0)
2016-06-02 19:12:21.003 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Sent Message: class=SendData[0x13], type=Request[0x00], priority=Set, dest=20, callback=86, payload=14 03 25 01 FF
2016-06-02 19:12:21.005 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: Recv Message: class=SendData[0x13], type=Request[0x00], priority=High, dest=255, callback=0, payload=56 00 00 02
2016-06-02 19:12:21.007 [DEBUG] [.serialmessage.ZWaveCommandProcessor] - Checking transaction complete: class=SendData, callback id=86, expected=SendData, cancelled=false transaction complete!
2016-06-02 19:12:21.014 [DEBUG] [ve.internal.protocol.ZWaveController] - Notifying event listeners: ZWaveTransactionCompletedEvent
2016-06-02 19:12:21.016 [DEBUG] [curityCommandClassWithInitialization] - NODE 20: updating lastSentMessageTimestamp
2016-06-02 19:12:21.017 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Node advancer - SECURITY_REPORT: Transaction complete (SendData:Request) success(true)
2016-06-02 19:12:21.019 [DEBUG] [alization.ZWaveNodeInitStageAdvancer] - NODE 20: Node advancer - checking initialisation queue. Queue size 1.
2016-06-02 19:12:21.020 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 20: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2016-06-02 19:12:21.022 [DEBUG] [ocol.ZWaveController$ZWaveSendThread] - NODE 20: Response processed after 62ms/3330ms.
2016-06-02 19:12:32.618 [DEBUG] [WaveSerialHandler$ZWaveReceiveThread] - Receive Message = 01 10 00 04 00 09 0A 71 05 00 FF 00 FF 07 03 01 00 99
2016-06-02 19:12:32.624 [DEBUG] [ve.internal.protocol.ZWaveController] - Receive queue TAKE: Length=0
2016-06-02 19:12:32.627 [DEBUG] [wave.internal.protocol.SerialMessage] - Assembled message buffer = 01 10 00 04 00 09 0A 71 05 00 FF 00 FF 07 03 01 00 99
2016-06-02 19:12:32.630 [DEBUG] [ve.internal.protocol.ZWaveController] - Process Message = 01 10 00 04 00 09 0A 71 05 00 FF 00 FF 07 03 01 00 99
2016-06-02 19:12:32.636 [DEBUG] [ve.internal.protocol.ZWaveController] - Message: class=ApplicationCommandHandler[0x04], type=Request[0x00], priority=High, dest=255, callback=0, payload=00 09 0A 71 05 00 FF 00 FF 07 03 01 00
2016-06-02 19:12:32.643 [DEBUG] [ve.internal.protocol.ZWaveController] - Event Listener org.openhab.binding.zwave.internal.protocol.initialization.ZWaveNodeInitStageAdvancer@9d7af4 already registered
2016-06-02 19:12:32.670 [DEBUG] [ssage.ApplicationCommandMessageClass] - NODE 20: Transaction not completed: node address inconsistent. lastSent=20, incoming=255

I have spent so many days trying so many different things and everything fails. I just started playing with OH for the first time. I come from using OpenZWave for over a year and the siren works fine with this other library. I wonder what am I missing or doing wrong.

I also have a problem with my new Yale lock YRD240 but that will go in another thread. Maybe once we figure out how to make the Siren work, will also solve the Yale lock. I will contribute back the YRD240 product spec once I can confirm that I can use OH2 with that lock.

Thanks for your help.
Gaston

Can’t offer much assistance with the siren. Are you using the latest nightly or even the beta3? I wonder if turning trace logging on would reveal anything?

Regarding the lock, you can give it a shot, but you may run into problems right now (I too have a Yale lock). Chris has said that he’s working on making some significant changes to the security class code used by locks.

Hi Jeremy,

Thanks for the reply. I was using nightly build of OH2 of 1 day ago. Set DEBUG level of zwave packages and I could not find anything that looks suspicious. I spent enough time on this so I’m switching back to OpenZWave for now. Might give it a try again later.

Thanks,
Gaston

Same thing over here. Did you solve it ?
Same configuration: Nightly OH2 beta3 with aeon gen5 dongle

Nope. :disappointed: I remember reading in some other thread that security classes are not fully supported yet. I switched to ozw but when they are supported I’ll give it another try.

I don’t think this device requires the security classes - I could be wrong but I think people are using it ok.

Yep, it’s a zwave plus device so security is optional. I included the device in a secure way so it was using security classes IIRC.

Security isn’t supported in openhab at the moment unless you’re using a non-standard binding.