Is where a possibility to create a Zwave alarm frame based on the message of - let’s say - MQTT message?
Background: I’ve sensors attached to different bus systems (Zwave, MQTT, …) In case OpenHAB receives an alarm event via MQTT I’d like to forward this event to all things attached to Zwave which are configured to react on that alarm type.
Simple example:
A Switch item based on MQTT receives a ‘flood alarm’. OpenHAB (or the Zwave binding) converts this event and sends it out to all things configured to react on this ‘flood alarm’
I don’t know of any means to send a ZWave alarm command but I was looking to do this, too, either as broadcast or preferrably even directed to a single device.
That’s what the OP asked for and why your response got my attention. @chris do you know of any way ?
This is possible as I remember adding this feature a while ago - I just don’t remember how. Clearly the way to do it is as any other command - it just needs to have an appropriate channel. Let me have a look at how to configure this.
Ok, so first this only works for devices to have a send_notification channel like that Fibaro wall plug, correct?
Checked a couple of my devices and that wall plug probably is more or less the only one to have that channel, so I would have to add it to all other devices’ database entries, correct?
Second, I tried with a plug of mine and did get OH to send a NOTIFICATION, but it didn’t make my plug-connected lamp blink. Param #34 = 63 (i.e. react on all alarms), #35 = Cycle
Did you ever get that to work ? Reading the thread you linked to, that remains unclear to me.
2018-10-28 14:24:17.359 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Command received zwave:device:ddd23e6c:node2:notification_send --> 1 [DecimalType]
2018-10-28 14:24:17.362 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Creating new message for command NOTIFICATION_REPORT
2018-10-28 14:24:17.363 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-28 14:24:17.367 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Command Class COMMAND_CLASS_ALARM is NOT required to be secured
2018-10-28 14:24:17.368 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Adding to device queue
2018-10-28 14:24:17.370 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Added 15152 to queue - size 25
2018-10-28 14:24:17.379 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 0F 00 13 02 08 71 05 00 00 00 FF 05 00 25 18 5A
2018-10-28 14:24:17.414 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling intialised at 1800 seconds - start in 1500 milliseconds.
2018-10-28 14:24:17.450 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: sentData successfully placed on stack.
2018-10-28 14:24:17.453 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: TID 15152: Transaction not completed
2018-10-28 14:24:17.484 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 24, Status = Transmission complete and ACK received(0)
2018-10-28 14:24:17.485 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-28 14:24:17.488 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Response processed after 76ms
2018-10-28 14:24:17.489 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: TID 15152: Transaction completed
2018-10-28 14:24:17.491 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: notifyTransactionResponse TID:15152 DONE
2018-10-28 14:24:17.492 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveTransactionCompletedEvent
2018-10-28 14:24:18.914 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling...
2018-10-28 14:24:18.916 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:ddd23e6c:node2:switch_binary
2018-10-28 14:24:18.917 [DEBUG] [converter.ZWaveBinarySwitchConverter] - NODE 2: Generating poll message for COMMAND_CLASS_SWITCH_BINARY, endpoint 0
2018-10-28 14:24:18.918 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 2: Creating new message for application command SWITCH_BINARY_GET
2018-10-28 14:24:18.919 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-28 14:24:18.919 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Command Class COMMAND_CLASS_SWITCH_BINARY is NOT required to be secured
2018-10-28 14:24:18.920 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling skipped for zwave:device:ddd23e6c:node2:switch_binary on COMMAND_CLASS_BASIC
2018-10-28 14:24:18.921 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:ddd23e6c:node2:meter_kwh
2018-10-28 14:24:18.922 [DEBUG] [ternal.converter.ZWaveMeterConverter] - NODE 2: Generating poll message for COMMAND_CLASS_METER, endpoint 0
2018-10-28 14:24:18.923 [DEBUG] [ternal.converter.ZWaveMeterConverter] - NODE 2: Generating poll message for COMMAND_CLASS_METER, endpoint 0
2018-10-28 14:24:18.924 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 2: Creating new message for application command METER_GET
2018-10-28 14:24:18.925 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-28 14:24:18.925 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Command Class COMMAND_CLASS_METER is NOT required to be secured
2018-10-28 14:24:18.926 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:ddd23e6c:node2:meter_watts
2018-10-28 14:24:18.927 [DEBUG] [ternal.converter.ZWaveMeterConverter] - NODE 2: Generating poll message for COMMAND_CLASS_METER, endpoint 0
2018-10-28 14:24:18.928 [DEBUG] [ternal.converter.ZWaveMeterConverter] - NODE 2: Generating poll message for COMMAND_CLASS_METER, endpoint 0
2018-10-28 14:24:18.929 [DEBUG] [.commandclass.ZWaveMeterCommandClass] - NODE 2: Creating new message for application command METER_GET
2018-10-28 14:24:18.930 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-28 14:24:18.931 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Command Class COMMAND_CLASS_METER is NOT required to be secured
2018-10-28 14:24:18.932 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Polling zwave:device:ddd23e6c:node2:notification_send
2018-10-28 14:24:18.933 [DEBUG] [ternal.converter.ZWaveAlarmConverter] - NODE 2: Generating poll message for COMMAND_CLASS_ALARM, endpoint 0, alarm null, event null
2018-10-28 14:24:18.934 [DEBUG] [.commandclass.ZWaveAlarmCommandClass] - NODE 2: Creating new message for application command NOTIFICATION_GET V0
2018-10-28 14:24:18.935 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Adding to device queue
2018-10-28 14:24:18.937 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Added 15153 to queue - size 25
2018-10-28 14:24:18.944 [DEBUG] [ing.zwave.handler.ZWaveSerialHandler] - NODE 2: Sending REQUEST Message = 01 09 00 13 02 02 25 02 25 19 FE
2018-10-28 14:24:18.976 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Adding to device queue
2018-10-28 14:24:18.978 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Added 15154 to queue - size 25
2018-10-28 14:24:18.983 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Adding to device queue
2018-10-28 14:24:18.986 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Added 15155 to queue - size 26
2018-10-28 14:24:19.012 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: sentData successfully placed on stack.
2018-10-28 14:24:19.017 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: TID 15153: Transaction not completed
2018-10-28 14:24:19.069 [DEBUG] [l.serialmessage.SendDataMessageClass] - NODE 2: SendData Request. CallBack ID = 25, Status = Transmission complete and ACK received(0)
2018-10-28 14:24:19.071 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-28 14:24:19.074 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: TID 15153: Transaction not completed
2018-10-28 14:24:19.085 [DEBUG] [nal.protocol.ZWaveTransactionManager] - NODE 2: Application Command Request (ALIVE:DONE)
2018-10-28 14:24:19.086 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: resetResendCount initComplete=true isDead=false
2018-10-28 14:24:19.087 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: Incoming command class COMMAND_CLASS_SWITCH_BINARY, endpoint 0
2018-10-28 14:24:19.088 [DEBUG] [ng.zwave.internal.protocol.ZWaveNode] - NODE 2: SECURITY not supported
2018-10-28 14:24:19.090 [DEBUG] [tocol.commandclass.ZWaveCommandClass] - NODE 2: Received COMMAND_CLASS_SWITCH_BINARY V1 SWITCH_BINARY_REPORT
2018-10-28 14:24:19.091 [DEBUG] [dclass.ZWaveBinarySwitchCommandClass] - NODE 2: Switch Binary report, value = 255
2018-10-28 14:24:19.092 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got an event from Z-Wave network: ZWaveCommandClassValueEvent
2018-10-28 14:24:19.093 [DEBUG] [ding.zwave.handler.ZWaveThingHandler] - NODE 2: Got a value event from Z-Wave network, endpoint = 0, command class = COMMAND_CLASS_SWITCH_BINARY, value = 255